Slashdot Mirror
iOS 10.1.1 Is Causing Battery Issues For Many iPhone Users (itwire.com)
An anonymous reader writes: A recent iOS update to 10.1.1 fix Apple's Health application has had unintended consequences for many users -- shutdown at 30% battery remaining and lack of audio using Apple Earpods. Users on an Apple forum report that the battery indicator jumps from 30% to 1% (dubbed the 30% bug) and a reboot is required where the phone then runs for a few more hours. Some have taken the iPhone back to receive a replacement only to find the same thing happens. Apple has not responded to the 11 pages of forum complaints but apparently, Genius Bar staff have identified unusual discharging of the battery -- which does not make sense if a reboot temporarily fixes the issue and returns the battery indicator to 30%. It also appears to affect all versions of iPhone that support iOS 10.x.
Apple and Samsung are having it rough this year. It almost seems like the neck-and-neck competition is causing everyone to skip QA.
It's a feature not a bug.
1) If your battery doesn't drop below 20% it doesn't degrade as quickly. Keeping your battery always between 20% to 80% will make your battery last longer.
2) The earbuds not working is just an upgrade to get older apple devices working like newer ones.
"That's the way to do it" - Punch
...you're discharging it wrong...
Imagine trying to test all the different types of hardware the code is to be deployed on... I mean, how could a small company like Apple afford to pay enough testers perform tests across a DOZEN (!!!) different pieces of hardware! Insane! It might even cost a million dollars a year!
I'm typing this response on my perfectly fine iPhone running 10.1.1 and jK$1...[NO CARRIER]
What the hell do those do?
You didn't read the updated EULA? You now share your battery 70/30 with Apple's advertisers and the NSA. Tim Cook was heard saying "I altered the deal. Pray I do not alter it any further."
I used to think Apple was the best choice for the phone because of the quality and reliability of the software. Now that my iPhone 5S has issues with it's lightning port, the battery drains like a madman with the new IOS, and clearly QC at Apple is not what it used to be... I'm looking at alternatives... preferably ones that won't catch fire.
What really frustrates me, and why I'm moving more towards open source software, is when they purposely design things so you will simply buy a new one. Example: on my iphone 5s, I keep it in Low battery mode, so the battery almosts lasts all day like it used to before the update. When I charge it, I have to watch it, because apple will turn the damn switch off automatically. They could automatically detect the their shitty software is draining my battery, or they could have options for me to turn off to improve battery life... but they'd rather I buy another $800 replacement and sell my used one for $150.
I hate to break it to Apple et al, but this symptom is not new. Had this on on our iPhone 6 going back over a year with my wife's 6s.
Apple, which has usually been good about these things, refused to replace the phone. I had the same issue on my last 6... I just held out until the 7 came out since I didn't feel like arguing with an Apple employee about it AGAIN.
My 7 has not had the issue... yet. But not I'm wary it will return since, if this story details are accurate, we're talking about software not hardware issues.
David Whatley
Funny to see how the great Apple is turning into a scam company... How long before Apple zombies wake up?
Acoustic coupler for a cell phone to have internet connection?
What are you, a hipster?
But it's so easy to use! I use it because I'm not a dork, and it's easy to use for real people, dorks!
Having very few hardware devices makes testing and deployment easier, but a huge swath of your customer base may be hit when a bug gets through.
Cwm, fjord-bank glyphs vext quiz
is the first truly 'nagware' version of iOS.
I usually wait a few weeks before installing upgrades for reasons like this. So when the 10.1.1 upgrade floated across my iPad, I did the usual and deleted it to save space and would manually install it later if no serious bugs were reported. This has worked with previous iOS versions in that once deleted, the upgrade would have to be manually installed and would not be automatically downloaded again.
Fast forward to iOS 10.1.1. Same process: iOS 10.1.1 upgrade automatically downloads (all 1G if it), I get prompted to install it or remind me about it later, I delete the upgrade to save space and everything is right in the world. Uhhhh - NO! Next day the 10.1.1 upgrade downloads itself again and again I get the install/remind message.
After a couple of rounds of this (download, delete, automatically download again), I gave up and stopped deleting it (to save myself from more 1G downloads) and just defer the install.
So in addition to the latest iOS upgrade glitches, iOS 10.1.1 has become the first version to be officially classified as nagware.
My 5S exhibited this battery problem once - went from 30% to about 5% in maybe 5 minutes.
The curious thing is, this was with 10.1.0. With 10.1.1 it has been just fine... and I'm one who uses this phone to make actual phone calls (not facetime, not sms, not imessage) that last 3, 4 hours. I also watch video on it, listen to music, stream to apple tv.. so yeah, this old phone gets used.
So, maybe this is model dependent? TFS says "older hardware" but my "old" 5S doesn't do this.
The "Civilized World" jumped the shark ca. 1973.
1) If your battery doesn't drop below 20% it doesn't degrade as quickly. Keeping your battery always between 20% to 80% will make your battery last longer.
So how come it continues to charge after hitting 80%?
Seriously though, having a "do not charge past 80% without having me answer a dialog box first" settings option would be a good thing for those of us who hardly ever drop below 40% on a normal day.
The cynic in me thinks the reason we don't have this already is that someone has patented the idea (don't bother to do a patent search, they probably used oddball terminology so they can lay in wait for infringers and hit them with $BIGBUCKLAWSUIT, sigh).
The non-cynic in me just supposes that, prior to the Samsung debacle, almost everyone cared more about "how much time do I have left until recharge" rather than "how many months left do I have before my battery needs replacing." As for me, on most days, I'd be fine with an 80% charge, but when I'm expecting to use the phone a lot in a given day without access to a charging station, I want to top it off the night before.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
A phone that runs on AA batteries is an idea that's past its prime for most customers. 10 years ago I would've jumped at something like this if it was under $10 for the phone and all I needed to make it work was a GoPhone-priced contract and a bunch of AA batteries.
Today, you can get a power-boosters for well under $20. If you are planning a trip outdoors and away from your car battery, get several of those and change them before you leave. Of course, if you are in an area without cell service, well, you won't be using a cell phone to communicate with anyway. I recommend a satellite phone or, depending on where you are going and if you are licensed as a ham, a ham radio, business-band radio, or even a CB radio along with the antennas you will need for your particular situation. I'm not familiar with all of the emergency-communciations equipement available for outdoorsmen, but I would be surprised if the "outdoor sports industry" didn't already have this issue covered.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
Good, I was just about to start considering replacing my battery. I'll wait for the inevitable patch. Just annoying because I've now had several instances where I needed my phone, and wham... shutdown at 20-30% for no apparent reason. I just assumed it was an older battery starting to fail.
Everybody I know who has seen this issue (counting me, that's six), and every note of this issue on Apple's community forums that mentions the SoC manufacturer, have one thing in common: Samsung manufactured SoC.
I have a TSMC manufactured SoC, and I don't have this problem anymore.
Spin the genius bar return wheel until you get a working phone. It appears to be a hardware defect, and being saddled with a flaky device is too much to bear.
I've kept my iOS devices on 9.x and each one nags me several times per day. I hate being interrupted when I'm trying to start a phone call of respond to an IM or ...
It hasn't yet reached Windows 10 levels of nagging, but Apple is clearly comfortable with going there.
As per the recent article: https://mobile.slashdot.org/st..., there is also a recall on the iPhone 6S due to a battery hardware failure which causes the phone to shut off anywhere between 5-40%. I just swapped the battery on mine through their recall program and it fixed it.
I noticed that the iOS 10 update included new firmware for the cellular electronics.
Since going to 10, and especially on 10.1.1, I've noticed worse connections on LTE, and Bluetooth.
I think they made a mis-optimization that uses more power and causes worse signal on my 5c.
I have to restart the phone often now, since it will not receive or send texts or phone calls until I restart.
Battery life and device temperature are both higher than before.
I think they messed up the firmware update, and the radio is working worse or getting into a loop condition and using up battery trying to push the cellular connection.
The issue is when the iOS does an over the air update. The data for the battery software gets corrupted and starts reporting false information. The way to fix this is to use iTunes. Do a full backup and then put the device into recovery mode and restore it. This method has worked every time so far.