zlacker

>>kotaKa+(OP)
Google is doing everything in their power to make me move to an iphone... between shit like this, effectively bricking some old models of pixels with un-rollbackable patches that destroy batteries, closing down the android development process, making absurd testing requirements to publish apps, etc.

Google doesn't make better phones, they were just less hostile to the consumer. That seems to be going away :(

>>gpm+ct
Wasn’t Apple the one actually caught throttling devices with an update to slow phones down under the guise of "saving battery"?

Leaving Google for Apple, and expecting a more open app store, is going to be disappointing. I’m not a Google fanboy by any means, just pointing out the landscape out there

>>james2+Uu
Apple throttled devices that had a weak battery, because the alternative is the CPU trying to draw more power than the battery can deliver, the voltage sagging, and the phone rebooting.

By itself, this throttling is a good thing and keeps phones usable for longer, because a phone that is slow is better than a phone that randomly reboots.

The problematic part was that they a) didn't disclose it, and b) did this for phones within the warranty period, so instead of the phone visibly crashing and you returning the obviously broken phone, it just lost performance which you might not have noticed in time to get a free replacement.

>>tgsovl+wz
The Nexus 6P had the same issue with random shutdowns, and although Google refused to do anything about it some users on XDA developed a patch that disabled all the performance cores completely.

> XDA user XCnathan32, along with assistance from two other users, created the fix and put it up for anyone to give it a whirl. Without getting too technical, the fix shuts down all four of the Nexus 6P octa-core Snapdragon 810 processor’s performance cores that seemingly prevent the phone from properly booting

https://www.androidauthority.com/nexus-6p-bootloop-fix-78930...