Android beta 2.9.99.124- official feedback post

[Laakkus]

When driving to work today, sent a map update request. I know the notification is disabled, BUT IT DIDNT GET THROUGH or I at least I cannot find it on the editor (old or new). Is there a problem with URs at the moment or is it a bug in this beta?

EDIT: (gmt+2) 12:37
It just took few hours ? to get to the editor. Must be the sync stuff..

[marka971]

I cannot see the map in Stockholm, Sweden. All I see is other wazers and traffic reports.

Screenshot_2012-01-26-12-05-34.png (187.89 KiB) Viewed 346 times

/Markus, Android 4.0.1, Galaxy Nexus

[marka971]

I cannot see the map in Stockholm, Sweden. All I see is other wazers and traffic reports.

Screenshot_2012-01-26-12-05-34.png

/Markus, Android 4.0.1, Galaxy Nexus

Ok, it works now after I cleared the data for the app, now I see the maps again.

Markus

[marka971]

"Refresh map of my area" not translated to Swedish.

/Markus, Android 4.0.1, Galaxy Nexus

[nbmagnum]

Hello,

the new version of Waze is very good and I really like it. Great job guy's.

I have attached some screenshot's. This are traffic reports.
For me, the message window is too big and it hide/overlap the actual information the map.

[NI-Chuck]

Looking good! This is the first Beta were I don't suffer from a garbled map until I swipe/go into settings and return. Will hit the road tomorrow and see how fairs.

[noamparn]

Still have this bug with the .124.

I have the same thing on my Verizon Droid 2 Global, OS 2.3.3, stock ROM.
I saw it in beta .120 (which was the first beta version I tried - before that I was using the official release version). It happened one time yesterday, after I upgraded to .124, but it didn't happen after that.
I use mine with the official Motorola/Verizon car mount, with the "Car Dock Home v3" application (not the standard "CarDock" app). The phone is in "landscape" mode in the car mount.

Usually, the blue "logo" startup screen shows up sideways (oriented for "portrait" mode, even though the phone is in "landscape" mode in the dock. This was the same behavior I saw with the release version prior to trying .120. Once the app loads, though, it is usually in the proper "landscape" mode.

When I was getting the "blue screen of Waze" bug with .120, the screen would display in "portrait" mode, as it does when first loading the app. However, sometimes it would flip the logo screen to "landscape" mode.

[noamparn]

If a whole class of Android devices suddenly become "too low-end" to run Waze reliably, it's going to cost Waze some long-time users.

I'm able to run this beta on my 2 year old HTC Magic with v2.2.1. I've not noticed any lag in the display. I do have to keep the number of running apps (and widgets) to an absolute minimum though, as I only have 96Mb for everything.

In that case, I'm at a complete loss. Maybe it's an issue specific to the Transform architecture, or to Sprint's distribution package, or to a particular app that I have installed, but the Beta on my phone is essentially unusable. (Anyone using a Transform, please chime in!) And it's not eligible for an upgrade until August.

Please don't take any offense in this, and I apologize if you've already done this with no change in the problem, but I'm going to ask the obvious "dumb" question here:
Have you tried rebooting? I had a number of issues when I first installed the beta (I just started with the previous beta version, .120). Waze couldn't find a GPS lock, it wouldn't even stay open (crashing), and I just did a battery pull on the phone. Once the phone came back up, everything was fine.
If you haven't done so already, it might be worth a try. You might also want to take another look at the other running apps you have, especially any that might hog the data connection. Some other app might be hogging the resources (perhaps a different app has even crashed or hung), and waze might just be a victim of that problem. One other thing to check could be the "data transfer" settings, perhaps they are not optimal for what you are doing.

[ozguy]

Still getting the same issue since 2.9.99.12

LG Optimus.

Display is corrupted when the map first loads, but once you do something that requires it to reload (such as enter a destination) it usually displays fine.
I can't take a screenshot, but the corruption shows red over the top of the whole map, and the text just appears as black blocks. Edges of speedometer are also not transparent. Looks like the problems all relate to things that are supposed to be transparent (since you can see what the map is supposed to look like, and then the red draws over the top of it).

LG Optimus is only 320 x 480 resolution. The speedometer takes up quite a bit of space on the screen. It would be nice if there was a way to choose a simpler speed display, since the gauge serves no purpose other than to look pretty.

[perlin]

Hi guys,

You can share your feedback on this beta here.
Please read the release notes before installing:
viewtopic.php?f=18&t=15443

Your feedback is very important to us, so feel free to comment about everything that comes in mind.

When reporting a bug, please mention your device + OS + ROM.
Always send logs - they help us better understand the problem.

Thanks,
Perlin