over heating and weak battery issue

[r1nstang]

Heres what I'm running. Simply stunning v2.2 ESE53
with kernal 2.6.29 low voltage 7 slot
I run the helixlauncher.

I charge my phone all night. it shows 100% when i unplug it. I leave for work i put it on vibrate and leave it in the car ...its 3am so its not hot nor is it freezing. I get back out to my car at about 8am...and its already down to 80%. screen wasnt on. no calls or messages. K9 email polls every 30 minutes.
by noon after texting a little bit maybe using adilko reader for 30 minutes. Im down to 40% battery.

I can plug it in. kill all processes and let it sit and it will charge up. Unplug it and just sitting there it seems to get up to 100 degrees F without doing anything.

Set CPU is set at on profiles.
charging 250max 125 min
sleep 250 max 125 min
power 1100 max 250 min
failsafe--battery 53.7C 1100max 125 min

I know the moto droid doesnt have the greatest battery life. but it seems like its been better then this before. Should I wipe the cache a few times and use a nandroid backup?

think for lack of a better term...the system just got clogged up??

Thanks for the help

[mjh68]

Heres what I'm running. Simply stunning v2.2 ESE53
with kernal 2.6.29 low voltage 7 slot
I run the helixlauncher.

I charge my phone all night. it shows 100% when i unplug it. I leave for work i put it on vibrate and leave it in the car ...its 3am so its not hot nor is it freezing. I get back out to my car at about 8am...and its already down to 80%. screen wasnt on. no calls or messages. K9 email polls every 30 minutes.
by noon after texting a little bit maybe using adilko reader for 30 minutes. Im down to 40% battery.

I can plug it in. kill all processes and let it sit and it will charge up. Unplug it and just sitting there it seems to get up to 100 degrees F without doing anything.

Set CPU is set at on profiles.
charging 250max 125 min
sleep 250 max 125 min
power 1100 max 250 min
failsafe--battery 53.7C 1100max 125 min

I know the moto droid doesnt have the greatest battery life. but it seems like its been better then this before. Should I wipe the cache a few times and use a nandroid backup?

think for lack of a better term...the system just got clogged up??

Thanks for the help

Not sure, but since I have been reading different developer's forums all night..work night shift I have seen similar posts on Koush's , Bugless forums and Some are starting to believe it is the SetCPU latest update. For sure the active widget for SetCPU is burning up juice , but even without using it people are noticing more heat and worse battery life.
I have run Chevy's , Bugless, and Koush' roms this past week and they all ran smooth , but did have battery issues. I just uninstalled SetCPU and redownloaded the version prior to the last update 1.5.1a so I will see if that gives me better battery life.

Sure seems that SetCPU is the most common element between the different roms.

[r1nstang]

hmm ill definiately give that a shot myself

[Desh]

put me in the camp that believes the poor battery life and over heating are b/c of SetCPU. Looking for a fix.......

[r1nstang]

got rid of setCPU and phones fine now. battery life is still kinda lacking...but thats always been an issue with the droid. but its not at melting temps while idle any more haha.

[GameBoiye]

Latest version of setcpu fixes the issue.

[gatewayad]

Latest version of setcpu fixes the issue.

It might take care of the heat issue but the battery drain issue. Losing 10% an hour not doing anything on the phone, wasnt like that that before the last couple SetCPU updates. I'm going to delete it and see how it goes for a couple days. Hope I can handle the lack of speed

[Desh]

i too was noticing the 10%/hr battery life, but have since setcpu to max 550, and things seem to be perfectly fact, and more than doubled the battery life.

[mdbray]

I would check and see what "Governor" you are using. The OnDemand (at least prior to 1.5.3a) governor would send the CPU from 125mhz to 1000mhz for no apparent reason. I didn't see any reason for the CPU to be jumping to max if it's idling and all processes have been cut. I have been giving "Conservative" a try and it seems to do a lot better about being more deliberate in ramping the CPU up (i.e. not as hyperactive) without sacrificing performance (sometimes when waking the phone it lags for a second but then it gets to work). I'll be watching battery life over the next few days.

[mikeofmikes83]

Juice defender really helped my battery life as did a low voltage kernel.

I also only run at high speed when I'm doing something that could use the higher speed; generally I stay at around 900mhz, which also really helps my battery life. An auto task killer helped a lot too. And as others mentioned, check your usage in setcpu, I find that conservative really helps.

Quick question, why would you want your phone's processor at 1.1ghz as a fail safe? I have mine set to 125 max/min at 47c