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.
Unless your Pixel 4a is from Verizon (locked), keep it.
Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk.
Once you have Magisk stabilized, install the Advanced Charging Controller, and configure it to halt charging at 80%.
That should solve your problems, and turn the updates back on. I don't think there is a way to make Google Pay work in this configuration, which is a drawback.
Problem with pretty much every modern battery-powered device is that battery is flogged to near death at every charge. From @marcan's mastodon post, Pixel 4a's battery is charged to 4.45V:
qcom,max-voltage-uv = <0x43e6d0>;
This is completely insane, and it's a small miracle that this phone didn't follow Note7's fate.
As for charge limiting... limit at 80% is an okay workaround (certainly better than no limit at all!), but it's far from perfect. Namely, with this approach, charge controller chip doesn't know cut-off is coming, and will shove several amperes into the battery until last second, thus overshooting safe voltage level. This wears the battery (less so than with no limit, but still more than necessary).
Battery charging limiting should be done by voltage: this way, controller chip knows where to stop, so it makes soft taper-off at the end of charge cycle, by gradually nudging current down to stay within voltage envelope.
Charging profile could be observed from a rooted adb console:
grep NOW <$(find /sys/devices/platform \
| grep battery/uevent$ | head -1)
(depending on phone model and firmware, some tweaking might be required to find/grep to get the right battery status file)
I'm not who you replied to but can you please do? I've been wanting to make a LineageOS device for a while but was being cheap (and it wasn't high enough priority). But maybe now there will be a lot of cheap Pixel 4a on eBay in the near future and I'll go for it.
>>> Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk.
Unless you have researched this and are comfortable doing these things, this is not something that's easy to do. I bricked my OnePlus Nord100 not once, but TWICE trying to install Ubuntu Touch.
It happened because the Nord100 shipped with a more current Android version (11.xx) and Ubuntu can only be installed over two very specific versions (10.xx) on the Nord. I bricked it once thinking it could be installed over the 11 version. Then I had to figure out how to reflash the phone back to the 10 version, then run the UBports installer.
I was lucky because I bought the Nord100 for like $50 on ebay so it wasn't a big deal if I wasn't able to unbrick the phone, but if you do this to a more expensive phone, the consequences are a lot more expensive.
I love Lineage OS and have it running on a Pixel 4XL, but my experience flashing and re-flashing the phone several times, and all the work I went into just to get UT running on that phone, really dampened my enthusiasm to ever do this again.
Thanks for the info! My pixel has already applied the update unfortunately - any ideas if switching to lineageos is still helpful in that case?
They’re not offering the free battery replacement in Aus otherwise I’d do that - hard to be sure that getting a new battery in a local repair shop wouldn’t be similarly affected by the new limits (presumably some sort of blacklist on serial numbers?).
"Either of these are terrible. At no point has Google came out and stated -why- they're pushing this update in the first place."
As I can still remember the days of software before "updates", I am still baffled by the always unsolicited "advice" amounting to "always update" without even considering what's in an "update". This "advice" is everywhere. Software quality control is at all-time lows I guess. Then came "automatic updates", decreasing the chance of computer user discretion even more, effectively removing user choice, i.e., case-by-case decision-making.
Perhaps some computer users, the rare ones who do not routinely follow unsolicited "advice" blindly, might respond to the question of updating with something like, "What choice do I have?" That there is no meaningful choice, or perception thereof, in deciding whether to install an "update" is not a coincidence, methinks.
Maybe updating is a gamble. There are winners and losers. On several occasions, I have won by not updating, i.e., blindly installing more code from so-called "tech" company without being to peruse the code. Other times I have gotten lost by updating. It seems that quite often the "updates" include code that serves me no benefit and in fact reduces the computer's utility to me. Meanwhile, it might increase utility for others or for the so-called "tech" company that collects data and sells ad services. One size does not fit all. Sometimes the losses can outweigh the gains, if any.
Hopefully there is a lawsuit filed over this Pixel 4a "update". Through discovery we may be able to learn what happened.
There's seems to be an army of aspiring CVE bros cargo-culting this idiocy; they pretend to live in a parallel universe where state-sponsored intelligence groups are spending millions to get at the cat photos on their phones.
Obviously the premise that you should just blindly update a device where you have no recourse if the update breaks workflow/functionality/user experience (android, ios) or tries to monetize the hardware you actually own (msft) is prima facie stupid.
> At no point has Google came out and stated -why- they're pushing this update in the first place.
The cynic in me recommends that anyone contributing to Google (or really any big tech company) projects to use "bug fixes and performance improvements" or "What's new:" (with an empty body) as commit messages and refuse to update them until we get useful changelogs for app updates.
>My least charitable view (and immediate reaction) is that they're purposely ruining a viable budget phone to make more sales.
My wife was using a pixel 4 until last year and upgraded to a 7, I took her old phone and switched it over to my info and used it for like 2 days before it got a random update and refused to ever work again. Her 7 just got an update a couple of days ago and the battery went dead and it refused to boot until it'd been plugged in for an hour and then would only boot into recovery mode before finally returning to normal. I think google just has something really screwed up with their update process.
Google pixel software is horrendous, shocking honestly for a company with Google capabilities. Bought pixel 6 at launch, could not take calls after an update (the speaker would just emit a high pitch tone 15s after connecting, I had to ask people to call me using messaging apps for a while, lucky I did not rely on my phone for work) and wifi would switch off by itself randomly and needed to restart phone to get it working again. Had to update to beta build to get these fixed. For my model and others, it seems like every update or 2 there are populations that hit the forums with battery drain issues. I will never buy a pixel ever again.
Great comment, even though I'm concerned whether my Pixel is a ticking bomb now. The update has been downloaded to my device, but before installing it, I decided to check Reddit and found out the battery issues. Since then, I'm dismissing the update prompt, praying to not miss-click.
The article got it wrong - even before the update has been published, Google already sent e-mail to registered users with a note that the upcoming update may reduce battery life and offered either battery replacement or money: https://support.google.com/pixelphone/answer/15701861 But the results people post are way beyond anyone expected.
Google products have consistently been timebombs. I recall the Nexus 7 which had storage that would grind to an unusable halt after a few years.
They don't have the culture or the integration to properly support old devices the way Apple can. Everyone vilified Apple for CPU governers that extended device life by underclocking instead of browning out... this is the kind of behavior that would have deserved the backlash they got.
But the bar is so low with Google and Android devices in general that the outrage will be limited.
The repair places have been overwhelmed; I've had three apppoints to replace my wife's 4a battery that have been cancelled because they ran out of stock due to huge unexpected demand.
> My least charitable view (and immediate reaction) is that they're purposely ruining a viable budget phone to make more sales.
Given the legal & regulatory trouble Apple got in and is currently in depending on jurisdiction for doing this, it seems highly unlikely Google would have picked now to attempt the same thing. Especially since it's literally a single device, and even the sibling 4a 5g didn't get the same treatment.
Apple did not “do this”. Apple ole didn’t ruin a perfectly good phone with an update. The throttling they did on phones with old batteries kept them from shutting off completely.
I feel this a lot. Android's used to differentiate themselves from iPhones by having useful technical features at a competitive price. I used to be die-hard pro-Android, but now I can find very few reasons to buy one.
Now the Android UI is sparse and wobbly, Androids lost call recording, sideloading is limited, and they raised their prices to cost as much as iPhones.
Meanwhile, iPhones got call recording, they opened up NFC (a bit) and they support CalDAV and CardDAV and SMB natively in its built-in apps. The "control center" on iOS is customizable, to the point they do what Android's quick tiles did before 2020 or so.
It's very frustrating-- I wish they still made Androids like they used to :(
I think I noticed around ios 7 things were getting bad. buttons didn't look like buttons, on-screen controls started being hidden, and form trumped function. Then like you said, ports disappeared and to me "do the wrong thing correctly" started winning.
but the worst thing is that apple sets an example. The same "simplify for sales, but not usability" technique has happened to countless other products in many industries. all laptops have elegant looking keys that have no curve to fit and center your fingers. Tesla cars have a pleasing-looking design, but when you drive them, you can't lean on the touchscreen to hit targets, you don't have drive selection or turn signal stalks to help you get into a parking space easily, and "elegant simplicity" is "cost cutting for the peons".
Did the 4a have anything other than an aux port? I definitely still miss it, having moved onto a Pixel 7, but on the other hand I've also mostly stopped listening to anything with headphones from it. In surprising fashion, the fact that my screen is still intact and I feel pretty comfortable watching videos in the shower has proven more valuable.
I also own a 4a - the amount of hoops Google performed to explicitly prevent downgrades for (only) the 4a by removing all old Android images (and only for it) leads me to fear your charitable view is true. Only the tinyest sliver of customers would ever try to downgrade / reflash their phone, it IMO doesn't make sense to do this if they just want to increase sales a bit. And then again, why only for the 4a.
Which, should it be true, would make the lack of explanation from Google horrible and asinine. If (and this is a big if, it's all speculation, because Google doesn't open their mouth) there is a hardware fault with the battery, I would very much like to know outright as a customer, no matter the PR damage for Google.
>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.
See the Fitbit Charge 5 issue from 2023 and it just happened again with the Sense and Versa...
My Pixel 4a battery started swelling up recently. I assume it's a Note 7 problem they are trying to avoid. Google did pay me $50 for my phone which is not too bad.
If they were trying to "purposely ruin a viable budget phone", what about the rest of now obsolete and just as budget Pixels? (like 3a, 4a 5g, 5a, etc.)
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) and planning to keep doing that for the foreseeable future.
Sucks having to choose between a potentially (even likely, seeing the trend) broken device or an unsecured one. Pick your poison.
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.
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.
Frankly, even the scarequotes around break feel misplaced. Your Mom can't use the device like she wants to. An accessibility feature is gone to the point you can't get it back. That feels pretty broken to me.
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 afterwards and saw hundreds of people with the same issue.
On Linux I can choose which "security" updates to install, and only install those. Why can't Windows and Android provide such a feature?
Stuff like this is why I keep printing entrance tickets and the like. I don't want to end up in a situation where I have to trust software that is known to have new bugs every months to get into a place without any sort of backup.
> Why can't Windows and Android provide such a feature?
Windows does.
Android "can't" because the OS is a partition image with libraries not intended to be updated piecemeal, not a collection of loosely related external projects like Linux is.
>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.
I had that happen like a year ago while I was getting ready to go to a concert in another state. Luckily I was able to call my wife have her login to my gmail and forward my digital tickets to someone else in my party.
It's crazy- I feel like outside of videogames, and sometimes programming languages, almost every single "update" makes things worse.
They shuffle the UI around, or put in more ads, or recently- add some new AI feature. Genuinely can't remember the last OS or App update I've been happy about.
Makes me sad to think of all the developers working long hours just to make their users upset.
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.
I think security updates are mostly BS designed to make users voluntarily give up control. Almost nobody would ever be affected by these CVEs but the ceding of control affects everyone.
If you ignore updates, you will get hacked. If you think a bad update is a problem, wait until you have to clean up a hack. It will cost more money and take more time than buying a new phone.
My advice is to buy phones from reputable manufacturers. I have had an iPhone for over 10 years and I have been very happy. The work well, last, and the performance is always good. My current goal is to keep my current phone 7 years. I will update it when Apple stops supplying updates.
> My advice is to buy phones from reputable manufacturers.
You mean those slowing down your phone on updates [0] and not providing critical security updates in time [1] while not allowing existing more secure alternative browsers [2]?
The true alternative is phones running mainline Linux. Sent from my Librem 5.
(EDIT: Just to be clear, and which is also mentioned in that post: unlocking the bootloader will reset the device. If your device is already unlocked though, you will be able to keep the data.)
Of course, I would just advise to switch to LineageOS directly, since Google has stopped providing security updates for the Pixel 4a already in August 2023. I've run LineageOS for years on the Pixel 4a and it has worked pretty much perfectly for me:
I'd also be interested to know if a Google Camera app installed post-facto to LineageOS is compatible with the remote control & viewfinder of the Pixel Watch.
Well, they are good enough for me, but to be honest, I'm not particularly picky... As said in a parallel post, you can get GCam in APK form (I run LineageOS without GApps) but I hear it's a bit trial&error to find one that works and I haven't bothered.
There's a nice video about this from Louis Rossmann [1] that talks about this in detail and tries to find some reasons for it, and he seems to suggest that the update was never about improving the battery life as in getting more usage per charge out of the battery, but improving it as in limiting the battery full charge capacity to minimize potential problems with it, because he (and others) assume that they identified bad batches and are trying to fix potential problems with them by limiting it.
This destroyed my phone, and their appeasement process was terrible too. There was no way for me to find out whether there was a supported repair shop nearby, the $50 cash was apparently through a very dodgy company, and then $100 google store credit didn't disclose that it's "upon review within three weeks" until after you irrevocably chose the option.
The whole thing is ridiculous and poorly handled. Sadly, if my phone had just cracked or failed to turn on, I'd probably have upgraded happily and moved on with my life. As it is, now I feel like something was taken from me. So it goes
I was a Nexus/Pixel user for 10+ years. Majority of the phones I owned during that time had some quirks or issues. The worst examples were Nexus 5X and Pixel 5 – both just suddenly froze one day, shut down, and never turned back on again. After that Pixel 5 surprise I grudgingly switched to iPhone 12 mini.
I still think Google’s Android UI is the best one out there for me, and I despise a lot in the iPhone UX (such as the keyboard) but I just need a phone that works and I can get repaired or replaced easily if I need to. At least in Finland, Google’s customer service has been abysmal over the years.
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. Apple might not be the best, but this was the last straw for me.
Lol this was the most blown out of proportion "gate" ever and a nothing burger really. The issue wasn't what Apple did, as it is a very common practice in the industry and I bet almost every other manufacturer did it too. The issue was that they didn't notify the user.
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.
I'm semi homeless and the forced Pixel 4a battery update made my phone unusable and I'm in a state of tears. What can I do? Reddit deleted my post (I am hoping it's not because of Google employees)
I don't want to get too long into what happened in my life, but I had a Pixel 4a and everything was running great. Even when I was on the streets homeless I was able to charge it. I'm still struggling in and out, and apparently there was an update that came automatically to my phone. I checked and talked to live support in the library and they said it was just a battery update and it will last a bit less. That wasn't a big deal I thought but now the update came and my battery went from many hours to maybe half an hour now and doesn't charge at all or very slowly. I have interviews and some other small jobs that I have to do and just hard life right now and I do not have any money for this. I am a bit emotional so I asked while tearing up to Google support why they did this and I can't afford this my life is in shambles but they didn't help me. Even with the battery replacement I do not live near any local shops and mailing it in would not be possible for my situation. I bought this phone when my life was good and I only like this one and want to use this one.
All my stuff is on here and I don't know too much about phones so I just want this to work. I don't have money to fix this. I feel like the phone will die any second. What can be done? I didn't know they would do this. My life just keeps getting worse... I always feared my phone getting stolen on the streets but never thought Google would steal my phone.
What can I do? I don't have much minutes or data and can't afford it, is there a number I can call Google directly? I don't want to play with the phone and do anything weird my life is on it and can't back it up.
I'm trying to figure out what the actual latest update is doing regarding the battery. I found an update to the kernel binary but it doesn't seem the source has been updated.
Can I submit a GPL request to Google to get the kernel source?
If you own a device, you're entitled to a copy of all GPL software that came with it, including some build tools. However, if the diminished battery performance comes from some kind of firmware update for an embedded microcontroller, you're probably out of luck there, unless that controller also runs GPL software.
But apparently sunfish-kernel only contains binaries.
Given there's an update to Image.lz4, that seems there's an update to the kernel. I also compared the binary to the previous version and found some new strings possibly related to battery charging profile.
If you're reversing this: I was curious if Google determines if your device is "affected" using the phone's serial, or the battery's serial. I've seen reports that people who replace the battery manually outside of the program still experience diminished performance. But of course that could just be because they replaced their defective battery with another defective battery.
Readit News
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/
Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk.
Once you have Magisk stabilized, install the Advanced Charging Controller, and configure it to halt charging at 80%.
That should solve your problems, and turn the updates back on. I don't think there is a way to make Google Pay work in this configuration, which is a drawback.
I can put all the URLs here if you ask.
Edit:
https://lineageos.org/
[I did not remember that Lineage hosts gapps images]
https://wiki.lineageos.org/gapps/
[IIRC, the APK is renamed to a ZIP and flashed with recovery, then name it back and install the app]
https://github.com/topjohnwu/Magisk/releases/tag/v28.1
https://magiskmanager.com/
https://github.com/VR-25/acc/releases/tag/v2023.10.16
As for charge limiting... limit at 80% is an okay workaround (certainly better than no limit at all!), but it's far from perfect. Namely, with this approach, charge controller chip doesn't know cut-off is coming, and will shove several amperes into the battery until last second, thus overshooting safe voltage level. This wears the battery (less so than with no limit, but still more than necessary).
Battery charging limiting should be done by voltage: this way, controller chip knows where to stop, so it makes soft taper-off at the end of charge cycle, by gradually nudging current down to stay within voltage envelope.
Charging profile could be observed from a rooted adb console:
(depending on phone model and firmware, some tweaking might be required to find/grep to get the right battery status file)That will reduce future wear, but won't suddenly make the battery better. If anything it'll make the battery even worse, at least in the short term.
[0]: https://www.xda-developers.com/psa-magiskmanager-com-not-off...
[1]: https://github.com/topjohnwu/Magisk
I'm not who you replied to but can you please do? I've been wanting to make a LineageOS device for a while but was being cheap (and it wasn't high enough priority). But maybe now there will be a lot of cheap Pixel 4a on eBay in the near future and I'll go for it.
Unless you have researched this and are comfortable doing these things, this is not something that's easy to do. I bricked my OnePlus Nord100 not once, but TWICE trying to install Ubuntu Touch.
It happened because the Nord100 shipped with a more current Android version (11.xx) and Ubuntu can only be installed over two very specific versions (10.xx) on the Nord. I bricked it once thinking it could be installed over the 11 version. Then I had to figure out how to reflash the phone back to the 10 version, then run the UBports installer.
I was lucky because I bought the Nord100 for like $50 on ebay so it wasn't a big deal if I wasn't able to unbrick the phone, but if you do this to a more expensive phone, the consequences are a lot more expensive.
I love Lineage OS and have it running on a Pixel 4XL, but my experience flashing and re-flashing the phone several times, and all the work I went into just to get UT running on that phone, really dampened my enthusiasm to ever do this again.
They’re not offering the free battery replacement in Aus otherwise I’d do that - hard to be sure that getting a new battery in a local repair shop wouldn’t be similarly affected by the new limits (presumably some sort of blacklist on serial numbers?).
If we install LineageOS, should we worry about Google's firmware update? Then why bother with all these steps?
Deleted Comment
As I can still remember the days of software before "updates", I am still baffled by the always unsolicited "advice" amounting to "always update" without even considering what's in an "update". This "advice" is everywhere. Software quality control is at all-time lows I guess. Then came "automatic updates", decreasing the chance of computer user discretion even more, effectively removing user choice, i.e., case-by-case decision-making.
Perhaps some computer users, the rare ones who do not routinely follow unsolicited "advice" blindly, might respond to the question of updating with something like, "What choice do I have?" That there is no meaningful choice, or perception thereof, in deciding whether to install an "update" is not a coincidence, methinks.
Maybe updating is a gamble. There are winners and losers. On several occasions, I have won by not updating, i.e., blindly installing more code from so-called "tech" company without being to peruse the code. Other times I have gotten lost by updating. It seems that quite often the "updates" include code that serves me no benefit and in fact reduces the computer's utility to me. Meanwhile, it might increase utility for others or for the so-called "tech" company that collects data and sells ad services. One size does not fit all. Sometimes the losses can outweigh the gains, if any.
Hopefully there is a lawsuit filed over this Pixel 4a "update". Through discovery we may be able to learn what happened.
There's seems to be an army of aspiring CVE bros cargo-culting this idiocy; they pretend to live in a parallel universe where state-sponsored intelligence groups are spending millions to get at the cat photos on their phones.
Obviously the premise that you should just blindly update a device where you have no recourse if the update breaks workflow/functionality/user experience (android, ios) or tries to monetize the hardware you actually own (msft) is prima facie stupid.
The cynic in me recommends that anyone contributing to Google (or really any big tech company) projects to use "bug fixes and performance improvements" or "What's new:" (with an empty body) as commit messages and refuse to update them until we get useful changelogs for app updates.
My wife was using a pixel 4 until last year and upgraded to a 7, I took her old phone and switched it over to my info and used it for like 2 days before it got a random update and refused to ever work again. Her 7 just got an update a couple of days ago and the battery went dead and it refused to boot until it'd been plugged in for an hour and then would only boot into recovery mode before finally returning to normal. I think google just has something really screwed up with their update process.
The article got it wrong - even before the update has been published, Google already sent e-mail to registered users with a note that the upcoming update may reduce battery life and offered either battery replacement or money: https://support.google.com/pixelphone/answer/15701861 But the results people post are way beyond anyone expected.
They don't have the culture or the integration to properly support old devices the way Apple can. Everyone vilified Apple for CPU governers that extended device life by underclocking instead of browning out... this is the kind of behavior that would have deserved the backlash they got.
But the bar is so low with Google and Android devices in general that the outrage will be limited.
Given the legal & regulatory trouble Apple got in and is currently in depending on jurisdiction for doing this, it seems highly unlikely Google would have picked now to attempt the same thing. Especially since it's literally a single device, and even the sibling 4a 5g didn't get the same treatment.
The silence is inexcusable, though.
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
Now the Android UI is sparse and wobbly, Androids lost call recording, sideloading is limited, and they raised their prices to cost as much as iPhones.
Meanwhile, iPhones got call recording, they opened up NFC (a bit) and they support CalDAV and CardDAV and SMB natively in its built-in apps. The "control center" on iOS is customizable, to the point they do what Android's quick tiles did before 2020 or so.
It's very frustrating-- I wish they still made Androids like they used to :(
They used to have a really good human factors/ui team. I remember Bruce Tognazzini and reading his blog.
https://en.wikipedia.org/wiki/Bruce_Tognazzini
https://www.asktog.com/
I think I noticed around ios 7 things were getting bad. buttons didn't look like buttons, on-screen controls started being hidden, and form trumped function. Then like you said, ports disappeared and to me "do the wrong thing correctly" started winning.
but the worst thing is that apple sets an example. The same "simplify for sales, but not usability" technique has happened to countless other products in many industries. all laptops have elegant looking keys that have no curve to fit and center your fingers. Tesla cars have a pleasing-looking design, but when you drive them, you can't lean on the touchscreen to hit targets, you don't have drive selection or turn signal stalks to help you get into a parking space easily, and "elegant simplicity" is "cost cutting for the peons".
sigh.
Which, should it be true, would make the lack of explanation from Google horrible and asinine. If (and this is a big if, it's all speculation, because Google doesn't open their mouth) there is a hardware fault with the battery, I would very much like to know outright as a customer, no matter the PR damage for Google.
See the Fitbit Charge 5 issue from 2023 and it just happened again with the Sense and Versa...
https://www.androidauthority.com/fitbit-sense-versa-3-batter...
The numbers just don't make sense.
Users who love 5-year-old phones can easily get a cheap used phone, which are in abundant supply.
And here I am, ignoring updates on my Pixel 6a since October 2024 (there were reports of crashes or bricking, what a surprise) and planning to keep doing that for the foreseeable future.
Sucks having to choose between a potentially (even likely, seeing the trend) broken device or an unsecured one. Pick your poison.
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.
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 afterwards and saw hundreds of people with the same issue.
On Linux I can choose which "security" updates to install, and only install those. Why can't Windows and Android provide such a feature?
Windows does.
Android "can't" because the OS is a partition image with libraries not intended to be updated piecemeal, not a collection of loosely related external projects like Linux is.
I had that happen like a year ago while I was getting ready to go to a concert in another state. Luckily I was able to call my wife have her login to my gmail and forward my digital tickets to someone else in my party.
It is also why it is so difficult to recommend an android phone because of google being an advert company first.
They shuffle the UI around, or put in more ads, or recently- add some new AI feature. Genuinely can't remember the last OS or App update I've been happy about.
Makes me sad to think of all the developers working long hours just to make their users upset.
Unfortunately, that is exactly how Google rewards performance internally
My advice is to buy phones from reputable manufacturers. I have had an iPhone for over 10 years and I have been very happy. The work well, last, and the performance is always good. My current goal is to keep my current phone 7 years. I will update it when Apple stops supplying updates.
You mean those slowing down your phone on updates [0] and not providing critical security updates in time [1] while not allowing existing more secure alternative browsers [2]?
The true alternative is phones running mainline Linux. Sent from my Librem 5.
[0] https://www.npr.org/2020/11/18/936268845/apple-agrees-to-pay...
[1] https://news.ycombinator.com/item?id=42780816
[2] https://news.ycombinator.com/context?id=42859836
https://xdaforums.com/t/undo-the-january-2025-update-without...
(EDIT: Just to be clear, and which is also mentioned in that post: unlocking the bootloader will reset the device. If your device is already unlocked though, you will be able to keep the data.)
Of course, I would just advise to switch to LineageOS directly, since Google has stopped providing security updates for the Pixel 4a already in August 2023. I've run LineageOS for years on the Pixel 4a and it has worked pretty much perfectly for me:
https://wiki.lineageos.org/devices/sunfish/
Android 15 (LineageOS 22) was just released for it.
Videos, on the other hand...
[1] https://www.youtube.com/watch?v=Xboo6sV-cJU
The whole thing is ridiculous and poorly handled. Sadly, if my phone had just cracked or failed to turn on, I'd probably have upgraded happily and moved on with my life. As it is, now I feel like something was taken from me. So it goes
https://images.ctfassets.net/d9ybqgejqp0w/7hP2z3Oyn8xH4TvFJt...
You can schedule an appointment here:
https://asurion.com
A retired coworker got a 4a off eBay two years ago, and it's eligible for a free battery replacement.
I still think Google’s Android UI is the best one out there for me, and I despise a lot in the iPhone UX (such as the keyboard) but I just need a phone that works and I can get repaired or replaced easily if I need to. At least in Finland, Google’s customer service has been abysmal over the years.
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. Apple might not be the best, but this was the last straw for me.
https://en.wikipedia.org/wiki/Batterygate
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 don't want to get too long into what happened in my life, but I had a Pixel 4a and everything was running great. Even when I was on the streets homeless I was able to charge it. I'm still struggling in and out, and apparently there was an update that came automatically to my phone. I checked and talked to live support in the library and they said it was just a battery update and it will last a bit less. That wasn't a big deal I thought but now the update came and my battery went from many hours to maybe half an hour now and doesn't charge at all or very slowly. I have interviews and some other small jobs that I have to do and just hard life right now and I do not have any money for this. I am a bit emotional so I asked while tearing up to Google support why they did this and I can't afford this my life is in shambles but they didn't help me. Even with the battery replacement I do not live near any local shops and mailing it in would not be possible for my situation. I bought this phone when my life was good and I only like this one and want to use this one.
All my stuff is on here and I don't know too much about phones so I just want this to work. I don't have money to fix this. I feel like the phone will die any second. What can be done? I didn't know they would do this. My life just keeps getting worse... I always feared my phone getting stolen on the streets but never thought Google would steal my phone.
What can I do? I don't have much minutes or data and can't afford it, is there a number I can call Google directly? I don't want to play with the phone and do anything weird my life is on it and can't back it up.
Thank you all.
When you got enough money, buy a phone. Not Google's one obviously. And transfer everything from the pixel to the new.
Keep the pixel for the incoming lawsuit.
Can I submit a GPL request to Google to get the kernel source?
https://github.com/bmaupin/pixel4a-battery-research
https://fosstodon.org/@marcan@treehouse.systems/113914172891...
It's possible the changes you're looking for are already listed on one of these repos: https://android.googlesource.com/device/google/sunfish-sepol... https://android.googlesource.com/device/google/sunfish-kerne... https://android.googlesource.com/device/google/sunfish/
(sunfish is the codename for the Pixel 4a)
But apparently sunfish-kernel only contains binaries.
Given there's an update to Image.lz4, that seems there's an update to the kernel. I also compared the binary to the previous version and found some new strings possibly related to battery charging profile.
Next I checked out the source using Google's documentation but the latest commit is here: https://android.googlesource.com/kernel/msm/+/refs/heads/and...
But maybe I'm looking in the wrong place.
[1] https://android.googlesource.com/platform/frameworks/base/+/...
I do have an idea about what it's checking to determine if a battery is affected, but I don't have enough data yet to know if it's just a coincidence.