Android 3.0.1.0 official feedback thread

[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

[crazycomputingdotnet]

Ok I have been using it for a couple of days, both in and out of navigation mode. It seems to be doing a lot better with keeping up the pace, expecially the slow down when in navigation mode and you go off it's recommended path. I haven't yet had the opertunity to go off the recommended path while eating cookies yet. Hopefully in the next couple of days.

It also seems to be better bonded with foursquare as well. I think the only time I had to rebond was after my first check in with this beta. Thanks for that one. Although (And I dont' know if this is FS or Waze) it does take a while for it to respond to you clicking on a locatoin before it gives you the check in page, there have been times where I have clicked on it again thinking that it didn't catch my touch and it has checked me in twice.

GPS still takes a lot longer to get established and it doesn't keep a good connection with the GPS. Before it was before the blue splash screen was done, now it can take a few minutes after, which is when I am already driving. It also is a lot more flakier with keeping cell tower connection. I tried to be observent as to if I was on edge, 3g, or 4g, and what my signal strength was, and it didn't seem to matter. Today on my way to work I was on a 4g with full bars, and still had network connection drop outs.

[crazycomputingdotnet]

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:)

[crazycomputingdotnet]

I noticed a bit of an issue with Waze in general but have forgoten to mention it until now. If you are able to report something but for some reason the client isn't able to talk to the server it tells you it can't connect and to try again later. However... If you are driving you are past the point of reporting and if you try to report the same issue again, the point on the map is not going to be in the correct position, so either Waze needs to try to report the issue x ammount of times again and put the point at the correct coordinates, or the verbage needs to be changed. I don't see many people wanting to turn around just to try again to report an issue....

[crazycomputingdotnet]

Ok I have been using it for a couple of days, both in and out of navigation mode. It seems to be doing a lot better with keeping up the pace, expecially the slow down when in navigation mode and you go off it's recommended path. I haven't yet had the opertunity to go off the recommended path while eating cookies yet. Hopefully in the next couple of days.

It also seems to be better bonded with foursquare as well. I think the only time I had to rebond was after my first check in with this beta. Thanks for that one. Although (And I dont' know if this is FS or Waze) it does take a while for it to respond to you clicking on a locatoin before it gives you the check in page, there have been times where I have clicked on it again thinking that it didn't catch my touch and it has checked me in twice.

GPS still takes a lot longer to get established and it doesn't keep a good connection with the GPS. Before it was before the blue splash screen was done, now it can take a few minutes after, which is when I am already driving. It also is a lot more flakier with keeping cell tower connection. I tried to be observent as to if I was on edge, 3g, or 4g, and what my signal strength was, and it didn't seem to matter. Today on my way to work I was on a 4g with full bars, and still had network connection drop outs.

I just wanted to update a bit now that I have had a chance to use it a bit more. Foursquare is a lot better in staying bonded, I would say that ~1 out of 10-15 checkins I have to rebond, so it is a vast improvement but not perfect. Both FB and Twitter was a set and forget experience, and have never had to relogin, it should be the same for FS.

And as stated before the GPS and Network both are flakey, there will be times where I will have a full signal on my phone but I will either have the searching for network, or when trying to report/checkin I will be greated with the wonderful no network connection message. This has resulted in missed oppertunities to help my fellow Wazers.

[crazycomputingdotnet]

I don't know if this happens every time, but when you are stopped and Waze starts showing you the issues, the first issue that pops up doesn't show where it is, instead it stays at your current location.

Also one out of every ~10 times I start up Waze the map/icon is shifted so the icon and the drive is in the bottom right of the screen. Going into something like settings and then back into the map has been correcting this.

[crazycomputingdotnet]

Yeterday, I dd some driving around for about 5 hours, It seemed like GPS was off more than on and the app hard crashed when coming up to a yellow slow down. Logs were sent.

[daehl]

Not sure if this is specific to the Android Waze client, but it's the only one I use. I have been using Waze 3.0.1.x religiously for the last month or so, and in all that time it has not learned any "preferred routes" based on my driving habits. It's very annoying as well, because it suggests quite ridiculous routes that take me 10-80% longer distance on my work commute. (I drive an 8.6 mile commute, but Waze continues to suggest 11mi & 14.2mi routes in the top three preferred routes, and the 8.7 mile route it does suggest has many more intersections and non-highway roads so that route takes at least 10 minutes longer than mine). I drive the same way every day, but Waze refuses to suggest the route I drive every day while using Waze.

I figured the Waze maps might have something to do with it, so I made a huge amount of map corrections to the city I live in, and they finally just started appearing live with the 2/12/12 map update today. I'm hoping that would help, and it has a little, but even today, there is still there is no sign Waze is learning my route to work.

Any thoughts or suggestions?

[daehl]

And please note that Waze learns your frequent destinations, not your frequent routes. It will always calculate the fastest route to your frequent destination.

Android Waze says it can learn routes. On the Routes pane it says "Tip: Teach Waze your preferred routes by simply driving them several times"

It looks like others have noticed this isn't working as well:

http://word.waze.com/forum/viewtopic.php?f=3&p=116411

They mention that it was working in the beta, (preferred routes would appear with a heart icon to indicate them along with displaying Waze's calculated routes) but not in the final release. If true, that would seem to indicate a bug in the 3.0.x Android client.

[daehl]

I also noticed that the Android 3.0.1.1 client is not displaying the same tiles as what appear online. Not sure if this has anything to do with the client itself. My guess is there is a separate map database just for the mobile clients. How else would it explain why the roads are different than the online "Live Map".

More details here:

viewtopic.php?f=8&t=17099&p=153109#p153109