Other Apple is slowing down older iPhones based on battery wear level [MERGED]

Another lesson to be learned - never buy last years model at a discount and just go for the flagship model on launch day, so it will last the longest before becoming obsolete.
Never buy an older Apple device. I learnt that the hard way with iPad Mini on iOS 9. I wouldn't wish the experience on my worst enemy.
 
Your battery degraded but it wasn't a defective battery. Apple has used sub standard batteries in some of their iPhones which cause them to shut down at lower battery percentages with Wear and this is probably on the iPhone 7 as well. Rather than fix the source of the problem Apple resorted to slowing down the phone as a bandaid solution to save cost.
This is what is being asked for proof.

If you posted your video we could maybe assess if you just aren't noticing the problem because that's the obvious conclusion in that scenario.
Based on your video and narrative the obvious conclusion is you are noticing things that aren’t there; eg a 3 - 5 second claimed delay.
 
This is what is being asked for proof.

You want proof of defective batteries? iOS 10.2.1 is the proof. iPhone 6s stopped shutting down after that update. It's also since iOS 10.2.1 the geekbench scores were gimped.


Based on your video and narrative the obvious conclusion is you are noticing things that aren’t there; eg a 3 - 5 second claimed delay.
So Apple is right and I am a liar?

Why am I not noticing this on my iOS 10 device by the way?
 
If a subsequent OS breaks what a previous OS does and has a negative impact on user experience and despite being informed, it's not fixed it's being intentionally not fixed.
Or it was broken and then fixed. The feature was really a bug that was subsequently fixed.
 
You want proof of defective batteries? iOS 10.2.1 is the proof. iPhone 6s stopped shutting down after that update. It's also since iOS 10.2.1 the geekbench scores were gimped.



So Apple is right and I am a liar?

Why am I not noticing this on my iOS 10 device by the way?
So iOS 10.2.1 Apple changed its power management algorithms. Possible, but still isn’t proof of all of this.
[doublepost=1513150718][/doublepost]
Or it was intentionally done to force people to get the X.

You are not telling me they couldn't fix such an obvious bug for over a year?
This is where the conjecture gets dicey. Can you prove this?
 
So iOS 10.2.1 Apple changed its power management algorithms. Possible, but still isn’t proof of all of this.
Then all those people who are having a slower phone should get it fixed free of cost. Will Apple do this? If they don't it's malice.
[doublepost=1513150788][/doublepost]
So iOS 10.2.1 Apple changed its power management algorithms. Possible, but still isn’t proof of all of this.
[doublepost=1513150718][/doublepost]
This is where the conjecture gets dicey. Can you prove this?
Can you prove it was a bug on iOS 10?
 
Then all those people who are having a slower phone should get it fixed free of cost. Will Apple do this? If they don't it's malice.
You need to prove the phone is slower in actual use? Are games slower? Is safari slower etc?
[doublepost=1513150902][/doublepost]
Then all those people who are having a slower phone should get it fixed free of cost. Will Apple do this? If they don't it's malice.
[doublepost=1513150788][/doublepost]
Can you prove it was a bug on iOS 10?
Can you prove it wasn’t?
 
You need to prove the phone is slower in actual use? Are games slower? Is safari slower etc?
Just a few days ago when we were debating planned obsolescence in that alternatives section and we were telling you geekbench scores do not matter and the older iPhones were slower in real world usage you were insisting that real world usage can't be measured and since the study showed the benchmarks were the same the phone wasn't slowed down


In order to define there "is an issue" it has to be measured. There is no definitive measurement to prove apple slows it's devices down. A study even supported that apple doesn't
We have now provided you with measurement.

Opening and closing apps serially is not real world use either. Benching the same means that “planned obsolescence “ is a myth and is more real world that app opening and closing.

Now you have been provided with proof that a section of the iPhone user base has their benchmarks dramatically lowered on newer iOS versions and you are asking for real world usage? According to your past posts since it no longer benches the same Apple has forced a section of their iPhone user base to give hem more money for no fault of theirs.


[doublepost=1513150902][/doublepost]
Can you prove it wasn’t?
Why did Apple not close the feedback?
 
Just retested today and my 6S is still slower than my 6.
[doublepost=1513152794][/doublepost]
You need to prove the phone is slower in actual use? Are games slower? Is safari slower?

For me, my 6S works about the same speed as my 6 if not a little slower. When I got it, it was much faster.

The Geekbench score is also lower than my 6 and the CPU DasherX App also shows a lower clock speed.

I don’t know what kind of scientific proof you are expecting on a thread like this, but with everything i have read on this topic, there are quite many reports of this behavior available on this forum and elsewhere on the internet.

I have no idea whether this is just a bug, or a feature or whatever, I just want to know why my 6S is testing mich slower than it should be and also want to know if this is an isolated issue or if I can expect the same behavior from my X in the future.
 
Last edited:
Just retested today and my 6S is still slower than my 6.
[doublepost=1513152794][/doublepost]

For me, my 6S works about the same speed as my 6 if not a little slower. When I got it, it was much faster.

The Geekbench score is also lower than my 6 and the CPU DasherX App also shows a lower clock speed.

I don’t know what kind of scientific proof you are expecting on a thread like this, but with everything i have read on this topic, there are quite many reports of this behavior available on this forum and elsewhere on the internet.

I have no idea whether this is just a bug, or a feature or whatever, I just want to know why my 6S is testing mich slower than it should be and also want to know if this is an isolated issue or if I can expect the same behavior from my X in the future.
Some iPhone 7 users are also reporting the issue on Reddit.
 
You have absolutely right. This is very serious complaint! But nobody cares. Instead of blame Apple for what they did on purpose reducing cpu for their battery problem. They are cared to buy new battery to improve the cpu.
[doublepost=1513155589][/doublepost]
That's an interesting finding, but it's not what the reddit thread is about, or what this thread started out about.

The reddit thread argues that Apple is using the firmware/OS to throttle the SoC based on battery capacity in order to reduce claims about battery wear and avoid random system shutdowns. If it's true, that's a really big deal because it's arguably fraudulent: Apple sold a defective device and covered up the defect with a firmware patch, rather than fixing the defect (at possibly great cost and certainly great embarrassment). The potential liability for that could be enormous.

What you're saying is very different. You're saying that below some level of battery charge (say, 50%) the system slows down. Why? Apple's response would presumably be: to preserve battery power. It's a sort of involuntary low-power mode. Could this be very annoying to you? Yes, it definitely could. Is this a fraudulent attempt to hide a defective phone? Not at all. Restoring normal speed system operation is as easy plugging the phone in and charging the battery back up. That is not the case with the reddit complaint, which can only be fixed with a battery replacement, and note that part of the fraud claim against Apple would be that Apple hid poor battery performance that would have required Apple to replace batteries by using a firmware patch.

Again, I get it that you might want to run the phone at full power all the way down to a dead battery. But that's qualitatively different than the reddit issue.

#413
You have absolutely right. This is very serious complaint! But nobody cares. Instead of blame Apple for what they did on purpose reducing cpu for their battery problem. They are cared to buy new battery to improve the cpu.
[doublepost=1513156223][/doublepost]
There’s hundreds of authorized Apple iPhone repair centers around just go and pay 80 bucks and get a new battery. The time is spent posting on the site you could’ve had it done!

So we will pay for their problem? You must be very clever! It's their problem to fix the software which slows down on purpose our phone. And when the battery performance will reduce and the software do the same thing we will buy again a new battery every 3-4 months? we buy the phone with a specific CPU frequency.
[doublepost=1513156739][/doublepost]
The wording here implies that they treat those with Applecare/Applecare+ the same as those without. If it retains less than 80%, they'll do it. If not, they won't.

They do not say anything about if you feel you need a replacement, you can pay for it. It says if it needs replacing, telling me they can dictate that without my input. They just indicate that you can change it if the test fails.
b81ca10b188b0627f4b3cb860e4e2d61.jpg
Except the problem of the battery they must give us an update so we must have the choice if our phones use all the cpu frequency or not!
[doublepost=1513157276][/doublepost]
I always buy an AppleCare warranty on my Apple devices. There have been many times when I’ve taken my device in before the two years was up, with complaints about Performance and battery life, and they’ll do a test but if it’s even slightly above 80% they will not replace the battery under warranty.

Yet they obviously know that even when the battery is at 85% or 90% of original capacity that they’re already throttling the speed AND THEY NEVER MENTIONED THIS TO ME. Also some other battery test apps don’t agree with apples diagnostics and will show worse battery wear than apple’s test shows.

Most recently, my son’s iPhone 6 battery was performing horribly after almost 2 years this spring, and we took it to Apple, and the Apple store told me that there was nothing they could do. The battery tested at 83% but you could watch the battery gauge climb down each minute as we used it.

I took it to batteries plus bulbs and paid about $80 for a new battery and performance and battery life returned to normal. He can confirm this story. Later I took the receipt to the Apple store and they told me too bad, even though the phone still had a week of apple care plus left.

EDIT - this battery and performance issue had resulted in my son buying a 7+ this spring, after Apple refused to help, and then I installed the new battery which fixed things because my daughter needed to replace her 5s and i wanted to see if I could salvage the iPhone 6 for her.
I always buy an AppleCare warranty on my Apple devices. There have been many times when I’ve taken my device in before the two years was up, with complaints about Performance and battery life, and they’ll do a test but if it’s even slightly above 80% they will not replace the battery under warranty.

Yet they obviously know that even when the battery is at 85% or 90% of original capacity that they’re already throttling the speed AND THEY NEVER MENTIONED THIS TO ME. Also some other battery test apps don’t agree with apples diagnostics and will show worse battery wear than apple’s test shows.

Most recently, my son’s iPhone 6 battery was performing horribly after almost 2 years this spring, and we took it to Apple, and the Apple store told me that there was nothing they could do. The battery tested at 83% but you could watch the battery gauge climb down each minute as we used it.

I took it to batteries plus bulbs and paid about $80 for a new battery and performance and battery life returned to normal. He can confirm this story. Later I took the receipt to the Apple store and they told me too bad, even though the phone still had a week of apple care plus left.

EDIT - this battery and performance issue had resulted in my son buying a 7+ this spring, after Apple refused to help, and then I installed the new battery which fixed things because my daughter needed to replace her 5s and i wanted to see if I could salvage the iPhone 6 for her.
[doublepost=1513158621][/doublepost]
No they do not that is simply untrue!
Battery will last easily the full year of the warranty. So if it’s beyond that it’s up to the user to replace the battery or buy Apple care for extended warranty!
ng me if the starter wears out after the warranty on my vehicle, that the company owes me a new starter? Sorry it doesn’t work that way.

If your vehicle has to go with 200km speed and on purpose the company reduces to 70km to protect a problematic battery i think that's not a guarantee problem! it's a scandal!
 
Last edited:
This is basically Apple's version of the Volkswagen emissions cheating scandal. And we all know how well that worked out for Volkswagen. I would expect Apple is going to need to break their silence soon and it will be interesting to see how they try to spin it.

I'm not sure I would agree, in the sense that it may be a valid reason for slowing down the processor when battery capacity or battery levels get low. But it's the lack of transparency from Apple and lack of a dialog box or setting switch alerting us to the situation that has us rankled.
 
It is just a poor coverup for the circuit and battery capacity design flaw that made certain iPhone models to shut down randomly especially in cold weather. They sacrificed the battery for the sake of thinness and now they are just throttling the performance to prevent those shutdowns.
 
Just retested today and my 6S is still slower than my 6.
[doublepost=1513152794][/doublepost]

For me, my 6S works about the same speed as my 6 if not a little slower. When I got it, it was much faster.

The Geekbench score is also lower than my 6 and the CPU DasherX App also shows a lower clock speed.

I don’t know what kind of scientific proof you are expecting on a thread like this, but with everything i have read on this topic, there are quite many reports of this behavior available on this forum and elsewhere on the internet.

I have no idea whether this is just a bug, or a feature or whatever, I just want to know why my 6S is testing mich slower than it should be and also want to know if this is an isolated issue or if I can expect the same behavior from my X in the future.
So my phone should have been affected also; brightness and speed. Phone was exactly the same after the battery swap. Which is why there is something else at play.
 
So my phone should have been affected also; brightness and speed. Phone was exactly the same after the battery swap. Which is why there is something else at play.
Why do you keep bringing your phone into this? It's already been said only those phones who have defective batteries are affected. There are phones with batteries which shut down at 20-30%. This was happening prior to 10.2.1. Apple released 10.2.1 specifically to fix that issue. Whenever iOS detects a battery which matches certain specifications it downclocks the CPU to prevent a shut down.

For the record, my 6 my 6 whose battery I replaced a couple of months ago doesn't show this but the score is above the average geekbench score. Take it as you will.
 
Just a few days ago when we were debating planned obsolescence in that alternatives section and we were telling you geekbench scores do not matter and the older iPhones were slower in real world usage you were insisting that real world usage can't be measured and since the study showed the benchmarks were the same the phone wasn't slowed down



We have now provided you with measurement.



Now you have been provided with proof that a section of the iPhone user base has their benchmarks dramatically lowered on newer iOS versions and you are asking for real world usage? According to your past posts since it no longer benches the same Apple has forced a section of their iPhone user base to give hem more money for no fault of theirs.



Why did Apple not close the feedback?
The study showed Apple did not slow down older devices. These results as passionate as people are, are anecdotal. You cannot prove planned obsolescence with what is being said here, which are some people’s spin. And then there is my phone unaffected.
 
The study showed Apple did not slow down older devices. These results as passionate as people are, are anecdotal. You cannot prove planned obsolescence with what is being said here, which are some people’s spin. And then there is my phone unaffected.
That test also is anecdotal as it did not test every iPhone on the planet.
 
Why do you keep bringing your phone into this? It's already been said only those phones who have defective batteries are affected. There are phones with batteries which shut down at 20-30%. This was happening prior to 10.2.1. Apple released 10.2.1 specifically to fix that issue. Whenever iOS detects a battery which matches certain specifications it downclocks the CPU to prevent a shut down.

For the record, my 6 my 6 whose battery I replaced a couple of months ago doesn't show this but the score is above the average geekbench score. Take it as you will.
Because my phone had a defective battery. Is that hard? It just took longer for the symptoms.
 
Because my phone had a defective battery. Is that hard? It just took longer for the symptoms.
Your phone was shutting down at 20-30%? Then that must be some other flaw related to the battery because none of the 6s shut down since 10.2.1.
 
That test also is anecdotal as it did not test every iPhone on the planet.
So right, one can’t make a broad sweeping generalization from a few posters out of tens of millions.
[doublepost=1513168454][/doublepost]
Your phone was shutting down at 20-30%? Then that must be some other flaw related to the battery because none of the 6s shut down since 10.2.1.
Excessive battery drain is the official reason.
 
So right, one can’t make a broad sweeping generalization from a few posters out of tens of millions.
It only takes a few cases to recognise a problem. For example, that date bug a few days ago. I was already past 12:15am and I was not affected nor were housands of other customers but no sooner did a few news sites report the problem a fix was rolled out on a weekend nonetheless.

I expect Apple will issue a statement on this soon. If they don't, well it's a slap in the face of the customers who had to shell out cash to get it fixed for no fault of theirs. I think they are entitled to s refund.
[doublepost=1513168748][/doublepost]
So right, one can’t make a broad sweeping generalization from a few posters out of tens of millions.
[doublepost=1513168454][/doublepost]
Excessive battery drain is the official reason.
That's a worne out battery. It happened with my 6 also a few months ago. The flaw for which 10.2.1 was issued is far more serious. The phone just shuts down at 30%. And it's on these specific phones that the CPU is being downclocked.
 
It only takes a few cases to recognise a problem. For example, that date bug a few days ago. I was already past 12:15am and I was not affected nor were housands of other customers but no sooner did a few news sites report the problem a fix was rolled out on a weekend nonetheless.
Not everybody believes this. This is why clinical trials are run the way they are. Date bug bad example I wasn’t affected, but that was a real bug unlike this, which is pure conjecture combined with hyperbole.
I expect Apple will issue a statement on this soon. If they don't, well it's a slap in the face of the customers who had to shell out cash to get it fixed for no fault of theirs. I think they are entitled to s refund.
[doublepost=1513168748][/doublepost]
That's a worne out battery. It happened with my 6 also a few months ago. The flaw for which 10.2.1 was issued is far more serious. The phone just shuts down at 30%. And it's on these specific phones that the CPU is being downclocked.
Don’t know what apple will do if anything. IMO, if people stopped with the nefarious intentions direction these threads would be more productive.
 
It only takes a few cases to recognise a problem. For example, that date bug a few days ago. I was already past 12:15am and I was not affected nor were housands of other customers but no sooner did a few news sites report the problem a fix was rolled out on a weekend nonetheless.

I expect Apple will issue a statement on this soon. If they don't, well it's a slap in the face of the customers who had to shell out cash to get it fixed for no fault of theirs. I think they are entitled to s refund.
[doublepost=1513168748][/doublepost]
That's a worne out battery. It happened with my 6 also a few months ago. The flaw for which 10.2.1 was issued is far more serious. The phone just shuts down at 30%. And it's on these specific phones that the CPU is being downclocked.

My suggestion is to not respond to I7Guy in this thread until he posts what many have asked. He keeps quoting his example as proof that what people are reporting are false, while not showing the proof of his speed tests.

Act3 has actually posted useful information, including his CPU test history showing a drastic improvement one day out of the blue. His explication is he had the battery replaced. Other's have posted similar results. I'm inclined to believe Act3 and others, including the accounts on Reddit. I personally think Apple has been effectively doing this for years by not optimizing iOS for older devices (until X.3 or so). By doing this, and taking almost a year to speed up older devices, they conveniently increase sales.

Until we see actual proof from the naysayers (the same proof they have asked for, then deny while not showing their own proof), they are just simply here to show their blinding love for Apple products.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top