iOS 10.1 Battery drain

"If the phones aren't supposed to work in higher temperatures such as the ones in Brazil and other places, they were not supposed to be selled here, right? The problem is obviously is not the weather, thank you for the acid answer, I mean it haha" Two years of going about listening to music, in Brazil, I do not see that as being short-changed. All my Brazilian friends also told me that computers and cars last far less due to salt humidity corrosion. But if you got two years out of a battery, over there, do not see it as a negative. Sure, great to get more, but we do not know usage either. My Gf goes running with her iPhone 5 in a pouch, average 22C summertime. Same at 40C in Brazil cannot be the same, right?

You still didn't get what I said. The phone worked pretty well before the update, the battery problems started after I updated to iOS 10. It's not a problem of battery cycles or humid and hot weather as my sister also has an iPhone 6, which is used in the same conditions as mine and happens to be older than mine, and it is working just fine. You see? My wild guess is that, as expected, her phone and my phone were not manufactured at the same time, and as you know, Apple may change, for example, the company which supplies them the batteries from one batch to another, therefore, my battery may have a problem that is not present in hers. So I guess that, with the update, some mad interaction between those "broken" batteries and the new system happened and caused the problem. Was I clear now? I don't mean to be rude or anything, but I'm honestly pretty tired of having a phone which is as useful a rock

Ps: as for the acid answer, I was not referring to you, but to the other person that replied you

And also, I'm sorry but I'm no really inclined to believe that all the phone that are having this battery problems is due to weather or natural decay of the battery, as it is happening with iPhones which were bought less then 6 months ago. Apple already admitted having a problem in some of the iPhone 6s batteries, which is already a win, but I don't think the have any ideia, or pretend not to, of the proportions of that problem.

Anna, you are new here- in a nutshell, everyone here their issue began or were timed with the iOS; 100 pages ago multiple discussions on batteries, different manufacturers. Everything you wrote is known. Perhaps you may also be aware that twelve people here, same symptoms started with the new iOS, new batteries resolved the issue completely. No failures. One is trying hard to damage the new battery with Pokemon Go, as of yet, still strong. Some others got a new phone, no more issue. Others had new phones with the recall serial number, battery replaced and issue was resolved. Being aware of it being time consuming, am pointing you to an authorized center, and to what we know has worked. It is the fastest way to get you fully connected. Unlike chips, screens or RAM, batteries vary from user to user, the chemistry affected as much by environment, use, and as, per recall, manufacturer. And yes, a new installation, with its own calibrations, amperage, safeties, etc can reveal fast if a battery is unable to hold. In some very rare cases, I read online, some people had a bug that a firmware reset. Here on the forum, people that came with the symptoms had the battery as a solution. All and all your perception of variables tells me that you are a very perceptive person, with critical thinking, understanding variables, perhaps an arts and science university graduate.

A few years ago had an iPhone 5 whose battery failed immediately after upgrading to iOS 7. Joined a lengthy forum on iOS supposedly damaging batteries. After Apple Care replaced the battery and the issue was resolved, returned to college science roots and a few hours reading on the science, and ever since, helped me understand that I had it in reverse. Installations stress batteries; shutdowns tie to electric stoppages. People see an iPhone; I see a controller reporting on a liquid, electrons at light speed and ions able or not to function

Sure, anna, again you are right, but you are comparing two different scenarios. Factory storage of lithium elements, at air, which accelerates oxidization and once packed, that battery is accidentally aged with the symptoms described in the recall. Then you can have an 11 months /600 heavy cycles, 15 months /1000 cycles or any 700+ cycles where batteries can reach randomly a similar electrochimical state. Regardless of case, when they go bad, they go bad with similar symptoms. Like in medicine, very known heart attack signs. Very predictable. Now, take a battery that is more fragile, or which has always been discharged fast below 30%, it will be far less reactive than one with same or more cycles but rarely dropped to 0%. Changing amperage requirements, and that stress will be too much. Generally new installations, multiple app and re-syncing for 30-60 minutes will stress enough that battery. In electircal engineerign the word is 'stress'. More you can read in the tabs at: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batterie s

And, as yourself said, you can have new batteries, under recall, reading high health but recalled as defective. Everything works. Another good example you can relate to is auto racing, interlagos. Under slow normal usage those F1 cars can drive thousands of kms at 140 km/hr. But under racing condition, that car oil is only good for 1 race, 300-400kms. So all this to say that it is difficult to forecast the electrochimical state of each one of those 500 million iphones out there, but, every second, some batteries aged beyond what hey can hold. One cycle or heat away from giving up. The liquid is less responsive, drying out, power intermittent, the module starts reinterpreting the %, and may or not shut it down as a safety.

The problem with discussing the iOS effect is that if anyone here could do it expertly, he would be working for 7 figures with any company. People have a hard time understanding that any OS install or reinstall, drivers, etc imposes a stress amperage on the beating heart, i.e. battery. And if it works with higher amperage- just like Pokemon Go is known to do, than the battery was used to the prev 600 cycles, that is self explanatory.

Thanks for the words, I've set an appointment to have the cellphone checked, I'm actually more disappointed than concerned. I only wanted an official answer like, "we now we have a problem, we are working on a solution", you know? I'm also worried with the possible replacement of battery because what if it doesn't work? I will probably have to pay for that replacement, so I see that as a potencial problem. Well, in any case, let's wait. I hope I can solve my problem and that Apple pay more attention to our concerns.

Apple has a 90 day warranty on OEM replacement; in North America major credit card companies also double such period if paying with one.. Might be able to get 180 days but I know that Ccs in Brazil are a bit different.

I too got the same battery issue. After updating my iPhone 6s Plus (which had no battery problems prior before) to IOS 10.2 newest, my phone lost like 30% battery. It would shut down within few minutes from -30% and when I plug it back in to charge it showed I still have 30%? This problem last for an few weeks until eventually the battery kind of sorted itself out. I think the new update software drained my battery more as I read there was an included software to check bad batteries problem. Still, my phone used to last a little much longer playing games. Hope the next software update can get things back to normal. And no my iPhone 6s Plus serial are not one of those affected.

Just to let you guys know about how my situation went...

I've been following every post on this thread and a few others about the problem, in an attempt to fix my IPhone 6s Plus. It had an extreme battery drain, and would drain around 7% an hour in standby. Also the % would skip around 3% at a time occasionally. After absolutely every single thing listed anywhere, I finally decided to send it in to Apple. I'm telling you it's worth it, they overnighted a box to me, which included a label to overnight it back to them. Once it got there, they decided that my phone could not be fix (which furthers my belief it's an IOS problem and they don't want to admit it.) so they sent me a new iPhone 6s Plus, overnight shipping. The whole thing took 3 days. The phone they shipped me has IOS 10.1 and my battery life is absolutely amazing, I've never experienced better battery life in any phones. 2hours and 18 minutes of usage and I'm at 90% still!!!

Thanks for posting, mxmrjoe. Assuming your battery problems occurred after you downloaded iOS 10.1.1, your experiences provide the strongest evidence yet that the problem is the operating system, likely linked to batteries that aren't completely new condition (assuming not everyone who has downloaded 10.1.1 has our problems).

My problems on both my iPhone 6 Plus and my older iPhone 5 (now an iPod Touch in functionality) occurred NOT when I downloaded iOS 10 or 10.1 but ONLY after I downloaded 10.1.1. And downloading 10.2 failed to fix the problem.

That Apple sent you a new iPhone 6s Plus with iOS 10.1 and not 10.2, the current iOS, provides further, albeit indirect, evidence that the problem, even as Apple sees it, is with its operating system starting with 10.1.1 and beyond. If not, why not send you the new phone with iOS 10.2?

Now, if your problems developed in your old iPhone 6s Plus with iOS 10 or 10.1, then it isn't clear that the operating system is the primary contributor to our problems since you are now enjoying uninterrupted service with iOS 10.1. But I still find it interesting, and perhaps compelling, that Apple elected not to send you the new phone with iOS 10.2.

Thanks again.

"it isn't clear that the operating system is the primary contributor to our problems since you are now enjoying uninterrupted service with iOS 10.1." Very accurate. As worded, his statements were self contradictory and the conclusion impossible; namely iPhone with iOS drain, replaced iPhone with same iOS is amazing, therefore, conclusion..iOS? impossible, can only be the changed variable, hardware. The two premises contradict. He proves that Sr Apple Support (with approved authorization and shipment, which myself used a few times previously) resolved the problem with a hardware replacement. Everything else can only be speculation, we will never know. Unfortunately, many users do not have this replacement option and have to take a chance on their next repair step.

"If not, why not send you the new phone with iOS 10.2?" This is just conjecture, proves nothing. Have had an iPhone 4, 5, a Macbook Air and two MBPs replaced this way, none ever arrived with the latest OS, but the latest warehouse state they where in, as they had been delivered waiting for some RMA. As these replacement units bulk up by hundreds of thousands, and OS updates pileup, it is extremely unlikely they ever get opened, seal undone, and manually update. Just does not happen. Cannot read in his iOS version any sort of conclusion.

Mxmrjoe, can you clarify how you went about making this happen -- meaning you got in touch with Apple by phone or electronically and they agreed to arrange this for you, or how? Was your phone still under either original warranty or Apple Care?

Sorry, but no. My old phone was fine until IOS 10.1.1. It was around 4 months old and I treat my batteries perfectly, always have. IOS IOS 10.2 Failed to fix it along with the betas. The new phone however just had 10.1, and absolutely no battery issues.

My phone did not have Apple Care Plus, it only had the original one year manufacturer warranty by apple. I contacted the support via the iPhone app, and just texted them, not call. I told them my problem and after saying everything I tried, the lady said I should send it in and that she can help me set it up. I said no thanks, I'll do it later. So a day later, I went to Apples website and setup a repair there. In the description box under the request for repair, you are to state your problem and how they can replicate it. I was honest, told them of the massive drain in idle and in use, told of the skipping of percentages ( this didn't occur when the last digit ended in a 5 or 0, I was sure to tell them this too, be very detailed!) make sure you include everything and how they can replicate it, I said you can leave it on standby for an hour and see the change. After I had sent my phone I contacted support again (same way) and asked if she could add a few more things to my notes. She did so for me, but the way she worded it made her sound like a technician so I think that helped a bit. The phone was in "diagnosing" for hours so I think they were actually experiencing the drain and searching for a hardware problem, but failed to be able to find what it was, I think that's why they sent me a new phone. Because like I said, it didn't start until 10.1.1, so I think they didn't want to admit it was a software problem so they just sent another.