Android Beta 3.2.1.995 Feedback thread

[perlin]

I updated to latest beta and to Android 4.0.4 Custom Rom (Maclaw.pl).
Now Waze doesnt start most of the time (it kicks me back to app drawer, notification icon stays) but when it starts it cant get my position...

Try a clean installation. Clear cache and delete the waze folder from the SD card. After that install the beta again. Please report back if this helps.

[TotMannGeht]

same probs...

deinstalled waze, deleted waze directory on sd, made a clear cache with crm, reinstalled beta...
nothing changed

i also saw a difference between waze and the other programs... if i start another gps programm the gps indicator blinks in the notification tray and stays when fix.... but with waze that indicator doesnt even show...

managed to start waze... opened waze a quickly after pulled down the notification bar... was able to send the logs....

[vitj]

I have sometimes problem during start of application. I got black screen, it possible switch off with "switch off" windows. When i repeated start, then application normally starts.

I had crash during navigation, application was frozen and from phone was going sound like machine-gun.
I am using phone SGS2 with CM9 RC2.

[theemike]

So far I have had good luck with the beta. The old one might not connect to the GPS half the time but this one is always connected

Sent from my DROID Pro using Tapatalk 2

[stuffhappens]

Found reason of frozen client app
Other users reported that the app freezes sometimes. Not sure if this is the same situation but I have found reason why every 3.x including this one sometimes freezes on my phone. It's always during data communication when the phone has slow connection or the connection is even lost.

When I long press the standby button, one of the features SGS2 offers in the menu there is to disable/enable mobile data connection. When I do it when the Waze client just communicates, the application frezes! Not for seconds or a minute but forever. Well, at least for more than 5 minutes until I reenabled the data connection. Then the client started to work again without termination. This is unacceptable behavior and the client has to communicate always on background with no single second frozen.

You are right... I found the same results.

I'll have to agree too - seems possible this is why Waze freezes on me soon after it starts, about 50% of the time and I have to reset the phone.

[stuffhappens]

Also a suggestion but is it possible in a future build we can have the ability to enter custom Events Radius, or maybe have 10 or 15 miles (in between 5 and 25)?

In the future will add an option to set the events only for your route. About the option to turn it off- not likely

A slider to choose a value would be best. My daily drive to work is 34 miles, so 25's too little and 50's too much.

I wouldn't select 'events only on route' as accidents or jams etc. a short distance off it might start traffic heading towards my route - causing problems that I will encounter some time in the future.

I need to know about the events near my route as soon as they are reported and not when the knock-on effect has actually begun to affect my journey.

[crazycomputingdotnet]

I haven't had a chance to fully test the new version yet. I am running into issues not related to Waze entirely. Over the (my) weekend (I am off Tue/Wed) I upgraded the MT4GS to Aplha 6 and it is having the same issue as alpha 5 was. Everything else but Waze connects to the network. Have to downgrade to Alpha 4 and get with the dev.

On my Tab for some reason I am not getting a connection on the phone network. When I start it up on the stock rom com.phone.android force closes twice and I have a feeling that is why. When I try to install the CM Rom, for some reason it installed the wifi version and will not allow the tmo version to be installed, so I am working on that issue as well. I think I am going to try to reinstall the stock rom tonight and hope it doesn't kill root.

I ran it on my tab on the way to work today up to where the map cache ran out even though I didn't have a connection, it is stable, but the icon placement is a bit wonky in landscape. Later on I will post a screenshot.

[j2002]

I'm starting to read the post so I don't know if it is already said: in this version I it is usual "to lost the route"
When Waze recalculates the route, it happens it doesn't found destiny or way or whatever.

[Autourdupc]

I still notice the issue of the Physical report list having less than the Voice command list, such as oil, ice, monsoon, flood, ect. I'm not quite sure whether this is an issue or just a lack of place/sub categories.

The main problem is that hazard options are different between countries (and between different times of the year). When we change them accordingly, it affects the menu choices - but not the ASR choices. We're going to create one version for both of them, but not sure when it will be implemented. Hopefully for next version.

Too many choices possible. Should think to delete some of them. It then be clear and easier to use.

[amiga6]

Losing very often the GPS contact I had waze up a couple of hours now and get disconnected frequently. Logs sent 03:20 Swedish time (02:20 UTC)