daniesy
macrumors 6502
11.2.5 is still in beta, they'll screw it up before the release, don't worry.
Apple Being Sued for 'Purposefully Slowing Down Older iPhone Models' [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
11.2.5 is still in beta, they'll screw it up before the release, don't worry.
DNichter
macrumors G3
This never happened with my 7 Plus or 6s. Why now with my X?
ObsidianIce
macrumors 6502
You seem confused....
The A8 processor core in the iPhone 6 and SE, even though clocked only slightly faster than the A7 processor cores in the iPhone 5s, actually has between 50% more and 2X higher performance. That big difference in performance could cause quite a difference in power requirements (both peak and sustained). My guess is that Apple enables a turbo-boost mode in their newer A chips that only gets near the max with fresh new batteries on a cool day.
69Mustang
macrumors 604
It not being an issue is an opinion. One I don't share. Agree to disagree on that. The diagnostic isn't that simple either. Anecdotally in this thread, it appears Apple won't replace batteries for customers even if they are willing to pay. So yeah, it's a bit more nuanced than the black and white version you present.
80 bucks for a battery and labor is reasonable
daniesy
macrumors 6502
Are you still using your 6S?
I always replaced my old model when the next one came out and never experienced these problems myself either...until this year when i kept my 7 Plus and the issues started to show.
it is throttled all the time when battery is "unhealthy enough". My 6s was running 911 Mhz all the time, after I replaced battery it went back up to where it should have been 1848 Mhz. It is consistent throttling. My friends phone was always at 600 Mhz before his battery was replaced. I'll take what I've seen with my own eyes over what any tech website states.
Last edited:
Err people’s phones are being slowed down when the battery degrades. In most of the world there is a two year warranty period, so if say after 18 months, they put a warning out saying change your battery, it would be at Apple’s cost not the consumers. Furthermore, if it ever came to pass that there was a known design flaw, in most European countries, consumers can make claims for up to 6 years irrespective of warranty status. Apple knew this and tried to make their phone “limp” over the warranty line or limp into the “upgrade” line.
I agree what they did is smart but I don’t think Apple needs to publish every step they take even in battery management. People found out about this by running benchmarks. It’s all silly.
Matthmaroo
macrumors newbie
Abazigal
Contributor
Apple can be doing the right thing here (by their own metrics) and people can still be legitimately upset. They are not mutually exclusive, you know.
my god... its code that was still the active, shipping code for product until just two months ago. its not like they have to go out into the job market to find people who can still code for iOS 10. Its not like they just deleted everything as soon as they stopped signing iOS 10. You make it sound like its trying to support Windows XP.
daniesy
macrumors 6502
You're wrong, you should believe Apple!
Darmok N Jalad
macrumors 603
It will be an interesting argument, perhaps. Many users will say that this software change is not a performance improvement (slower processing speeds), while Apple can argue that it IS a performance improvement (prolonged battery life, better stability). Is Apple obligated to reveal what its software patches do? I think so long as they prove their intentions were to help users and not obsolete hardware, they will likely only suffer a public black eye.
As a 6S owner, I'd rather they just disclose this more transparently, which I suspect may happen depending on how this falls out. I've been debating changing my aging battery, and had I known that this was why my phone was slower--and not blaming iOS11--I would have saved myself some hard resets and misguided frustration. Seems this secret move just let iOS11 take more blame than maybe it deserved?
As a 6S owner, I'd rather they just disclose this more transparently, which I suspect may happen depending on how this falls out. I've been debating changing my aging battery, and had I known that this was why my phone was slower--and not blaming iOS11--I would have saved myself some hard resets and misguided frustration. Seems this secret move just let iOS11 take more blame than maybe it deserved?
Rogifan
macrumors Penryn
That’s not what the EULA says.
I don't drink the kool aid, lol. I do like my apple products, I don't like them screwing with them.
Everything is nuanced. I just don’t believe it is such a massive conspiracy or problem that it warrants lawsuits or other massive coverage. Everyone now knows. Done and done
They replaced tons of batteries for free. They replaced mine because I was in the bad batch and now works like a dream.
Wildkraut
Suspended
Read the internet forums, posts on social sites or simply other threads in here.
There are many cases where people had semi new devices, and their battery replacements got rejected depite having sporadic shutdowns. Which got "fixed - cough,cough” by a software update later.
If you didn’t read this, then sorry for coming late to the party.
I hope this class action hits Apple really hard.
I have an iPhone 7 and an HTC 10 that I use daily. The iPhone 7 is on 10.3.3 (I have several 32-bit apps that I use frequently that do not have an update) and my HTC is on Android 7.0. Neither of those have a degrade in performance (that might be because I haven't update my iPhone 7), but they both exhibit battery problems. My HTC 10 (which I got the day the black model released in Australia) often dies when when using it at around 15% charge give or take. If I don't use it, it can stay up to 1%. I've had this issue now for maybe 6 months-ish, and it's getting worse. My iPhone (which is much newer; I got it last November or October), now dies below 10%, usually around 5%, if I'm using it (if not, it can also last to 1%). This is normal for batteries, I think. I now have an extra reason not to upgrade to iOS 11 because I don't want my phone throttled. I do use it with a battery case most of the time so it's hardly an issue, but I kind of wish batteries would last longer than just a year, especially when spending this much on a phone. Kind of makes you wish you still lived in the replaceable battery days 
. I also have another problem with my iPhone 7; it charges really slow, charges from 20% to 40% in a few hours. I'm not sure if it's the charger or the cable or the phone itself. I tried two different cables with two different chargers, but I think it's probably the cable, and I'll try another one tonight. We'll see how it goes.
In terms of phones dying, it's not just Apple's phones that have this problem, but it seems to be just Apple's phones with this "throttling" issue. Given a choice (like a toggle) to switch this setting on and off would be lovely.
. I also have another problem with my iPhone 7; it charges really slow, charges from 20% to 40% in a few hours. I'm not sure if it's the charger or the cable or the phone itself. I tried two different cables with two different chargers, but I think it's probably the cable, and I'll try another one tonight. We'll see how it goes.In terms of phones dying, it's not just Apple's phones that have this problem, but it seems to be just Apple's phones with this "throttling" issue. Given a choice (like a toggle) to switch this setting on and off would be lovely.
gnasher729
Suspended
The slowdown happens when the battery gets old. Obviously when an iPhone 8 is released, the first iPhone 7 have old batteries.
LordVic
Cancelled
While I usually agree that not everything is always as big as we make it out to seem
There are a few questions that are still not answered from Apple that make this seem bigger
Why did Apple not speak of this until evidence unequivocally showed what they were doing?
Why was this in since 10.2.1 without it ever appearing in a patch note?
Why has Apple lied about throttling performance as recent as a few weeks ago when they’ve been doing this since 10.2.1? And only admitted to it after being called out?
That’s questionable behaviour. Even if it’s as minor a thing as you believe, the way Apple handled it is pretty bad