iOS 6.1 Battery Life

Restoring to factory settings fixed my issues with data leakage and battery drain on my iPhone 4 on Verizon.

Don't worry, IgalSc, the battery dainage will return. Maybe not today. But probably tomorrow. (experience talking) It comes and goes.

Just weighing in. I updated my iPhone 4 to ios 6.1 from 5 (don't recall the full number) and after that the battery drained in 4 hours after a full night on the charger. I never had this happen before the update. My phone always kept a charge for over a day, maybe two. I don't make a lot of calls, just a moderate number and I use wifi when I am at home and whenever it is available.

The drop off was really dramatic. I never had to worry about my battery not lasting when I was gone for the day. Now my battery is dead in just a few hours unless I have a place to recharge while I am out. That is not very useful. In fact, it makes the phone useless if I am out for a walk or some such. The battery will be dead before I get back from my hike. (an example of a situation where I cannot charge my phone...well maybe with a solar or battery pack...but still!!)

I updated from iTunes through my computer. I did not pay a lot of attention to the process, just allowed the update to proceed automatically.

I turned off notifications, push on my email and toggled wifi. (and I tried a number of other fixes here) Still have the problem. I will try completely resetting the phone through my computer...as suggested here. I hope it helps. The phone is really kind of useless in this condition. I was thinking I would upgrade to ip5, but I am leery because of this power issue.

Hope Apple is listening!

Do you guys think this is good for an Ipod Touch 4th generation:

65%,Usage:4Hours,57 minutes,Standby:1Day,1Hour

Is that good?

I updated from 5.1.1 to 6.1 and the battery life has dropped substantially. With 5.1.1, I could get ~7-8 hour usage time and ~24 hour standby time. With 6.1, I can actually see battery going down ~3% every minute, this is insane! I'm also getting ~5 hour usage time and ~12 hour standby time, which is half the life I used to get with 5.1.1.

This is disappointing Apple! I love the new features in 6.1 but it's crazy that the battery life goes down the drain like no other.

The Official Solution from an unnamed source within that fruit company in Cupertino:

The bug in iOS 6.1 is a ping-pong infinite loop trying to talk to the Exchange server. Unfortunately, just rebooting doesn't fix the issue. Deleting the account is necessary to remove the problematic invitation response from the queue.

The workaround is annoying, but effective:

- Delete your Exchange account

- Recreate the Exchange account

- Do not respond to meeting invitations from the device until 6.1.1 comes out.

I just contacted Apple. They have given us the ability to contact them free because of the 6.1 update. They said the issue is a firmware update that needs to occur. They suggested backing up to the cloud, then restoring as a new phone, then pulling stuff back from the cloud. We will see if that works.

I did a backup and restore as new 6.1 phone, then restored my backup files ontop of that. no problems now.

Great news So click me as correct answer 🙂 ha Glad it worked for you.

Well so would you now agree that maybe what I mentioned WAY back was truth and not a made up answer as you suggested? Just curious not trying to stir you up again but you insisted that what I had suggested was made up and speculation and would no way help the situation. BTW that ActiveSync bug has been around way before iOS 6 or 6.1. I would hope that 6.1.1 would fix it but would be surprised is it does.

Don Louv wrote:

The Official Solution from an unnamed source within that fruit company in Cupertino:

The bug in iOS 6.1 is a ping-pong infinite loop trying to talk to the Exchange server. Unfortunately, just rebooting doesn't fix the issue. Deleting the account is necessary to remove the problematic invitation response from the queue.

The workaround is annoying, but effective:

- Delete your Exchange account

- Recreate the Exchange account

- Do not respond to meeting invitations from the device until 6.1.1 comes out.

Hi sbailey4, here is quote for you:

"Listen to me now or believe me later". ...just joking, I hope nobody got offended...

Anyway, there are some issues that might prematurely drain the battery.

For example, just yesterday I tried a few apps and some of them left location services icon ON in the menu bar. So the "System & Monitoring Tools" application reported only ~85% idle CPU -- after rebooting it was back in the normal ~95% range again.

Yes, the system should automatically shutdown such unnecessary processes. And as Don Louv wrote, it is interesting that responding to Exchange meeting invitations might also trigger such behaviour.

Not had much expierence with touch device but it would appear to be close to iphone as far as music and video. Don't see any standby spec posted. But that looks decent to me. You would need to determine what kind of use etc. But at that rate you potentially get over 2 days standby and over 10 hours of use (Since you have 65% remaining not 50%) If potentially the stdby was same as 4s and audio is same:

25/200=12.5%= standby used, 5/40=12.5% =audio used (assumed all usage was music) so 100%-(12.5+12.5)=75% should be remaining and you are at 65%. But again that is assuming all usage is music which it probably isnt. Add any wifi usage or video and it changes things but 65% and 75% is pretty close estimate and that is based on the max spec posted by Apple. Apples spec is Audio 40hr and Video 7hrs and they dont list standby or wifi. I pulled the 200 from the iPhone 4s standby spec. So I would say that is decent from the 10,000 ft level 🙂

Pizza98704 wrote:

Do you guys think this is good for an Ipod Touch 4th generation:

65%,Usage:4Hours,57 minutes,Standby:1Day,1Hour

Is that good?

Haha I hear ya,, And yes he has a point as the bug that was hinky with responding to exchange meeting was supposidly just addressed in 6.0.1. Perhaps there is still work to be done there but that particular issue was if you declined or accept a meeting it would do so for all participants. Wow that could get hairy in a corporate situation. Not really heard that doing that would hang it up and create the issue we are discussing but certainly it could I suppose. I suspect that Apple engineers are going to have to work with MS engineers hand in hand to utiltimately get ActiveSync working correctly with Apple's iOS. Perhaps they(MS) dont want it to. They can add that as a feature and ad compaign for Windows Phone that ActiveSync, it "Just works" with WP8 😎

Matti Haveri wrote:

Hi sbailey4, here is quote for you:

"Listen to me now or believe me later". ...just joking, I hope nobody got offended...

Anyway, there are some issues that might prematurely drain the battery.

For example, just yesterday I tried a few apps and some of them left location services icon ON in the menu bar. So the "System & Monitoring Tools" application reported only ~85% idle CPU -- after rebooting it was back in the normal ~95% range again.

Yes, the system should automatically shutdown such unnecessary processes. And as Don Louv wrote, it is interesting that responding to Exchange meeting invitations might also trigger such behaviour.

No sbailey4.

Sorry.

You WERE speculating. You were giving out 5 steps that had no basis in actual knowledge. Yes, one of your steps made the symptom go away... temporarily. But it was always going to come back. And you wer making people jump through time-consuming hoops that in some cases might cause them to lose data. Some of your 5 steps were way off in the weeds and were just causing confusion and distraction. Example: This had nothing to do with "battery calibration" or any of that crap.

No, this is not the same bug as 6.0 (and was fixed in 6.0.1). Same area of code: Exchange Server interaction with iOS. Different bug. Very, very different symptoms.

I went away (after our discussions) until I had actual confirmation of the actual bug, and the actual workaround. From Apple engineering. Not speculation. I sent logs off my device to the engineering staff at Apple. They confirmed the cause, and THEY specified the workaround. Not me.

No, you didn't solve this one. And if you were close, it was just luck. Sorry. You hand out lots of responses, but you have what I refer to as Male Answer Syndrome: You don't have the answer, but you can't stand not helping, so you make up an answer in a vacuum. And people believe you, because you seem to sit in a position of knowledge and authority. And your answers are based in some past experience, so sometimes they seem to be correct, or at least close, but in the end you were just guessing.

And I was searching for proven truth. Not speculation.

Sorry if this is harsh. I'll go away now and never bother you again.

Oh ok whatever. Guess there was no chance that you would admit that maybe you were wrong and maybe I did have a little knowledge regarding iOS. If it makes you feel superior calling me names that's fine. I wont fault you for that. So since Apple engineer told you personally that exchange bug and I just guessed it (according to you) makes me wrong and them right? Even though we said the same thing effectively "delete the friggin exchange account and re add it" which you clearly stated was hogwash and un warranted and BS and would not work. Now all of a sudden your "unnamed source" said it and it makes it correct and still makes me wrong somehow. Nice logic there. Anyway I am glad you got your confirmation however. And clearly you have no idea what I do know regarding the other items I posted .You call it a guess I call it knowledge so we will just leave it at that. Have a nice life! oh and tell you unnamed personal source thanks for the confirmation! Its nice to know someone at Apple confirmed what i said!