Galaxy S2 Android ICS 4.0.3

Upgraded from beta using Market. Took it for a quick spin. Using other phone called myself then made a phone call with Waze in background. No issues. Looks good.

Galaxy Tab 7.7 Android Honeycomb 3.2.

Updated through Market from beta. Starts with no problems. Have not road tested yet. Many wazers out there.

http://witekm.com/waze/capture_34.jpg

Phone: Galaxy Y S5360
Waze Version : 3.0.1.1
issue keep force closing after several minutes n have to be kill several time.

Perfect version, very rare timeouts for alternative routings.

Sent from my HTC Desire HD A9191 using Tapatalk

n1c0s wrote:I just update to 3.0.1.0 but I saw a new permission needed by waze to access private data...

Could you explain me why this permission is needed ?

http://www.waze.com/forum/viewtopic.php?f=3&t=16659

Autourdupc wrote:Updated now from last beta.
Crash when first launch !!

One should nearly always completely remove the old version instead of upgrading, especially if previous was the beta. There are usually a host of issues associated with upgrading Waze. Not sure why, but it seems to affect both iOS and Android.

Zerenia wrote:2. Reports filtering does not seem to work. Filtering on reports on my route does not change the list of reports, nor does filtering on report from my group. I see all reports in whatever radius I have chosen, regardless of the filter applied.

That filter is only to the list as you view them. It does not apply the filter beyond the list being viewed. There is no way to filter what appears on the map nor what pops up.

Htc Hero
stock rom with OC enabled

new waze is painfully slow
2D with autozoom almost unusable
3D a bit better but keep losing GPS
popups make things worse, I cannot disable popups so whenever i am close to a red light camera or speed trap the system just hangs there for a good 20 seconds...
Whenever I stop annoying messages popup, and im again crawling.
reporting is painful since popup takes a good 3 seconds to come up
speedometer can't be enabled or the system begins to crawl again
Just one question, what is the need to see the road names when im driving over 40 mph???
it just slows everything!
Voice announcements are again painfully slow, its like: at the next roundabout (3 sec pause) take (3 sec pause) the second exit...by that time im already out...
Papaya still works best for me, snappy enough and not bloated...

Motorola Motoluxe XT615.
Waze randomly freezes the phone badly in 3D (need to remove battery) and reboots it in 2D. Bluetooth seems to increase the problem. Had removed the folder on SD and reinstalled it from scratch, no changes, still freezes phone.

Not sure if there is a more upto date feedback thread, but just wanted to say that I really have issue with the 'roads disapearing above 40mph'. It was always good to see roads around you to give you a approximation of where you area. Also if you are not using Waze to route you, just to provide feedback back to the network, and you're driving on a 'street', you end up with no roads at all around you.

Can I officially ask for that to be made an option, so those of us who know what we want, can disable/enable it. If you don't want to do that, you could always just dim the surrounding roads rather than getting rid of them completely.