I already stated as much my guy, they screwed up letting users know what was going on. First in the release notes, second in the press release they put out about it. That’s why Apple was found to have deceived customers and rightfully so.
I’m not arguing that. I’m just stating the intentions behind it have been completely dominated by the media and reader’s reactionary responses to hearing “Apple slowed down your phone”. All I ever said here was that there was a very good reason for doing so, and it wasn’t planned obsolescence.
As for lineageos, it also slows down the CPU as needed when a consumed battery cannot output the necessary power or when the operating temperature exceeds safe limits. Most OSes do that. The ones that don’t cause data corruption.
You seem to misunderstand the issue still. It’s not an OS issue. It’s an issue with a consumable part becoming consumed. Until the update, iPhones just shut off when the OS tried to pull too much power. All Apple did was trade shutoffs (compromising user data) for dynamic CPU throttling (sometimes slower performance but your data is fine). Where they screwed up was in telling the users what they were doing and why.
It doesn’t matter if we’re talking about iOS, Android, a fork, or something else. An OS has battery management capabilities or it doesn’t.
That doesn’t change the fact that Apple should’ve been more transparent, but you’re not avoiding this very common method of resource management because of the type of device you have, unless lineageos can defy the laws of physics and consumable batteries.
I already stated as much my guy, they screwed up letting users know what was going on. First in the release notes, second in the press release they put out about it. That’s why Apple was found to have deceived customers and rightfully so.
I’m not arguing that. I’m just stating the intentions behind it have been completely dominated by the media and reader’s reactionary responses to hearing “Apple slowed down your phone”. All I ever said here was that there was a very good reason for doing so, and it wasn’t planned obsolescence.
As for lineageos, it also slows down the CPU as needed when a consumed battery cannot output the necessary power or when the operating temperature exceeds safe limits. Most OSes do that. The ones that don’t cause data corruption.
You seem to misunderstand the issue still. It’s not an OS issue. It’s an issue with a consumable part becoming consumed. Until the update, iPhones just shut off when the OS tried to pull too much power. All Apple did was trade shutoffs (compromising user data) for dynamic CPU throttling (sometimes slower performance but your data is fine). Where they screwed up was in telling the users what they were doing and why.
It doesn’t matter if we’re talking about iOS, Android, a fork, or something else. An OS has battery management capabilities or it doesn’t.
That doesn’t change the fact that Apple should’ve been more transparent, but you’re not avoiding this very common method of resource management because of the type of device you have, unless lineageos can defy the laws of physics and consumable batteries.