Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Bug Iphone Apple

iOS 10.1.1 Is Causing Battery Issues For Many iPhone Users (itwire.com) 91

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.
This discussion has been archived. No new comments can be posted.

iOS 10.1.1 Is Causing Battery Issues For Many iPhone Users

Comments Filter:
  • Apple and Samsung are having it rough this year. It almost seems like the neck-and-neck competition is causing everyone to skip QA.
    • Re: (Score:3, Insightful)

      by Anonymous Coward

      The iOS issue is a software bug that can be fixed with another update. You seriously think that's in any way comparable to hardware issue that causes phones to burst into flames and forces a total product recall?

      • And I fixed it by doing a hard reset on my iphone6s.

        Press and hold power+home button for 15 seconds.

        Now battery life is better than ever.

    • by Gr8Apes ( 679165 )

      Apple and Samsung are having it rough this year. It almost seems like the neck-and-neck competition is causing everyone to skip QA.

      Yep, phones are bursting into flames everywhere causing the gorilla in the phone market to recall all its phones. Wait, that's just Samsung. Meanwhile, Apple has uncovered a couple of bugs in a brand new OS that's been out less than 2 months. And yes, there are some significant changes under the hood, attempting to fix some of the core issues introduced in iOS9, which was unstable throughout its lifetime. However, 10.1.x seems to have regressed somewhat and a few more of those underlying issues appear to st

      • the gorilla in the phone market

        Is that anything like a bull in a china shop? Just seems like a bad idea from the start.

        Maybe the phones bursting into flames was to protect you from said gorilla?

      • by I4ko ( 695382 )

        Exactly. IOS 9 and 10 were not needed. They didn't bring anything really new, only made things harder to use. The best IOS version was the IOS 8 before the update that introduced Apple music. There was absolutely no reason to make changes, except to support new hardware.

      • Apple and Samsung are having it rough this year. It almost seems like the neck-and-neck competition is causing everyone to skip QA.

        Yep, phones are bursting into flames everywhere causing the gorilla in the phone market to recall all its phones. Wait, that's just Samsung. Meanwhile, Apple has uncovered a couple of bugs in a brand new OS that's been out less than 2 months...

        To attempt to diffuse the pissing match between Apple and Samsung, let's take a look at the iOS issue a bit closer.

        It's a bug that appears to affect older hardware.

        Seems the attempt to remain backward compatible to justify their obscene pricing model for cellular hardware has finally bit them in the ass. Or has it?

        Given the fact that Apple's latest line of "Pro" hardware comes in a nifty sealed case, devoid of all upgrade paths (including the hard drive), I wouldn't be surprised to find that this "bug" i

        • by Gr8Apes ( 679165 )

          I only know that the iOS bugs have been issues for me, personally, since iOS 9 came out. No, it's not just problems on older hardware, not withstanding the headphone jack going dead, which obviously can't happen on an iPhone7. iOS 10 looked like it fixed a few of the major ones, but that was only the first week or so of playing around with it. It appears the root bugs are still there, although they've been bandaided over so the occurrence is much less often. The major actual app failure I used to see has n

        • their obscene pricing model for cellular hardware

          There is very strong empirical evidence that Apple sells their stuff for prices lots of people are willing to buy. Moreover, iPhones are reasonably priced for top-end smartphones, which they are. Apple isn't interested in competing for the low end of the market.

          I'm nowhere near convinced that the new MacBook Pros are a good idea, but then I never have owned an Apple laptop.

          • by Gr8Apes ( 679165 )
            I've owned several MBPs (2006, 2009, 2011, 2012, 2013, and 2014) several personally. I can say that through this year, MBPs were some of the best laptops out there in terms of performance and quality constructions, despite the decreasing ability to fix things yourself. I have not compared the newest MBPs so I cannot speak to them. As for performance comparisons, I'm comparing it to a slightly older hex-core desktop outfitted with SSDs. The performance between the two is comparable for most work loads, which
      • I think your fanboism is showing. I also wasn't just talking about new iOS devices. Crap video implementations causing phones to lock? Touch death? If you think these are a couple "minor" issues you probably should keep quiet - you are tarnishing your own brand.
        • by Gr8Apes ( 679165 )
          Not my brand. And you'll note I'm critical where Apple deserves criticism. Sadly, that's in more and more areas of late. It may actually happen that I move onward to something else in the future, but Apple will need to fall further both in usability and reliability or the current crop of alternate hardware software will need some major improvements before I'd hop on their platforms. Android is still a mess, maybe with Google taking stricter control they may be able to wrestle something reasonable out of it.
  • by Oswald McWeany ( 2428506 ) on Monday November 28, 2016 @09:08AM (#53376749)

    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.

    • by 110010001000 ( 697113 ) on Monday November 28, 2016 @09:21AM (#53376827) Homepage Journal
      Basically the people complaining lack courage.
    • Yeah but then the battery indicator is still wrong. It should be adjusted so that the indicator maps 0-100 to 20-80.

    • by AmiMoJo ( 196126 )

      Modded as insightful as funny, and a few troll mods from the fanboys. A lot of people really missed that whooshing noise, huh?

      FWIW you can generally charge LiPo batteries to 100% without issue. Nissan used to offer an 80% limit mode on its electric vehicles, but removed it because it didn't make any difference. Modern LiPo chemistry doesn't care, as long as you don't over-charge it. You can generally get down to about 10% before it starts suffering noticeably faster degradation too, and the battery itself u

    • 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

      • by dgatwood ( 11270 )

        So how come it continues to charge after hitting 80%?

        Because that's a lot of capacity to lose. I doubt that the difference between stopping at 80% and stopping at 100% is enough to be worth the rather significant loss of capacity.

        That said, the OS already does various tricks to minimize the damage caused by fully charging the batteries. For example, in OS X and iOS, IIRC the top several percent are hidden. When the charge level hits about 95% (I forget the exact number, and it might even vary depending o

    • Yes, I can confirm this feature.

  • by thatkid_2002 ( 1529917 ) on Monday November 28, 2016 @09:25AM (#53376855)
    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!
    • What is the point of testing when you know people are going to buy the product in droves? Seems like a waste of a million dollars to me.
      • by AmiMoJo ( 196126 )

        Problems like this always have costs. Some people will return the phone to the place they bought it from for a refund or replacement, costing Apple money. Some people won't buy another iPhone because of the bad experience, or because of all the problems they read about online.

    • even cost a million dollars a year

      I know some Indians who'll do it for $10k

  • I'm typing this response on my perfectly fine iPhone running 10.1.1 and jK$1...[NO CARRIER]
    • The new iPhones have PCMCIA 14.4k baud modems.
  • 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 har

    • by Anonymous Coward

      Way to go, Mr Consumer!
      You had a phone that exhibited the problem. The company had bad service and refused to fix it.
      So, you bought a new phone from the same company?

      Are you familiar with the term 'negative reinforcement'?

  • 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.

  • by Anonymous Coward

    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 aut

  • 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.

  • 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... [slashdot.org], 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.

"If you want to eat hippopatomus, you've got to pay the freight." -- attributed to an IBM guy, about why IBM software uses so much memory

Working...