Apple has admitted they slow down your older iPhones. I explain what they mean and go over what they should do about it.
Gear I used to make this video: http://kit.com/Zollotech/zollotech-gear
Recent Wallpaper on imgur: https://imgur.com/Ul95qfk
Recent Wallpaper on Pinterest: https://pin.it/f2k2umioquqt6a
Support ZOLLOTECH on Amazon: http://amzn.to/2jxmglN
video music: Virgo – royalty free on AudioBlocks
Outro Music: “Sunday” by Otis McDonald – Available in the YouTube Create Audio Library
Good video, sir.
As I see it, one fix for this issue would be for Apple to add security updates to older iterations of the iOS and not decertify them – that way, owners of older iPhones who don’t want or need the latest and greatest apps and updates could still use a safe, snappy, quick iOS that is truly compatible with their device’s processor. Because one problem is just processor kludge coming from a newer iOS on a phone not optimized to use it.
The other issue is, of course, Apple’s software-induced throttling of the CPU when the battery can no longer handle the peaks – in itself, not a horrible thing, although inconvenient for owners who expect reasonably smooth and fast performance from their device. This is, in my opinion, not something Apple should have implemented under cover of night. It should have been clear that the throttling was happening, or it should have been optional, with Apple issuing a caveat that unless the user had a battery replacement, the phone was likely to power down or reboot at inopportune times.
There’s also been talk that Apple started this because of faulty batteries in the 6s line, rather than do a recall, to avoid negative press. But I don’t know much about that.
I will say that in my personal experience, upgrading my iPhone 6 to iOS 11 so I could backup and be ready for my new iPhone X, the iPhone 6 has become pretty much unusable since I left iOS 10.3 behind. It’s slow to open apps, it stutters, etc. The battery is at about 80% of its original capacity – I don’t believe this this a throttling issue, but rather an iOS issue, one that would be resolved if Apple gave users the option to choose the iOS they want on their particular device (my first point).