• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Huge battery drain issues

I've never had great luck with my battery life but most of the time I can make it from 6AM to 10PM without completely dying (though sometimes it's been close).

A typical day's use:
* 10-50 message sent (text/google talk)
* 1 or two short calls on average
* 30-45 minutes of browser / facebook app
* 30 min. music, usually Pandora on 3G
* 2 email accounts, 1 gmail, 1 stock mail app, checked on the hour

There will occasionally be some use of maps or navigation but not often for more than a half hour.

GPS and wifi are on only when I'm using them, which is rarely. Bluetooth and auto-sync are never on.

I had skype installed when I was on harmonia 1.2, but haven't installed it on AOSP CM7, latest available on Rom Manager.

I installed the ROM last night, unplugged at 7:30 AM with a full charge, and by 2:50PM I am down to 39%. I have installed a few things today - swype, setcpu (uninstalled now), gtalk, facebook, gmail, done a little chatting and web browsing, 15 minutes worth of navigation, and that's about it.

My cpu is set (using cyanogenmod options) to min 320, max 729MHz, conservative.

I'm so frustrated because I had heard that this was one of the best ROMs for battery life so I was hoping someone might be able to point out something I'm doing that's causing this kind of poor performance. This is significantly worse even than the stock phone with all the VM crap on it.
 
Did the increase in battery drain happen after you overclocked your phone? That might be the problem, or at least part of it. The faster you have it running, the more battery is uses. I recommend installing setcpu again (you did pay for it after all so might as well use it, right?) and make a couple of profiles based on your preferences. For example I have a profile for when the screen is off, the phone only runs 122 min, 245 max conservative. That way I don't have a whole lot of drain when I'm not using the phone.
 
Actually, testing has proven that underclocking can increase battery drain. Since most apps only use the CPU intermittently, if they require a higher CPU than the minimum set, more power is used ramping up the speed. Here are a couple of discussions about it:
http://forum.androidcentral.com/vir...71693-optimizing-battery-drain-optimus-v.html
http://forum.androidcentral.com/opt...attery-drain-optimization-tests-part-2-a.html

Check your battery usage under settings>>about phone>>battery usage to see what parts of the system are using the most juice. From that screen, you can click on the graph to get more details about the main battery hogs, ie phone signal, wifi, gps, awake, screen on. The two worst battery drains are wifi and a poor phone signal. You can see the quality of the phone signal under the battery usage graph (after clicking on the first graph). Green is good, yellow is bad. The poorer the signal, the more the phone tries searching for a better one.

I had a similar day to yours as far as usage on my phone goes, in fact I used mine more than you stated, here's my battery life today:
ScreenShot-5-2.png
 
I installed the ROM last night, unplugged at 7:30 AM with a full charge, and by 2:50PM I am down to 39%. I have installed a few things today - swype, setcpu (uninstalled now), gtalk, facebook, gmail, done a little chatting and web browsing, 15 minutes worth of navigation, and that's about it.

These things (especially Navigation) will eat up battery fairly quickly. But it shouldn't be causing that much drain.

As Jerry mentioned, underclocking can actually be bad for the battery. I would up it to at least 480mhz. I keep mine at 600mhz, although I have a SetCPU profile set to go down to 480 when the screen is off. My battery does just fine.
 
I don't now if this will help:JerryScript mentioned a fix for the time without service problem that causes battery drain that was discussed in a previous thread. He said to toggle airplane mode on for 20-30seconds at boot up,then turn off. Don't know if this is your problem but it can't hurt to try.
 
Back
Top Bottom