iOS 10.1 Battery drain

I have this problem now for several months on my Iphone 6 without any helpful reaction from Apple. I don`t even think about spent some money to replacing the battery because on the one hand it looks like it doesn`t always solve the issue and on the other hand its clearly something with comes with the iOS upgrade and therefore it`s something that should be fixed from Apple.

Currently I plan a new smartphone later this year and given the experiences I have recently made with this issue it will be definitely not another iphone. I don`t want to pay such an high amount of money for an device which is not really working and comes with such an lousy support.

Was looking into my paperwork now, as I said they replaced my original 6s that was failing with 20% and gave me a new one/different phone - I see the date was October 2016 and the notes in the receipt I was given say:

Issue: Battery has nearly failed

Steps to Reproduce: Verified in diagnostics

Cosmetic Condition: Handset is in very good condition

Proposed Resolution: Replace handset as this was previously positioned. Educated customer that we would normally replace the battery, and that this was an exception

I have this problem now for several months on my Iphone 6 without any helpful reaction from Apple. I don`t even think about spent some money to replacing the battery because on the one hand it looks like it doesn`t always solve the issue and on the other hand its clearly something with comes with the iOS upgrade and therefore it`s something that should be fixed from Apple. If your iphone is over 1.5 years, over 700 cycles, it is very normal. 6 was a much more demandign highware than a 3 or a 4. Your battery likely did its job. All those here in your similar situation (shelf and operational done battery) whom replaced it had full resolution. Every single one. And many came back to admit it was not the iOS. So trust the science, trust the Apple disclaimer when they say 500 cycles. That is quite good if you got more than that.

Took it into Apple store this month and was told that with 500 charge cycles the battery was borderline due to fail! What they failed to recognise is that the only half of those charges were in the first 15 months of ownership and the next half were in the 3-4 months after upgrading to 10.1! It's not rocket science. There are a few users that also had issues sub 500 cycles. They did resets, Apple support, customer care. Some had battery replaced with Apple and the issue was gone. The 500 figure is correct, and, for example, 200 cycles (not 500) sub 30-0% can mess up a battery (less electrons, less Lithium ions to move back, think of old oil in a hard revving race engine)- it is just a fact and why Apple also introduced the Low Power Mode some of us do not use. Some owners have had the issue at the 10-11 month membership so they had pretty good coverage. But you have to trust that 15 months on a phone that has more power than the Apollo Spacecraft put together, is actually pretty good. Only my Macbook Pro do I expect 1000 hard cycles, and 1.5 years into owning any phone I expect having to replace the battery. I get more as I use the science to a fault, for example, never high drain below 30%, ever (gaming, videos e.g.)

Question AppleYoda, was your issue fixed.. I do remember you spent over 100 pounds for it, but was it fixed.. all our peers whom replaced theirs claimed resolution thus far. As for your new battery, with normal 1.5 cycles per day use, is it unreasonable to expect more than 12-15 months of use, or over 500 cycles...

Updated my 2 years old iPhone 6s. It jumps from 30% charge to 1% in a few seconds then shuts down. As soon as I reboot 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. Recently I keep my phone in a low power mode. Up to now, the freak accident did not repeat, even when the battery charge goes below 30%. How can it be a battery problem? When it suddenly shuts down, immediately when connected to a charger, it reboos and show a 30% or more battery charge. At that point, I immediately unplug, and it keep running!

Altom, have you tried Apple Support, diagnostics, Genius Bar, it is a good start. If you check above answers I gave to similar 2 yr marked peer, you could have done 700 to 1000 cycles on that iPhone. If you check online battery science, you will find out that 30% is the do or die figure for an ailing old or done battery. it is a near vertical amperage demand, health and depth of discharge ability. What happens is that there are less electrons and Li ions to move. As the gel or Li liquid increased viscuosity/age, or too much sub 30% demand, it simply cannot deliver anymore. Too much resistance. Then it shuts down. The control module then has to make sense of these figures. And at that point any Li health decreases dramatically, days, a normal electrical engineering fact. Online you will find out e.g. Battery University the life charts.

When you replug the charger you simply give a defribilator type shock and it wakes up at the last read. Another analogy is taking a high performance car with old oil- it can drive well still- but at Laguna Seca or Indy. it will not last two laps.

When a battery reaches the cycles and age we are discussing, it is one random amperage spike away from final decay. Dying symptoms have been the same in any system, Android or iOS, going back 10 years: sudden drain, sudden shutdown, jumps down, and notable poor sub 30% performance. Your 6S has more power than Apollo 13 and NASA's computer put together, and it delivered for 2 full years. Quite good.

You are not the first user whom came with 2+ years battery issue they resolved it and all likelihood so will you.

If the battery is *actually draining* it's not the 10.1/10.2 issue. The OS issue is that the phone behaves as though its battery is totally drained, and shuts down, but pops back up to a level as high as 49%, but generally between 20-30% THE INSTANT the connector hits the connector port. So either: A MIRACLE!! Updating to iOS 10.1 or 10.2=INSTANT 0-25% charge--or something in the update borked the phone's ability to 'read' the battery's actual charge-level, and it responds completely as though the battery were dead.

I understand mutant, but can we compare the users above with a < 12 month use 6S, and anyone with 2 years, or paikinator's 4 year old iPhone 5... I do not think so. Also, it is relatively known, any installation is a stressful process. In electrical engineering they call 'stressful' the technical word anything that updates coding, rearranges amperage parametres. Any operating system install - all the way to a coding update which bricked a billion plus mars satellite- as stressful. So yes the process of plugging and reinstalling does have an amperage effect, and it speaks more as the the battery's ability to withhold the transition than to the iOS. I think the 6S recall issue, owners having young batteries and issues, is not at all the same as 1000 cycles iPhone. Yet, no matter the issue, when a battery fails, they all fail the same way. Sure one can change the circuit breaker parameters, but it is always similar symptoms. One friendly user was telling us that she got 6-10 hours normal usage before the update. And that she got 2 years of the prev battery. I told her that her battery life was low before the upgrade. She eventually admitted using an non-OEM, and these are often rated for a few weeks of use. Non-OEM, non Apple controller, her iPhone 5 had little chance. She is probably changing the battery as we speak with an OEM one. So similar symptoms, different issue altogether.

In some very rare cases you get fires, little warning, 55 incidents took 17 bn $ out of Samsung. That is extremely rare. If anything, I rather have an iPhone that shuts down as a safety than catching fire. Also, in news- that the recent Egyptian crash may have been caused by a phone placed on cockpit front under the window- max heat especially at altitude their devices were bound to fail. One flight, one cycle, everyone gone.

You seem to be stuck on blaming the battery. Remember, these people didn't have any battery issues before the update. Like myself. The problems start immediately after the upgrade. You need to put more blame on the OS upgrade. For all we know it may be labeled the battery killer. You can't keep trying to defend the OS.

Belisarius, don't put words in people's mouths.

Yes replacing the battery resolved my issue, so far. No, I do NOT admit the battery was past shelf life. Apple says it was still good and it did NOT get heavy use in the 1.5 years I've had the phone. I did NOT use battery draining apps like PokemonGo. Quite a few of the others that have had success with a new battery would also disagree with you.

The problem DIRECTLY started after my upgrade to ios 10. I literally remember the next day trying to figure out what happened and uninstalling apps like facebook messenger which I had only installed a few days before. Guess what...the problem started after installing fb messenger, I'm not blaming it on that because removing it didn't fix it. Too bad, I couldn't remove ios 10, to prove my point.

Solution is not always causation. OS imprinting, a theory you posted about may be what made these batteries appear to fail earlier. Maybe the batteries are really bad and IOS 9 just worked with them? I don't know, that's Apple's job to figure out.

I am inclined to agree with Mr or Mrs Lumpypotatoes here. I posted a screenshot a day or so ago showing that my *brand new* 6S plus was suffering from the severe battery drain problem. It can't have had more than 10 or 11 charge cycles at the most. There is no way one can claim that is a bad or worn out battery. No apps were run on it - so one cannot claim it was a corrupt app. The phone was a replacement for a one-year-old iPhone 6S Plus. Which ALSO suffered from severe battery drain. The problems on the previous phone only started when I upgraded to iOS 10. Now I *MAY* be wrong, but the evidence I have experienced here is that *something* in iOS 10 is changing *something* about the way the iPhone manages the battery. It seems to affect iPhones in numerous ways, be that rapid discharge, incorrect display of % or unusual shutdown. Perhaps it is coincidence and I am the unluckiest person in the world, having an old battery fail at the very moment I installed an update, and then a brand new one fail the day I was sent the phone. The ONLY way I could find out would be to back-install 9.3 on my brand new phone. *But I can't do that*. So for anyone who believes the problem is NOT with iOS 10, what happened to my fairly-new and BRAND NEW phones that caused this problem?

Perhaps it is coincidence and I am the unluckiest person in the world, having an old battery fail at the very moment I installed an update, and then a brand new one fail the day I was sent the phone. Most unfortunately, yes. A few were fortunate to have the entire iPhone replaced, no issue whatsoever, 10.2. Yours is the first to whom I read happening.

Ok it just happened to me again. Battery claims 3% power, when it was 100% just an hour ago. Connected to power and IMMEDIATELY--wuup!--80%. 'Low power mode turned off.'

No reboot after connecting to power, because phone thought it still had 3% battery charge remaining.

wtaf. Fix this, Apple. Fix it. Hardware, including batttery, is fine as far as I can tell. This is a software problem.

Not that it changes your opinion about my luck or makes much of a difference, but the ENTIRE phone was replaced, not just the battery. We're talking about a brand new phone failing in exactly the same way as the previous phone, but with nothing connecting them other than the fact I (stupidly) upgraded the brand new one to 10.2 just as I had the previous one.

You should have 90+ days for a replacement or residual Apple Care, I am sure Apple Support with assist you sufficiently to get a working one. Years ago I had an iPhone 4 fail the camera, they replaced it, two replacements came with a pinkish-recalled hue. No issues after. And march 2016 two new Macbook Pros arrived with crashing hardware. same crashes. Apple concluded a batch problem, replaced them, the third is a tank. I am sure these happened to extremely few Apple users.