Quote:
Originally Posted by Recursion
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.
|
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