Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For those still under warranty/AppleCare+, I took in my iPhone 7 that was running at 1.6GHz when battery is less than ~75% battery and running at 1.3GHz when less than 50% battery. Battery wear was at 85% capacity (checked using Coconut Battery).

I showed the Genius the CPU DasherX view and the Geekbench 4 scores that demonstrated the discrepancy. The technician literally dismissed all of that evidence. He said that Apple doesn't troubleshoot with third-party apps. The easy way out, IMO.

Alas, he processed an exchange as a "courtesy" because he said "slowness" is not covered under warranty. He didn't really seem to understand the technical details I was trying to explain.

Replacement iPhone 7 had 11.0.3 installed. A10 Fusion showing 2.3GHz as expected. Geekbench 4 scores back to normal scores. Scores normal, even with 60% battery charge.

YMMV.

How old was your iPhone?
 
So for anyone who is interested, apple support ran diagnostics on my one year old iPhone that runs at 901mhz and suggested to me that in a couple of months I may have to replace it -.-
 
I've measured 1315/2252, 1056/1660, 794/1540 with geekbench 4 (single/multicore), depending on battery level, almost fully charged, 75%, and lower, respectively.
 
For those still under warranty/AppleCare+, I took in my iPhone 7 that was running at 1.6GHz when battery is less than ~75% battery and running at 1.3GHz when less than 50% battery. Battery wear was at 85% capacity (checked using Coconut Battery).

I showed the Genius the CPU DasherX view and the Geekbench 4 scores that demonstrated the discrepancy. The technician literally dismissed all of that evidence. He said that Apple doesn't troubleshoot with third-party apps. The easy way out, IMO.

Alas, he processed an exchange as a "courtesy" because he said "slowness" is not covered under warranty. He didn't really seem to understand the technical details I was trying to explain.

Replacement iPhone 7 had 11.0.3 installed. A10 Fusion showing 2.3GHz as expected. Geekbench 4 scores back to normal scores. Scores normal, even with 60% battery charge.

YMMV.

Interesting -- the numbers in your first paragraph are about what I see on my iPhone 7 with 87% battery capacity. Mine's running the latest iOS 11.2. How does your replacement behave at various charge levels after you update to 11.2?
 
Interesting -- the numbers in your first paragraph are about what I see on my iPhone 7 with 87% battery capacity. Mine's running the latest iOS 11.2. How does your replacement behave at various charge levels after you update to 11.2?

Replacement iPhone 7 runs at 2.3GHz, battery charged to 60% on 11.2.
 
For those still under warranty/AppleCare+, I took in my iPhone 7 that was running at 1.6GHz when battery is less than ~75% battery and running at 1.3GHz when less than 50% battery. Battery wear was at 85% capacity (checked using Coconut Battery).

I showed the Genius the CPU DasherX view and the Geekbench 4 scores that demonstrated the discrepancy. The technician literally dismissed all of that evidence. He said that Apple doesn't troubleshoot with third-party apps. The easy way out, IMO.

Alas, he processed an exchange as a "courtesy" because he said "slowness" is not covered under warranty. He didn't really seem to understand the technical details I was trying to explain.

Replacement iPhone 7 had 11.0.3 installed. A10 Fusion showing 2.3GHz as expected. Geekbench 4 scores back to normal scores. Scores normal, even with 60% battery charge.

YMMV.

And this is why this throttling pisses me off. Instead of replacing defective batteries that can no longer a fully power the CPU except when fully charged (often not even that!) Apple would rather throttle down the CPU in order to make their sub par batteries seem to last longer...
 
Apple builds these very solid devices with exotic materials to last a long time...only to provide batteries that have to get changed (at high cost) in only 2 years? And since the batteries are sealed very tight and require tools like a hot air blower to open them it is not any easy thing to do.

How about Apple work on more reliable, safer, longer lasting battery technology instead of fluff like emoji animations?

Too hard a problem, I guess. If they can't buy the technology, they just go for the easy stuff.
There isn’t some evil Apple conspiracy here. This is the state of the art in high capacity, high power batteries.

And of course the people drawing emojis for Apple aren’t battery engineers that have been pullled off the iPhone.
 
But is it possible Apple deliberately did this given what happened to Samsung with the Galaxy Note 7 battery debacle? It may be to ensure that we don't have a overheating battery situation with older batteries, and given how dangerous a lithium-ion battery catching fire can be (as Boeing found out with the 787 Dreamliner battery packs), I'd rather have Apple do this than suddenly have a bunch of older iPhones with scary battery failures.
 
But is it possible Apple deliberately did this given what happened to Samsung with the Galaxy Note 7 battery debacle? It may be to ensure that we don't have a overheating battery situation with older batteries, and given how dangerous a lithium-ion battery catching fire can be (as Boeing found out with the 787 Dreamliner battery packs), I'd rather have Apple do this than suddenly have a bunch of older iPhones with scary battery failures.

Without throttling, the phones shut down not blow up. Note 7 had batteries with manufacturing defects that inflamed as they were charged. There is nothing in common between the two cases. Apple case may be worse though since Samsung owned up to their problems and replaced all phones (even though the phones themselves were fine) while Apple seemingly is trying to cover up the problem to avoid the recall.
 
  • Like
Reactions: Smartass
Without throttling, the phones shut down not blow up. Note 7 had batteries with manufacturing defects that inflamed as they were charged. There is nothing in common between the two cases. Apple case may be worse though since Samsung owned up to their problems and replaced all phones (even though the phones themselves were fine) while Apple seemingly is trying to cover up the problem to avoid the recall.
A recall why? Batteries that go bad after 3 years? Samsung had to own up to their issues, they didn’t want to burn down a house.

But all of this is just at conjecture.
 
This is my wife’s, launch day iPhone 6s. Definitely getting throttled.

b0J2RVD.jpg
 
Replacement iPhone 7 runs at 2.3GHz, battery charged to 60% on 11.2.

Interesting. Next question would be to see the reported CPU at various charge levels. Does it still drop, just at different charge levels? Or does it stay at 2.3Ghz the whole way?
 
lol @ I don't believe Apple would do that.

Smartphones have reached an impasse of sorts, there are only so many features to add to a rectangular shaped device that is all screen. They want and need you to update continously in cycles, and battery degradation is a great way to do that, slowing down the device is a great way to do that. I've always believed (but not been very vocal) that they do this. Sad.
 
  • Like
Reactions: dysamoria
That doesn’t seem to prove that point either because my 6s did not have reduced screen brightness. The last post conjectures overheating.

How do you know your 6s didn't have reduced brightness, maybe you didn't notice it. Have you checked the white point settings as shown in that thread I linked?
 
  • Like
Reactions: Smartass
this is so true, i noticed that in my old iphone,
it's became very slow and the only major difference is battery life..

so I suspect that it has something to do with that
 
It takes courage to save millions in service costs by denying a systemic problem, then covering up the problem by slowing down users' phones without telling them.

except that they didn't really save millions because they were replacing batteries left and right for every phone in the range of affected models, whether they had a bad battery or not. and many phones that were out of the range but still in warranty
 
How do you know your 6s didn't have reduced brightness, maybe you didn't notice it. Have you checked the white point settings as shown in that thread I linked?
Because I have been able to see the 6s in direct sunlight prior to the battery replacement; which I have been able to do since it’s new and the brightness did not change after the replacement.
 
YMMV, but I think what's more interesting than the two different CPUdasherX results is the two identical Geekbench results. Which version of GB?

latest one: 4.2

the two identical geekbench results also puzzle me.
I'll put the iPhone into battery save mode (900MHz) and run GB again.
[doublepost=1513162463][/doublepost]
YMMV, but I think what's more interesting than the two different CPUdasherX results is the two identical Geekbench results. Which version of GB?

So...
the CPU is now permanently clocked down to 1200MHz
the geekbench results stay at the above values.

when enabling battery saving mode, CPU clocks down to 900 MHz
GB then reports 1500 / 2500.

not cool.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.