Is crApple Playing Games With iFrauds? YES!
The Market Ticker - Commentary on The Capital Markets
Main Navigation
Full-Text Search & Archives

Legal Disclaimer

The content on this site is provided without any warranty, express or implied. All opinions expressed on this site are those of the author and may contain errors or omissions.


The author may have a position in any company or security mentioned herein. Actions you undertake as a consequence of any analysis, opinion or advertisement on this site are your sole responsibility.

Market charts, when present, used with permission of TD Ameritrade/ThinkOrSwim Inc. Neither TD Ameritrade or ThinkOrSwim have reviewed, approved or disapproved any content herein.

The Market Ticker content may be sent unmodified to lawmakers via print or electronic means or excerpted online for non-commercial purposes provided full attribution is given and the original article source is linked to. Please contact Karl Denninger for reprint permission in other media, to republish full articles, or for any commercial use (which includes any site where advertising is displayed.)

Submissions or tips on matters of economic or political interest may be sent "over the transom" to The Editor at any time. To be considered for publication your submission must include full and correct contact information and be related to an economic or political matter of the day. All submissions become the property of The Market Ticker.

2017-12-21 07:00 by Karl Denninger
in Company Specific , 479 references Ignore this thread
Is crApple Playing Games With iFrauds? YES!
[Comments enabled]

Oh if true this is nastiness .....

So, Poole used Geekbench's benchmarking testing to find out. He conducted single-core tests on iPhone 6s and iPhone 7 units running different versions of iOS. His findings suggest that Apple has made a tweak in iOS 10.2.1 to 11.2.0 that appears to throttle the iPhone's performance when the smartphone's "battery condition decreases past a certain point," Poole said.

The change was likely made after iPhone 6s users reported that their smartphones would spontaneously shut down even when there was seemingly more than enough life left on their batteries. Apple acknowledged the shutdown problem and offered a battery replacement program. The company also released an update to address it.

I'll tell you what's going on here with the batteries.

As lithium batteries age they are unable to sink as much current as they used to be able to -- either charging or discharging.  At a certain point this becomes noticeable; you seem to have plenty of power, you turn on the GPS in the phone (which has a high drain) and whammo -- the phone shuts down.

"What?!  I had 40% left!"

Uh, no you didn't.  The battery was severely compromised; it had voltage but no current delivery capability and when you hit it with a heavy load the voltage collapsed.

If you've ever gotten into your car, the lights come on, you turn the key and click! -- that's the same thing.  Voltage looks ok at first blush (your lights are working inside the cabin) but as soon as you try to put a heavy load on the battery (for the starter) the voltage goes to an effective zero because the battery cannot deliver the required current.

The correct answer to this problem is to replace the battery -- it's worn out.

Of course that's hard and expensive if the unit is out of warranty because all the iPhones have sealed the battery inside the case, which prevents you from changing it quickly and easily.  So have most other manufacturers these days.

But what if the phone is not out of warranty?

Then Apple would eat the repair.

So if they throttle the CPU when the battery is a bit low and they detect an older device then Apple might get away with not replacing as many batteries under warranty on those devices.  If the user gets another month or two before he gets pissed the company avoids warranty repairs.  There's enough incentive to do it right there; we need go no further.

Note that iPhones frequently do not go a full day on a charge.  Most lithium cells are good for about 500 cycles.  If you have to charge twice in a day this means that before one year is up you have a good crack at having a dead battery.

Which Apple eats, unless......


No, but a pretty darn good hypothesis.  And if they can get you to buy a new phone instead by thinking your "old phone" is "too slow" then it's so much the better -- for them, of course, even though the only real fault is that the battery has worn out.

There's no proof that's what is going on of course, but this is a scenario that fits what's being reported.....

Oh wait... there is proof.

Our goal is to deliver the best experience for customers, which includes overall performance and prolonging the life of their devices. Lithium-ion batteries become less capable of supplying peak current demands when in cold conditions, have a low battery charge or as they age over time, which can result in the device unexpectedly shutting down to protect its electronic components.

Last year we released a feature for iPhone 6, iPhone 6s and iPhone SE to smooth out the instantaneous peaks only when needed to prevent the device from unexpectedly shutting down during these conditions. We’ve now extended that feature to iPhone 7 with iOS 11.2, and plan to add support for other products in the future.

In other words rather than replace the batteries which are old and failing they'll "mask" it -- until it's on you and then hope you buy a new phone.

Oh, and cripple your device's performance at the same time which they also hope will cause you to buy a new phone.

Thanks for the admission, *******s.

Why didn't they pop up a message and warn you that the battery is compromised?


When does this firm have a zero stock price as a result of this sort of outrageous and intentional crippling of something you own for the explicit purpose of trying to con you into buying a replacement when they deliberately caused the condition you're complaining about?

When you stop behaving like children and demand that this sort of crap be met with a prison term.

Which will be never, right?

View with responses (opens new window)