Well I tried all kind of things today and cannot get Voice commands to work properly with my 3 week old phone. I even tried giving Google some voices, and Google has no problem in understanding. Guess I will have to stick with pressing the screen to send alerts, etc.

tstrempfer wrote:Same problem here. GS3, stock Android 4.1.2. A few months ago voice commands for traffic or hazards used to work. But no more. What is frustrating though is that once I reach my destination, if I wait for a bit and fire up waze again, and "test" a voice commanded hazard, it hears me just fine. It's only when I'm underway it doesn't work. A fix here would be HUGE, because as mentioned by others, feeding back this sort of road intel to the community via screen taps is way to dangerous. The voice idea and menu structure I think was well thought out (when it worked for me way back when anyway). But now I am no longer able to contribute feedback to the community.

That is exactly what I am experiencing. Once I get where I am going, and fire up Waze again, it works perfectly with test commands. Hours later, on my way home, I start Waze, drive a mile or so, try to send a command, and it won't work.. Looks like quite a few people on this thread are having the exact same problem. I am running stock Android 4.2.2

I have tried both options blue tooth on setting and both off. It still will not pick up commands. Works fine on phone speaker only but that make the app to dangerous to use while driving! All this started with the last download so I'm pretty sure it was in the new voice commands that were installed. I have an I phone 5 but it sounds like it hits many type of phones also. My wife has not downloaded the upgrade and hers still works fine with blue tooth

Yes I have the same issue. I've not been able to get waze to hear/understand any voice commands. Same symptoms - no matter what I say I get back "try again" a couple of times and then "cancel." I haven't yet tried to figure out why or fix it. I will note that I can use the native voice recognition with no problem to search for destinations by hitting the microphone button on the navigate screen, so it doesn't seem to be a hardware problem.