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

Froyo Update Not Worth It- Battery life problem

I was having this problem with the 2.2 as well. Last night, I installed Juicedefender and rolled back Google Maps to the previous version, since I noticed internet chatter saying it was hogging too much battery. My battery life has been much better today--at least as good as it was on 2.1. Tomorrow, I plan to update Maps (since I do like some of the new features) and see if Juicedefender alone is enough to do the trick.

Hope this info helps someone!
 
I am a novice user (no root, etc) but have owned the original droid for about 10 months. Never had battery problems until the update, then battery wouldn't last more than 4-5 hours. Disabled task killer and problems seem to have vanished. Even with task killer on, apps seemed to re-start second after they were killed. It is possible the "killing" and restarting were using the juice. Maybe?
 
This is so weird. A guy at work has this same problem -- his Droid1 battery was only lasting 4-5 hours. He just got the update yesterday.

On the other hand, I got my update yesterday, too, and my battery seems to be lasting longer than normal. I never use Facebook or Twitter on my Droid1, I leave Wi-Fi off all day (except when I do a manual update of things at work), and I never surf the web. But that's the way I used it before the update, too.

I also turned off "all animations" in Settings, and my Droid1 seems a LOT snappier than ever, and that's even running Launcher Pro.
 
Using 2.1 I've never run out of power during the day. Since my upgrade I have to charge mid-day to make it through the day. Battery use says display, phone idle and cell standby account for the vast majority of the usage. I have turned down screen brightness and I'm experimenting with other settings to solve the one nagging issue.:confused:
 
What does animations do anyway? What's getting animated or not...?

I just tested a few time with and without. What I see is with animation on switching screen to another app. opening apps. etc it smooth transition. With it off it Just snaps open.
Gonna leave mine off just to see what happens...
 
Can it be apps re-syncing after the update?
I would turn everything off; GPS, WiFi, BlueTooth, Automatic Syncing, ect, and then systematically turn each one on after 8 hours or so each to try to get a pattern.
Unfortunately I think the Battery Use detail is missing too many features that run in the background.
I find it hard to believe that the new release is a battery hog by default. It's gotta be something specific.
 
What everyone reading and replying to this thread needs to remember is this:

Not only are our DROIDs not 100% identical, because of the apps that we install even DROIDs that are very very close to identical are going to exhibit different issues when compared side by side.

That being said, those of you that installed the update normally should really try grabbing the "Master Update" from Peter Alfonso and installing it on your phone to see if it makes a difference. However, before going that drastic, there are a couple of things you need to realize.

  1. If you use a task killer that automatically kills tasks that you do not want running, and those tasks keep reloading themselves into memory, YOU'RE KILLING YOUR BATTERY YOURSELF!!!! The rationale is that as you kill a task, the system works to remove it from memory, which means that it then performs the tasks it always does when it kills a task - which requires electricity to do. Then the task automatically loads back into memory - requiring more electricity to do so. Repeat, ad nauseum.
  2. If you have apps that are not fully 2.2 compliant, or apps that were installed under 2.1, and may need to be uninstalled and reinstalled under 2.2, then they could adversely affect your experience again, In such a case I always recommend folks hat updated to 2.2 to perform a factory Reset when experiencing odd issues, including battery life degradation.
  3. Some apps out there will suck battery - and with FroYo's slight overclock as well as the JIT that is now stable and enabled in 2.2, you have to expect some battery degradation. judicious use of your phone and manipulation of your settings will help overcome this problem pretty effectively.

So, in short:

First, stop auto killing tasks!!!!

Next, try a factory reset first and see if it helps.

Finally, if it doesn't help (or not enough to your liking) then use the master 2.2 update from Pete's site to update your phone to 2.2 again, using all new files as opposed to the patched process.

HTH
 
I see all the post about ATK being bad and how wonderful the droid manages apps. That is BS! the droid allows to many unneeded apps to run in the back ground. One area the Iphone kills the droid. I do agree that killing apps and then the apps starting back up does kill the battery, but if the droid would not run so many dang apps at once we would not have half the issues. Funny, the droid starts to lag after a while, I open ATK and it has a bunch of crap running on its own that doesn't need to be, and memory is down to 30. I kill some apps, and the phone is as fast as can be. But to the topic of this thread my phone list the display a lot higher than what it was before 2.2
 
As for the apps that run in the background, if they continually restart then killing them don't give you jack, b/c for the temporary time that it frees memory and you can 'do things' is eventually killed again by those same apps.

You're better off rooting your phone and manually removing those apps completely so they don't autostart. And I did not say manually I said automatic killing specifically.

If they are apps that you have installed yourself, then perhaps you need to evaluate if those apps are worth having - why have an app for, say, sports, when you can always jump on the browser and check sports in real time from any of a number of sports websites?

Also, if you are not using automatic brightness, it is gonna kill the battery pretty quickly too.

I have my phone overclocked to 1200 MHz (50% higher than stock FroYo, and over 100% over the older 2.0/2.0.1/2.1 speeds) running all the time until the battery drains too far (~30%) and I get a full day's use out of my phone. I also have 175+ applications that I have installed in addition to the ones that come with the phone - so you can't tell me that my advice is BS.
 
Johnlgalt you are a big contributor to this forum and your advise is usually spot on. I agree with everything you said except for the bit about auto brigjtness. Certainly you could agree that running on the lowest brightness setting is clearly more battery efficient than running on auto. Auto brightness will regulate the screens brightness of course, but keeping it on low all the time is clearly more efficient than having it waiver higher or lower.

That said I would really like to figure out what is killing my juice. I have already factory reset and baterry pulled. I do not use a task killer (seriously folks are why are we still having this debate? You don't need one!), and I am very scrupulous about monitoring my baterry by using both the battery usage screen and the battery history screen (which is hidden - you need to use an app like battery left widget to see it). Nothing is different about my usage and no program is going crazy and my battery still lasts almost half as long as before. This is ridiculous.

The battery history screen is different from the usage screen which tells you percent of usage. The history screen tells you how long your phone has been running since unplugged, how long wifi and Bt have been running, your partial wake time and what apps have woken the phone from sleep and for how long, what apps use the sensor and for how long, what apps use gps and for how long, what apps have used the network and for how long, and cpu usage by app. I advise all of you to get an app like battery left widget or battery history or better cut (which will let you make the shortcut to the battery history which is just in android but hidden). I have found many a battery offender this way and learned plenty of qualitative info about my usage with it. You all should do this to see if you have an going nuts.

That said, what the heck is wrong with MY battery cause maps is not running rampant in my phone (no app is) and my battery still sucks. Any more tips? I'm still within a year I may need to swap this thing out. Maybe the update revealed a broken sensor or something.
 
I also have battery issues...what i did was let the battery totally drain and then charged it up. I read somewhere this calibrates the battery...after 1 day of doing this it has seemed to work as from midday to 9pm i only lost 30% and I used it for music, emails, text, etc. It is worth a try!
 
I know from building a few laptops that they would often need to run "Battery Learning" calibration software to interact with the regulating chip in the Li-Ion battery.
Just wondering if maybe the 2.2 update reuires a battery pull or something to recalibrate the battery discharge/charge rate?
A shot in the dark, piss in the wind, grasping at straws, whatever you wanna call it....LOL
I've encountered freakiness with the Droid apparently not even recognizing the battery when installing kernels it didn't like.
 
just got home from work 15h 7m with 40% pretty much same settings as posted yesterday morning..

Something me and a fellow working were talking about.
My LG Decoy would barely make it through the nights when I was doing 8hr shifts, pretty much just texting and internet browsing (if you wanna call it that on that lame web browser). His phone kinda like the ENVY touch but ATT version makes it through the 12 hr shift barely, if he gets on the internet he says it's gone in 1hr..

So I find myself lucky to have such a high tech device and getting 15hrs+.

I know that if I run GPS, play movies, search the internet etc.. that I would not get 15hrs straight and still have 40%..
 
OK. So when I first force updated to 2.2 FRG01B my battery life sucked terribly. I did a factory reset and it seemed that after a week my battery was performing the same way it always had. I also wanted to see if Juice Defender would help and the day I ran it I lost 2 to 3 hours of battery life. Uninstall!

I have also found that Verizon says the Droid Battery is out of stock and unavailable but the Droid 2 uses the exact same battery. They also now offer an extended life battery for the D2. I among several others have purchased this which comes with a different battery door to make the slightly thicker BP7X battery fit. This is day one running the larger battery. I was getting 11-12 hours on stock battery with Froyo. Go to this forum to read more and see pictures: Droid 1/2 Extended Battery - Droid Forum - Verizon Droid & the Motorola Droid Forum
 
Already did the full discharge cycle business twice now. No luck there. I will give it a few more days of tinkering things and then it's going back.

As for the extended battery, Seidio also makes an extended battery for the Droid, with a replacement door. It probably is more pricier than the verizon one though, it's like $70. It's either 2600 mAh or 2800 mAh, i can't remember.

My battery life is about 11-12 hours now, and that is with me using the phone for about 15 minutes every hour (running 25% of the time since unplugged). Before the update, this same usage landed me about 18-20 hours. I could certainly make it from 6:30 am to 11pm on a single charge and end the night around 20%.
 
Already did the full discharge cycle business twice now. No luck there. I will give it a few more days of tinkering things and then it's going back.

As for the extended battery, Seidio also makes an extended battery for the Droid, with a replacement door. It probably is more pricier than the verizon one though, it's like $70. It's either 2600 mAh or 2800 mAh, i can't remember.

My battery life is about 11-12 hours now, and that is with me using the phone for about 15 minutes every hour (running 25% of the time since unplugged). Before the update, this same usage landed me about 18-20 hours. I could certainly make it from 6:30 am to 11pm on a single charge and end the night around 20%.

The Seidio case apparently adds like a half inch to the thickness of your phone or something like that. The D2 extended battery adds like a millimeter.
 
Some apps out there will suck battery - and with FroYo's slight overclock as well as the JIT that is now stable and enabled in 2.2, you have to expect some battery degradation. judicious use of your phone and manipulation of your settings will help overcome this problem pretty effectively.

Errr... Just-In-Time compilation should IMPROVE battery life, as it takes less CPU than direct interpretation. (The next thing would be static precompilation, but I digress.) However, it can make a CPU-bound program make the CPU use more power per clock cycle due to increased die utilization; that may be what you're getting at.
 
Johnlgalt you are a big contributor to this forum and your advise is usually spot on. I agree with everything you said except for the bit about auto brigjtness. Certainly you could agree that running on the lowest brightness setting is clearly more battery efficient than running on auto. Auto brightness will regulate the screens brightness of course, but keeping it on low all the time is clearly more efficient than having it waiver higher or lower.

That said I would really like to figure out what is killing my juice. I have already factory reset and baterry pulled. I do not use a task killer (seriously folks are why are we still having this debate? You don't need one!), and I am very scrupulous about monitoring my baterry by using both the battery usage screen and the battery history screen (which is hidden - you need to use an app like battery left widget to see it). Nothing is different about my usage and no program is going crazy and my battery still lasts almost half as long as before. This is ridiculous.

The battery history screen is different from the usage screen which tells you percent of usage. The history screen tells you how long your phone has been running since unplugged, how long wifi and Bt have been running, your partial wake time and what apps have woken the phone from sleep and for how long, what apps use the sensor and for how long, what apps use gps and for how long, what apps have used the network and for how long, and cpu usage by app. I advise all of you to get an app like battery left widget or battery history or better cut (which will let you make the shortcut to the battery history which is just in android but hidden). I have found many a battery offender this way and learned plenty of qualitative info about my usage with it. You all should do this to see if you have an going nuts.

That said, what the heck is wrong with MY battery cause maps is not running rampant in my phone (no app is) and my battery still sucks. Any more tips? I'm still within a year I may need to swap this thing out. Maybe the update revealed a broken sensor or something.

If you keep the brightness at dim all the time it will definitely use less battery, but I ma actually referring to people who don't do completely dim / auto brightness, and leave their phone's display medium to high brightness all the time.

Furthermore, again, the kernel with FroYo is Overclocked to 800 MHz - as opposed to the stock 550 in previous stock ROMs. No matter what your battery is not going to perform as well if you have things like sync, GPS, etc. running all the time.

I have seen claims that FroYo is better at battery management but I can say this after running FroYo for 3 months - it has given me no better, but no worse, results.

Another thing, and especially for those of us who have had our DROIDs for a very long time - LiON batteries have a (reported) 250 charge cycle before they start exhibiting issues with such things as battery not charging fully or lasting as long. I have had my DROID since day 1 - and even before I went to FroYo I was not getting great battery life from when I first got the phone. I know that I was OCd, and running a custom ROM, and running a ton more apps than when I first got it, but i was going ridiculous. I purchased a couple of spare batteries online as well as a battery charger, and those spares are lasting me about as close to my original battery when it was new as possible, given that I have ungodly amounts of apps installed as well as being OCd, and running a custom ROM.

Now, I have had my phone off the charger for approximately 2 hours now, and my screen was blank. I just checked my phone's battery use and I have the following:

  • Phone idle 28%
  • Cell standby 21%
  • Android OS 10%
  • Wi-Fi 9%
  • Display 4%
  • Facebook 4%
  • Maps 3%
  • LauncherPro 3%
  • android.process.acore 3%
  • Scorecenter 2%

Battery level shows at Discharging and at 100%.

You be the judge.

Already did the full discharge cycle business twice now. No luck there. I will give it a few more days of tinkering things and then it's going back.

As for the extended battery, Seidio also makes an extended battery for the Droid, with a replacement door. It probably is more pricier than the verizon one though, it's like $70. It's either 2600 mAh or 2800 mAh, i can't remember.

My battery life is about 11-12 hours now, and that is with me using the phone for about 15 minutes every hour (running 25% of the time since unplugged). Before the update, this same usage landed me about 18-20 hours. I could certainly make it from 6:30 am to 11pm on a single charge and end the night around 20%.

So, you've performed battery pulls, complete discharges, factory resets, and it still happens?

Last thing you can try is to use the Master update from Pete's website and see if something got botched in the patching process when moving from 2.1 to 2.2/

Errr... Just-In-Time compilation should IMPROVE battery life, as it takes less CPU than direct interpretation. (The next thing would be static precompilation, but I digress.) However, it can make a CPU-bound program make the CPU use more power per clock cycle due to increased die utilization; that may be what you're getting at.

Which many of the apps that are in the stock system that auto-run and stay running probably are, eh? Or am I incorrect about those being CPU bound apps?
 
I'm going to try the pulling the battery after it fully discharges (shouldn't take it long now since it's pretty much already dead.) I can also try a factory reset I guess. My problem seems to be that the phone isn't recognizing that the charger is connected at all. I've tried with my multimedia station, directly to the charger, through my computer and my car charger. No go. The phone never indicates that the charger is connected, no message and no little lightening bolt on the battery indicator. I'm holding on to a tiny thread of hope that some of these steps will help. The pessimist in me says they won't.

UPDATE

Ok, after pulling the battery, it does seem to be charging now, albeit more slowly than before the update. Thanks for the tip. Hopefully it will not have issues after this.
 
But why has my display % gone up quite a bit, and also other peoples as well since going to 2.2? I use auto brightness, but I swear it seems like it does not work the same as it did before. The screen seems brighter than it did before while inside.
 
So, you've performed battery pulls, complete discharges, factory resets, and it still happens?

Last thing you can try is to use the Master update from Pete's website and see if something got botched in the patching process when moving from 2.1 to 2.2/

I will try this. I have tried everything else.

If I was experiencing a noticeable but trivial difference in battery life, I would be happy as that is to be expected. But when my battery lasts literally half as long, I have to call BS. After I try your suggestion, that only other thing I can do is wipe again and install no additional apps, leave my exchange unconfigured (which I've already tried anyway), and see what I've got. I have 2 different batteries and this battery life issue is persistent with both of them, so I don't think it is my battery. My battery history screen doesn't show any app running rampant, but at this point, nothing makes sense so who knows.
 
Back
Top Bottom