Live data from Hacker News

Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

androidcentral.com

71–80 of 370 posts

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#71
post #17
post #10

This needs more coverage. Perfectly good phones are getting thrown out because of a software update.

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.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#72
post #30
post #5

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…

I'm a weirdo who carries two pixel 4as. I'm also waiting for a response regarding the $100 voucher on one of my phones... My other one I took in for the free battery replacement, and that's doing OK. But yeah, I was planning to go for a Pixel 9 or 9a (when that's been out for a while), but this forcing of the hand by google is absolute BS, and the alternatives are unsatisfactory.

I recently ordered a Fairphone 5, imported from the UK. Stock Android experience, replaceable battery, SD card slot, unlocked bootloader and modding is encouraged. Its basically what the Pixel (Nexus) line was originally supposed to be.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#73
post #51

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)…

I was visiting my parents for the holidays and came across this exact mindset. I usually push them to update for security, but I learned that they stopped doing that this year. Apparently some update broke/removed/changed an accessibility feature on their phone in a way that I couldn’t figure out how to revert. My mom had updated her phone first so only she was affected. My dad now refuses to update his phone and both of them have completely stopped updating for fear that something else will “break”. I can’t really blame them, but it does worry me and now I’m trying to think of what I can do to secure their devices if they’re not going to update.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#74
post #51

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.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#75
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 and want to mitigate a repeat of the Galaxy Note 7 without saying it outright and causing a panic.

My least charitable view (and immediate reaction) is that they're purposely ruining a viable budget phone to make more sales.

Either of these are terrible. At no point has Google came out and stated -why- they're pushing this update in the first place. And as someone who hasn't updated I'd really like to know if my phone presents an immediate threat (and I'm sure Governments and airlines would also like to know) before I remotely consider an update that'll practically destroy my device.

On top of this, within a day of being notified about this update, Google drastically raised the price of new Pixels on their store. Again if I'm charitable it could just be automatic global market price updates, but that goes out the window when Google must have prepared this update, FAQs, support plans, etc, then released it just before said price updates. The $100 discount recourse doesn't go far when the 8a jumped from £379 to £499. It's hard not to feel suspicious about it.

While I'm here, I did briefly write about my experiences with the 4a, though I'm far from a competent tech writer: https://callmeo.live/blog/ode-to-the-pixel-4a/

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#76
post #17

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.

Isn't that just 3 years after release? Is that normal for Google phones? Yikes.

For older Google phones (as well as most other Android ones) it is the standard. (AFAIU this was mostly due to Qualcomm’s policies and lack of pushback from Google et al.) Newer Google ones get 5–7 years[1], and Samsung has also switched to a similar support term (but keep in mind that only Samsung’s flagships get monthly security updates).

[1] https://support.google.com/pixelphone/answer/4457705

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#77

Speaking as a Pixel 4a customer with this update: I received the update, and like everyone else, my phone battery started draining incredibly quickly. However, after getting the free battery replacement, my phone's battery has returned to draining as normal (and on the plus side, has somewhat renewed the life of this phone).

Ditto. Replaced battery, phone is as new.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#78
post #73
post #51

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)…

I was visiting my parents for the holidays and came across this exact mindset. I usually push them to update for security, but I learned that they stopped doing that this year. Apparently some update broke/removed/changed an accessibility feature on their phone in a way that I couldn’t figure out how to revert. My mom had updated her phone first so only she was affected. My dad now refuses to update his phone and bot…

Hmm. Assuming Android, install Firefox with uBlock Origin, and hide the Chrome and App Store launchers someplace deep?

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#79
post #73
post #51

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)…

I was visiting my parents for the holidays and came across this exact mindset. I usually push them to update for security, but I learned that they stopped doing that this year. Apparently some update broke/removed/changed an accessibility feature on their phone in a way that I couldn’t figure out how to revert. My mom had updated her phone first so only she was affected. My dad now refuses to update his phone and bot…

The software industry has known how to do this for a very long time, but some companies refuse to do it. You maintain a "sustaining" branch just for security and other legitimately urgent fixes, and a main branch for everything else. Users are nudged more strongly to apply the sustaining fixes and the main update branch should be optional.

We have immensely powerful version control and branching at developers' disposal, much better than at any past time I can think of. Yet, most companies insist on having a single release that increments, and users must take everything or nothing whenever they update.

Phone/OS manufacturers are actually better than most, and both major operating systems do provide security updates in parallel with major (feature) updates, but only for a very short amount of time.

Re: Google Pixel 4a's old firmware is gone, trapping users on buggy battery update

#80
post #78
post #73

Earlier quoted context omitted.

I was visiting my parents for the holidays and came across this exact mindset. I usually push them to update for security, but I learned that they stopped doing that this year. Apparently some update broke/removed/changed an accessibility feature on their phone in a way that I couldn’t figure out how to revert. My mom had updated her phone first so only she was affected. My dad now refuses to update his phone and bot…

Hmm. Assuming Android, install Firefox with uBlock Origin, and hide the Chrome and App Store launchers someplace deep?

It’s not an ad thing. It was an OS level accessibility feature dealing with text sizing and other reading related settings.
Post reply on HN