Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

My iPhone 7 is throttled


  • Total voters
    93
I'd rather a video proof because you could easily toggle LOW POWER MODE ON to run the benchmark and then toggle it off after results was generated.
 
I'd rather a video proof because you could easily toggle LOW POWER MODE ON to run the benchmark and then toggle it off after results was generated.
Why does anyone need to show you rock solid proof of an issue Apple has already acknlowledged and Geekbench have already documented? OP’s results are perfectly consistent with what Apple and Geekbench said.
 
  • Like
Reactions: souko and macfacts
Why does anyone need to show you rock solid proof of an issue Apple has already acknlowledged and Geekbench have already documented? OP’s results are perfectly consistent with what Apple and Geekbench said.

UGH. Just to rule out possible tricks to game the benchmark score. I'm not requiring him. I said I'd rather a video proof. IDGAF if he provides it or not though, more of a suggestion.

Also, Yes, Apple confirmed such throttling BUT didn't say criteria for triggering the "optimization" of CPU just a vague, "when battery deteriorates". is it 84% is it 79%?
 
  • Like
Reactions: macfacts
I'd rather a video proof because you could easily toggle LOW POWER MODE ON to run the benchmark and then toggle it off after results was generated.

I think we ought to give the benefit of doubt to the intentions of the poster, but I don't think we should take it as a given that the tests were performed under valid conditions.
 
I've had results that are more than slightly different. The first time I ran GeekBench 4, my iPhone 7 appeared throttled. I ran it again a few hours later and it was normal.

If you think your phone is throttled and you don't have a weak battery, try charging your phone and running it again later.
[doublepost=1514300563][/doublepost]

I got pretty drastic variations just by running GeekBench 4 twice. I don't know what the deal was, but I got what appeared to be modestly throttled results one time, but it was normal a few hours later. My phone isn't showing any signs of being throttled so I can only conclude that other factors can affect GeekBench scores and the results might need to be taken with a grain of salt. We have no idea what kind of conditions people are running their tests under. If you've got tons of background tasks going, that ought to affect your score, wouldn't it?
I ran geekbench several times yesterday and today on my one year old iPhone 7 and got pretty similar results varying by an amount of under 100 points (single-core around 3500 and multi-core around 5900).
 
My 85% capacity 7+ 11.1.2 around 500 charges

Not throttled

Then again it wouldn’t be :D

Initiated with 11.2
 
My 85% capacity 7+ 11.1.2 around 500 charges

Not throttled

Then again it wouldn’t be :D

Initiated with 11.2
But we can't really trust Apple, so it's quite possible the throttling has been there since iOS 10 days even (for iPhone 7/7+ phones).
 
But we can't really trust Apple, so it's quite possible the throttling has been there since iOS 10 days even (for iPhone 7/7+ phones).

Yeah u never know. But they’d be in extra deep doo doo more than they already are right now for this if they were lying about iOS version in their statement

It’s so absurd they think the average person, not just aficionados, are gonna upgrade every friggin year. And they’re forced to update by being bothered 24/7 about updates
 
I ran geekbench several times yesterday and today on my one year old iPhone 7 and got pretty similar results varying by an amount of under 100 points (single-core around 3500 and multi-core around 5900).

Those are the scores I typically get too, but one of my runs gave me half the normal score.
 
I've had results that are more than slightly different. The first time I ran GeekBench 4, my iPhone 7 appeared throttled. I ran it again a few hours later and it was normal.

It's normal for other stuff to slow down an iPhone (background downloads, iOS unloading unused apps, cell tower signaling, and etc.) You might have run one with and one without that stuff going on.

Those are the scores I typically get too, but one of my runs gave me half the normal score.

The A10 on an iPhone 7 also has two different kinds of ARM CPU. One is fast, one is slower. iOS doesn't tell you which one it uses to run an app, and potentially could switch between the fast and slow CPU mid-benchmark.
 
  • Like
Reactions: smirking
It's normal for other stuff to slow down an iPhone (background downloads, iOS unloading unused apps, cell tower signaling, and etc.) You might have run one with and one without that stuff going on.



The A10 on an iPhone 7 also has two different kinds of ARM CPU. One is fast, one is slower. iOS doesn't tell you which one it uses to run an app, and potentially could switch between the fast and slow CPU mid-benchmark.

Lol

You just made me feel like a10 is a trap
 
Can we not just downgrade to 10.3?

No. Apple stops signing older versions of an O/S usually within weeks of a newer version being available. Once they have done that then it's all but impossible for normal users such as us to downgrade to that version.

In this case, Apple stopped signing 10.3.3 at the start of October.
 
I don’t give a damn about what score my phone has on geek bench. What I care about is how my device performs in real life doing tasks. If it still feels snappy then that’s what I care about.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.