HomeLatest ThreadsGreatest ThreadsForums & GroupsMy SubscriptionsMy Posts
DU Home » Latest Threads » Forums & Groups » Main » Latest Breaking News (Forum) » Suit: Apple slowed iPhone... » Reply #5

Response to Judi Lynn (Original post)

Sat Dec 23, 2017, 01:14 AM

5. Not defending Apple but...

I understand what they did in a fundamental sense and it appears to be a practical solution at face value. They can detect when a battery is getting aged (electrically soft) and the software revision forces the processor to slow down to prevent the phone from crashing.

Where I would fault Apple is in not clearly notifying customers as to exactly what their updates do, and what options are available to users (such as battery replacement). I'm not an Apple user (and never will be) but from what I've seen in friend's phones, the upgrades just start installing with no more than a simple yes/no window without any technical explanation.

My experiences with Apple customer service (helping friends) has not been good and their web site sucks. They assume everyone has an Apple-brain, LOL.

Maybe the law suits will get their attention and force them to be more informative and straightforward with customers.

Reply to this post

Back to OP Alert abuse Link to post in-thread

Always highlight: 10 newest replies | Replies posted after I mark a forum
Replies to this discussion thread
Arrow 23 replies Author Time Post
Judi Lynn Dec 2017 OP
virgogal Dec 2017 #1
ileus Dec 2017 #16
unblock Dec 2017 #2
cstanleytech Dec 2017 #10
mentalslavery Dec 2017 #3
elmac Dec 2017 #4
LineReply Not defending Apple but...
KY_EnviroGuy Dec 2017 #5
unblock Dec 2017 #13
JustABozoOnThisBus Dec 2017 #15
Jane Austin Dec 2017 #6
PoindexterOglethorpe Dec 2017 #7
cstanleytech Dec 2017 #11
PoindexterOglethorpe Dec 2017 #22
unblock Dec 2017 #14
Grins Dec 2017 #18
PoindexterOglethorpe Dec 2017 #23
emulatorloo Dec 2017 #8
DoubleAgentOrange Dec 2017 #9
dembotoz Dec 2017 #12
Grins Dec 2017 #17
moonseller66 Dec 2017 #20
DeminPennswoods Dec 2017 #19
crazycatlady Dec 2017 #21
Please login to view edit histories.