asendra
They are charging the same for almost two years old hardware than they would if It had been updated, but the user gets a worst product, and in the long run, experience.
the solution to the problem was the correct one, they just forgot one important detail.
TELL THE USER!
As a result, plenty of people, (including myself) noticing their two year phone starting to slow down quite a bit, decided to upgrade to the new and shiny model, instead of just replacing the battery, because who would have known that was the problem?!
“But the average American has less than $4,000 in savings, while 57% of U.S. adults have less than $1,000 to their names.”
https://www.usatoday.com/story/money/personalfinance/budget-...
There is no way to do all that properly with an Apple Watch as of today. Not to mention the pain that is to wait for the screen to turn on to see if you are running at the proper pace/HR vs a Garmin watch.
Apple watch just doesn't cut it. I own both (AW2 and Garmin 735xt) and I gave up trying to use the AW for any of the sports that I do. (Running, swimming, biking, gym, Triathlon)
I know that’s what happened to me with my 6s at least.
If your phone randomly shuts downs, or it last less time between charges, you know it must be a battery issue. You go to Apple or whatever, and fix it paying no more than 79$ (maybe even free if it still has warranty!)
If you hide it and degrade performance, people don't know its a battery issue, leaving them to suffer a slow phone, or spending 700+$ on a new phone.
No matter the good intentions, and the "good solution" they implemented, they fucked up.
It was painful to hear.
That's the main problem here.
Around the release of iOs 11 (not sure exactly when because it was gradual and I was also on the iOs 11 beta) my 6s became incredibly slow, almost unbearable, until last month I decided to upgrade to an X because of how slow it was. Was planning a year more but I just couldn't see myself using it 1 year more.
Now I see via CPU Dasher and Geekbench that my 6s with a battery less than a year old (95,7% original capacity, 406 cycles) is running at 1400-900Mhz, (almost always between 1200-1000Mhz) instead of 1800Mhz.
That has never happened before, there was no precedent for that, and no way of knowing it was a battery issue. The only solution for most people was buying a new phone.
a. Good luck when you run out of battery on your AirPods, or you loose one, or you forget them etc. It sure is nice to have the flexibility (Not to mention the much higher audio quality with proper iems/headpphones)
b. My X is considerably bigger and specially, heavier than my 6s.
I finally decided to upgrade to an X because how bad it was. Turns out it is throttling by as much as 50% (I still have the phone) so I could have just spent 79$ instead of buying a new iPhone.
The same will happen to a lot of people.
The battery still has 95.7% of the capacity, with 400 cycles, yet my device is throttling the cpu between 30% and 50%. It was how slow it was running that made me upgrade this year instead of the next which was my original plan.
If I had known that replacing the battery fixed the speed problems I would have saved the money.
They really need to communicate this reduced power state to the user.
What you really mean is that his car couldn’t account for his massive balls.
It’s racing ffs, if you can take it flat, you take it flat.
BTW, that's the half-size "bocadillo" there ;)