[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

So nice, you must post it twice.

[eurohunter]

I just noticed that by updating Google Maps to the latest version (march 9), the screen doesn't go haywire on rotation anymore. As for the Gallery app, we can always find a substitute (I like QuickPic.) This way I guess we can mark Issue 13 as solved.

[htrakr]

Could this be the reason why some people have much better battery life on their phone than others?
Free Apps Drain Smartphone Batteries | TechWeekEurope UK

[rete]

Originally Posted by htrakr

Could this be the reason why some people have much better battery life on their phone than others?
Free Apps Drain Smartphone Batteries | TechWeekEurope UK

I guess a general statement like that is a broad brush. If you want to know what is eating battery, install Betterbatterystats.

[rete]

Originally Posted by eurohunter

I just noticed that by updating Google Maps to the latest version (march 9), the screen doesn't go haywire on rotation anymore. As for the Gallery app, we can always find a substitute (I like QuickPic.) This way I guess we can mark Issue 13 as solved.

There seems to be an OpenGL ES problem with this build. That is probably the reason for the graphics corruption in some apps. I noticed that google maps 6.40 does not go haywire upon rotation, but gallery3d.apk still does. You can replace it with a version that doesn't have the rotation problem (like the gallery3dr.apk in this thread) but the underlying problem is still present.

Quadrant reports that my phone is using OpenGL ES 1.0 - I guess with the libGLES we have we *should* be seeing 1.1

[arrrghhh]

Originally Posted by rete

There seems to be an OpenGL ES problem with this build. That is probably the reason for the graphics corruption in some apps. I noticed that google maps 6.40 does not go haywire upon rotation, but gallery3d.apk still does. You can replace it with a version that doesn't have the rotation problem (like the gallery3dr.apk in this thread) but the underlying problem is still present.

Quadrant reports that my phone is using OpenGL ES 1.0 - I guess with the libGLES we have we *should* be seeing 1.1

There's always been questions as to whether our hardware supports 1.1 or not. I think we've tried 1.1 libs, but our hardware might not support it...

[rete]

Originally Posted by arrrghhh

There's always been questions as to whether our hardware supports 1.1 or not. I think we've tried 1.1 libs, but our hardware might not support it...

Interesting. The HTC Hero with for all intents and purpose identical hardware to Rhodium (MSM7200/7600/Adreno 130) does support 1.1...

[arrrghhh]

Originally Posted by rete

Interesting. The HTC Hero with for all intents and purpose identical hardware to Rhodium (MSM7200/7600/Adreno 130) does support 1.1...

I thought we had the Qualcomm MSM7200A. Either way, I do believe we have the Adreno130. Perhaps we're not using the right libs? I don't know.

[rete]

Originally Posted by arrrghhh

I thought we had the Qualcomm MSM7200A. Either way, I do believe we have the Adreno130. Perhaps we're not using the right libs? I don't know.

Like Rhodium, the Hero also has the MSM7200A (A = 65nm vs 90nm for non-A) in GSM phones; 7600 in CDMA/GSM phones. My Telus Rhodium has MSM7601 (the 1 indicating a Broadcom patent workaround).

Hero and Rhodium are very similar hardware-wise, down to the same amount of RAM/ROM.

[arrrghhh]

Originally Posted by rete

Like Rhodium, the Hero also has the MSM7200A (A = 65nm vs 90nm for non-A) in GSM phones; 7600 in CDMA/GSM phones. My Telus Rhodium has MSM7601 (the 1 indicating a Broadcom patent workaround).

Hero and Rhodium are very similar hardware-wise, down to the same amount of RAM/ROM.

Yes, but they are not identical. The Magic is also pretty similar, just less RAM. Tattoo/Legend I gather is also pretty similar.