With Android 16, Google is also royally screwing over the AOSP community. Without proper access to the source, ROMs such as Lineage, Graphene etc. will suffer.
(My advice is not to stay on Stock ROM and accept Google invading your privacy but instead fight back by complaining to Google)
This is a safety feature since there’s a serious risk of battery overheating. I would be careful and accept the update or get the battery replaced by official google. Unless, of course you like to live a dangerous lifestyle.
The Pixel 4A update made my phone completely unusable. The battery meter became meaningless and I had to replace the entire phone.
An update that functionally bricks the device does make me safer, I suppose, but frankly I’d rather choose whether to take the risk. Now is not a convenient time to replace this damn device.
If this is a safety issue, google should issue a recall and pay for the mistake by replacing your battery for free. It’s their design flaw.
Also don’t promise 7 years of support if you brick the device 2 years in.
I’m not google. But, those affected by this issue should raise their voices and ask for free battery replacement and/or get discount for an upgrade to the pixel 8a or a free 7a upgrade.
I think google is banking on the fact that despite all this, people will stay with them and give a very slim discount. But only once they complained loud enough.
The do trade-ins all the time.
The thing is, bi-yearly phone replacements are not needed for most people anymore. Recent mid range phones can last double that.
Performance is good enough with modern SOCs. And new sets don’t have new essential features, so keeping them alive for cheap is a no brainer for most. Especially if support is promised.
Jesus, I moved from a Pixel 4A to 6A because of the damn issue. Should I flash LineageOS or something on here?
GrapheneOS is what I use. The installation was basically idiot-proof.
With Android 16, Google is also royally screwing over the AOSP community. Without proper access to the source, ROMs such as Lineage, Graphene etc. will suffer.
(My advice is not to stay on Stock ROM and accept Google invading your privacy but instead fight back by complaining to Google)
Isn’t source still available, but only final release branches? It would still be annoying, but it’s not turning into close source.
Yet, at least.
That’s what I was referring to: https://discuss.tchncs.de/post/38402246
This is a safety feature since there’s a serious risk of battery overheating. I would be careful and accept the update or get the battery replaced by official google. Unless, of course you like to live a dangerous lifestyle.
The Pixel 4A update made my phone completely unusable. The battery meter became meaningless and I had to replace the entire phone.
An update that functionally bricks the device does make me safer, I suppose, but frankly I’d rather choose whether to take the risk. Now is not a convenient time to replace this damn device.
If this is a safety issue, google should issue a recall and pay for the mistake by replacing your battery for free. It’s their design flaw. Also don’t promise 7 years of support if you brick the device 2 years in.
I’m not google. But, those affected by this issue should raise their voices and ask for free battery replacement and/or get discount for an upgrade to the pixel 8a or a free 7a upgrade.
I think google is banking on the fact that despite all this, people will stay with them and give a very slim discount. But only once they complained loud enough. The do trade-ins all the time.
The thing is, bi-yearly phone replacements are not needed for most people anymore. Recent mid range phones can last double that.
Performance is good enough with modern SOCs. And new sets don’t have new essential features, so keeping them alive for cheap is a no brainer for most. Especially if support is promised.