Quote:
Originally Posted by Recursion
1. Previous bullshit content ignored. Not the place for it, this thread is for "testing," not for fine-tuning a working product. I'm pretty damn sure the first post spells this out pretty clearly. Anyhow....back on topic:
2. ndno, is that all you did? Hmmm...
3. Had another crash last night, fresh boot, untouched...crashed about 10 mins later. Was a completely fresh FRX05 folder w/ 3.11 kernel. Notably, when I copied fresh FRX05 folder to SD, I had connected phone (as Disk Drive) to Win 7 machine under Vindows latest Titanium build, W7 checked SD Card for errors and "fixed" them. This may have something to do with it? Gonna reformat Fat32 & do a virgin run.
4. Regarding battery issues, what do you all think about the battery code possibly overcharging? I don't think these batteries have on-board ICs to control charging; I'm thinking the battery code oversees charging. My reasoning is simply because the batteries get so &@#$ hot when charging under XDAndroid. Charging under WinMo never gets that hot. And not to freak anyone out, but my prior battery that was performing like a champ lost its ballz after I charged under XDAndroid all night. Next morning the battery was hot as $41t. Under Vindows, the performance loss was very noticeable. Popped in a new battery, and feeling the Vindows love again.
If (I'm totally off-base)
Then (Don't serve me anymore alcohol)
Else (We may want to avoid, or at least drastically limit, charging under XDAndroid until there's some clarity on this topic.)
Hell, my battery could've been ready to die (it was a year old, but ballzy as hell).  |
Quote:
Originally Posted by ndno
Yeah, if you're using setcpu, un-install it; it's probably causing instabilities messing around with the system clock.
Yeah, I'm worried about charging under android also; I had a few times in which my tp2 didn't go to sleep (an app or process probably running in background) and I left it charging overnight; next tomorrow, it was sizzling. I don't think the battery driver is working quite right under android yet; maybe the battery is fully charged in reality but the driver thinks it's not full yet and continues to allow the charging to go on, causing overheating. Overheat for long period = shorter battery life.
Sent from my FRX05-ized TP2
|
Battery charging is not correct in Android, for sure.
I heard there's two methods for charging - fast and slow. Basically the way it is supposed to work, is it is supposed to fast charge up to a certain %, then trickle charge the rest - I have a feeling it's constantly fast charging, so when it hits that certain % it just keeps on going... and never ramps itself down.
I'm thinking with the new batt code they're going to address this, but there is a lot the devs are throwing around.
I never charge in Android overnight, as it does get ridiculously hot in Android when charging for long periods.
Don't know if this is better or worse for the battery, but I leave it overnight to see how deep sleep drain is, then I charge it at my desk while tethering USB. Phone still gets hot as heck, but it's also tethering while charging - not saying this is the right way to do it, but I've done this for a couple of months now and haven't had any significant battery-related problems.
However, as far as batteries affecting performance? I highly doubt it, but I guess stranger things have happened...
As for the crashes, that is confusing. It almost has to be the new battery code... but why isn't everyone having those crashes? Hmmm. I'll have to do some more investigation on this.