No difference if I completely power off and reboot the phone. Usually within a few minutes of restart, it starts running hot and the battery indicator will almost visibly run down without me doing anything on the phone itself (and with all background apps shut off).
The phone's "Battery Usage" list is useless, as it shows things like Mail being used for 3 minutes, and using 25% of the battery power since last charge. Varying apps are listed as huge battery sucks even when I don't think they are (Calculator anybody?!?) At this very moment, it is saying that Apple Remote took 26% of the battery charge, Messages took 11% and the Home & Lock Screen took 9% since last charge - about 30 minutes ago!
Things that I expect to suck up the battery, like the Moves app, says only 2%.
I've even plugged my phone into my PC and gone into XCode to check the logs to see if anything is standing out, but nothing in the logs point to a particular app or process chewing battery time.
Immensely frustrating. Another dev friend of mine has said that the iOS 10.2 beta has fixed most of his problems, so I may download that from our developer account and see if it works.
EDIT: Just thought I would point out that I have done a full factory reset on the phone and restored from iTunes backup twice now, with no improvement at all.
I'm not sure why or how things got better. At first I could see the battery power dropping in almost real time. Using safari for a few mins would bring me from 90% to 80%! (Eg - more than 1% drop per minute).
I then disallowed almost all apps permission to refresh in the background. But that didn't really help much.
I also noticed the phone seeming warmer than usual. But I wasn't sure if I was imagining that, being biased by the quickly-depleting battery.
Agreed that the battery usage tool isn't very helpful. I think it just shows which apps were used by % of time in foreground, not by multitasked allocation. Eg, this was dominated by Safari and mail for me.
I also let the phone completely discharge a couple times and recharge fully. Some people say this can help condition the battery, though I'm not sure how much truth to that for these batteries.
But after a few days things just went "back to normal", and I went back to getting a fully day's use of charge. I haven't changed my permissions back, so most apps remain without background execution priveledges. I haven't noticed any limitations to my productivity with this change.
FYI - I basically charge my
phone daily, overnight when I go to sleep. I'm usually around 20-30% when I plug it in for the night.
But nearly two months later, the problem continues unabated. The heat is a real worry as it is too uncomfortable to have in my pocket anymore (the metal edges become almost too hot to touch), and I am wary of charging it when I am not nearby to monitor for any problems (oddly - it doesn't seem to heat up so much when charging, but I want to be 100% sure).
On that note: Apple support in Germany is severely lacking, compared to the US.
I had a display issue with my brand new (company support contract covered) MBP's screen in 2014. the left 25% of it went into becoming colorful pixel stripes.
I was on a business trip in CA when it happened. The Apple store in Carlsbad, CA, was happy to replace the screen for free. But it would take two weeks.
As I had to fly back to Berlin, Germany, a week later, I booked an appointment in the Apple flagship store on Ku'damm there instead (2 weeks waiting time!).
I was 5mins late (finding a place to park there is difficult). They told me my appointment had ceased and I needed to book another one. I complained but no avail. So I did book another.
Another two weeks later I finally could show them my screen.
They told me I had caused this and I needed to buy a new screen.
Oh yeah, they were arrogant too.
If there's something we still haven't figured out in Europe (vs the US) it's great customer service.
I contacted Apple Italy (I live here, bought it here) and was perfectly candid about what happened and the fact that I recognised it was my fault but wanted the screen replaced (at my cost) anyway. The waiting time was quite long.
So long in fact I mentally calculated it would make more sense to book an appointment with Apple in New York and had it fixed there whilst on a business trip.
So I went to the store in NY at the appointed time, very candidly explained what had happened and that it was my fault, fully expecting to be charged — and instead they fixed it for free in less than 20 minutes.
I was stunned.
After several trips to a service point, eventually Apple told me that this is not a hardware issue but a software one and to expect an iOS update that will resolve the issue. No estimates as to when that would be. I asked if it's ok to try the public betas to see if the fix was in and an Apple support rep said it's fine. Unfortunately the latest public beta doesn't fix this. As of now I just assume that my battery indication is off by 40% and I treat my phone as if the battery is empty when I'm out and I see it drop below 50%.
I never understood how people are happy to pay premium prices and possibly an AppleCare when you still have to book appointments weeks in advance and go to a store in person.
To quote - "Under EU rules you always have the right to a minimum 2-year guarantee at no cost.
This 2-year guarantee is your minimum right. National rules in your country may give you extra protection: however, any deviation from EU rules must always be in the consumer's best interest."
This is also on Apple's customer support pages when you check if you're still in warranty. It says that local rules apply when you're out of Apple's limited 1 year warranty.
To directly quote from the article you posted:
"But, after 6 months in most EU countries you need to prove that the defect already existed on receipt of the goods, for example, by showing that it is due to the poor quality of the materials used."
But it's nothing like that now. Apple is back to 1 - 2 week wait on repairs, just like the third-party repair stores before the Apple Store existed here. Much of the point of AppleCare for me - same day repairs in any major city around the world - is gone now.
I took my phone into an Authorised Service Provider, who ran a diagnostic and said there was nothing wrong, but that the symptoms I described matched up with a software issue that had been acknowledged by Apple. Apple’s documentation on the issue, they said, indicates that resetting the phone to factory defaults will resolve the issue, but if you then restore a backup affected by the issue, the problem returns. The Authorised Service Provider advised me my best bet was to either wait for Apple to fix the issue, or take my phone into an Apple Store.
After waiting a few more weeks, I took my phone into an Apple Store. The Apple Genius that helped me confirmed the Authorised Service Provider’s take: that the issue was an acknowledged software bug. The Genius commented that he was surprised it hadn’t been fixed yet, because Apple had acknowledged the bug quite some time ago.
The Genius offered to replace my phone under warranty, noting that it might not fix the issue, but that was all he could do for me. I accepted the replacement, and thankfully the issue has not recurred with the new phone, even though I restored my backup from my old phone to it.
My spouse, whose phone was bought at the same time, was also affected by this issue, and was also able to obtain a replacement from our local Genius Bar. The problem has not recurred for her new phone either.
It's not normal battery drain, nothing could cause the battery to jump from 30% to 0% instantly. It wouldn't explain the percentage jumps when plugging back in, or how usage in the cold causes shutoff when under 50%.
I fear Apple knows there is a defect in millions of 6/6s devices and they are hoping they can ride it out though natural phone attrition.
Just started yesterday. My phone gets hot (not Samsung fire hot, but pretty warm) when the battery level is plunging, which suggests that something is actually chewing up wattage. At least in my case.
The strange thing is that my partner has seen the same issue on an iPhone 5 since 10.1.
Lesson Learned: put off system/app upgrades until after travel, stick with the tried and true.
I'm used to this for work (e.g., always perform upgrade on Friday afternoon after close-of-business) but it is a new phenomenon to apply my work practices to my personal phone!
The battery will drain extremely fast (typically lasts about half a day, with light usage), and will randomly and suddenly die when reporting 20, 30, or even 50 percent remaining.
The unpredictability of when the phone will completely die makes this problem particularly frustrating.
Connecting a charger cable results in it immediately reporting 20/30/50 percent battery again.
Have already had a Genius bar appointment to resolve. The 'Geniuses' ran the usual battery diagnostics, and said the battery was close to their 80% threshold, but were adamant a full restore would resolve the issue. They were rude and dismissive, and point-blank refused to replace the battery, or handset.
I did a software restore, and lo and behold, still have the issue.
Reset all settings
Run battery to flat and then charge to 100%
Restore entirely from backup
Look at running processes with Instruments (normally MediaAnalysisD was pinning the CPU even when in standby)
Switching basically everything off (background refresh, mobile data, etc.)
Nothing made any difference at all.
The battery was draining at roughly 1% every 8 minutes, even when it was in flight safe mode. In use, I would be at 20% battery by the end of the day, whereas my old 6 would normally be at 60-70%.
There is definitely something going on that Apple can't work out, even when they run diagnostics on the handset.
Their solution in store was for me to format the phone and run it with nothing installed, etc. for a couple of days. I basically expressed clearly how this wasn't an option for me after having paid so much money for a device that I'm reliant on for business communications and eventually they gave in and swapped the device, since then it's been a night and day difference. I get to the end of a day on 75%.
ÉDIT: as I was typing the comment, the level actually dropped from 22 to 1!! About to go dark :)
How I fixed it: Settings > Privacy > Location Services, and review which apps are constantly using GPS.
This would line up with other's comments on it magically fixing itself after a few days.
Do not store photos on the iOS device.
What I am not sure of is whether iOS will attempt face recognition on photos transferred to it from another source.
For example, the Sony M5 has a very unpredictable glitch - it did have a "workaround" (unlike this iPhone bug) but which significantly degraded usability - it was to to resort to 3G WCMDA network, 2G GSM GPRS/EDGE. I'm glad I didn't get it (free off contract)
SoC chips are far more predictable because they don't degrade as much as batteries do, they're more "solid"/"fixed". That's not to say they don't have issues, companies do have yield issues and defects but they're caught at the very beginning, not later. That's unlike batteries because their issues are often caught later after they're out of the factories, it's why Samsung was surprised. They wouldn't be stupid to sell bad batteries to destroy all of the momentum they had going.
Apple tends to have more technology in their batteries to ensure they don't overheat, charge consistently and so on but that doesn't actually resolve all of the chemistry issues.
When you have an unpredictable part, you're bound to have unpredictable issues with software.
In this case, it's not the battery that's giving Apple issues, it's the combination of software and battery. Apple is just at the point where everything is so complex that it is virtually impossible to fix them quickly and to get it right the first time. However, Apple can and needs to step up and offer free battery replacements, stop with these BS programs they have for iPhone 6/6S now.
Anyone else have this happen? (Carrier: EE in the UK)
Who knows, maybe Apple has decided to include Google Play Services in ios 10.1 ;)
(not for any ideals mind you, but because of limitations of the store sandbox)