Android beta 3.0.2.3 - feedback post

[crazycomputingdotnet]

When I fired it up today it wouldn't lock into the GPS data. restarting didn't help. I had to do a reboot to get the client to lock in. Don't know if it is the client or the envirement, but logs were sent.

I had to do the same thing today. On my way home from work GPS locked in normally, but on my way to work, I had to reboot my phone to get GPS, and it took longer to get. Also there was a point where the maps were flickering. This happened for about 5-10 minutes. I will point out that I was off network at this time but I haven't seen this before, and this was a few minutes after the reboot so memory/cache / enviroment was clean and fresh. I was on the V-C theme this time, and I normally run the editor theme. So I don't know if that makes a difference.

[gerben]

The GPS gets a raw fix from the data connection after a reboot (it is told what satelites to look for). If there is no data connection, the GPS unit needs to find out by itself what satelites it should look at, which can take up to 15 minutes.

[crazycomputingdotnet]

The GPS gets a raw fix from the data connection after a reboot (it is told what satelites to look for). If there is no data connection, the GPS unit needs to find out by itself what satelites it should look at, which can take up to 15 minutes.

When I leave from work I am on my wifi and I am normally on a week network connection. I have not had the issues of getting a fix on previous betas.

[dsantosx]

Good i have no problem with the beta.

[bedo2991]

When in navigation mode I try to search a single letter destination (Ex: "P") I got the error "No connection with the server". I tought the servers were unavailable, but searching for longer words it worked. If you don't want to provide search for short strings maybe it's better to change the error message to: "The string you provided is too short" instead of blaming poor servers .

[Brshk1]

This beta is working well for me. It survives better in background, I can even use a browser or check forums. The official market one was killed whenever it wasn't active on screen (phone & OS details in my signature).

There is a minor glitch, very likely present in previous versions, but never paid enough attention until now. It has to do with automatically suggested destinations at Waze start. They take precedence over user selected ones, which is a little bit annoying. If unnoticed, one could be heading to the wrong place!

The action sequence is more or less:
- open Waze
- quickly select a destination
- Waze starts calculating route, BUT...
- if at that time there is a usual destination, such as home or work, the calculation is cancelled without notification and the route presented is the automatic one.

It happens more often than what my description might suggest. My understanding is that if the user has manually selected a destination, the client shouldn't replace it.

[a4bolek]

The GPS gets a raw fix from the data connection after a reboot (it is told what satelites to look for). If there is no data connection, the GPS unit needs to find out by itself what satelites it should look at, which can take up to 15 minutes.

That might be the case if you fly across the world and turn phone on in new location. Receiver stores last fix and satellite table. On restart it should not take more then a minute to get new fix.

Steps I took to check this. WiFi off, phone off, battery out, SIM card out, battery in, phone on. It took 38 seconds to get first fix.

Screenshot_2012-04-15-00-29-34.png (95.3 KiB) Viewed 376 times

[assasukasse]

Motorola XT615 Motoluxe android 2.3.7 stock

1) beta randomly reboots phone (but does not freeze it anymore)
it mainly happens when popups are displayed (especially the speed cam alerts)

2) speed trap and traffic light notifications are extremely intrusive and slow, phone sometime hangs at the notification and doesn't continue till i manually close it. When several notifications are displayed in a row even GPS signal lost notice is displayed.

3) HUGE memory or CPU footprint. Papaya was running smootly on an HTC hero, 3.X has having difficulties running on a modern phone. Most of the problems arise when notifications are displayed.

4) bluetooth devices make things worse, when bluetooth is connected is very likely the phone will hang or reboot at notification display or during routing.

5) before the phone reboots the keyboard becomes unresponsive, it is not possible to go to home or close waze.

I would strongly recommend finding a less intrusive notification method, speed traps request anyway an editor to approve or remove them, there is no need to pop-up the notification and countdown to 0. A simple flashing icon and a voice alert will do the job much better, when clicked the icon would open up the "is not here" button.
Bloating bloating bloating, the app seems to be sluggish, if the price for some nice graphics is a sluggish navigator I prefer the ugly ones!

[Harrievanofferen]

Today i had map data issues during the entire morning. Refressing map data, reboot of phone etc.etc. nothing worked. Around 11 in the morning or was over.
Was on the htc Desire with Android 2.3.3 tested since release of the 3.0.2.3

Tomorrow gonna start testing on the htc One x with Android 4.0.3.

Regards,

Verstuurd van mijn HTC One X met Tapatalk

[davboc]

There is the same big problem like in the stable version and the other beta: is impossible to add more than one unnamed street in the favourites, I hope that this issue can be fixed