That planned obsolescence conspiracy gets more and more complex, sinister, and twisted day by day. It's amazing such complexity can be put in and pulled off by a company that supposedly can't have a calculator that adds a couple of single digit numbers together properly.
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.
Other Apple is slowing down older iPhones based on battery wear level [MERGED]
- Thread starter IsaacM
- Start date
- Sort by reaction score
So there's no other simpler way?
I dont know if I want to do all that for 5-6 devices in my house
And with editing files and restoring settings with various 3rd party apps makes me feel uneasy about software bugs or other issues that might get transferred to my devices.
I just want to stay stock on ios 10 without all the nonsense involved.
Really. Feels like hacking the registry in Windows, except that at least doing that doesn't require downloading third party software.
[doublepost=1513618501][/doublepost]
That's not optimum, but In Real Life(tm) you will never notice the difference (as your results show).
But as mentioned earlier most of that isn't needed and it's just a matter of installing a profile which is fairly quick and simple.
so already after 1 year apple is starting to screw over iphone 7 customers.... nice.
hypothetically, yes.
No you are the person bringing up "lying". I am suggesting alternative scenarios that could play out here other than by reason of "planned obsolescence"
Yes, there definitely seems to be an issue with battery and throttling. I'm more likely to ascribe this to incompetence rather than planned obsolescence, though.
Either way, it needs to be addressed (via battery recall, iOS update, etc).
Interesting so according to that article iOS 11.2.1 is when Apple wrecked the iPhone 7 just like how they did the 6s in 10.2.1. Prior to iOS 11 the 7 was running just fine. The writing is on the wall at this point. Looking at this data its plain as day planned obsolescence has been executed on iPhone 7 and my experience with the device perfectly backs up what that data shows
"The distribution of iPhone 7 scores under iOS 10.2.0, iOS 10.2.1, and iOS 11.1.2 appears identical. However, the distribution changes with iOS 11.2.0 and starts to look like the iPhone 6s distribution from 10.2.1."
This fix will also cause users to think, “my phone is slow so I should replace it” not, “my phone is slow so I should replace its battery”. This will likely feed into the “planned obsolecense” narrative.
"The distribution of iPhone 7 scores under iOS 10.2.0, iOS 10.2.1, and iOS 11.1.2 appears identical. However, the distribution changes with iOS 11.2.0 and starts to look like the iPhone 6s distribution from 10.2.1."
This fix will also cause users to think, “my phone is slow so I should replace it” not, “my phone is slow so I should replace its battery”. This will likely feed into the “planned obsolecense” narrative.
You have an iPhone 7? And you noticed something different suddenly since iOS 11.2 where all this supposedly started to appear, or you had issues all along with iOS 11 well before 11.2?
https://9to5mac.com/2017/12/18/iphone-battery-performance-issues/
Today, Geekbench founder, John Poole, published an article describing his findings after diving deeper into the relationship between iPhone performance and battery age.
As can be seen in the results above, Poole notes that the issues become pronounced moving from 10.2.0 to 10.2.1 to 11.2.0.
When it came to the iPhone 7, the issue didn’t appear to be present, until the test with iOS 11.2.
Poole believes that Apple added a software adjustment for iPhone 7 with iOS 11.2, similar to what it did to correct the iPhone 6s shutdown issues with 10.2.1. He goes on to share Apple may have created a misleading “third state” of slower iPhone performance without any notification that could convince users to upgrade their devices earlier than planned.
I still have my 7 Plus. This report confirms the stuttering and battery drain I have been facing in iOS 11 all along
I would never choose power management/slow downs over shutdowns.
Even if they refuse to pay to replace my battery I'd pay out of pocket so my device is not throttled like a turtle.
With words like "believes", "thinks", "narrative", etc. it's consistent with what I've been bringing up.
I've been skeptical, though not vocal, on this/in this thread. The GeekBench analysis really takes the jumble of idiosyncratic, often subjective, reports in the reddit thread and applies some discipline.
At this point I think the ball is in Apple's court. Will they respond?
Batterygate pretty much confirmed with hard-evidence.
Yup. The developers of Geekbench confirm a section of the iPhone userbase has been induced into upgrading. This is the developer of an major benchmarking app who has done a deep dive on this with multiple iPhones.
iPhone X and iPhone 8 are next on iOS 12.
Glad they're keeping track of this data, puts an end to any debate about whether or not this is really happening. It's clearly a change Apple's made recently, and it definitely impacts a large percentage of older phones.
Apple has clearly discovered an engineering fault with their power supply designs, which was causing phones to crash as batteries aged.
In order to avoid having to replace the batteries of the impacted devices -- many of which are still under warranty or AC+ -- they developed this CPU underclocking code to mask the issue. A hardware-crashing phone by definition is in need of warranty service, but a slow phone is still "working" and so Apple does not have to repair it.
I think we need to make an effort to distance this discussion from the "planned obsolescence" conversation. That is not what is going on, and framing the issue in that context weakens our argument. Apple's misconduct here is in covering up the power delivery fault in their devices, NOT a deliberate attempt to slow down older phones in order to sell upgrades.
It's important to keep the conversation focused on the real nature of this issue if we want any kind of resolution, the most obvious of which is that any device which requires under-clocking to prevent crashing should receive a free battery replacement (if it's under warranty or AC+).
--
Just as an aside, I want to note that this issue -- excessive crashing when the battery has lost capacity -- is not unique to iPhones, and has been a common problem in the Android world for as long as I can remember. It's never been made into a big story because, until recently, Android phones generally had user-replaceable batteries.
My 13 month old 7+ was at 99% before I sold it and I never noticed any slowdowns. Battery life was always excellent with that device. I never let it drop below 20% and would rarely go below 30.
But what you've been experiencing wouldn't necessarily be consistent. The findings showed that nothing of this sort applied to iPhone 7 prior to 11.2, this all those things you've been posting about prior to 11.2 couldn't be related to this based on that information.
i think it's time for apple to explain what's going on.
And what does that show as far as any actual reasoning and intent (if it exists)? This has nothing to do with what I've been talking about--after all this time either you are somehow still misunderstanding this particular aspect of discussion or just trying to deflect from it, but in either case that hasn't been what it's been about as far as the part that I've been commenting on.Look at this scientific chart
