Android 3.0.1.0 official feedback thread

[flyfire]

Upgraded from Android market today. Version shows 3.0.1.1. The same problem as, or even worse than, v2 is this app gets confused and recalculate every time exiting from parking lot. Tonight I drove from a restaurant back to my hotel which is 1.6 miles away. Waze originally calculated the correct route and began to recalculate when I drove around the restaurant to the exit. And after I parked my car at hotel, the recalculation was not completed yet. 5 minutes for recalculation! If I were on a highway, how many exits are passed？ Seems I have to use Google Nav till new update is available.

[Suik]

Personally to me it seems, that waze v3 is capable of route recalculation in a timely manner when I am driving outside cities i.e. not that complex roads & streets structure. The less options to drive, the quicker the recalculation. When driving in the city, the recalculation takes from 2 minutes to forever (does not recalculate even if I finished my trip already).

Plus it seems, that when waze is not able to recalculate the route for longer time (cca. 5 minutes) it looses somehow data connection and is not able to re-connect until shutdown and waze restart.

EDITL: I forgot.....there are again this routing server issues pop ups appearing quite often.

[fotrik]

Driving into work today I was unable to report a car that was stalled out in the middle of the road because Waze was not able to grab on to the network connection. (No Network connection error). It was in the city and I had a full 4g connection. (Insert comments from previous thread(s) here:)

Had the same problem several times in area with poor GSM signal. The client needs to be improved to collect the reports locally also when the connection is not available and send them when the connection is got again. I hope that developers read this thread and put a high priority on it.

[hl97531]

I was using Waze last night and the program consistently lost GPS signals, eventually the program froze. Logs sent. I switched to Google map after phone reboot and GMap didn't has the same GPS issues.

[bombebomb]

I never read the entire thread, but I will post my findings anyway.

It seems to run normal, however it now will cause my Samsung Droid Charge with factory android on it to reboot once, once it reboots, I reopen and it works fine.

Has this this several times.

In short

Samsung Droid Charge
Factory Android 3.x
Hard reboots often on first start up of waze

I have tried killing most apps before starting waze, and just starting it up normal.

[southdave]

Samsung Galaxy SII v2.3.3

After i installed the new version i am still having a few issues. Whenever it has crashed i have sent off the logs.

The new release does appear to be getting quicker and quicker.

The default setting after install for Unit was KM again instead of what i had set it to (Mile). I have reported this for each upgrade i have performed.

I have also got a bit closer to pinning down all my crashes.

Every single one i have seen since the upgrade to 3.0.1 has been tile related and i have been able to reproduce some of them just by navigating around. I have tried a cache clear as well as re- caching my ocal tiles

Most of the issues i can see (as i don't have my eyes on the screen all the time im driving) are when i increase my speed and the map zooms out, it then struggles to draw/download the tiles, hangs for about 30s to a min and then offeres up Force Close. Sometimes if i leave it i find that i am still being offered navigation direction via voice in the background with the force close in the foreground. Not knowning the code but this might be related to some tile code (downloading / displaying) not releasing back to the OS regularly enough for Android to be happy (stuck download/display thread etc).

The last issue i am still having is related to the overlay that displays the the directions (at the top of the screen) and the time/distance/speed at the bottom. Often they will all just turn grey but the background map will continue to update and i will continue to get voice directions. If i select Menu/report while in this state either the dialog window will all be grey or the whole screen will go grey (back key returns to map with grey over lays). This usually does not lead to a crash but i close and restart to get the rest of the graphics back.

Kepp up the good work and i hope you can fix some of the last crashes as it is by far my best GPS tool i have on my Android at the moment.

Dave

[bangus236]

just a couple of issues that i would like to see improved on later versions:

1. when i stop temporarily (to go to atm, to use phone, etc) it sends report that the road i'm on is on "complete standstill" when it really isn't. although a pop-up appears asking if there is a traffic jam, it would still send the "standstill" report even if i click "no". i hope there would be an option to pause tracking?

2. since there are a lot of unavailable waze landmarks in my country, i usually find destinations from foursquare. i actually set my "work" & "home" from foursquare. going home, waze tells me that i have reached my destination but i am more than 500 meters away from the flag. but going to work, even if the "car" is already on top of the flag, it still wouldn't stop routing. i hope on later updates, there would be an option to control the distance to destination when it will say that you are there.

thanks!

[pospa_net]

Hi.
On my SGSII device. New version of Waze is still crashing. I have used it for about 10 minutes and I have collected 22 crush reports by now (all of them are sent). Situation is pritty the same on my wife's Samsung Galaxt Ace. Where can I download previous version? This one is realy unusable.

[aka_serge]

Perfect version, very rare timeouts for alternative routings.

Sent from my HTC Desire HD A9191 using Tapatalk

[cheniro]

Samsung Galaxy SII v2.3.3

After i installed the new version i am still having a few issues. Whenever it has crashed i have sent off the logs.

The new release does appear to be getting quicker and quicker.

The default setting after install for Unit was KM again instead of what i had set it to (Mile). I have reported this for each upgrade i have performed.

I have also got a bit closer to pinning down all my crashes.

Every single one i have seen since the upgrade to 3.0.1 has been tile related and i have been able to reproduce some of them just by navigating around. I have tried a cache clear as well as re- caching my ocal tiles

Most of the issues i can see (as i don't have my eyes on the screen all the time im driving) are when i increase my speed and the map zooms out, it then struggles to draw/download the tiles, hangs for about 30s to a min and then offeres up Force Close. Sometimes if i leave it i find that i am still being offered navigation direction via voice in the background with the force close in the foreground. Not knowning the code but this might be related to some tile code (downloading / displaying) not releasing back to the OS regularly enough for Android to be happy (stuck download/display thread etc).

The last issue i am still having is related to the overlay that displays the the directions (at the top of the screen) and the time/distance/speed at the bottom. Often they will all just turn grey but the background map will continue to update and i will continue to get voice directions. If i select Menu/report while in this state either the dialog window will all be grey or the whole screen will go grey (back key returns to map with grey over lays). This usually does not lead to a crash but i close and restart to get the rest of the graphics back.

Kepp up the good work and i hope you can fix some of the last crashes as it is by far my best GPS tool i have on my Android at the moment.

Dave

Dave, for the last issue can you please upload a screenshot?
Regarding your crashes we found the logs and the dev team will take a look at it.

I would like to thank you and all of you guys for your feedbacks, we are reading it all and everything is documented.
Nir