Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Apple openly admits they never even once tested iOS in the real world!

2 views
Skip to first unread message

Harry Newton

unread,
Dec 29, 2017, 10:45:40 AM12/29/17
to
*Apple openly admits they never even once tested iOS in the real world!*

Verbatim quote:
"Apple is basically telling us that it+IBk-s not testing iOS updates
appropriately."

*Apple makes its *users* do the testing for them!*

Verbatim quote:
"Apple had to wait for user feedback to realize that the iPhone slowdown,
which Apple caused, is to blame for the poorer user experience on older
iPhone 6 and iPhone 6s devices."

Reference:
<http://bgr.com/2017/12/29/iphone-slowdown-scandal-apple-fix/>

Harry Newton

unread,
Dec 30, 2017, 4:44:43 AM12/30/17
to
On Fri, 29 Dec 2017 15:45:38 +0000 (UTC), Harry Newton wrote:

> Reference:
> <http://bgr.com/2017/12/29/iphone-slowdown-scandal-apple-fix/>

This is the truth.


1. They put in the "wrong batteries" (we can get into the details of the
CPU demands and "chemical aging", but suffice to say they didn't test the
devices since Apple never tests anything in the real world - so they were
surprised by the unexpected slowdowns - which simply means that it was the
wrong battery for the given phone).

2. Many people report the unexpected shutdown issue on iPhone 6S. Apple
investigates and finds a "very small number of iPhone 6s devices" get an
official recall. In their statement, they're very specific about the root
cause: "a battery component that was exposed to controlled ambient air
longer than it should have been".

3. Soon after, Apple says iPhone 6S battery issue turned out to be bigger
than first thought and that they "would be releasing a software update next
week to garner more information".

4. Two months later, Apple comes out with a software update with a "fix"
that (magically) reduces unexpected shutdowns by 80%. This is a separate
issue than the initial assessment of a "battery component that was exposed
to controlled ambient air longer than it should have been".

5. It turns out that in iOS 10.2.1 an Apple genius came up with the bright
idea of *secretly*, *permanently*, and *drastically* throttling the CPU
speed (in half!) which instantly "reduces the unexpected shutdowns by 80%".

6. Of course, they could have added a few sentences in Battery (in
Settings) explaining that the permanent & drastic throttling was active and
how to solve it (changing the battery). Does this mean that some people are
going to change the battery when Apple would prefer them to just buy a new
iPhone? Absolutely. But this is the kind of thing you would expect a
reputable company to do: being transparent and explaining themselves even
if that means losing a few phone sales.

7. Of course, Apple could have disclosed that performance would be
drastically affected when they released 10.2.1; but you only expect that
type of honesty from a reputable company.

8. Apple did not disclose the root cause of the "second" issue, despite
being incredibly specific about it the first time.

9. Apple didn't disclose who would get performance reductions as part of
their fix; hence it's entirely possible some users were throttled right
away (which was a little over a year after the 6S even came out) - which
would explain why Apple wouldn't be upfront about what the fix was.

10. Apple support wasn't informed that replacing batteries would have any
impact on performance so they never recommended customers just replace the
battery when they complained of the unexpected shutdowns and the subsequent
"fix" of permanently throttled CPUs.

11. Apple desperately tries, as does nospam, to palm this all off as
"normal" when it's patently obvious that no other smartphone has
"unexpected shutdowns" unless it's from a faulty battery. Apple is
duplicitiously trying to portray this as this can happen to any normal
functioning device, but it's really done just so they don't have to replace
faulty hardware they've sold to the unsuspecting customer.

12. Apple releases a bullshit explanation which isn't even in the least
true because they use clever phrases (like "dynamically managed") that
don't imply to the casual reader what everyone who knows about batteries
knows - which is that there is no battery fairy that magically "fixes"
batteries that are pematurely "chemically aged" already.

To wit:
"This power management works by looking at a combination of the device
temperature, battery state of charge, and the battery's impedance.
Only if these variables require it, iOS will dynamically manage the
maximum performance of some system components, such as the CPU and GPU
in order to prevent unexpected shutdowns."

iPhones with older batteries may also more aggressively dim their screens,
have lower maximum speaker volumes, and even have their camera flashes
disabled when the system needs more peak power than the battery can
provide. The whole approach actually quite clever, but *secret*,
*permanent*, and *drastic* (throttling to half the original CPU speed)
isn't a substitute for the lost speed.

harry newton

unread,
Jan 1, 2018, 8:56:35 PM1/1/18
to
Everyone but the Apple Apologists realizes Apple never tests iOS in the
real world!

Verbatim quote:
"*Having thrown out rushed update after rushed update*
(*often to detrimental effect*), iOS 11.2.5 needs to restore
customer confidence."

<https://www.forbes.com/sites/gordonkelly/2018/01/01/apple-ios-11-2-5-release-iphone-battery-problem-slow-down/#655237bc3b5c>

Customer

unread,
Jan 2, 2018, 4:44:04 AM1/2/18
to
If you think Apple is evil, consider this:


I purchased a *new* Verizon branded HTC smartphone 20 months ago.  I'm not sure who to blame but "they" still have not published a wpa2 KRACK fix.

FWIW, Microsoft, Linux *, dd-wrt, Ubiquiti and other e-toy manufacturers released patches within days.


Do you think I'll ever buy another HTC, Android or Verizon product again?



0 new messages