AlanOfTheBerg wrote: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.
Moderators: support, Unholy, krankyd, The Fej, perlin
AlanOfTheBerg wrote: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?
MaliciousWolf wrote: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.
AlanOfTheBerg wrote:MaliciousWolf wrote: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.
invented wrote:Yes, having the screen black out whenever I put a finger over the proximity sensor is annoying.
Users browsing this forum: Google [Bot]