running on 5s.battery is average. no shutdown.. only annoying update apple music.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Says iOS 10.2.1 Update Has Significantly Reduced Unexpected iPhone 6 and 6s Shutdowns [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Something tells me this is just to get people who are still on iOS 9 to upgrade to iOS 10 so that the graphic show a higher % of people on iOS 10. Why does this trend sound familiar?
Kind of sketchy? Really that's all?
Ok let me get this straight, Apl soldiering without protection is scause of the IC chips coming loose inside as described in great detail by iFixit...a design flaw (because they eliminated the shield covering to save on cost a few cents) . they after months of refusing to admit they had a problem, finally after uproar they come up with pay $149 to have it fixed..and replace it with another flawed phone?
That's far beyond sketchy , its consumer abuse.
All 6/6+ have this design flaw.
They should have recalled all of the iPhone 6/6+ which are ticking disasters and replaced them with that original 90,000,000 order they had to scale down with the "now fixed design" and done the right thing for consumers...but no its another cash grab of the consumer (not at fault) paying $149 to have it fixed,
So Apl finally makes a bigger phone and reduces structural redundancy? Gee what great decisions Apl.
Ridiculous. More ridiculous people still trust them.
Last edited:
They could send something like a push notification to the OS itself to enable a hidden element of the UI. You normally wouldn't want to do this as could be confusing to the user but on something very minor this could be done.
I have to say, I had much less sudden shutdowns in last couple of weeks on my iPhone 6. I attributed this to the warmer weather as for me this really only was an issue when the ambient temperature was close to freezing (and I held my phone for long periods in my hand so it could cool down to something close to ambient). But it is possible that 10.2.1 also contributed to this improvement.
Last edited:
I got lucky. My wife's 6s and my daughter's 6 escaped the shutdown issues.
[doublepost=1487901632][/doublepost]
[doublepost=1487901632][/doublepost]
I'm not wearing my glasses so I might have missed it in the article. Where did it say it affected the majority?
but the bigger emojis and sticker packs were worth overall system lag and auto shut down on iOS 10. Looking forward to the mess that inevitably will be iOS 11.
Sharing my personal experience: my iPhone 6 was always shutting down just under 40-50%. After the update it hasn't happened once, so YAY! 
It's called manufacturing variations. A lot of complex products suffer from some variations during manufacturing. Whether something rises to the level of warranting an out-of-warranty free repair (or even a recall) depends on three main factors:
a) How egregious was the error made during manufacturing?
b) What percentage of users (within an identifiable subgroup, eg, defined by production batches) are affected?
c) How much does the issue affect the user or could even cause damage to goods or life?
The last one can trump both conditions (a) and (b), see the Note 7 debacle, it certainly wasn't restricted to a subgroup and thus the actual percentage of affect users was pretty small and at least at the time of the recall no egregious error in the manufacturing process had been found but the danger when the issue occurred was pretty high.
Usually, condition (b) is a requirement for an out-of-warranty repair though if (c) is fulfilled (without the danger part) and the issue doesn't seem likely to be caused by the user a goodwill exchange essentially can be made by implicitly assuming condition (a) to be fulfilled as well. But for any official recognition of an issue, you need to satisfy condition (b).
Last edited:
It said within a few days. So assuming its there just not enabled and somehow they will enable it in a few days. Supposedly you want see it unless your battery is deemed as needing replacement. So not seeing it is a good thing.
"Manufacturing variations"? I'm calling you out on your ********. DESIGN flaw. It was DESIGNED poorly. It was their DESIGN that causes this. It has been documented by experts EXACTLY what they changed and WHY it's a design flaw.
A design flaw affects 100% of the devices. Or at the very least 100% of the devices that were subjected to certain level of wear and tear (that still falls squarely into the normal usage bracket).
My point is that if you were to look at the eventual failure reasons (besides clear external damage) of devices after their normal usage span (eg, five years for phones), you could argue that everything that fails is a design flaw as it could have been designed to last longer. Thus only devices that last forever are without design flaws (or manufacturing errors). All I want to say is that failure of any component really only becomes egregious when it can be shown that more than X percent of the devices are affected. Below that threshold, it is called bad luck.
Really, I am not commenting on any specific issue. I am just saying that making an egregious error (in the design or during manufacturing) alone is not sufficient for outrage. You also need a high enough percentage of affected devices. Depending on how egregious the error was and how much the user was affected, that percentage can be pretty low. But imagine if exactly 3 out 3 million shipped Note 7 devices had caught fire. Would that have been enough for a recall?
A TON of Iphone 6/6+ repairs showing up at repair shops is (more than X ) especially with Apl's self-professed uncompromising standards they hold others too AND the exorbitant prices paid.
It's not a hack to address the issue, but something there to help those who might still experience it for some reason to be able to potentially recover from it easier at least.
I did wonder why I was getting persistently pestered to install the updates after every unexpected shutdown at between 30 and 40%. All you had to say was "It fixes the battery problem" in the first place, Apple.
And I had my iPhone 6 replaced after 18 months, out-of-warranty, by Apple, after Bluetooth stopped working. Stuff happens, how you (as a company) react to it, is what matters.
We can talk about 'shoddy design' but only with numbers (percent of devices needing repair after X months/years). And those numbers have to be put into context (ie, compared with other brands, or other electronic devices of similar price range or of similar relative prices to their respective markets).
What a difference five years makes in the life of a company. I remember a time when stuff like this happening was an exception, not the norm at Apple but I guess whatever makes Timmy the most money at the expense of everything else.
No , you can directly compare to previous designs form Apl and see "clear as day" the fatal 6/6+ design flaw side by side . IF its flawed that egregiously after deviating from a know good design then its not fit for consumer consumption. only reason they skated on this , is it wasn't a safety issue just a horrible design lessen cost deceitful issue
Last edited:
They "reduced" the issue, did not fully fixed. My 5s still has this damn problem. Even at 45% charge, it shuts down unexpectedly.
My problems with the battery and 10.2.1 were only solved after I payed 50 bucks to replace the battery.
I don't believe Apple anymore.
I don't believe Apple anymore.
My iPhone 6 will shutdown below 70% when exposed to cold or jump from 68% to 9% at times but as soon as you plug it in it jumps back to 68%.
And sometimes it stays at 1% for over an hour with regular use.
But I figure this is happening because it's over two years old and needs a new battery.
[doublepost=1487908631][/doublepost]
Right now 10.2.1 is 14D27. The next might be 14D30
And sometimes it stays at 1% for over an hour with regular use.
But I figure this is happening because it's over two years old and needs a new battery.
[doublepost=1487908631][/doublepost]
Apple can release an updated version of 10.2.1. I experienced that with 10.1.1 After I updated iTunes kept saying there was this same update. I reapplied the update and the version bumped up a few digits.
Right now 10.2.1 is 14D27. The next might be 14D30
We have had many recalls, voluntary repair programs, class actions suits and similar with Apple products over the last 20 years (let's call it the second Jobs era). I'm afraid, you have not convinced me yet that the iPhone 6 and 6+ was a serious aberration from all the other Apple products that came before it. To convince me, you need to show me numbers on all Apple-acknowleded repair programs on all their products from the last couple of years that demonstrate that the iPhone 6 is a clear deviation.
Last edited:
That pretty much goes for any issue ever...
[doublepost=1487910412][/doublepost]
In some cases it is an actual worn battery issue. That's not to say that that's what it is in your case, but depending on how old your phone is and how many charging cycles the battery has gone trough, it certainly can be a decent possibility.
My 6s plus has never unexpectedly shut down nor has my wife's 6 plus or 7 plus. Most of these problems are always in America.