Ongoing/Overlooked/Unresolved Storm OS: Confirmed Bugs and GUI Issues (NOT Hybrids)

[JRSCCivic98]

Since a thread such as this is missing off the site, I figured I'd compile a list of bugs that I've found in pretty much ALL pre-release OS versions we've seen up to now. As they get resolved, I'll pull them off... maybe. This post will be updated from time to time as I find and document issues. Please do not pepper this thread with reports of "My browser is missing after I update to OS .xxx".

If you are running 4.7.0.75 or Hybrids and are having issues, this thread DOES NOT APPLY TO YOU.

Also, chances are good that unless you're an advanced user, you won't be able to find any bugs that "should" be on this list. I'm not trying to discourage you of posting them, but do please search the forums IN DETAIL and make ABSOLUTELY SURE what you're posting hasn't already been mentioned in other threads.


This is a SPECIALIZED list of bugs/GUI glitches mean to serve as a guideline for RIM to fix, because both the carriers and RIM have overlooked each and every single issue on this list. This isn't your regular "post your bugs" thread, that's what those other Official Version Number bug threads are for.


So, here's the list....

First and foremost, the major issues at hand are some cosmetic ones that need to be resolved ASAP as about 90% of them were not present in OS .7x versions. Please see this thread http://forums.crackberry.com/f132/co...rsions-190059/ for details on that.

Further bugs are as follows:

Old emails that are restored after an OS upgrade will turn into a RED X instead of an OPEN ENVALOPE if you open them agin and cursor up into the header of the email or down through the body of the email. (Apperently this happens because the BB tries to "Get More" for an email that doesn't have more to get. However, if the email is a long one and it does have more bytes to get towards the rest of the body of the email, this will not happen and the auto request goes through and properly propagates the rest of the email. Workaround for this is to turn Auto More OFF under General Email Options. When set to NO, you can open old emails and cursor around and it will not trigger a false "Get More" and corrupt the envalope status of the email. The bad part about this is that you have to manually hit Menu/Get More or Menu/Get More All on long emails, which can be a pain if you constantly get large emails.

Issues with Home Screen in lanscape going back to standard coloring when/if you have your display settings set to revese contrast or greyscale. Fixed in OS4.7.0.151

Unplugging from a power source with the handset locked causes it to unlock.

Holding down Mute DOES NOT ENTER STANDBY as all other Blackberries do.

T for Top and B for Bottom keyboard shortcuts do not work on lists when in Portrait QWERTY, but they do in Landscape. (In Portrait they only move up or down one line/item.) Additionally the keyboard shortcuts for Reply and Reply All in emails or texts while in Portrait QWERTY do not work, but they work fine in Landscape QWERTY. Fixed in OS4.7.0.151

Not being able to swipe keyboard up on any screen that doesn't have a toolbar at the bottom. (Ex. Owner Information screen... you scan swipe keyboard down to hide, but cannot swipe up to show it.) In addition to this, now under OS4.7.0.151 you can no longer swipe up the keyboard on any screen with a toolbar either. Step in the wrong direction RIM.

On Phone dialpad view, if you swipe slowly up each row of numbers from bottom to top from 7 to1, 8 to 2, and 9 to 3, you will actually cause the blue highlight to stay lit on 1, 2, or 3 respectively.

Unable to edit the browser URL field once you type something and make a mistake. (You have to backspace, you cannot touch/edit as you can in other text fields.) Fixed in OS4.7.0.151

In Options/Language, the orientation is locked to Portrait only... (the screen will not change to Landscape when handset is rotated while in this screen.)

"Full Keyboard" setting for portrait mode keyboard is not persisted through backup/restore. The setting is restored as "SureType".

Keyboard characters in Portrait QWERTY (sometimes in Landscape) will shift up or down a few pixels on the keys individualy (meaning, not all of them line up properly) after extened period of uptime from device. Doesn't seem to be linked to anything except perhaps free memory left after severals days of uptime, but this is speculation.

If you bring up the virtual keyboard on the home screen and type a key it takes you to the Phone app. On the home screen if you actually hit the letter on the keyboard that corresponds with the "First" letter on each of the number pad keys (i.e. a=1, d=3, g=4, etc.) it actually dials the corresponding number. To add to this, in OS4.7.0.151 the keyboard now changes layout to numbers only wacked out for a split second right before it transitions to the phone app.

If you set a side convenience key to bring up the virtual keyboard and you bring it up in in Zen mode (not all icons showing on home screen in Portrait) and then transition to Landscape, the keyboard does not stay on the screen. However, if you bring up all the icons in portrait and then "convenience key" the keyboard, it'll transition back and forth. The only thing is that when it transitions back to portrait, it'll drop back down to Zen and you have to hit Menu once to bring up all the icons and the overlapping keyboard (this is the normal behaviour if you were to bring up the keyboard using the menu choices rather then the convenience key).

If you're on the home screen (Landscape or Portrait) and you bring up the virtual keyboard and then scroll up on the icons, the screen tears BADLY. Below is a screenshot of the screen tearing. Fixed in OS4.7.0.151

[markdental]

Nice list Civic.

*228 = data loss until reboot...

[JRSCCivic98]

Originally Posted by markdental

Nice list Civic.

*228 = data loss until reboot...

That's only currently on .132, so unless it continues on the futher releases after .132 or .141, it won't make the list.

[markdental]

Originally Posted by JRSCCivic98

That's only currently on .132, so unless it continues on the futher releases after .132 or .141, it won't make the list.

It's on .141 too.

[JRSCCivic98]

I'll add it if the next release is botched as well.... and I'll also add the Unlock bug with all buttons as well if that doesn't get fixed.

[DanGPhotography]

I still have the issue where when an alert tone is playing the phone will freeze. If a hard key is pressed during an SMS alert it will freeze for up to 20 seconds. I have had this since .86 and have tried many ways to fix it including the wipe, load .75, then .122 process and such.
Thought it might be an issue with the OS accessing the SD card but switching the locations of the files did not make a difference. Its the one bug that drives me nuts... haha.

[markdental]

This thread was stickied so quickly I'm not sure anyone saw it...It just blends in.

For a while I thought you deleted it Civic, then I happened to look up and see it.

[iprayforrain]

Well how about :

Continuous track music (no pause between tracks) has a 1 sec pause when changing tracks

This has been present in every build and is a real sad statement for a modern convergence appliance

[iprayforrain]

not 100% when this one started but is present in .141.

While listening to music throught the headphones with media player in the background and another app such as windows messenger, viigo, vz / bell navigator in the foreground, the music keeps playing when tracks change but the sound stops

After some thought this one also has been going on for a while. Pause then play fixes the problem untill the next track change

[markdental]

There is also a problem with Audio Boost, where if you get a call or alert while listening it will disable and you will not be able to re-enable until you reboot.

[mrZoSo]

These three things don't happen on mine. It's strange how things happen on one phone and not another, and yet the hardware is "suppose" to be the same. The Storm is a strange beast indeed.

Unplugging from a power source with the handset locked causes it to unlock.

On Phone dialpad view, if you swipe slowly up each row of numbers from bottom to top from 7 to1, 8 to 2, and 9 to 3, you will actually cause the blue highlight to stay lit on 1, 2, or 3 respectively.

While listening to music throught the headphones with media player in the background and another app such as windows messenger, viigo, vz / bell navigator in the foreground, the music keeps playing when tracks change but the sound stops

[iprayforrain]

Originally Posted by mrZoSo

These three things don't happen on mine. It's strange how things happen on one phone and not another, and yet the hardware is "suppose" to be the same. The Storm is a strange beast indeed.


While listening to music throught the headphones with media player in the background and another app such as windows messenger, viigo, vz / bell navigator in the foreground, the music keeps playing when tracks change but the sound stops

BTW wired headphones not BT. Just tested it again w/ viigo after bat pull. play album open viigo wait for track change and audio is gone.

[JRSCCivic98]

Originally Posted by mrZoSo

These three things don't happen on mine. It's strange how things happen on one phone and not another, and yet the hardware is "suppose" to be the same. The Storm is a strange beast indeed.

Unplugging from a power source with the handset locked causes it to unlock.

On Phone dialpad view, if you swipe slowly up each row of numbers from bottom to top from 7 to1, 8 to 2, and 9 to 3, you will actually cause the blue highlight to stay lit on 1, 2, or 3 respectively.

While listening to music throught the headphones with media player in the background and another app such as windows messenger, viigo, vz / bell navigator in the foreground, the music keeps playing when tracks change but the sound stops

What version of OS? Because if you're going to say .7x version, that's why it doesn't apply to you.

[madphone]

Originally Posted by JRSCCivic98

I'll add it if the next release is botched as well.... and I'll also add the Unlock bug with all buttons as well if that doesn't get fixed.

Have we seen the changes made from .132 to .141 to be sure that this is actually a bug and not a change intentionally made by RIM?

and this:
"Unplugging from a power source with the handset locked causes it to unlock." may not be a bug either. If my device were in a cradle and I got a call I would want it to unlock when I removed it??? Again, are we sure that it is a BUG?

Thanks civic. This is a great idea, just a thought that some of the items we might call a bug are things that RIM intentionally put into a build, and the only way to know that is to get the pages of changes made from build to build.

[mrZoSo]

Originally Posted by JRSCCivic98

What version of OS? Because if you're going to say .7x version, that's why it doesn't apply to you.

I've ran them all, I just put a hybrid(9530 .141/5.0.0.90) on tonight and tried the same 3 things and it still doesn't exhibit those three things, except for the lock feature, which seems hit or miss now, after trying it about a dozen or so times.

@iprayforrain - I'm using a wired set too.


And like madphone said, are some of these bugs or intentionally suppose to be there?