Originally Posted by Recursion (Post 2068508)

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.

Originally Posted by Recursion (Post 2068508)

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). :dontknow:

Originally Posted by ndno (Post 2068525)

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

Originally Posted by rpierce99 (Post 2068571)

I charge overnight every night and have had no issues. I don't even find it to be hot when I pick it up in the morning.

Originally Posted by arrrghhh (Post 2068581)

Interesting - do you charge off USB or AC? Also, do you know what mA your charger is running at?

I'm curious if that effects it. I haven't charged my phone overnight in Android really ever, but when I used to charge for a few hours it would get pretty hot. Now I just charge at work when tethering, so of course it's going to get hot :p.

Originally Posted by ndno (Post 2068399)

***
Is it just me or does it seem like charging under Android is very very slow? :scratch:

Originally Posted by ffkip911 (Post 2068514)

auto kill seems to actually work when phone goes nighty-night---getting lots of free mem on wake-up -- upwards of 90mb free

been on for a whopping 5 min, will test for the rest of the day

@Recursion...will check batti temp on/off charger on/off data....give me a few hours to get numbers

baseline: off charger, no data 80.5 degrees (ambient is 70) batti showing 100% charge---plugged in with NO charge icon in taskbar OR sense clock (with data--temp, SD mem, HD mem)

plug in usb with screen off--batti still at 100% waiting 5 min.

time's up and with screen off/phone sleep, plugged into usb----no temp change.

You may be pulling data (google sync????) check mem usage

Originally Posted by ndno (Post 2068525)

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.

Originally Posted by arrrghhh (Post 2068556)

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.

Originally Posted by ffkip911 (Post 2068572)

off usb for 2 hours, push email, media, aloqa (pulling data), vlingo (pulling data)---batti to 84% and verified against WM.

again, off usb for 2 hours and batti temp is 80 degrees---charging now...will check temp in 1 hour

Originally Posted by arrrghhh (Post 2068581)

Interesting - do you charge off USB or AC? Also, do you know what mA your charger is running at?

I'm curious if that effects it. I haven't charged my phone overnight in Android really ever, but when I used to charge for a few hours it would get pretty hot. Now I just charge at work when tethering, so of course it's going to get hot :p.