ios 10.2.1 to 10.3 battery drain

Hi there,

Iphone 7, Since upgrading to 10.2.1 and now 10.3, The battery life has been horrible.

Especially in standby where it can be charged at 100% and within 4 hours sitting and not being used it will drop 20% battery, Its starting to get very annoying as i'm now having to charge my iphone twice a day, I would be lucky to get 2-3 hrs device usage according to battery settings. I also have friends with the same issue since updating to 10.2.1 and beyond.


Any ideas on what is causing it as i've tried the 10.3.2 public beta and no change in issue.

Starting to with i hadn't sold my Pixel.


Dan

Posted on Mar 31, 2017 5:00 PM

Reply
Question marked as Top-ranking reply

Posted on Sep 7, 2017 11:04 AM

Let me try to be helpful. Whatever the problem is, it is NOT a problem with the specific version (in this case, 10.3.3). If you assume it is a problem with the version you will never resolve it. There are a couple of reasons I say that. The first is that this was a trivial change, adding a few lines of code to block a hacker from taking over the radio chip. There is no way such a small change could have created a battery drain problem.


The more general reason is that in the 10 years and dozens of updates that have been released, there are a small number of phones that report increased battery drain after EVERY update. The number of reported problems for 10.3.3 is an order of magnitude fewer than for several other recent releases, and even those were small numbers. There are only two cases where this was actually a problem with the release; 2.0 and 3.1.0. And the many thousands of posts after each of these releases demonstrated that.


If it isn't the version itself, what causes the sudden change in battery life? Sometimes when a version is installed it causes a problem in an app. The update process terminates running apps, and not all of the 1 million+ apps are coded to handle that gracefully. When they restart they may have lost the status of whatever they were doing. They keep retrying and failing, consuming battery in the process.


Another possible related cause is Microsoft Exchange. There is a flaw in the Exchange ActiveSync protocol. It has been there forever; fixing it would require a protocol change, which would break billions of devices that use ActiveSync. So Microsoft doesn't fix it. If an ActiveSync device loses its place in what it was doing it creates a new connection to the Exchange server. But the Exchange server doesn't know about the problem. It accepts the new connection, but doesn't kill the old one, which keeps trying and failing, again using energy. If you have an MS Exchange account and you have a battery problem (even not associated with an iOS update) either turn off the account in Settings, restart the phone, and turn it back on. Or delete it, restart, and add it back.


In general, go to Settings/Battery and see which apps are using the most energy. Wait at least a day after the update to do this, so you have 24 hours worth of data.


Troubleshooting steps for sudden changes in battery life:

  • Kill all running processes, then restart the phone. Note that this will not necessarily fix the problem of stuck apps, however, because they may restart in the same state they were in when killed.
  • Connect to iTunes, restore iOS, and restore your backup. This does 2 things: it deals with the possible but unlikely problem that the iOS version on the phone is corrupted, and it also assures that all apps restart fresh. Remember that app data must be restored, which uses energy, so wait at least 24 hours to see if the problem is resolved. If not:
  • Repeat, and set up the phone as new. Do not log in to iCloud. Do not install any email accounts, calendars or contacts. Do not install any apps. If the problem is still present after a few hours your phone has a hardware problem.
  • If this does resolve the problem try restoring your backup. If the problem comes back you have corrupt data for one or more apps. You can try to figure out which app from Settings/Battery.
492 replies

May 24, 2017 7:30 AM in response to t33j4y

I'm the guy who wrote about my experiences with this problem in an earlier comment, and who is now on my 5th iPhone 7. I thought I'd report back after having used it for the past three days (still early, I realize). The phone I received on Saturday, and which was restored from a backup, is giving me better battery life than any iPhone 7 I have had so far, including the one I purchased on launch day. So far, it has not heated up at all. I'm keeping my fingers crossed!


Throughout my many and lengthy phone and online chat conversations with Apple tech support, and in person with techs at my Apple Store, there was no consensus about what was causing the problem. The assumption that it must be software was the reason we set up the first three replacement iPhones as new phones, but that did *not* fix the problem. True, that does not prove that the problem is not software-related, but it was why the senior advisor allowed me to restore this iPhone (the fourth replacement) from a backup.


I have no explanation for this, and neither does Apple, at least not that they have shared with me. The thing I want to emphasize here is that *every* Apple support person with whom I have spoken has said that it is *not normal* to experience rapid battery drain, over-heating, and the incorrect reporting of standby and usage as identical when they are not. Apple does not consider these problems to be acceptable. While it's possible that some users may experience problems like these because they are not following ideal battery conservation procedures, that cannot explain why users who previously had no problems suddenly begin to have issues.


I do think that one should not rule out the possibility that it's hardware-related. Just because an iPhone's battery passes the diagnostics tests does not mean that the phone itself is not defective.

May 24, 2017 8:56 AM in response to Phil M2

I've talked with apple support 4 times.

My aggravation must have been obvious so the requested that a supervisor call me on the phone.

Her solution was factory recover the phone . Rest as new on the phone and download my backup from iCloud , not my computer . She suggested that downloading the backup from the computer may be redone loading something corrupt .

This has not helped.

It's a iOS issue. 10.2 perfect. 10.3 battery problems . Plain and simple. In 2 hours time form starting iOS update to signing back in to my phone post update problem began.

The woman I was chatting with before the phone call was almost defensive. She stated a few 1000 phones with problems doesn't point to an iOS problem. That statement was made by her without me saying anything about this or any other forum about this problem. Tells me they know there is an issue just not willing to fix it or don't know how to fix it.

I'm done. This is ridiculous. I shouldn't have to search all over to try and debug an issue that they caused. .

Only solution I see is make ios10.2 reavailable

May 24, 2017 9:02 AM in response to anthodavis

It very well could be an iOS issue, but my first iPhone 7 failed using iOS 10.2.1, so in that case at least, it could not have been an iOS 3.x problem, since the iPhone failed before iOS 3 was issued.


We also have to allow for the possibility that while the problems are the same, the causes of the problems may not be the same for everyone who is having them.

May 24, 2017 9:05 AM in response to anthodavis

anthodavis wrote:


It's not an app problem. That's just stupid. It's an ios10.3 problem.

Then why haven't the 300 million users who updated to 10.3 descended on this forum to report it? Why haven't my two iOS devices on 10.3.2 exhibited it? Why haven't the usual apple-hating trade press sites gone gaga over it? Why are there people who say that it must be 10.2, because that is when they experienced the problem - and that's the version you want to go back to? If you read through this thread alone, you will find lots of users who have fixed it, using many different solutions. It isn't a problem - it is a symptom. And like all symptoms, it can have many unrelated underlying causes.

May 24, 2017 9:06 AM in response to anthodavis

I agree with you that it's not an app problem since I also had the situation you're talking about, where Safari was the worst culprit when it came to battery usage. But that's based on the battery usage data reported on the phone, which may not be accurate.


The bottom line is that Apple doesn't seem to know what the real problem is, and so their fixes are hit or miss at this point.

May 24, 2017 9:31 AM in response to Lawrence Finch

Actually if you read back through the entire conversation thread almost everyone who has posted says this started with ios3 . I can verify that because I have read every post. I found this conversation day 1 and have followed since.

Don't know anything about your phone or the other 300 million iPhone users but mine started with ios10.3 and nearly everyone else on this conversation did too.

Don't think it's to hard to believe if a 1000 people find and post to one thread there is 10times the people having issues but just looking for answers but don't reply

May 24, 2017 9:37 AM in response to Lawrence Finch

It's amazing how everytime that Lawrence says something, he points out that we are doing wrong. That we don't know how to use an iPhone.


-Why haven't 300 million users who updated to 10.3 descended on this forum to report it?
A: Because not many people knows about this forums. Because many people is so used to charge their phone twice a day even if is not empy, so they don't realize that the battery is draining faster than usual. Because many people doesn't even use their phone to work, but just as a gaming console or a music player, so they don't realize of the importance of having a good battery performance the whole day. There are now 3 threads in this forum talking about the same, more and more people it's starting to complain.


-Why haven't your two iOS devices exhibited that problem?
A: Lucky you but, do you realize that denying a problem just because it hasn't happened to you it's absurd?


-If you read through this thread alone, you will find lots of users who have fixed it.

A: Wrong. People in this thread has recived a new iPhone because they couldn't fix it. Not even Apple Support could fix it. They have even tried to use their phones totally empty, without installing any app, without logging to iCloud, and the problem continues.



People in this thread is trying to find a solution for a problem. Stop blaming people because they don't know how to use their iPhone, when not even Apple Support can find a solution for this problem. To receive a new iPhone it's not exactly a solution.

May 24, 2017 5:43 PM in response to Danjohn1

I'm not 100% on this answer, but I would like to take a crack at it. I just purchased iPhone 5s the other day, and it ran on 10.0.2 and battery was perfect. So today I made the idiotic decision to update to 10.3.2 without checking for issues. I to now have battery drain issue. The only noticeable difference I see now is iCloud. First of all it's just sitting in settings at the top like a sore thumb, and annoying to look at honestly! I'm guessing either it's refresh rate, or that it's always on now is part of the problem? So I logged out of it and my battery seemed to be a bit better, but it wiped out my notes, contacts, and photos until I logged back in. Like I said I'm not 100% on the answer, but I'm willing to bet it's part of the issue.

May 24, 2017 7:45 PM in response to -Kobra-

It seems that whatever ios the phone comes with new out of the box is not the problem. in fact it seems that the ios it came with is optimized for the phones best performance. It's once you update the software after having used the original ios. it is then when the battery and other issues begin. I was LOVING my 7 plus that I got back in April. After the 10.3.1 update I noticed immediately the battery drain. 10.3.2 didn't improve. What I would give to go back and not click the update button!

May 25, 2017 4:11 AM in response to Lawrence Finch

Lawrence, It doesn't have to be a silent update though. It should be one which the user is made aware of what will be done and to confirm (or not) to update. It really is straight forward. You are finding reasons why not rather than being more positive.


I also noticed that many of the high level contributors (not just you Lawrence) are tending to minimise or defuse this issue at the moment. Either we all are really stupid or they know something we don't. I know you will hark back to numbers affected, but I think one contributor has addressed that and clearly its not all iphones, but many iphones. Why doesn't Apple just come out and ask the users if their phones are affected? Then you can more accurately how widespread this is. It will be a gamble, as it could be massive and they will have to deal with it. As it is, they seem happy to just deal with those who complain the most or make others wait.


Lawrence, are you saying that this level of anxt, frustration and inability for Apple Support to resolve all cases is typical of an IOS update? Also how do you know that all the "resolved" cases you spoke about are permanently fixed?


I still feel, because of the wide variation of successes, that there is a hardware component incompatibility somewhere (batch or manufacturer related).

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

ios 10.2.1 to 10.3 battery drain

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.