After borking my Pixel 4a battery, Google borks me, too
After borking my Pixel 4a battery, Google borks me, too
arstechnica.com
After borking my Pixel 4a battery, Google borks me, too
14 comments
-
I have to keep relearning the old lesson—as I am once again with this Pixel 4a fiasco—that cheap gear is not always the best value in the long run.
Not the conclusion I would've gone with but Google fans at this point aren't particularly pro-consumer
-
I know right? I was expecting "I will not buy Google again", not "I will buy the more expensive model next time"...
-
With all the stuff about the ruthless efficiencies of multinational corporations, I took it more to mean 'ill cough up the dough for a fairphone next time'. But maybe I'm projecting my own reaction to getting fucked by the 4a (all things considered, I'm actually kind of ok with the degraded battery life in the end, spent the 50 bucks on a couple external batteries and I rarely even need to use them).
-
Sounds like a justification to buy expensive Smartphone.
-
-
-
Why not just install Graphene? That's the only reason I'd spring for Google's hardware.
-
How would that help in this case? If the Google battery-nerfing update is legitimate, then it's preventing Pixel 4a phones from catching on fire or whatever.
To be clear, I'm not trying to justify Google's handling of this situation created by their own defective hardware fuckup.
Sent from my Pixel 4a.
-
-
Why not just roll back to the previous version? The Pixel 4a isn't supported anymore so it's not like you're missing out on security patches or anything.
-
Apparently it just affects certain batteries. Those affected can go boom.
I would not go back to the previous version.
-
I heard they removed the previous builds to avoid this very scenario.
-
14 comments