Android beta 2.9.99.124- official feedback post

[slicer]

Do you use the "Car Mode" app ?

Because if this app is not running, I haven't the bug. I can plugged and unplugged my device without losing map screen.

[southdave]

I have been getting a lot of "Force Close" messages with this and the previous beta when i have been panning around the map. I have sent over 10 lots of logs in the past two days for you to assess.

Seems to hang when it is either downloading or displaying new tiles in an area i have not been to before. Within a few seconds of the UI hanging i get a force close message.

I have a SG S2 stock ROM 2.3.30


Dave

[fotrik]

Do you use the "Car Mode" app ?

Because if this app is not running, I haven't the bug. I can plugged and unplugged my device without losing map screen.

I see! No, I don't have this application.

[slicer]

It's the default app which is launch when you plugged your device on the dock, on stock ROM.

[fotrik]

It's the default app which is launch when you plugged your device on the dock, on stock ROM.

No, I don't have such an application in my phone.

[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.

[fishter]

I know this is an "unofficial ROM", but I've installed on CM 6.1.

The app starts slowly, then runs well for a few minutes before the phone reboots. This is both with and without navigation being on.

On restart the app doesn't start at all. Black screen for 10-15s then back to the launcher. I get round this by erasing the Local Data and restarting.

[khaytsus]

I'm sure what I'm seeing isn't typical, or there would be panic in the streets. My phone is over a year old (*gasp!*) and doesn't have a lot of free memory.

Yeah, 256M of ram is pretty low-end, my Nexus One is two years old, but it does have 512M of ram, could possibly be the difference. It's also possible there's a rendering issue, have you tried 2d vs 3d?

[harling]

I'm sure what I'm seeing isn't typical, or there would be panic in the streets. My phone is over a year old (*gasp!*) and doesn't have a lot of free memory.

Yeah, 256M of ram is pretty low-end, my Nexus One is two years old, but it does have 512M of ram, could possibly be the difference.

Aw heck, I'm lucky to see 50M (available) during normal operation. Tell me it isn't "paging" to flash...

The thing is, 2.x didn't have this problem. 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.

It's also possible there's a rendering issue, have you tried 2d vs 3d?

I'll have to test that. My sense, though, is that the problem is not the screen refresh itself, but something that monopolizes the system to the point where the screen-refresh code isn't getting enough opportunities to run. Call it a hunch.

[Timbones]

Aw heck, I'm lucky to see 50M (available) during normal operation. Tell me it isn't "paging" to flash...

The thing is, 2.x didn't have this problem. 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.