Android beta 3.2.0.995 feedback thread

[Mike-1323]

I have a comment about syntax that TTS uses which has been bothering me ever since I started using waze.
While approaching a turn the TTS prompt is along the lines of: "In point one mile . . . get ready to turn right." I interpret that as wait for 0.1 mi then get ready to turn right. I've always thought the appropriate way to express the prompt would be more like: "Get ready to turn right in point one mile." Maybe it's just me being anal, but I mock the TTS directions every time that I hear that.

[Autourdupc]

We have the speech alert, only when above the speed limit !
I think that having always a speech alert would be better and great !

Hmmm ... could get annoying if there are many speed cameras within a short distance.
or example I know roads in Austria where there are 5 Speed cameras within 5 km ... I would be annoyed if I would hear that every time I pass and not speeding ...

This is wy a setting would usefull for this function.

[crazycomputingdotnet]

Ok, I was finally able to be quick enough to grab a screenshot of an issue I have noticed since the 3.0.0 betas. Sometimes the first alert that pops up shows the alert at your location instead of the location of the alert:

I am here, but the police man is about 10 miles or so north...

Screenshot_2012-07-09-12-21-13.png (131.01 KiB) Viewed 199 times

Also today I was searching around for some of the places I needed to go to, and I started searching right after the splash screen popped up, well I would be half way in my search and the screen would refresh and I would have to start typing in my search term again. One of the times the screen refreshed three or four times before I was able to fully type in my search term, a couple times it happened after I pushed enter. I don't know if those processes that happen when the screen refreshes can happen durring the splash screen or not, but it would be perfered that when the map loads it is ready for you to do whatever you need to do, like search or navigate or whatever. I would rather have a longer splash screen time.

[fotrik]

At certain location here https://world.waze.com/editor/?zoom=5&l ... TTTFTTTTFT client draws something strange. It's OK in Livemap and Papyrus but the result in the client even when a map refresh is forced is strange. See the attached picture.

[fotrik]

And one bug more. Why the Waze client always dies when on background for a minute or more? I see the icon on the top status line, I see it also in the Android notifications page but when re-opened the application is started from scratch and reports a crash. I run other applications like IMO which have no problem to stay in background, so what's up with Waze?
Seen on my Samsung Galaxy S2 with 2.3.5 stock ROM but on other phones of my friends too.

[plausiblydamp]

I don't know if this was also happening in previous versions but earlier today I got a speed camera warning based on the direct physical distance rather than the road distance, didn't have chance to take a screen shot however...

The road in question sort of doubles back on itself and the camera was ultimately on my route but I got the warning at about 400 meters from the camera, unfortunately I wasn't on the stretch of road approaching so the distance dropped to about 300 meters before I was then moving away from the camera, by the time I reached the U turn in the road and actually started approaching the camera it was reporting a distance in excess of 1.5 KM

[gerben]

Still happening: wrong spoken streetname if a roundabout is announced after 'and then'.

[khaytsus]

Has anyone been having any trouble when moving around on the map and selecting other Wazers, etc? It seems like randomly when I do this the client freezes for 30+ seconds then eventually un-freezes.

It never freezes during normal navigation if I don't touch or mess with it, but if I'm sitting at my desk looking around town to see how much Waze traffic there is in the area I see it all of the time, not sure what to make of it.

[crazycomputingdotnet]

Has anyone been having any trouble when moving around on the map and selecting other Wazers, etc? It seems like randomly when I do this the client freezes for 30+ seconds then eventually un-freezes.

It never freezes during normal navigation if I don't touch or mess with it, but if I'm sitting at my desk looking around town to see how much Waze traffic there is in the area I see it all of the time, not sure what to make of it.

Actually yes, I usually get a prompt from my OS saying that Waze isn't responding with a wait / force close option.

[gerben]

Has anyone been having any trouble when moving around on the map and selecting other Wazers, etc? It seems like randomly when I do this the client freezes for 30+ seconds then eventually un-freezes.

It never freezes during normal navigation if I don't touch or mess with it, but if I'm sitting at my desk looking around town to see how much Waze traffic there is in the area I see it all of the time, not sure what to make of it.

Has been happening for a while, even before the 3.2 betas.