Voice Commands reference (old) + New "OK WAZE"

[Annie-Od]

Thanks. No music since I turn the volume off when reporting. Other reports such as heavy traffic and police seem to work much more consistently. I did get a hazzard report to work once this morning (first time ever) but 4 other times it didn't work. I have good cell signal when trying to report,too. Google voice searches seem to work fine.

[Annie-Od]

What I mean by failed:

1.App listens. I say "Report Hazzard". App says "Try Again".
2. App listens. I say "Report Hazzard" again. App says "Can't Hear You".
3. App listens. I say "Report Hazzard" again, usually a little louder. App says "Cancelled".

[Annie-Od]

Thanks. I have done 1 and 2 and when I get to 3 just said "car". That fails for me. I will try saying "car stopped" and see if that makes a difference. Sometimes I don't get past 1 ("Report Hazzard") before it fails.

[Annie-Od]

Using the cmd file I have tried saying "reporting vehicle stopped on shoulder". It still doesn't work. Can this be fixed in the app?

[Annie-Od]

Thank you. I have tried it the way it is listed on the help page: Report Hazzard, On Shoulder, Car. It either fails when I say "report hazzard" or when I say "car". Either way I have not been successful at reporting this with a voice command. I appreciate any help!

[Annie-Od]

I can get all of the voice commands I have tried to work except the one for reporting a hazzard. Most of the time I am trying to report a vehicle on the shoulder. I have tried saying "vehicle on shoulder". The only time this works is when I'm sitting at home trying to figure out why it doesn't work while I'm driving. I have also tried saying report hazzard and going through the prompts. Every time i get to the point of saying "car" it fails. What am I doing wrong?

[Annie-Od]

This is with a phone mic. Unfortunately, I haven't gotten a Bluetooth headset working yet. I'm still working on that part.

[Annie-Od]

Although I am still new to Waze, I have been able to resolve a few of my issues with Voice Commands and thought I would post that information here in case it helps someone else. I use a Samsung Galaxy Core Prime phone, Android 5.1.1 and Waze Version 4.5.0.1

I started with no access to Voice Commands at all. Went into Waze > Settings > Voice Commands and Enabled and set to Activate with 3 fingers. Unfortunately, my Samsung Galaxy Core Prime does not recognize 3 fingers as a "gesture". When that didn't work, I changed the selection to 3 fingers or wave.

With that I was able to get the Voice Command screen with the microphone. But, it would always show as "Waiting". It seemed to not hear me. I got out of Waze and went into my phone settings. Under System I chose Language and input > Voice input. Apparently my phone did not default to any type of voice input. I first chose Enhanced Google Service, but for some reason (which I don't understand yet) that didn't work. Then I chose Basic Google Recognition and exited settings.

I went back into Waze with that setting, and now Voice Commands work. It doesn't always recognize what I am saying, but I have able to do several reports by voice. If I figure that out, I'll let you know.

Hopefully, this is helpful to someone.

[Annie-Od]

I am new to Waze and can't get voice commands to work on my Samsung Galaxy Prime. Can anyone help? I have followed all of the instructions I have found without success.

[Ankh-Morpork]

I have noticed recently that the voice commands aren't working, especially when trying to report a hazard on the road. Reporting traffic, police, etc. Works most of the time but whenever I try to report a hazard, It keeps saying "try again", "I didn't hear you" and finally "canceled". I know it's not myself who's too quiet, as I'm almost shouting trying to get it to hear me . I have a feeling it has something to do with spotify and my music, but turning down/pausing my music doesn't help either. It would be nice if waze could not only fix this issue but also add a feature to pause spotify when you wave or tap the screen with three fingers to make voice commands easier to hear . Anyone else having this issue? If so, any temporary fixes?

Yes, I still have the same problem. It could previously only understand me when driving really slow, but with the latest version even when standing still it refuses to understand me. When previously "Report heavy traffic" worked fine, with the latest version it now sits there listening and doing nothing while I'm repeating the command louder and louder each time. It's just not worth it anymore, this way.