Well don’t we all agree that throttling the way we face it shouldn’t even exist in the first place, independently on what it is being triggered by
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.
Apple Makes $29 Battery Replacements Available Immediately for iPhone 6 and Newer
- Thread starter MacRumors
- Start date
- Sort by reaction score
I read the thread... did you? Are you denying that for people geekbench does not represent real life usage? Not everybody sits at home looking at geekbench 24/7. This does NOT mean that throttling is okay. They can both be true.
So is this still dependant on Apple's minimum level for battery replacements?
My iphone 6 had the battery cut off issue and when I went to get a replacement last summer at the Apple Store in Brent Cross the guy told me that it was just above the level to qualify for the battery replacement and instead I'd have to go for the full out of warranty replacement (which I didn't).
My iphone 6 had the battery cut off issue and when I went to get a replacement last summer at the Apple Store in Brent Cross the guy told me that it was just above the level to qualify for the battery replacement and instead I'd have to go for the full out of warranty replacement (which I didn't).
Logical fallacy. Neither Apple or the developer who posted that quote are saying that auto shutdowns could only occur when running a benchmark. iOS is looking for big peaks/valleys in power draw relative to available voltage. Benchmarking triggers this at nominal voltage levels specifically because it's not designed to operate like a normal app and doesn't allow standard idle time, but standard apps could potentially trigger it if the voltage was below nominal levels...which typically is around 20% charge for lithium ion batteries that aren't EOL yet. Voltage available starts to drop very steeply around 20% or lower charge in a healthy non-EOL battery.
I think we have to be specific about this. People are angry at Apple at everything surrounding the throttling. People are accusing Apple of throttling at Year One, making shoddy batteries, creating hardware that csnt be supported by the battery, etc. i agree we need to investigate, because any of those, if true, is not what I or any customer shoukd stomach.
However, if Apple begins throttling at like year 3 than their biggest sin is transparency and I think people would be less angry about that then crappy tech that is made to break within two years.
People are angry because it seems not to be year 3 for many
Not even year 2
And even it is was ...Jesus, just tell them
People deserve to know
And I mean no disrespect - the iPhone isn't meant or designed to be an overclocked water-cooled monster. I haven't built water-cooled beast systems in a long, long time, but I think I can dust off the cobwebs enough to follow you though
You are 100% right . I'm getting off topic here. Your experience is far more appropriate than mine with PCs. My bad .
Well I'm waiting for the new update they will provide to give the user more insight in the battery. Let's wait for that.
No one is denying that iOS does throttle in specific situations. But unless you're using an app that doesn't allow idle time like Geekbench and is artificially loading the CPU to it's maximum at the same time, you're unlikely to experience throttling at nominal voltage with a healthy battery (i.e., above 20% charge). Voltage available drops off a cliff around 20% or less, but that's not a fault of iOS. That's just a standard weak spot for current lithium ion battery technology.
Is anyone saying geekbench represents real life usage ? Who ?
My point is that it's a tool, it has a score before and after apple's throttling.
Feel free at the people on this thread that are denying the validity of geekbench .... they are deflecting.
I could careless the scores it produces, all I care about , score before and after 10.2.1 - which lead to apple confirming they throttle .
How valid geekbench is ..... who cares..... anyway , I'm dropping the PC tangent I got drawn into.
The current insight Apple is giving you is the low power warning at 20% charge. That's the general point that lithium ion batteries lose their ability to provide something close to the nominal voltage. Voltage available to the CPU drops steeply around that point and is below nominal very quickly.
Yes they are. There are people on here in denial that a user would be impacted .
Forget about geekbench , it's not really Relevant , and a silly tangent that is defecting from the real issue......
Did Apple introduce throttling , Yes, done.
This puts a whole new light on all those graphs and pie charts that Apple touts so many people have updated to the new iOS. Could people have upgraded iOS thinking this might make my phone faster because right now it's really slow. When in reality it was being throttled.
The graphs are valid and do represent the situation, for a new phone with a good battery.
Chasing those scores also created this situation . Though they wanted bragging rights for single core speed, which they did beat android nicely .
The throttling introduced is specific to auto shutdown potential. If your battery is not already at EOL and has more than a 20% charge, then it's highly unlikely any throttling to prevent a shutdown is going to take place. Geekbench can trigger throttling at any charge level specifically because it's not designed to idle or load the CPU like a normal app. Thus, claiming that Geekbench throttling = iOS is always throttling at nominal voltage is HIGHLY misleading.
Stop deflecting - people don't use geekbench
People have crashing iPhones and Apple introduced throttling- its as simple as that .
Your assessment of when it happens, still does not change the fact Apple introduced throttling .
Stop the deflecting.
Yes, we should stop saying "automatic shutdown", actually it's a crash due to a hardware failure.
Exactly - now spin is in full affect that it's an "automatic shutdown" - it's a critical crash
Stop using rhetorical devices as a smokescreen for a lack of facts. It's clearly been stated that auto shutdown could potentially happen when using a standard app. However, that doesn't change the fact that auto shutdown is highly unlikely for standard apps unless there's an available voltage issue...and the most likely scenario for potential problems with available voltage and a healthy battery is around 20% charge or lower. That's when lithium ion batteries decline rapidly in terms of the voltage they can provide to the CPU.
People on this thread act like throttling is new. Apple has been throttling laptops over dead batteries for a while. Obvi theres throttling over thermals as well. This is a transparency and expected lifetime issue.
Also, genuinely curious, does anybody actually know how hrottling works? Is it all the time, only when battery is below 30 percent, only with this many cycles, etc. this is all good information to have.
Also, genuinely curious, does anybody actually know how hrottling works? Is it all the time, only when battery is below 30 percent, only with this many cycles, etc. this is all good information to have.
Auto shutdown ? Are you serious ? It's a crash. Just stop it .
You are just posting the same thing over and over.
Do you accept Apple introduced throttling in 10.2.1 ?
That would be misleading. A "crash" can occur due to software only. People experience that on desktops/laptops that are plugged in to an electrical supply and have steady voltage available to the CPU. Auto shutdown is the correct term to use in this situation because it's specific to a lack of voltage for the CPU load.
A crash is a crash - a crashed device doesn’t shut off. A insufficient current fault that results in power down is a hardware failure but it isn’t a crash. And the hardware must be intentionally shut down in that situation - insufficient instantaneous current, unless it is essentially zero, wouldn’t shut down the device on its own. Presumably hardware on the device detects insufficient voltage and initiates power down to prevent further problems.
No, it's not just a "crash". The system has a built-in shutdown to prevent damage when the CPU requires more voltage than the battery can provide.