UI Bug in iOS application V3.1.1

by **MaliciousWolf** » Mon Mar 19, 2012 9:20 pm

I am using the Waze application on an iPhone 4 running iOS 5.1 (9B176).

Recently I detected an annoying UI bug since updating waze to V3.1.1.

When clicking the menu icon at the bottom left corner, and then clicking on My Waze, instead of bringing me to the My Waze main menu, it takes me directly to the My Mood list instead. Then when clicking the back button at the top left while viewing the My Mood list, instead of going back to the My Waze menu, it skips it and goes directly to the main "Menu" selection screen. Summarized, the My Waze menu is being skipped all together when proceeding forward and back between the first and last steps.

This only occurs upon start-up of the application, or when returning to the application after viewing other applications while it is running in the background. After going through the above steps described above once, the menu screens load in the correct sequence without any issue.

Visual Description:

First clicked on My Waze.

My Waze menu skipped, instead displays My Mood.

Upon clicking back button in above picture, My Waze menu skipped yet again, and main Menu displayed.

Upon clicking My Waze again, My Waze menu finally displayed.

It is nothing that really hurts the application at all, just is annoying to me lol.

There is another bug I have noticed as well, and it is even more annoying but I have no clue how to really visually report it or retrace steps that lead up to it for it is randomly occurring.

When driving around, my iPhone's backlight kicks on and off, on and off, basically flickering depending on how the phone moves, this includes when I am making a turn or a tight curve. If the phone remains in one position (again it is not a set position and completely random), the screen will go black, and then when I shake the phone or stand it up right or lay it down depending on its previous position, the screen will light up again. I know their is a feature called keep-backlight on, and I have left it at its default "On" position for I do not want it turning off no matter what for battery conservation is not a concern to me for I have a car charger. Re-installing the application does not fix this bug at all, and it occurs multiple times each day I am driving, and closing the application and rebooting it only temporarily solves the problem.

by **AlanOfTheBerg** » Mon Mar 19, 2012 9:53 pm

The My Waze/My Mood is not a bug if I understood what you wrote. Those are two buttons. The larger portion of the icon button is for My Waze, but the smaller top-right corner of the button takes you directly to My Mood. You just have to be mindful of exactly where you tap.

by **AlanOfTheBerg** » Mon Mar 19, 2012 9:58 pm

As to the second situation, are you by chance laying it down or in a space where the proximity sensor for voice commands might be kicking in? Try changing the activation method settings to 3-finger tap instead of 3-finger+hover. (Hover=proximity sensor)

by **MaliciousWolf** » Mon Mar 19, 2012 10:56 pm

Hmm, didn't realize all this time while using waze that the little icon that showed my mood was in fact a button as well lol. Well dumb mistake there. As for the second issue I'm having, I'll try your method you suggested. Thing is though, I have the voice command feature turned off, and never use it.

by **AlanOfTheBerg** » Mon Mar 19, 2012 11:14 pm

MaliciousWolf wrote:Hmm, didn't realize all this time while using waze that the little icon that showed my mood was in fact a button as well lol. Well dumb mistake there.

I learned by trial and complaint and being "schooled" in the forum myself.

MaliciousWolf wrote:As for the second issue I'm having, I'll try your method you suggested. Thing is though, I have the voice command feature turned off, and never use it.

Yeah, that may have nothing to do with it. #graspingatsraws

by **GeSpot** » Tue Mar 20, 2012 5:33 pm

It sounds to me like you may be having some problems with your proximity sensor on your phone. How new is your phone?

by **MaliciousWolf** » Fri Mar 23, 2012 3:24 am

GeSpot wrote:It sounds to me like you may be having some problems with your proximity sensor on your phone. How new is your phone?

Phone is a little over a year old. It is not the proximity sensor though, for as I have stated before I do not use this feature at all, and this problem has only occurred in waze.

I figured it out though, and it is most definitely a bug for I can repeat it over and over again. When the voice command feature is set to "off" (i.e. disabled), but the activation is set for "hover & 3 fingers", the screen will flicker when a hand is waved in front of the sensor as if to bring up the voice command prompt. However, seeing how this feature is turned off at the time, it automatically cancels out, so fast that all that is seen is just a flicker and no prompt.

The only way I have resolved this at this time is by setting activation to "3 finger tap only".

This is something I believe waze should look into, for I believe the "hover & 3 fingers" is the default setting which I'm sure may be causing other users to experience this bug when they have the voice command feature turned off.

by **gettingthere** » Fri Mar 23, 2012 5:50 am

We ran into a similar issue when Beta testing Waze 3.1 for iOS. Waze was aware of the issue and supposedly fixed it...

It is/was related to allowing you to know about and allow you to turn on the Voice Command function on first run of Waze, I believe. But obviously it's not totally fixed.

by **MaliciousWolf** » Fri Mar 23, 2012 4:54 pm

gettingthere wrote:We ran into a similar issue when Beta testing Waze 3.1 for iOS. Waze was aware of the issue and supposedly fixed it...

It is/was related to allowing you to know about and allow you to turn on the Voice Command function on first run of Waze, I believe. But obviously it's not totally fixed.

Yeah it is not fixed, and quite annoying as well. Occasionally it will cause the screen to go permanently blacked out as well, and only exiting out and restarting waze solves that. I have had this happen during crucial turns when I need to take a quick glance at a street name for waze is to delayed on sounding it out before I approach the turn. Here the screen is completely blacked out once I turn the phone to take a look for the mount always shifts a bit at times. I took the right turn though in the end, still though hope this is resolved in the next update.

by **AlanOfTheBerg** » Fri Mar 23, 2012 4:59 pm

Why don't you change it to 3-finger tap only and leave it that way if you don't use the voice command feature?