91–100 of 370 posts
Same problem here (a few hours of battery life and it's very slow to charge now). This update makes no sense at all, excepted if you want to force your users to buy a new phone. For me, it should be a RED flag on the Pixel lineup and on the confidence in Google. I filled https://www.stopobsolescence.org/ .
Just bought a pixel 9 pro fold. I am now returning it. Tricks like this mean I won't be a customer.
I received the email from Google notifying me of this "battery performance update" for my Pixel 4A which actually drains the battery faster , so it left me scratching my head wondering what a "performance update" is for Google. After the update, my battery was depleted at an alarming rate. I applied for the $100 voucher but I've never heard back from Google. So I decided to bite the bullet and moved to iPhone instead…
Am I the only one that had the immediate thought of "this seems intentional" when they read that they're offering the credit for a newer pixel?
> Google has acknowledged the mess and offered compensation: a free battery replacement, $50 cash, or $100 credit toward a new Pixel.
Hi, (soon to be ex) Pixel 4a user here. Regardless of why this update has happened, the way Google have went about this update is sketchy at best, and deceitful at worst. To be plain: this phone has been EOL for 1½ years now. This update has appeared out of the blue and specifically decimates the battery + charging capabilities. My most charitable view is that Google have found a major fault with the Pixel 4a battery…
I really hate how in subsequent generations, they faithfully cloned Apple's design decisions of removing ports and making the device gigantic.
"For customers who are dissatisfied with iphones,
Our product is a slightly different iphone-like device."
I mean come on now, what the hell...
About twice a decade google makes a good phone and the others are just iphone knockoffs
Earlier quoted context omitted.
Google 4a user here. They pushed an update while I was on a ski trip in Korea - I updated an hour before getting on my bus and.. the application launcher started crashing on unlock. I couldn't open any apps. Thankfully, I was able to get into the settings and switch to Lawnchair without a working "desktop UI", but without a second application launcher I would have been totally screwed. I checked the Play Store afterw…
Nonsense like this is why I personally will never buy a google hardware product ever again. It is also why it is so difficult to recommend an android phone because of google being an advert company first.
(My Pixel 6 is rock solid on that by the way.)
Earlier quoted context omitted.
Google 4a user here. They pushed an update while I was on a ski trip in Korea - I updated an hour before getting on my bus and.. the application launcher started crashing on unlock. I couldn't open any apps. Thankfully, I was able to get into the settings and switch to Lawnchair without a working "desktop UI", but without a second application launcher I would have been totally screwed. I checked the Play Store afterw…
Nonsense like this is why I personally will never buy a google hardware product ever again. It is also why it is so difficult to recommend an android phone because of google being an advert company first.
Earlier quoted context omitted.
Google ended security updates for the Pixel 4a in August 2023, so running this as your daily driver was already problematic. Fortunately, LineageOS officially supports the 4a, and v22 (aka Android 15) was just released for it.
This attitude (and the word "problematic") is so tiring. What is the actual problem with running it as your daily driver? What specific vulnerability are you actually concerned about? Unless there's something like an arbitrary code execution bug in one of the networking/radio stacks, "there aren't updates" is a statement with approximately zero useful information.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-43096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377...
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4377...
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49747
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-49748
These are just the RCE bugs without user interaction that were fixed with the January update. They are in the Bluetooth stack.
As soon as they dropped the Nexus line, things went downhill fast. IMO the nexus 5 was peak android.
Concur, switched to iPhone around this time, as Android just started to feel like a knock off iOS rather than an alternative.
Earlier quoted context omitted.
Google ended security updates for the Pixel 4a in August 2023, so running this as your daily driver was already problematic. Fortunately, LineageOS officially supports the 4a, and v22 (aka Android 15) was just released for it.
This attitude (and the word "problematic") is so tiring. What is the actual problem with running it as your daily driver? What specific vulnerability are you actually concerned about? Unless there's something like an arbitrary code execution bug in one of the networking/radio stacks, "there aren't updates" is a statement with approximately zero useful information.
*Written from my 4a.
I'm (we all are) constantly reminded to update our phones to latest available updates, but sh*t like this is what teaches users to instead disable and ignore updates indefinitely, under the premise of "if it works don't touch it" (addendum: "... because most probably an update will break it") And here I am, ignoring updates on my Pixel 6a since October 2024 (there were reports of crashes or bricking, what a surprise)…
The way Google botched the Android 11 update to my Pixel 4a was the nail in the coffin in convincing me to go back to iPhone. I don't want to upgrade my Android and see a totally different UI every single time. I want consistency and I don't want Google to mess with things that already work. This is very childish on their side and just shows that Google engineers and managers don't use their own products.
Unfortunately, that is exactly how Google rewards performance internally