[TESTING] XDAndroid GBX0C 2.3.7 Build

[fortunzfavor]

Originally Posted by tp2userp

What's the battery life with this build?

I am getting about 8 hrs in GXB0C, default package from the post, on full charge (from Winmo).

If you're on the .27 kernel, use the xdaledregime apk in the android apps folder to see if your device is sleeping.

Also, consider upgrading to one of the newer kernels if sleep is indeed your problem. That solved my sleep problem. Once you get whatever the issues is fixed, there's an app in the market called battery calibration (or something close to that) that will reset Android's battery stats and probably increase the accuracy of your battery meter a little -- it's something recommended for all users changing builds or batteries.

[arrrghhh]

Originally Posted by fortunzfavor

If you're on the .27 kernel, use the xdaledregime apk in the android apps folder to see if your device is sleeping.

Also, consider upgrading to one of the newer kernels if sleep is indeed your problem. That solved my sleep problem. Once you get whatever the issues is fixed, there's an app in the market called battery calibration (or something close to that) that will reset Android's battery stats and probably increase the accuracy of your battery meter a little -- it's something recommended for all users changing builds or batteries.

The new build has both Xdaledregime apps .

I'm also uploading another bundle. Not sure how, but I managed to screw up netloc again. I swear it's good this time, lol...

I'm also ditching OI/Astro for ES per a few recommendations & based on some research. Uploading soon, the filename will stay the same - just watch for 'date modified' to change.

Edit - ran into a hiccup and had to make clean it and start over... at any rate, should be up in a couple of hours. Will update this post once I do.

Edit 2 - build is up on the .cz mirror site. Should get pushed to the main files.xdandroid.com soon...

Edit 3 - both mirrors look good.

[countzero]

I've poked around a little, but haven't done in-depth searching.

Weird issue after updating to GB0C on my phone: settings and apps have bad orientation. Home screens are fine. Kinda funny. Disabling auto-orientation rectifies the issue, but of course it no longer auto-orients.

Anyone see this? I have re-used my data.img from GBX0B, will try a clean image.

On 3.3 kernel from autobuild.

On the upside, seems snappier and wifi/tethering works peachy.

[arrrghhh]

Originally Posted by countzero

I've poked around a little, but haven't done in-depth searching.

Weird issue after updating to GB0C on my phone: settings and apps have bad orientation. Home screens are fine. Kinda funny. Disabling auto-orientation rectifies the issue, but of course it no longer auto-orients.

Anyone see this? I have re-used my data.img from GBX0B, will try a clean image.

On 3.3 kernel from autobuild.

On the upside, seems snappier and wifi/tethering works peachy.

Odd, never heard of this. Interested to see what a fresh data.img brings...

Curious, is it ALL apps, or just certain ones?

[countzero]

Originally Posted by arrrghhh

Odd, never heard of this. Interested to see what a fresh data.img brings...

Curious, is it ALL apps, or just certain ones?

All apps - except the home screen and app list. Those two are both OK. Problem is present in fresh data.img.

I did use the suggested gsensor_axis=2,1,3, as I have for a long time across all builds.

I have a Rhod400.

Totally bizzarre!

[arrrghhh]

Originally Posted by countzero

All apps - except the home screen and app list. Those two are both OK. Problem is present in fresh data.img.

I did use the suggested gsensor_axis=2,1,3, as I have for a long time across all builds.

I have a Rhod400.

Totally bizzarre!

Well, the values changed for DIAM, but I don't think they changed for RHOD.

The home screen doesn't rotate tho, unless you have an aftermarket launcher - Launcher2 doesn't rotate at all, unless you open the KB.

That is the correct gsensor setting, so I'm not entirely sure what's going on... You're literally the only one to report this, so I have to think it's something environmental with your setup/device.