jimstriple wrote:When getting alerts (e.g. "Watch out; Car stopped on shoulder ahead") the distance given (in feet) is wildly short. It seems that the distance are very close to meters rather than feet. This is not a show stopper once used to it, since it is easy enough to compensate, but very annoying.
Motorola Droid Razr w/ Android 4.1.2
monita_rb wrote:I have a Galaxy Young, Android 4.1.
I been having the same problem since around a month ago: Waze closes by itself, seconds after being launched.
The only thing that I get to see is a piece of map (???) with the sign "big". But only for a few seconds... After that, it closes, no error message or anything!
I've already tried uninstalling and re-installing but no good.
People on forums with the same problem have found that the only workaround is to install the previous version... I find this unbelievable..
Dzzydvl wrote:I downloaded Waze 3.7.2 yesterday and started using it. When I'm on wifi, Waze starts up fine but when I'm connected to 3G, Waze would open, display the splash screen, display a blank map with "Big" on it, display the map and promptly force close itself. This would happen repeatedly.
I'm using Nexus 4 with Android 4.3
Superfraggle wrote:brucebarnes wrote:Waze fails to send the traffic report when it is triggered by the alert caused by the car slowing down.
It generates 2 pop up messages:
Uh-oh can't send report
Uh-Oh Can't get Alert Position
Manually resending the traffic report works.
Samsung S3 Android 4.1.1 Waze 188.8.131.52
It is likely an issue that the location is not initialized by the alert trigger
I get this all the time to. Keep meaning to check the beta forum to check if it's a known big or not
usa_fpdk1bex wrote: My trip to DC started on Monday and I came back on Thursday.AndyPoms wrote:Also remember, the week runs Monday -> Sunday it is not a running total over 7 days.
Users browsing this forum: Google [Bot], thom_p