UI Bug in iOS application V3.1.1

[MaliciousWolf]

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.

[MaliciousWolf]

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.

[MaliciousWolf]

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?

That's what I said I'm doing currently. I'm just reporting the issue is all and my fix.

[MaliciousWolf]

I set waze into debug mode, and repeated the process that creates this issue then submitted the log files. Hopefully waze support actually looks at these files to help correct the problem.

[MaliciousWolf]

I set waze into debug mode, and repeated the process that creates this issue then submitted the log files. Hopefully waze support actually looks at these files to help correct the problem.

that's great, thanks! I would submit a ticket referencing this thread from the support page if you haven't already, and mention the date/time you uploaded logs.

Since you're clearly technical, I suggest running Waze in debug mode if you are not already. It increases the verbosity of log captures.


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

I am assuming the support ticket feature is the process when you click email a Rep in the Nanorep widget correct? And fill out all the information? If so I just done this, referenced this thread, and detailed the date and the time of when I submitted the log files as you suggested. Now we wait

[MaliciousWolf]

Yes, having the screen black out whenever I put a finger over the proximity sensor is annoying.

I have not received any feedback yet from waze support on that status of the ticket I have opened up. Just thought I'd update everyone.

[musketball]

Yeah, I had that same problem. Put it to 3 finger tap only this morning and the problem went away. Obviously a flag not being set properly.