[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix! - Page 68

steveholtam · #**671** (**permalink**) 04-18-2011, 05:31 PM

I've not had a corrupted data.img file in a long time. Are you jumping from build to build and trying to reuse yours? Unless your just doing these incremental updates from Wistilt, I would pretty much start from scratch with a new data.img file.

If you are saying that you are getting a corrupt file on the same build, I would suspect your sd card.

**arrrghhh** · #**672** (**permalink**) 04-18-2011, 05:56 PM

Yea, I very rarely have to blast out my data.img - and I've actually had a few instances where it wasn't necessary.

The theory is cache gets hosed, or there's some database that gets hung. Just depends on what it is, and what the phone is doing - I've had some that the whole system just FC'd on everything, and it was just a bad/corrupt contacts db.

Hopefully the data.img issues will at least be mitigated on NAND, if not disappear entirely - on partitioned SD card builds, I think the issue has gone away.

**Recursion** · #**673** (**permalink**) 04-18-2011, 08:34 PM

Quote:

Originally Posted by arrrghhh

Yea, I very rarely have to blast out my data.img - and I've actually had a few instances where it wasn't necessary.

The theory is cache gets hosed, or there's some database that gets hung. Just depends on what it is, and what the phone is doing - I've had some that the whole system just FC'd on everything, and it was just a bad/corrupt contacts db.

Hopefully the data.img issues will at least be mitigated on NAND, if not disappear entirely - on partitioned SD card builds, I think the issue has gone away.

It's happened once (definitely), and the second time (just recently), I had some sluggishness rear its head every so often, so I just started from scratch & the problem went away. I probably installed something from market that didn't sit right.

Yeah, I'm hoping the same thing...mitigated or corrected. I'm gonna try NAND this weekend when my time frees up more. Damn work.

albumleaf · #**674** (**permalink**) 04-22-2011, 01:23 AM

Arrrghhh, I tracked down my previous issues with the old kernel, it was simply the battery reading too high and my overclock destabilizing things. I have had ONE random reboot over the past three days with heavy usage. Great work everyone!

Gremlin75 · #**675** (**permalink**) 05-03-2011, 04:09 PM

Just wanted to post my two cents - been running the SCBS kernel for a couple of weeks now, and everything works great! Seems like the battery meter is more accurate - but still have shorter cycle time between charges than WinMo (but that doesn't bother me!).

One question - when you analyze the logs, is it a good idea to always select ALL of the logs? I've got about 12 or so of them, which makes the analysis process lengthy - if it results in a better outcome, that's fine. Just curious about it.

Gremlin

**arrrghhh** · #**676** (**permalink**) 05-03-2011, 07:40 PM

Quote:

Originally Posted by Gremlin75

Just wanted to post my two cents - been running the SCBS kernel for a couple of weeks now, and everything works great! Seems like the battery meter is more accurate - but still have shorter cycle time between charges than WinMo (but that doesn't bother me!).

One question - when you analyze the logs, is it a good idea to always select ALL of the logs? I've got about 12 or so of them, which makes the analysis process lengthy - if it results in a better outcome, that's fine. Just curious about it.

Gremlin

Yes, the more data used to calc the algo, the more accurate the algo should be - you might not need to use all 12 logs, but the wider types of drain you have the better.

What I mean by 'wider types of drain' is fast drain from watching videos, slow drain from deep sleep, low battery levels (less than 20%) high battery levels, etc. The more variance, the better the algo will be.

Obviously the more data the app has to churn thru, the longer it will take to calc an algo.

shadowlaos · #**677** (**permalink**) 05-03-2011, 09:00 PM

which startup txt is good for the regular tp2? i don't have it unlock yet

**arrrghhh** · #**678** (**permalink**) 05-03-2011, 09:05 PM

Quote:

Originally Posted by shadowlaos

which startup txt is good for the regular tp2? i don't have it unlock yet

What does this have to do with the testing kernel?

Follow the build thread, that and the FAQ show you how to figure out which phone you have. I can almost guarantee you have a RHOD400.

So... use the startup for the RHOD400.

Also, you don't need to HSPL (unlock) to run Android. Currently it runs off the SD card, so there's no flashing involved.

Please, in the future, post in the correct thread.

shadowlaos · #**679** (**permalink**) 05-03-2011, 09:14 PM

Ok thanks
how do you turn off the orange led light?

**arrrghhh** · #**680** (**permalink**) 05-04-2011, 09:04 AM

Quote:

Originally Posted by shadowlaos

Ok thanks
how do you turn off the orange led light?

You don't.

Orange LED = full wake

Solid Green LED = full sleep

Blinking Green LED = wakelock present (something preventing the device from sleeping, like GPS).

If we ever reach the point where all sleep-related issues are resolved, then the LED can be reclaimed for notifications.