View Single Post
  #467 (permalink)  
Old 03-14-2011, 07:59 PM
Recursion's Avatar
Recursion
Rockin' the Red!!
Offline
 
Join Date: Mar 2008
Posts: 858
Reputation: 2330
Recursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIPRecursion is a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] Updated 3/11/11 New Kernel - TONS of changes!!

Quote:
Originally Posted by ndno View Post
***
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.
Quote:
Originally Posted by ffkip911 View Post
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?
Quote:
Originally Posted by ndno View Post
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.
Quote:
Originally Posted by arrrghhh View Post
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.
Quote:
Originally Posted by ffkip911 View Post
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.
Quote:
Originally Posted by arrrghhh View Post
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.
__________________


Reply With Quote