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
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]
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
Look at this. https://www.att.com/cellphones...
It is the best replacement for a smart phone since sliced bread.
What do you mean, "your battery"? It's Apple's battery; you are just holding it for them. Holding it wrong, I might add...
Jokes aside, I've found Apple's hardware to be mostly reliable, but I too get ticked off by software updates that seem designed to make you get a new phone. Still, my wife is still happily using her 5s, and I have a 4s test phone that still works well. Even got a pair of 3GS phones doing duty as wall mounted control panels for home automation. The one time we got burned by a software update was when it fried the WiFi chip in a 4s (and Apple didn;t offer anything out of warranty on that one)
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
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
The batteries in the older 5s phones are reaching end of life. I've replaced several of them for clients. It's a really simple battery swap if you're good with tools, but check here first to be sure you're not covered for a free battery: https://www.apple.com/support/...
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.
Acoustic coupler for a cell phone to have internet connection?
Don't laugh.
In about 1993 or so, I was affiliated with an organization that provided dial-up internet for people affiliated with it. When PPP was relatively new, I cranked my 14.4 modem down to 300 bps just to see if it would work.
It did. The connection was rock-solid. No dropped packets. Granted, I could out-type the character-echo in a "telnet" window (they didn't have ssh back then), but it was rock-solid. I've had worse (but still working, barely) service in the past year when my cable company was having problems and dropping 20% of packets.
A year or two later, the organization providing put out a bulletin saying they would stop supporting anything slower than 2400. I'm pretty sure the organizaiton stopped providing routine dialup service ages ago.
By the way, thanks to audio-compression and other factors, a plain-jane old-fashioned dialup modem probably won't connect at anything better than 2400 bps (historical note: acoustic-coupler modems that went faster than 2400 bps were uncommon - it was simply too hard/expensive at the time). You'll probably get a better quality connection at 1200 bps or 300 bps. If you need to use a serial connection on your computer at faster speeds, there are ways to do it, but not using an old-fashioned dialup modem.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
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.
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.
Nothing! Apparently.