Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

Go thru what you disabled... I hope you wrote it down or somehow kept track of it.

If you didn't, then you might have to start over. I completely hosed it the first time and disabled way too much, and of course didn't document it. I hope you backed up your data.img! I at least did that, so reverting was easy :p.

Cool.

As for battery life, without any usage!?!? Do you have GPS on? That shouldn't kill sleep anymore, but perhaps it is for you? I'm not sure what would cause such horrible battery life - my battery is by no means new, and I usually get 10 hours with very little usage. 5-6 with moderate usage.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

GPS is off.. I really need to get this battery issue fixed.. on WM, i get all day..

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

For the physical kb, when I type (i.e. "i", "n", etc) I get a pop up with suggestions; how do i turn that thing off, it's annoying and waits for me to press back-key.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

Have you tried any different kernels? Last I checked .39 produced very good battery life results.

Other than that, I guess try to reduce the number of apps that are syncing constantly, and turn off data when not in use.

This happens when you hold the button. I've had it pop up a few times, just hit the X button. I don't think there's a way to disable it without hacking userland - it's an Android feature.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

One other thing, I made a call to cell from another phone, it takes a while for the incoming call to show up on the TP2, is this a known issue? Thankx

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

To say it's well known is an understatement.

Seems to be a uniquely CDMA problem. No foreseeable solution, considering the guy who rewrote the RIL did so for CDMA completely blind.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

what does the error, Android.process.Acore unexpectedly stopped working mean?
it only gives me a force close option and the message box shows up shortly again after i tell it to force close. i did some searching on the interwebs and found that many people that run into this error have edited the contacts and the screen resolution or something of the sort. for the people with regular android phones they can reset the phone or delete the last few apps that were downloaded, but i havent used my phone for anything in the last 48 hours except a few calls. so do i need to format my sd card and start all over from the begining.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

Nah, this issue is a confusing one. I believe it's due to permissions getting hosed (or some other data.img corruption? Usually from a bad/sudden shutdown).

You can either try and do the fix_permissions.sh script from Cyanogen, or just create a new data.img.

This is basically starting from square one tho - so make sure you have a backup of your apps/data.

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

ok thank you and by chance how do i prevent this from happening again

and you are right i did have an issue with the screen not coming back on so i popped the battery out and this would have caused this as what you said, but the only reason i did it was because the screen wont unlock when the battery gets really hot, so how do i fix this? if there is a fix

Re: [TESTING] XDAndroid GBX0B 2.3.7 Build
 

Well patience is always a virtue when using this project. I always make DAMNED sure the phone is truly dead - try hitting power many, many times (but not all in a row!). Wait. Try swiping where the unlock "should" be after hitting power. Try plugging in USB, see if you can get into adb... etc.

Not really a fix for SoD's, we just need to figure out why they happen and write better code :D.

As for prevention, I think you know - the less sudden shutoffs, the better. I'm also considering doing some guides on how to make dedicated partitions and use ext4 - supposedly it helps with issues like this. Journaled FS on a SD card seems dumb, but a lot of people said it helps.