iOS 10.1 Battery drain

Hello.


Updated my iPhone 5 to iOS10.1 and have been having battery problems.


1 - It jumps from 30% charge to 1% in a few seconds then shuts down.


Now here is the stranger part.


As soon as it reboots after connecting to a charger it show 30% charge. When I unplug it right away it still shows 30% and runs like nothing happened for a good few hours.


So it goes from zero charge to 30% in the time it takes to reboot? Strange.


2 - Shutting the phone down at night with a good 80% charge, it won't reboot in the morning due to no battery charge. I plug it in and its back to 30% in a few seconds.



Thanks for any suggestion in advance.

iPhone 5, iOS 10.1

Posted on Oct 25, 2016 6:38 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 30, 2018 4:44 AM

Hello genya,


Yes, it was batteries all along. New batteries resolved the issues. iOS 10 only hid it. Myself and a few other Apple customers worked hundreds of hours to bring this in the open with proof. You likely read some articles I contributed to. Key in this process was 'proof.' Some of us had no coding science but enough electrical knowledge and studies to identify the battery as the only possible culprit. Hopefully when you left the forum a year ago you went and changed the battery, not the phone. Some geniuses knew, some did not. Either case, in the end, Sr Apple management made the decision we wished for: full admission and a solution. My preferred solution is a new tech, solid state batteries, will see about that.

1,950 replies

Dec 26, 2016 8:31 AM in response to HobbsN

GOod luck. The Apple reps do their best to help the customers. 2 reps helped me with restoring my phone, but the problem still persists. I am working with a an Apple Support rep through Twitter right now. I hope Apple knows how wonderful their employees are with their customers. They really are trying to help with this huge problem. I suggest going through Twitter too...they are working so hard with Apple customers.

Dec 26, 2016 8:52 AM in response to lozeerose

They've been very helpful... they've run the Battery Diagnostic tool (they ask for your Serial Number, which they use to enroll your phone into this mode, then you switch on WiFi and go into Privacy > Diagnostics... then you set it off and it reports back. My battery came back as 'Passed'. As well as testing the battery, the tool collects a load of configuration settings - as they told me that I had implemented a number of battery saving settings.


I've also gone through the Battery Usage for the last 24 hrs - Settings - 31%, Home and Lock Screen - 23%, Facebook - 17% (Facebook is running in the background, I am logged out). So it could be partly due to Facebook? So I may quit Facebook and monitor things for a few days?


I think the issue that I have seen/seeing is the fact that the update was continuing to re-index things for a while after I took it off charge. So I think I'll monitor things for a few days and see what happens.


I did also ask of they had an idea regarding when the final release of iOS 10.2.1 will be out. They don't have that information at present.

Dec 26, 2016 9:50 AM in response to Mjolcresure

Problem was occurring for me prior to iOS 10.2 I don't believe it has happened since (yet). The problem also appears to be affecting OS X 10.11.6. I was loading a video on Youtube, the screen went black, I pressed power button multiple times, and then the alert telling me my battery was dead displayed. I plugged in the charger of my Macbook Pro and after re-logging in, what do you know? The battery percentage said 34% remaining.


OS X syslogs from around time period:


12/26/16 12:18:08.730 PM SpotlightNetHelper[489]: tcp_connection_destination_handle_tls_close_notify 235 closing socket due to TLS CLOSE_NOTIFY alert 12/26/16 12:18:08.731 PM SpotlightNetHelper[489]: tcp_connection_tls_session_error_callback_imp 235 __tcp_connection_tls_session_callback_write_block_invoke.434 error 32 12/26/16 12:18:09.520 PM SpotlightNetHelper[489]: tcp_connection_tls_session_error_callback_imp 236 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22 12/26/16 12:18:09.520 PM SpotlightNetHelper[489]: tcp_connection_tls_session_error_callback_imp 237 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22 12/26/16 12:18:28.885 PM SystemUIServer[326]: LSCopyApplicationURLsForBundleIdentifier error:Error Domain=NSOSStatusErrorDomain Code=-10814 "kLSApplicationNotFoundErr: E.g. no application claims the file" 12/26/16 12:18:32.545 PM authd[142]: copy_rights: _server_authorize failed 12/26/16 12:18:32.616 PM authd[142]: copy_rights: _server_authorize failed 12/26/16 12:18:46.537 PM com.apple.xpc.launchd[1]: (com.apple.preference.energysaver.remoteservice[94472]) Service exited due to signal: Killed: 9 12/26/16 12:18:48.000 PM syslogd[46]: ASL Sender Statistics 12/26/16 12:19:53.000 PM com.apple.Safari.History[94476]: dyld: lazy symbol binding failed: Symbol not found: _initializeSandbox Referenced from: /System/Library/PrivateFrameworks/SafariShared.framework/Versions/A/XPCServices/com.apple.Safari.History.xpc/Contents/MacOS/com.apple.Safari.History Expected in: /System/Library/StagedFrameworks/Safari/SafariShared.framework/Versions/A/SafariShared 12/26/16 12:19:53.000 PM com.apple.Safari.History[94476]: dyld: Symbol not found: _initializeSandbox Referenced from: /System/Library/PrivateFrameworks/SafariShared.framework/Versions/A/XPCServices/com.apple.Safari.History.xpc/Contents/MacOS/com.apple.Safari.History Expected in: /System/Library/StagedFrameworks/Safari/SafariShared.framework/Versions/A/SafariShared 12/26/16 12:19:53.331 PM diagnosticd[136]: error evaluating process info - pid: 94476, puniqueid: 493027 12/26/16 12:19:53.331 PM com.apple.xpc.launchd[1]: (com.apple.Safari.History[94476]) Service exited due to signal: Trace/BPT trap: 5 12/26/16 12:19:53.332 PM Spotlight[425]: XPC connection was invalidated 12/26/16 12:19:53.363 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[94477]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash 12/26/16 12:19:54.779 PM SpotlightNetHelper[489]: tcp_connection_tls_session_error_callback_imp 239 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22 12/26/16 12:19:54.780 PM SpotlightNetHelper[489]: tcp_connection_tls_session_error_callback_imp 240 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22 12/26/16 12:19:54.784 PM com.apple.xpc.launchd[1]: (com.apple.Safari.History) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

Dec 26, 2016 11:25 AM in response to Mjolcresure

I have tried to recalibrate battery with the 10.1.1 update after I first noticed the problem. It had no effect. My iPhone 6 (128GB) behaves normally until I get to ~30 % charge (sometime more and sometimes less) and then it rapidly looses remaining charge and shuts down if I don't get it plugged in. Brief recharging (on the order of 2 mins and the battery reads at or above 30%.

Dec 26, 2016 12:10 PM in response to csl

I do not get it why people spend so much time trying to resolve an issue that appears known, identifiable (30 to shutoff is fairly evident), and nor resolvable by consumers alone. Nor would I try to call Apple that to say it does not work and ask for a new unit, go at a Genius bar, show again the issue and get a new one. For the rest, lots of engineers are trying to resolve the issue- or the ONE guy at Cuppertino, but he must be on Holidays. Come on guys, never watched Christmas Carol? Do you really want Apple to recall from vacation its ONE iOS engineer and resolve YOUR problem as, evidently, you are running energivore apps such as browsing or social media? Have you not learned that the problem is you until such moment Apple admits that you are not? they even went as far as to remove the battery time indicators and so on. What else do you need, a phone lasting full day or something???

Dec 26, 2016 12:18 PM in response to Mjolcresure

As I noted in a previous post, my iPhone 6 has the 30% bug which I noticed after updating to iOS 10.1 and it still happens with iOS 10.2.


To help clarify the hardware component I checked its battery using the Battery Life App and iBackUpBot. My iPhone was bought in Oct. 2014 and according to iBackupbot on a mac, the CycleCount: 613; DesignCapacity: 1751; FullChargeCapacity: 700. As I understand it, this means that the battery can now only hold a charge of 700 mAh out of the original spec of 1751mAh (vs the nominal 1810 mAh for the iPhone 6). This is flagged as a bad battery by Battery life. 2 things come to mind:


1) the 30% bug may result from the bad battery or the interaction of the bad battery with the software update. It would be nice if Apple would weigh in on this. For those of you who have replaced your battery, does the 30% bug go away?


2) It seems to me that this is excessive battery decay for a cycle count of 613. As others have said Apple specs the phones so that the battery is 20% consumed after ~500 full cycle charges. My battery has been consumed by 60% in 613 full charges. i.e. 300% greater consumption for only 23% more charges. I know milage varies depending on a number of conditions but this seems to me to be excessive wear. Could this result from a fault-prone battery to start with? Could this result from changes in iOS that hastened its decline?


Comments welcome. Especially from Apple engineers.

Dec 26, 2016 12:56 PM in response to csl

Apple engineers are not required to answer, and not even the very helpful site https://www.google.ca/search?q=battery+university+lithium+ion&ie=utf-8&oe=utf-8& gws_rd=cr&ei=_oBhWL7lKMymjwScoKLYDA


in two full years of cycles a single bad cycle can damage a Li-Ion battery, e.g. going running or cycling with the phone on a hot day (left in car), or very cold day (-35C), etc etc etc. For example as I never take my cell at work- cannot bring it in, am used to seeing my cells with hundreds of cycles but less than 20% loss. but yes, a new OS with new SMC controller software might look at some of these batteries and deem them as non functional. Happened to me on one iPhone 5, barely used, a new OS bricked the battery draining it very fast. Apple replaced the battery and the problem went away.


So yes, bad drain, temperature and constant background usage can shorten a battery life pretty fast. And some, as the Fedex airplane crash demonstrated, are just bad from day 0. Even if 1/10000 batteries were defective, that is ONE HUNDRED PER MILLION, and so on. As Apple sells million of iphones, anything higher that 1/10000 failures begins adding multifold to this issue. Think Samsung: NOT ALL batteries by that manufacturer exploded. It only took dozens but wiped out 17bn of Samsung capitalization. Int he Iraqi desers I always kept my iPhone off and insulated, and left it months later without any loss of life. Many others used their phones and they failed rapidly.


An iOS poorely managing the energy consumption will therefore expose battery flaws exponentially faster (happened to Microsoft Surface recently, just google it). So this iOS merely exposed the battery flaw. Because, if every single Apple iPhone 6 6s 7 was affected - or even a third, Apple would be shut down with repair requests and it would be a major PR disaster. The current issue, although mediatized, is also affecting only a fraction of users and Apple likely knows which ones *by batch and ser. number)., but may be digging its heels to admit responsibility and avoid a major recall. So they could spread out the troubleshooting over 1-2 years and putting the time wasting effort on you, the owners, with all these needless steps.


I recommend Apple Genius bar and changing the battery. Pay for it- you will have 1 yr warranty. If issue is resolved, we know what caused it. If not, it is the iPhone itself shorting. I know people running 5 5s and 6 6s ios 10.2 no issues. Personally I am staying with 9, but that was a rebellion against Apple's new cumbersome iOS 10 styling and poor ergonomics.

Dec 26, 2016 1:09 PM in response to Beisarius

I have to say that you (and me, and couple of other fellows) are the only ones who really see the big picture. Until Apple acknowledges this as an issue, there is no issue. Until someone dies or something because it could not call emergency services because it's phone as died at 40% battery remaining, it's not an issue at all. Until every affected user start do migrate do Android or even Windows, it's not an issue for Apple.


Since nothing seems to be an issue, enjoy all your fine working emojis.


This issue is surely worse than originally thought.


As someone already said: "at least Samsung had the guts to face the problem..."


Your call Apple

Dec 26, 2016 2:40 PM in response to Pungkulan

This seems very similar to how mine behaves. Interesting as it's happening for you on iOS 9.3.4. I noticed the odd battery behaviour only after upgrading from that to 10.1 but then that also happened around the time it started getting cooler so I hadn't discounted the possibility that the iOS update correlation didn't mean it was also the cause It would be interesting to map out where everyone who is having battery issues is. I wonder if there are many experiencing it in Australia or Africa right now or if it is primarily those in the Northern Hemisphere? It seems more people with iOS 10 have the problem but the fact it can affect others suggests it's not solely an iOS 10 issue and that there's some other confounding factor, right?


I'm not sure whether it's a separate issue but all my apps are behaving as though they're being set up on a new phone - requiring me to sign in or select preferences that I had previously chosen. Can this happen after a hard reset? I thought it would only be after restoring from a backup but I have not done that.

Dec 26, 2016 2:57 PM in response to Mjolcresure

At least it's a bit relieving to read that I am not alone with this new stupid bug. It happened a few times when I was jogging that the phone died with battery by 30, 35%, and I thought it was because of the cold or humidity (it's raining quite a lot here in Ireland).


But just today, for example, I was listening to music at home, the battery was 45% and then, voila, dead. Only to plug back and get the battery with 50% within a few seconds.


Completely unreliable.

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.1 Battery drain

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