Opera 9.5.1 Beta1 Build 1718 Important Bugs..

Opera 9.5.1 Beta1 Build 1718 Important Bugs..

1.When open Opera9.5 beta1，Opera9.5 beta1 will alway disable SMS notification and Email notification sound,Must manully to turn it on again.

2.when input address or input data with input field in web page, Opera9.5 beta1 will alway change SIP to default Winodws mobile Keyboard....

My phone is HTC TYTN II (WM6.1 EN)

#1 is being looked into, and #2 is listed as a known issue.

I can confirm #1. I don't understand why a web browser has to fiddle my sound settings. Can someone please explain this? Does Opera also change other sound settings? Or maybe some system settings?

I have an HTC Tytn II as well and it disables notifications on SMS/Email for me too. How bizarre - I'm not sure why there should be any interaction between a browser and audio settings. Actually I think it disables all or most of the sound settings together with display message/vibrate/flash light. I think I'll wait until this is fixed before using again as it's a pain to have to re-enable them all.

Cheers,

Ashley Emery

Originally posted by BigQ:

When open Opera9.5 beta1 Opera9.5 beta1 will alway disable SMS notification and Email notification sound,Must manully to turn it on again.

This is serious! All device alerts, alarms, and sounds are universally deactivated whenever OMo is started or exited!

Wow, guess I will wait to try it until the next beta.

Interesting, in the notifications the IM settings don't get changed, however everything that is system seems to. SMS and... reminders!!! are the most important...

Why on earth would you guys even be touching that part of the registry!?!?! /boggle

all option get disabled for all notifications for me.

I love the browser but this is a huge problem with the messaging notifications being turned off. My phone will still ring but sms, mms, email, and sync sounds are turned off. Is there an expected patch or fix coming soon?

I second the "why on earth would you guys be touching that?" I understand that its a beta (and a good one at that), but I don't expect a beta of a program to start messing with system settings that it doesn't even use.

#1 Verified, and very upset.
Phone: HTC Titan (Sprint PPC 6800) WM 6.0

Dear Opera Team,
I am very disappointed and very frustrated by this invasion of my system settings. I have been a Opera Mobile supporter for Years, and have now lost my trust in your software. Let this be a lesson learned the hard way (by losing me and many others as supporters). I don't appreciate software that messes with things it shouldn't. This is one of those "bugs" that should have been captured in your pre-beta stages.

My 2 cents,
BenHoltz

Yeah just checked this on mine HTC 8925, running wm6. I realize this is a beta so certain errors are to be expected, but this seems outside of what should be reasonable. Can we get a patch for this ASAP? This is a make or break thing. I'm going to have to uninstall the beta and stop testing if this isn't taken care of quickly

Originally posted by robbyb413:

I'm going to have to uninstall the beta and stop testing if this isn't taken care of quickly

Note that if you do want to keep testing and not lose your settings, do the following: before starting OM, open the notification settings and leave it open. Then, open OM and use it. After exiting OM, your setting should still be there. At least, it worked for me.

Originally posted by Petehead:

Originally posted by robbyb413:

I'm going to have to uninstall the beta and stop testing if this isn't taken care of quickly

Note that if you do want to keep testing and not lose your settings, do the following: before starting OM, open the notification settings and leave it open. Then, open OM and use it. After exiting OM, your setting should still be there. At least, it worked for me.

That is ridiculous that you would have to do that to test a web browser... Along with the "out of memory" Problem, IMO this software is not even ready for a closed beta.

Originally posted by Jakuren:

Why on earth would you guys even be touching that part of the registry!?!?!

I don't know what's causing this, but the registry is where Windows keeps track of programs. Just about all installed programs need to interact with the registry.

Remember that you are using a beta which has not been widely tested by the public on all the numerous device configurations out there. This is why there is a beta - to make sure things like these are caught before the final version.

Originally posted by haavard:

Originally posted by Jakuren:

Why on earth would you guys even be touching that part of the registry!?!?!

I don't know what's causing this, but the registry is where Windows keeps track of programs. Just about all installed programs need to interact with the registry.

That's why he mentioned "that part of the registry".

1. I do not have any problems with getting any notifications with opera open or closed.. Still get the popup as well as sound.. But after testing this was b/c I use PhoneAlarm which takes over the notification/sound settings... When I disable PhoneAlarm I also get the same missing sound.. But still get the notification popup..

2. As for the keyboard. Opera really isnt the first program to do this so I have a NullKB installed and set as default.. For those that dont know NullKB makes it so no keyboard pops up.. Useful for devices that have slide out keyboards other hardware keyboards.. But the problem I do notice is if you have it set to auto full screen and your using a hardware keyboard it will go to full screen before your done typing in the URL.. This doesnt happen if you use the onscreen keyboard.

3. For all those people saying they wont use Opera again because a Beta version has bugs.. Clearly you dont understand the point of Beta testing.. Its to find the bugs and report them so they can fix them.. If you dont like bugs.. Then dont use the Beta version.. Simple as that... .. For first beta release this is very nice and I am really looking forward to the final release..


My phone is a HTC Mogul on Sprint Network

Originally posted by pyrotech1620:

1. I do not have any problems with getting any notifications with opera open or closed.. Still get the popup as well as sound.. But after testing this was b/c I use PhoneAlarm which takes over the notification/sound settings... When I disable PhoneAlarm I also get the same missing sound.. But still get the notification popup..

2. As for the keyboard. Opera really isnt the first program to do this so I have a NullKB installed and set as default.. For those that dont know NullKB makes it so no keyboard pops up.. Useful for devices that have slide out keyboards other hardware keyboards.. But the problem I do notice is if you have it set to auto full screen and your using a hardware keyboard it will go to full screen before your done typing in the URL.. This doesnt happen if you use the onscreen keyboard.

3. For all those people saying they wont use Opera again because a Beta version has bugs.. Clearly you dont understand the point of Beta testing.. Its to find the bugs and report them so they can fix them.. If you dont like bugs.. Then dont use the Beta version.. Simple as that... .. For first beta release this is very nice and I am really looking forward to the final release..


My phone is a HTC Mogul on Sprint Network

Very agree your points...

Opera mobile is the best browser on Windows mobile.

Waiting for the fixed version and continue testing...

hi folks,

first want to say well done on the beta, yes it has bugs but it is probably the best mobile browser out there as it stands and has huge potential.

next, the issues.

i have used some of the versions off the htc diamond that have been floating arround the web and comparing the two on my polaris, have to say that in most respects the beta exceeds what has been unofficially available, its faster, more stable and smoother scrolling, personally think it exceeds the 'other' browsers (pie, netfornt, etc) now for browsing performance

now the issues,

for me the killer is the browser defaulting to the windows sip, this is stated to be a known bug but does not affect the versions installed on the diamond, what has changed? for me this renders the browser practically useless from the point of being user friendly, this i suspect is the bit that puts a lot of people off at the moment.

second, the memory footprint, this eats the device memory, there needs to be a ballance between cache, speed and processing memory that will work on most devices?

third, the notifications, i can understand why people are concerned, i use these for work, having them turned off caused me a few issues today

forget the flash being turned off, i know some people have noted this. i can understand why you have done this, it's best to get the overall browsing experience right first.

good luck in improving this, can't wait for future versions. for me if you get the above right i would probably buy this without flash:)

regards

Chris

I think its great so far
the only thing with mine is it doesnt reflow or w/e its called. the article is already "reflowed" b4 i even zoom in.
this happens on all pages i visited so far.
anybody else getting this?

I'm very pleased so far with the browser. It really is very nice and you're on the right track. I just had a couple of comments.

1. I too have the notifications problem (all notifications being cleared).
2. When the culprit is found, I hope there will be a quick build released as this particular bug really deters many users from even opening Opera Mobile.

Thanks again for a great browser and keep up the good work. I understand this is a beta and will try to treat it as such. The only glitch is that this particular bug seems to affect an area of the registry (of a device that is also many peoples primary phones) that really should never get touched by browser software.

tested on an HTC Kaiser/TyTN II (AT&T Tilt, using AT&T official ROM, no modifications).

thanks

First of all, congratulations Opera because this navigator is really impressive

I can confirm too the 1st bug (tested in an HTC TyTN with Official Spanish WM6).

As the other people said, it's really annyoning...


Best regards.

Besides messing with the notifications settings I can no longer sync (via activesync) with my exchange account (mail2web) after using Opera Mobile 9.5b1. I have to delete the account in ActiveSync and set it up again to make it work.
I can't figure out why Opera is also messing with this!
On an HTC P3600 with WM5
Greetings

MAK

I can confirm #1 as well! WM6.1 8525

Originally posted by pyrotech1620:

For all those people saying they wont use Opera again because a Beta version has bugs.. Clearly you dont understand the point of Beta testing.. Its to find the bugs and report them so they can fix them.. If you dont like bugs.. Then dont use the Beta version.. Simple as that... .. For first beta release this is very nice and I am really looking forward to the final release..

Aside from the one guy who apparently thinks one bug is worth abandoning a company, I don't think anyone is being unrealistic here. A quick fix is needed for this if people are going to keep testing. This is a huge issue that impacts some of the core functionality of the device for many of us - notification of emails, messages, and appointments, and quite frankly something that really is unrelated to functionality of the browser (skyfire, previous opera mobile browsers, etc didn't have this issue...) so it's completely warranted to say "hey opera, you guys need to fix this like yesterday or people can't continue to test and give feedback". I mean this is first and formost a device targeted for enterprise business applications... some of the people may have them as toys but there are those of us that want to participate and can add valuable feedback but can't sacrafice things like this.

The whole point of beta testing is to have people put it through the paces and test the software in a more open environment, and if people are uninstalling it the issues will take longer to spot and eliminate making the beta period drag on and yield a portentially lower quality product.

Wholly shit, that is why my text message alerts stopped working! I though something was up with the phone.
This is a very very bad bug, how did it get missed before releasing beta 1 after the months of delays?

Originally posted by MAK11:

Besides messing with the notifications settings I can no longer sync (via activesync) with my exchange account (mail2web) after using Opera Mobile 9.5b1. I have to delete the account in ActiveSync and set it up again to make it work.
I can't figure out why Opera is also messing with this!
On an HTC P3600 with WM5
Greetings

MAK

I can NOT confirm this bug.
I activesync with mail2web as well and activesync is still working fine.
Just all my notifcations have beem disabled.
I've missed 5 or 6 messages today already that I should not have.
Uninstalling the beta for now. I can't use something that disables half my phone when I run it.
Going back to the Diamond-ripped Opera Mobile. It didn't have any of these bugs.

does anyone know how to fix the notifications alert sounds issue? I cannot even play any mp3 files anymore!!! no sound whatsoever!!! is there a registry fix? Opera people can you please let us know? You have effectively disabled all the beta testers' phones...

Only having the disabled notifications here. Sound works normally, phone rings as usual too. Just takes a few clicks to reenable the notifications. If you leave the settings page open while Opera is running they don't get deactivated.

I am seeing another bug that hasn't been mentioned. If I have Opera open and allow my phone to go into sleep mode, when I turn it back on Opera is closed. This doesn't happen with any other application. Is any one else seeing this? This is not as bad as the notification, keyboard, or memory issues, but still important.

I would also like to add that the notification problem is such a huge bug that I cannot continue to test this beta. I realize and understand the purpose of a beta and I love the browser, but will have to wait until it is fixed before I continue my evaluation.

Using Sprint Mogul w/ WM 6.1.

No sleep issue here, if I have opera open, turn off, turn on, exit from S2U2 opera is still there and in foreground. TyTn II WM6.

Haavard is there a way you can find out for us when this notification thing is going to be fixed. Same thing is happening on my VZW XV6900 aka HTC Touch. Also none of the touch keypads work. When I use the Touch Keyboard the one that is similar to Blackberry's suretype keyboard all it does is type in the numbers for that key instead of the letters. Also there is a certain website that it freezes on that I would rather not post here for business reasons but if you want it I can email it to you. Other than that the browser itself is amazing. I love the double tap zoom and it is so much more than Pocket Internet Explorer will ever be. I can't wait to see the final product.

Echoing previous comments. I'm always an early adopter and active beta tester. But with an error such as disabling notification, I won't install it. I'm fine with bugs within the software but not those that disable use of my device. I fully understand its beta, so I have no qualms with bugs; I just choose not to participate in the beta test, as anxious as I was.

Anxious to see a quick update to this bug... others can remain, but I hope you fix this one ASAP.

Kilrahvp,
If I turn off and back on it's still open. However, if I allow it to go into sleep mode by itself (mine turns off after 1min of inactivity) it will be closed after I turn it back on and unlock S2U2.

I was just using the beta on my XV6900 aka Touch and received a text message while in the browser and the sound came through fine but once I exit the program it disables it I don't know if this helps find the problem.

Originally posted by mag921:

I allow it to go into sleep mode by itself (mine turns off after 1min of inactivity) it will be closed after I turn it back on and unlock S2U2.

I just tried letting it go to sleep by itself, opera is also still in foreground upon wakeup (normal behavior).

Using Opera Mobile 9.5b1 on my Samsung SCH-i760 and having no problems with sounds when receiving notifications.

On my SCH-i760, I lost notification after I exited Opera mobile 9.51 b 1718. jkatzpac, do you still have notification sound on after you exit the browser?

I have Voice Commander and Opera hasn't disabled it. Still getting message notifications fine. One suggestion unrelated to the sound issue. It would be nice if the links would either change color or highlight in some way when touched. Hard to tell if the screen is reacting to the touch without waiting to see if the load bar is running at the bottom of the screen.

Originally posted by Petehead:

Note that if you do want to keep testing and not lose your settings, do the following: before starting OM, open the notification settings and leave it open. Then, open OM and use it. After exiting OM, your setting should still be there. At least, it worked for me.

That worked for me once, but not the second time.

Originally posted by Kilrahvp:

Just takes a few clicks to reenable the notifications.

"A FEW CLICKS"?? Try more like 20 different settings, each with sound, display, light, & vibrate options to check!

Agreed... I had to reconfigure 16 (yes I counted them) notifications. Arg... and it's so fast too

The same problem with sms/email notification (HTC Touch Cruise, WM6 Official).

Wow, I was so glad when I tested this beta and saw the performance; but now I see this problem ... I've checked the notifications and all of them except phone calls are disabled! SMS, MMS, Notifications, all! This on my HTC Touch.

I'm uninstalling Opera 9.51b1 until this is fixed. I understand a beta is a beta, I've tested every Opera Mobile beta that has been released, but this bug is too big for a beta, or even an alpha version. I accept an occasional crash, but messing the notifications is too much.

I'm closing this thread since the title unfortunately does not reflect the specific content of the thread, and two seemingly unrelated and yet frequently reported issues are brought up.

If anyone wishes to create separate threads for these issues and continue the discussion there, that's fine. Just make sure that the thread title accurately reflects the contents of the thread.

By not using a proper thread title, you are making it harder for everyone else to find existing threads discussing bugs they may find, and thus the forum is flooded with duplicates and it becomes difficult to keep track of everything.