lunarplexus wrote:Honestly, I don't know the radius but it should be pretty big since I usually get 20 to 27 wazers nearby but i just think that's in my city because we don't have a lot of wazers in New Delhi. So, i too would like to know the radius.

And yes, it is a standard feature in the client that shows for a few seconds. Makes me feel good no matter what the radius is.

Sent from my HTC Desire Z using Tapatalk 2

I'm not sure of the radius either, but i know that it is large since I usually see numbers in the 2000-4500 range. It may not be a radius around your current location but rather a count of wazers in a defined area that includes your current location.

Voice command have never worked well for me so I disable them. Every version I turn on voice commands for a couple days and end up getting frustrated with it so shut it off. My experience with this version wasn't any worse than any of the previous versions (not noticeably better either).

DG567 wrote:I think this was changed because users requested it. Personally, I prefer it to pause because I listen to vocal podcasts in the background.

I know a number of users, including myself, requested this as we listen to audiobooks while commuting.

I can't perform a category search anywhere except my current location.

Specifically, if I manually pan the map and tap-hold a location and open the information page about that location and then select more -> set as start point then select categories -> gas stations and prices from the navigation menu, I get the stations around my current location, not my selected start point location.

Been aware of Waze since last Sept when I jumped ship from WM to Android. But not until I got upgrade from my crappy Android 2.3 to the GS3 did I manage to install the waze app (coz the space it took).

Anyway, overall I feel the app worked fine, but I need to report one major issue.

Seriously, you guys may want to modify the way Voice command works on Android app. For one thing, the 3 finger tap never worked on my device and I had to use wave over the front camera. And you might want to add instructions for the gestures too. I had no idea that "wave" was activated by the front camera until I noticed the glare from the camera one time in dark light. I thought I need to wave the phone. And 2nd of all, voice command in normal driving conditions is plain useless. I tried w/ my Jawbone icon bluetooth (it has killer noise cancellation algorithm), and without. The device would not recognize my command even I shouted. I guess you somehow configured it to get voice from the phone mic all the time, and the road noise basically killed the function.

I noticed that people suggest some force bluetooth setting for ios app, but I do not see it in the android version at all, the only available setting for voice is to "route voice through speaker".

Thanks.

I'm so surprised nobody but me report the problem with voice command. So how's everyone doing in reporting the events?

I tried with my bluetooth earphone and without both, somehow the app always try to pick up the voice command through the phone's mic, which basically got overwhelmed by the regular road noise while driving. It's always a hit or miss, and 90% of the time, it would not recognize my full command no matter how loudly I shouted. I feel very unsafe if I have to tap on screens to report anything while driving.

I have been running the Watchdog app for a long time. Waze never showed up as a CPU suspect until the last few days.

Now I've got a very strange situation: I properly exited Waze with no errors. Yet it continues to eat up 50-60 percent of the CPU, forever!

I see that others are having battery drain problems since the new version of Waze came out... but they don't suspect Waze because they have exited.

Looks to me like there's a real issue here. Waze is not really closing, and/or some kind of Waze-owned subprocess continues to eat CPU after exit.

Is there any way to help debug this?

BTW, an effective yet painful workaround is to reboot after using Waze.

I admit it I'm a noob. I upgraded and now Waze 3.6.0.0 disables my GPS. Can someone send me a link to the version from March 15? That worked for me.

Motorola Triumph
Android 2.3.7
Waze 3.6.0.0

This is my first time reporting a bug. About 1 of 5 times that I start waze, it completely freezes my phone OS forcing me to pull the battery and reboot.

I don't feel like it has gotten better or worse since the latest update.

How can I help to get this this issue fixed?

Phone details in sig.

Having so much issues with play store version vs the last beta. Traffic layer does not even show up for me. Tried to uninstall and now I can't use the restore favorite command, tells me I don't have Internet connection and closes the app. Going back to beta.

Sent from my SPH-L710 using Tapatalk 2