Yesterday, I went all day (12 hours that is) without recharging. Last night I upgraded to 2.2. Today, after being off the charger for 4 hours, it is down to 20%. Anyone else seeing a decrease in battery life since going to 2.2?
I can confirm your theory. After fully shutting down Safari, my battery life returned to pre-2.2 levels. It was the same in the morning as it was when I left it the previous night. After leaving Safari "open" for several hours, the battery was drained to ~10%. It seems the change in Safari is the culprit. Thanks for your research.
OK. I appear to have fixed the problem ( at least for now). To recap, nothing had changed on my phone other than the upgrade from 2.1 to 2.2. I always had one email account, an Exchange ActiveSync account, set to push. My battery life went from like 40 hours to 4 with 2.2. But, I discovered through some tinkering that push seemed to be the culprit. So on a whim from something I read in this thread, I deleted my Exchange account, rebooted the phone, then re-added it.
So far, that seems to have worked. I am using push and everything else I had always been using, and battery life seems to be as good as it was before.
Not sure what the connection is, but thought I'd share my results if it helps anyone else.
Thanks so much for your tip Antonio! Quitting Safari using the method you described seems to have resolved most of the battery issues I was experiencing since the 2.2 update. Note that prior to the 2.2 update I already had my mail accounts set to manual check, no fetch or push. So my battery life was pretty good. That's what made the 2.2 update such an obvious issue, as my iPhone would be asleep and fully charged at night, and yet I'd wake up in the morning and it would be completely dead.
Hopefully Apple's devs will figure out the Safari issue soon.
I updated my phone on Tuesday/Wed of last week and did not notice anything terrible until yesterday. I use my phone extensively in my business. Around 5-6 hours of phone time per day, plus push exchange for work email, browsing and ipod about 1-2 hours, plus some apps, etc.
Anyhow, I usually would have to recharge daily when I turned in for the night. Well, yesterday I noticed my phone was dead about 2-3 hours after taking it off and fully charged. My phone was also hot. I woke up this morning and hit this message board, read this entire thread while completely recharging my phone that in about an hour had drained by about 25%. I then followed some of the tips, hard stop of Safari, delete and reinstall my exchange server, and with 1 hour of phone time, my baby is back!!! It is still on close to 100%, and that also includes playing prices right for about 10 minutes while drinking some coffee.
My wife and I both have 3G iPhones. My wife doesn't use hers much during the day as she has retained a smaller Sony Ericsson phone for calls ( the iPhone starts out slim but it bulks up a lot with a leather protective case ), so she NEVER has battery issues. The very next day after I upgraded her phone to version 2.2, she tells me that its battery was flat. For the next few days I note that with virtually no use at all the battery runs down in less that half the day. I made no changes to any settings before or after the update.
Neither turning the phone off and on, or completely restoring it made any difference to the power drain, so I looked for other things to turn off. I changed MobileMe from PUSH to FETCH (hourly) and that seems to have worked. Bluetooth and 3G were already disabled.
So it appears that PUSH can go crazy after the update even if there is nothing to actually push. I have read that deleting and recreating the mailbox settings can fix the problem. Hope so, I'd like to turn PUSH back on again. I updated my own 3G iPhone at the same time without any problems at all.
I've shut off push and auto fetch and still have the short battery life coupled with a very warm iPhone symptoms. I also have the calendar set to manual sync. My email accounts are all set to manual fetch. I don't use Exchange.
As soon as I get it charged up again I'm going to try the "quit Safari by holding the button down" approach.
just a follow up from previous post. It's been 2 full days since implementing Antonio's suggestion of hard quitting Safari by holding the Home button down, and since then the iPhone's battery has been back to normal. Haven't had the need to do a restore. So for those still having or just noticing this issue, make sure you try Antonio's suggestion of completely quitting Safari by holding the home button down, i.e., with Safari open on your iPhone, hold the home button down until the screen goes black and your main menu appears. Usually takes about 5 secs.
I'm also affected by this "mysterious" battery drain in 2.2. Which wasn't an issue with my replacement iPhone 3G that was running 2.1.My first iPhone 3G experienced this battery problem with 2.1.
My phone is also running hot for some reason. Which has never happened on my first 3G or my replacement 3G. I'm really starting to become really unsatisfied with my iPhone!
I have a feeling the facebook application has something to do
with the battery and overhearing issues. I have already tested everything above which hasn't worked this is my last option.
So, a co-worker has a 2.1 phone. I have been comparing the 2.1 and the 2.2, and it looks like ActiveSync is causing the issue. Both phones are configured for push, yet when you have the mail client open, the 2.1 phone sits idle after initially connecting to the server. The 2.2 phone, however, continues to cycle through "Checking for mail.." repeatedly. If I turn off push and leave it on pull, then my battery life is returns to the same as the 2.1 configured for push.
Incidentally, my phone is a new phone (I returned the old phone due to the total battery life lost due to all of the re-charging I was having to do) that came with 2.1. I upgraded to 2.2 and then configured activesync. I did not restore my old configuration, so this would appear to be an issue with 2.2 and activesync.
Anyone else have 2 phones, one on 2.1 and one on 2.2, that can test this with activesync? This could be a patch level issue on the exchange server where the 2.2 version of activesync and the exchange server are not communicating properly, or it could be an issue with the 2.2 version of activesync in general. If you wish to test this, open the mail client to your Inbox and watch the status at the bottom. If your phone is like mine, you'll see it checking for mail every 6 or 7 seconds. Please post back your findings.
i have an issue since the 2.2 upgrade i have noticed if i plug the phone in and listen to music or watch a movie it is like i don't have it plugged in at all. the phone has stopped changing while in use. it only charges while it is idle. apple says it charges slower when in use but it should be charging. but when my phone says battery at 20% when plugged up there is a problem. it didn't do this on the 2.1 firmware. i have an appointment at an apple store tomorrow so they can tell me what's wrong with it. but i already know some developer missed a few lines of code and they screwed us.
Just my two cents. I had the same problems (the back of iPhone getting very hot, the battery unable to last for more than 6-8 hours, etc...). I tried the Safari-closing, Mail-closing, "every single App-closing" method and it didn't work for me. Then I tried deleting both my GMail and MobileMe accounts, then turning off the phone, turning it on again and configuring both accounts. So far so good, battery is now performing as before the upgrade. 7 hours in stand-by and, 2 hours of use and around 60% of charge. I hope it helps...
The "proper closing" on Safari did not have any positive effect in this case. The battery still drained in about 3-4 hours.
However, just like Aythami, we subsequently blew-away the Exchange account, power-cycled, then recreated the Exchange (ActiveSync) account. That was friday afternoon. The user reports that (so far) the battery life seems to be good.
We'll give it one more day to make sure but things look promising.
Maybe the update to 2.2 messes with an email setting or two that causes lots of retries, causing the battery to run down? It sure seems like it.
