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

[ndno]

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

[arrrghhh]

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

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.

[rpierce99]

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.

[ffkip911]

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

[arrrghhh]

Originally Posted by rpierce99

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.

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 .

[rpierce99]

Originally Posted by arrrghhh

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 .

It's a 1A AC charger, but as I said in IRC i'm not really sure if it pairs at 1A because it's not necessarily a matched charger for the phone.

[Recursion]

Originally Posted by ndno

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

Sounds like battery code is trickle charging when that happens.

Originally Posted by ffkip911

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

noob alert!! auto kill? is that an app, or built into the OS?

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.

Don't have setcpu installed.
Arrrghh's note regarding battery code acting nutty sounds like the issue. Forgot to mention that my battery was actually slightly warped after it got hot. So yeah, I'm only gonna charge under android between 0 and 70% just to be safe.

Originally Posted by arrrghhh

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.

Sounds like that's it, bro. Fast v. trickle charging problem. Nomo overnight charging for me...0-70% is it.
Not what I meant by "battery performance." I meant how strongly (long) the battery holds its charge under load. New battery under Vindows stays at 100% unused for 4-5 hours with new battery.

Originally Posted by ffkip911

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

Thanks for the checking, bro. I'm thinking the code isn't properly picking charging mode. It might be that apps, data usage, etc. might be mucking up the state determination, or maybe the logic may be wrong in the first place. I'm sure it'll get fixed up sooner than later, since that's a pretty important part of the OS.

Originally Posted by arrrghhh

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 .

I wouldn't doubt that it does. The less ballzy charging source would definitely make a difference. So yeah, drawing some of the current for other tasks (data) would pull down the amps fed to battery charging.

Ahhh...on topic is nice.

[ffkip911]

temp got up to 103 and stayed----charging indicator on both taskbar and on my sense clock stopped showing charging (showing 100%)

trying to see if I can get this hotter. (103 is warm---nothing like tethering)

[ffkip911]

I think autokill is installed (set it up to kill aps on sleep--usually get back to at least 75-85 mb free)) quickboost (dl from market) is a quick mem free up tool. also, HTC sense clock (DL from market) with settings ---sense flip clock but displays outside temp, batti temp, free mem, storage mem, and batti charge

I did have my PP set to 14 and running Vin's titanium---WM gives me 108 free, android gives me 100 at boot, then drops to 75 when it's done caching (aloqa, vlingo, live wallpaper, google talk)


ohhhhh.......................charged to 100%, unpluged, pluged back in....batti at 100% and temp is FALLING!!!!!!!!!!!!! 99degrees now in 5 min

[gtmethod3]

I've been using android 100% of the time on my phone since September 2010 with the same battery my phone came with and have't had a single battery problem except the occasional failed charge.

The only times where I notice the battery is getting warm is:
1. Orange LED SOD (thing is on fire) not plugged in
2. using the device a bunch
3. using device while plugged in

I almost always use AC charging with the standard HTC chargers (TP1 and TP2). I have not noticed much increased heat while charging. Again this is the same battery I've been using since the beginning. For me, it is safe to say android hasn't affected my battery at all.

I have not ever had any heat problems with the TP2. The thing can get pretty warm sometimes, but nothing close to hazardous to me or the components. I remember the days where my TP1 would overheat and refuse to charge. Design flaw!