FORUMS

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

What’s Next for Samsung and Its Flagships?

If we were to say that the Galaxy S6 was a leap of faith made by Samsung, we … more

The Ultimate Showcase of dBrand Skins

In the search for ways to protect, accessorize, and personalize; a user has many options. One … more

Huawei’s Rapid Rise to Third Place in the Smartphone Race

Huawei has quickly grown to become one of the world’s biggest … more

[TESTING] XDAndroid GBX0C 2.3.7 Build

11,596 posts
Thanks Meter: 3,731
 
By arrrghhh, Retired Forum Moderator / Recognized Developer on 31st December 2011, 05:41 AM
Post Reply Subscribe to Thread Email Thread
3rd May 2012, 10:43 AM |#691  
Member
Thanks Meter: 1
 
More
After 24 hours of testing i had just 2 problems. No sound and no autobacklight
Everything else works flawless including WIFI, GPS and finnaly my camera works awesome nice work!

I'm on the latest kernel 3.3.4, running on a rhod100.

I will upload logs in the afternoon.
 
 
3rd May 2012, 02:01 PM |#692  
Senior Member
Thanks Meter: 6
 
More
Unhappy
I've been running this release on Sprint CDMA Rhod since last week with the kernel pack that was the latest at the time (the one before 3.3.4). I've been happy as BT was apparently working, not very well, but I actually made a dozen plus calls with BT, and it was fine. Kind of, because after sleep it would not always recognize that the earpiece was there to connect to, or in couple of occasions when I turned on the earpiece the phone would completely freeze.
Then yesterday all heck broke loose. 1st the phone got completely unresponsive, i.e. no reaction of any kind on any key press. I was not home to see if was really dead by hooking ADB, so I did the battery pull.
After that stuck in bootani for 5+ minutes. Another battery pull, it booted, but would FC everything. Shutdown then reboot. Stuck in bootani, booted after 2 more tries, everything FC again. I checked then and saw 3.3.4 kernel. Put it on, wiped data, put original rootfs on and tried to start from scratch. As I posted in kernel thread, it would not go through initial boot getting stuck on calibration, as if ts-calibration file was not in the directory. After that I reverted to 3.3.2 and it went through, though I made no attempts to use BT for now.
3rd May 2012, 03:40 PM |#693  
Senior Member
Thanks Meter: 332
 
More
Quote:
Originally Posted by djcrosstunez

After 24 hours of testing i had just 2 problems. No sound and no autobacklight

Sound is an issue on your end -> make sure you have followed the csv directions to the "t".

Auto backlight on rhod 100 - Make sure you boot with auto-backlight OFF in winmo. Even then, I am not sure if anyone has ever tested auto-backlight on RHOD100 -> i know you guys have funky panels. As far as i know, it's been tested to work on 210 and above. Perhaps test to see if it works for you on .27 - should be similar as in 3.x, same mechanism is used in both kernels. If it doesn't work then someone needs to do some haret tracing in winmo.

Quote:
Originally Posted by ObviousMan

After that stuck in bootani for 5+ minutes. Another battery pull, it booted, but would FC everything. Shutdown then reboot. Stuck in bootani, booted after 2 more tries, everything FC again. I checked then and saw 3.3.4 kernel. Put it on, wiped data, put original rootfs on and tried to start from scratch. As I posted in kernel thread, it would not go through initial boot getting stuck on calibration, as if ts-calibration file was not in the directory. After that I reverted to 3.3.2 and it went through, though I made no attempts to use BT for now.

Bluetooth hasn't made it to 3.3.x. It's on my phone I just need to find time to run down to my car and see if pairing works fine. If for whatever reason you need bluetooth, probably 3.2.x is your best bet.

Impossible to tell re: any of your other problems -> you've supplied no logs, and the solution to these problems isn't obvious ObviousMan. FCs and stuck in bootani usually means issues with your data.img. However you are starting with a clean slate and still experiencing these problems, could be that your sdcard is dying. No idea.
3rd May 2012, 09:28 PM |#694  
Junior Member
Thanks Meter: 1
 
More
I tried out GBX0C. Phone runs smoothly, camera works. Unfortunately the problem still exists that the phone loses internet connection in low signal areas (commuting by train). Sometimes it can be fixed with airplane mode on/off, but often it requires a reboot.
Let me know if logs would be of any help (but I understood this is a known bug already).

Also I had the phone freeze completely on charging twice now.

Kernel 3.3.4
Rhod 100 uk /AUO
3rd May 2012, 09:44 PM |#695  
Senior Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by detule

Bluetooth hasn't made it to 3.3.x. It's on my phone I just need to find time to run down to my car and see if pairing works fine. If for whatever reason you need bluetooth, probably 3.2.x is your best bet.

Impossible to tell re: any of your other problems -> you've supplied no logs, and the solution to these problems isn't obvious ObviousMan. FCs and stuck in bootani usually means issues with your data.img. However you are starting with a clean slate and still experiencing these problems, could be that your sdcard is dying. No idea.

Good to know that BT was not even suppose to work in 3.3.x
I tried 2 different SD cards (8gb class 4, 16gb class 10 - pretty much brand new), both formatted with HP tool. Yes, I gave up quickly and went back to 3.2 as I needed to use the phone and could not get to U/L logs.
Once 3.3.x with your BT update will make it into the build, I will try to do a proper debug if it starts going sideways. For now, sticking with 3.2.x
Thanks.
OM
5th May 2012, 05:10 AM |#696  
Member
Flag PA
Thanks Meter: 2
 
More
Quote:
Originally Posted by arrrghhh

For MMS, did you setup an APN?

FWIW, I cannot get the APN setting to save... anyone else?
5th May 2012, 11:00 AM |#697  
Member
Thanks Meter: 2
 
More
Any more people who have trouble getting the phone asleep in GBX0C? I installed LedRegime to check if the phone went to sleep, but it seems it is almost the whole time awake. Well, that explains the bad battery life...
On FRX07 the phone was a real Sleaping Beauty... Logs needed?
5th May 2012, 12:41 PM |#698  
walter79's Avatar
Recognized Developer
Flag #484047
Thanks Meter: 3,716
 
Donate to Me
More
Quote:
Originally Posted by Stijnjits

Any more people who have trouble getting the phone asleep in GBX0C? I installed LedRegime to check if the phone went to sleep, but it seems it is almost the whole time awake. Well, that explains the bad battery life...
On FRX07 the phone was a real Sleaping Beauty... Logs needed?

Use CpuSpy to check deepsleep.
5th May 2012, 01:57 PM |#699  
Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by walter79

Use CpuSpy to check deepsleep.

Hmm... CPU Spy tells me the following:
Time in state:
528MHz: 15%
245MHz: 84%
Unused CPU states:
122MHz, Deep Sleep

So it does seem that the phone doesn't go to sleep...
Logs are here
5th May 2012, 03:17 PM |#700  
Senior Member
Thanks Meter: 667
 
More
Quote:
Originally Posted by Stijnjits

Any more people who have trouble getting the phone asleep in GBX0C? I installed LedRegime to check if the phone went to sleep, but it seems it is almost the whole time awake. Well, that explains the bad battery life...
On FRX07 the phone was a real Sleaping Beauty... Logs needed?

I was having similar issues getting the phone to enter deep sleep, and after a day of testing it became apparent that my rhod100 wouldn't sleep if wifi was set to on, regardless of the wifi sleep policy (ie. When Screen Off). If I manually toggle wifi and then turn the screen off the device would sleep almost immediately. Sooo this was good to know but not good news as I don't use data and need wifi for everything. But I installed a program from the market called GreenPower free which can override androids inbuilt sleep policy for wifi and control when the wifi sleeps and wakes (and can control syncing schedule and data connection - haven't tested the latter)
For me after setting up GreenPower the way I wanted my phone now goes to sleep (deep sleep, xdaledregime green light) within minutes of turning the screen off and stays that way until wifi comes on after 1 hour and stays on for 2 min for sync, etc then deep sleeps again, and repeat!

The other day I was getting about 5 hours of screen off before battery died now I just got 13 hours of light to moderate usage and some periods of deep sleep on an incomplete charge (about 1.5 hours) from within Android.

This is on the latest kernel 3.3.4 (may 1) and latest bundle GB0XC (may 3), I don't know if this problem was unique to my device or if it may be similar to problems that others are experiencing but hopefully this helps some of you out like it has me.

As of now this old beauty just got a new lease on life as this is the first time I have found an Android build for the rhodium that can last a day off the juice.

Huge thanks to ALL the developers involved in XDAndroid and specifically to Detule and Arrrghhh for all their work on the MSM72whatever branch of the project!
5th May 2012, 04:30 PM |#701  
fortunz's Avatar
Senior Member
Flag inside
Thanks Meter: 105
 
More
Quote:
Originally Posted by Stijnjits

Any more people who have trouble getting the phone asleep in GBX0C? I installed LedRegime to check if the phone went to sleep, but it seems it is almost the whole time awake. Well, that explains the bad battery life...
On FRX07 the phone was a real Sleaping Beauty... Logs needed?

I still haven't installed GBX0C, but I had sleep problems in GBX0B with the bundled .27 kernel. Have you tried any .39+ kernels? Bear in mind, there are different xdaledregimes, the original apk doesn't work with the new kernel, so to see if it does indeed sleep, you need to install the right one with the right kernel.

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes