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 Now Faces 26+ Lawsuits for 'Purposefully' or 'Secretly' Slowing Down Older iPhones
- Thread starter MacRumors
- Start date
- Sort by reaction score
Doesn't mean they can't miscalculate, or in the case of the gigantic application envelope of the iPhone and the notoriously fickle characteristics of batteries in general, mis-GUESS...
Good for you, so what? it still hasn’t helped with you understanding what people are saying. Or why they are raising law suites. And you shouldn’t presume People shouting loudest are not technically experienced... because you have no idea who they are or their history and knowledge.
Only on your device. Not so on many many other iPad devices. Why is yours different? Maybe it's badly misconfigured? or otherwise broken...
The rub in all of that is the "Certain Conditions" phrase.
The Application Envelope for something like an iPhone is uncommonly-HUGE, and the variability of batteries is also quite large.
Put those two "Huge" and "Quite Large" pools together, and what you have is something that DEFIES anything like ***ACCURATE*** failure-rate-analysis theories, Six-Sigma Process Control, and hi-rel engineering practice, Mr. "I know some engineering terms to throw-around".
And as far as Engineering "Ethics"; what do you mean by that side-swipe?
Can jail broken phones even install new iOS? I don't know, that's why I'm asking.
If I ever experienced shut downs like this on any phone I used, I would decide I needed a new battery or there was a faulty connection to the battery. Apple masked this by just slowing the phone, which would lead me to the conclusion that the phone was now not up to the software demands. By not giving a message that the battery may be needing replaced it leads to the obvious conclusion of deception.
You are correct.
I am judging by apparent technical knowledge-level of the online posters on several forums.
I am an engineer; that's just the way I talk.
Or maybe, just maybe, it is FACT after FACT.
Ever consider THAT possibility, even ONCE? Of course not!
It was speculated that the only thing intensive enough to trigger the throttling was the benchmark & battery test apps themselves - so that is where I am coming from.
Apps are launched all day, every day. So how does it make sense to say "only during peak usage" when it is triggered all the time.
Anyway, even typing a text message resulted in 1-2 second delays in key presses on the throttled iPhone 6 that I had. Does typing an iMessage also constitute "peak usage?"
Is scrolling "peak usage?"
Is "Apps refreshing in background" peak usage?
Direct quite from Apple web site:
https://support.apple.com/en-us/HT208387
...the user may notice effects such as:
- Longer app launch times
- Lower frame rates while scrolling
- Backlight dimming (which can be overridden in Control Center)
- Lower speaker volume by up to -3dB
- Gradual frame rate reductions in some apps
- During the most extreme cases, the camera flash will be disabled as visible in the camera UI
- Apps refreshing in background may require reloading upon launch
- Cellular call quality and networking throughput performance
- Captured photo and video quality
- GPS performance
- Location accuracy
- Sensors like gyroscope, accelerometer, barometer
- Apple Pay
Last edited:
Considering how FB contrives to make you depressed, co-dependent, and totally pliant to their
undisclosed agenda, folks shouldn't just be OK with their phones shutting off when they open FB, they should be grateful!
What I don't "get" is how you call people yelling the loudest are the same people with the LEAST amount of actual technical knowledge/experience.
Care to connect the dots for me?
Are people like you being deliberately obtuse. Phone random shutdowns directs people to the conclusion that the battery is gubbed and needs replaced. By slowing the phone secretly, people are led to another conclusion. Not making the reason for the phones running slow is the reason for all these legal claims. People were DECIEVED!
And so am I.
That's why I am calling your bluff.
No matter what typical engineering theory and practice says, you can't deny the fact that something as popular as an iPhone, with millions upon millions of users doing WAY different things with it, and with millions upon millions of those users' batteries experiencing almost as many different charge/discharge cycles and habits (some people tend to always deep-cycle their batteries, some people tend to always top-off their batteries every night, etc.), are going to form a dataset that has millions upon millions of statistical outliers, with every ONE of them thinking that THEIR experience is THE one that should be "designed-for".
IOW, there is literally NO WAY that Apple (or anyone) can design a secondary-battery-powered device that has consistent, unit-to-unit performance, especially over-time that will "please" everyone, regardless of their usage or charging habits (or the luck of the draw of their particular battery). The statistics are just too "noisy".
And ESPECIALLY not with the variability of batteries. We just aren't that good at controlling all the factors that determine EXACTLY how a particular battery will perform, ESPECIALLY OVER TIME. It's at best a statistical crapshoot.
Garbage in, Garbage out. Not that Apple has Garbage batteries; but that our collective understanding of batteries in general is pretty much Garbage, when it comes to predicting what YOUR battery will do, ESPECIALLY OVER TIME.
There is exactly zero evidence that iPhone batteries aren't capable of running the phone properly unless they're brand new. Apple's statement refers to and much of the anecdotal evidence is based on batteries that are years old, under heavy strain, operating in cold temperatures, chemically degraded, or some combination thereof. Your reference to 95% health is entirely arbitrary. The update wasn't remotely "stealth," it was publicly announced. Your speculation that any Genius told any customer to buy a new phone if they weren't happy is exactly that: speculation.
So overall, also a pretty poor comparison.
Fact you want to hear?
Fact is that my 6s+ started having crappy battery life after 6 months. From 75% left in battery life to 20% when I get home.
Guess what Apple did in my case? "Oh wait, you are experiencing crappy battery life? Let me slow down your device and please allow me to call it a "feature" too."
Apple: "We take care of customer."
Joe @ Macrumors "Keep in mind that Apple is not permanently or persistently slowing down older iPhones. Even if your iPhone is affected, the performance limitations only happen intermittently, and only when the device is completing demanding tasks. "
The above appears to be FALSE as per Apple:
the user may notice effects such as:
[doublepost=1515190561][/doublepost]
I think the issue is not "cheap batteries", but rather that the batteries are TOO SMALL. They sacrificed battery capacity in order to make the Thinnest Phone Ever.
The above appears to be FALSE as per Apple:
the user may notice effects such as:
- Longer app launch times
- Lower frame rates while scrolling
- Backlight dimming (which can be overridden in Control Center)
- Lower speaker volume by up to -3dB
- Gradual frame rate reductions in some apps
- During the most extreme cases, the camera flash will be disabled as visible in the camera UI
- Apps refreshing in background may require reloading upon launch
[doublepost=1515190561][/doublepost]
I think the issue is not "cheap batteries", but rather that the batteries are TOO SMALL. They sacrificed battery capacity in order to make the Thinnest Phone Ever.
Hard to tell. An iPhone is running dozens of processes in the background, plus multiple alway-on radios. While you are typing:
Who knows if the battery is providing most of its max power to the cellular radio to check for new text messages from some distant cell tower? Or iCloud is uploading old movies. Or the processor is running voice recognition stuff to see if some noise around you resembled Hey Siri? Or the flash memory storage system is doing background wear leveling or data compression of memory data? Etc.
There is no reason for an iPhone to shut off unexpectedly unless there is something seriously wrong with the battery. As the battery gets used, the voltage drops. To compensate, the phone increases the amperage draw. There is bottom limit to the voltage, and once that threshold is reached the phone considers the battery to be depleted and at 0%. The software knows the battery level at all times based on the voltage reading.
In order for this system to stop working, the voltage reading is either incorrect or the battery has a fault where it cuts out at a higher voltage than the phone is programmed to recognize as empty. A battery with normal degradation will not behave in this manner, i.e., cutting out at a higher than expected voltage. Either way, it's a hardware problem that Apple is attempting to mask with a software patch that reduces performance peaks. When performance spikes, so does the voltage and/or amperage draw.
The proper way to have dealt with this issue would have been to inform those with compromised batteries. All they had to do was pop up a notice saying that the phone is experiencing reduced performance due to a battery issue, and to have the phone serviced to restore full performance. If under warranty, a free battery replacement should be provided. And give the user the choice to toggle this battery saving feature on or off until they can have the battery replaced. Easy, right?
But they did not do this. The only plausible reason is that they do not want the user to be informed of a possible battery issue. Why would they not want the user to know? This is where you will find Pandora's box.
I say... Free iPhones for everyone! lol
In order for this system to stop working, the voltage reading is either incorrect or the battery has a fault where it cuts out at a higher voltage than the phone is programmed to recognize as empty. A battery with normal degradation will not behave in this manner, i.e., cutting out at a higher than expected voltage. Either way, it's a hardware problem that Apple is attempting to mask with a software patch that reduces performance peaks. When performance spikes, so does the voltage and/or amperage draw.
The proper way to have dealt with this issue would have been to inform those with compromised batteries. All they had to do was pop up a notice saying that the phone is experiencing reduced performance due to a battery issue, and to have the phone serviced to restore full performance. If under warranty, a free battery replacement should be provided. And give the user the choice to toggle this battery saving feature on or off until they can have the battery replaced. Easy, right?
But they did not do this. The only plausible reason is that they do not want the user to be informed of a possible battery issue. Why would they not want the user to know? This is where you will find Pandora's box.
I say... Free iPhones for everyone! lol
Last edited:
Regardless it is not "few and far between slowdowns" as some are implying. It's overall VERY slow.
I had a throttled phone, have you tried one yourself firewood ??
