Google Pixel 4a's old firmware is gone, trapping users on buggy battery update(androidcentral.com) |
Google Pixel 4a's old firmware is gone, trapping users on buggy battery update(androidcentral.com) |
1. first one suddenly started bootlooping out of nowhere 2. second one's battery suddenly expanded out of nowhere and couldn't hold a charge more than 10 min 3. thrid one's battery started failing and woudln't turn on unless I plugged it into an external battery bank.
Sll 3 times while I was abroad and they are almost IMPOSSIBLE to get repaired. they use all csutom parts so none of teh repair shops were famiilar with them. google wouldn't do a thing till I came back to the united states to get the repairs done.
After 3 of these pieces of shit, I switched to an iphone. It just works. I've had zero issues with it and at least apple care won't force me to buy a ticket back to the states just to replace it.
I gave it away to someone who needed it more and upgraded to an 8a. My mission with this phone is to use it for 10 years.
https://web.archive.org/web/20231113025141if_/https://dl.goo...
I would guess just down clocking the CPU or something.
Apple does stupid and shady stuff too, it is certainly not perfect, but Google has always had a cultural attitude permeating their organization since the beginning that wanted to avoid doing any sort of real customer support, and preferenced boxing customers into something kafkaesque over doing the right thing.
For all the dumb shit Apple has done, I can walk into any Apple Store and talk to a person and get my problem resolved for a nominal fee (if any), their devices get 5+ years of security updates (usually closer to 7 years) and I upgrade before that ends anyway for other reasons (typically about every 4-5 years), in the interim my device "just works". I've effectively never had a problem with an Apple device since I've switched. I was an early adopter of Android, made my own customer ROMs and shared them on XDA Developers Forum, and otherwise was big on Android, but it became really clear to me very quickly that the app ecosystem is a mess (security and otherwise), the core OS has huge privacy and functional design issues, and Google as a steward and a first-party handset manufacturer is not the company you want to do business with.
This really sucks for everyone impacted, and I understand why many many people (including my wife) choose to stay on Android, but you should really give some thought to this. What do you /actually/ do every day with your phone, and what would better serve you? As someone who wants to spend as little time on my phone as possible, and I use it as a tool, that needs to actually work when I need it, and I travel often, iPhone is clearly a more reliable choice.
Phone was a few months old, having bought a new from HK when I went traveling.
Last decent sized pixel and it was so light.
I posted about it and they suggested that I keep a backup phone available at all times, thanks folks.
I only just found out a month ago that the Android update caused its performance to tank, then put LineageOS on it, and was shocked to find that 13-year-old tablet was not only still usable but actually kinda good.
Lol, I opt out on every new pixel phone
https://www.androidcentral.com/wearables/fitbit-charge-5-bat...
> For some devices (“Impacted Devices”), the software update reduces available battery capacity and impacts charging performance.
https://support.google.com/pixelphone/answer/15701861?hl=en&...
More details in marcan's reverse engineering of the closed-source update: https://social.treehouse.systems/@marcan/113914172433692339
Where do I find this info on my phone?
adb shell cat /sys/class/power_supply/battery/serial_number
This happened in a few stages:
Rollout of the new release (Jan 8 or so; I got it maybe Jan 16?)
Folks showed you could get the old update (I don't recall specifics) and block the OTA URLs (developer settings I think?) to prevent re-update.
Google decided to make it harder to get the old firmware.
I couldn't be arsed to wipe my phone, so am just living with the new shitty future for now.
What is going on at the Pixel team??? They have probably single handedly cost Google millions of dollars
It seems like it limits max charge voltage on one exact model of the battery to much lower limit. I bet there's a reason for it and reverting the change most likely isn't the smartest for safety.
What I don't get is why Google just doesn't come out and say it.
Anyone else have this problem? Is it well known?
anyway, iPhone 13 Mini until it dissolves into dust.
Mine has already updated, and I'm wondering if I had a chance to say no.
I have never had any battery issues. Now Google wants to effectively brick my beloved phone? And giving me $50 for the trouble. What. The. F. is going on.
I've requested the $50, shall be paid out within 18 days they say.
So sad. I really like (soon liked, probably) my 4a.
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:
[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]
qcom,max-voltage-uv = <0x43e6d0>;
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)
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.
> https://magiskmanager.com/
[0]: https://www.xda-developers.com/psa-magiskmanager-com-not-off...
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?
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
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.
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.
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:
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.
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?
Whatever else you think about Google, I think you'd agree that is a much better response than what Apple did.
She bought an iPhone.
Unfortunately, the 5G variation doesn't appear to be part of this program.
Out of luck, that’s what.
2) Request a $100 Google Store credit that you can put toward the purchase of another Pixel phone or other hardware.
3) Request a $50 cash payment.It has worked for 3+ years and held a charge for 2-3 days easily until the other week when they pushed the battery patch. Now it dies in a few hours with light usage.
I asked Google support on what will happen if I get a battery replacement and it's still draining fast. They won't answer.
Google reps at a repair center said a battery replacement is unlikely to fix the drain issue since the drain behavior is attached to an OS update you can't opt out of.
This is really frustrating to be ignored by Google after they essentially bricked a fully working device that I paid for.
This is a type of move where I'm tempted to de-Google myself over this, including deleting my YouTube channel with 20k subs that I've been regularly posting to for almost a decade.
My whole business (selling courses and contract work) depends on SEO from Google and YouTube and I'm close to saying fuck it and destroying all of that out of principle on how poorly they are treating folks over this issue. I haven't made that decision yet but it's close to be honest. Close enough that I'm openly posting this message.
For me, it should be a RED flag on the Pixel lineup and on the confidence in Google.
I filled https://www.stopobsolescence.org/.
Decent summary post here: https://www.lambdalatitudinarians.org/techblog/2025/01/09/th...
There was some news at the time that the 4a would be getting a 'battery performance update' and that it would result in some users getting a warning about their battery performing poorly and some would be eligible for $50 or a repair.
When I eventually got around to prepping the phone for the kid, lo and behold, the update was ready, I did it, and the battery was bad, and it linked me to the battery performance campaign page...
Which needed the IMEI, then said I could get $50, a $100 coupon or bring it in for repair, and there was a shop reasonably near me. I brought it in and they swapped the battery in about 2 hours with no extra drama.
I don't know why you would throw your phone out from this update... Although I wouldn't be surprised if you had already thrown it out because the battery performance was an issue before the update too.
Google denied the issues existed forever, then shipped a fix that somehow made them even worse, and made the phone unusable for years. I hope we were not the only ones.
The Moto was half the price of the 4a and is still receiving updates.
Since then this whole debacle has unfolded. GrapheneOS's installation instructions say that it updates the phone's firmware to the latest early in the installation process. GrapheneOS's releases page has a "2025012701" release for Pixel 4a. But the release notes don't have any mention of Pixel 4a since version 2023100300. I'm trying to figure out if GrapheneOS has actually updated their Pixel 4a image since then, and whether it would install the battery breaking firmware.
The problem is, the Pixel 4a is not designed to have the battery be swapped and it's common to break screens and other parts of the phone in the process. You can look up what's involved and it's no surprise that this is the case.
It's basically a nice little case of hardware and software anti-consumer policies working together to break people's devices and force them to consume more.
Without legislation nothing will change.
The small credit does not cover the cost of inconvenience.
* Send from my now charging 4a
I still have not restarted my phone since the update. But my wife has and her phone does not hold charge for a day, compared to 48h before the update. Battery percentage gone completely unreliable. She's only doing slow charges since then in an attempt to have battery management chip somehow recover. Hard to see what they tried to "fix"
Yesterday I got my new 8a, installed grapheneos and it works very well! So far no massive issues. When I tried this on the 4a some years ago, netflix complained about general certificate stuff and casting was broken, microG et al was barely holding on. Now, no problems at all!
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...
Videos, on the other hand...
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.
Then they announced a $29 battery replacement program for phones that were affected by this battery issue. https://www.pcmag.com/news/report-apple-is-refusing-to-repla...
I also remember some rumor that all Pixels must access WiFi before they will allow bootloader unlocking in the developer options.
Cisco Duo also runs on this device.
This will be a decision for the app vendor, but I'd rather get monthly updates than maintain a locked bootloader.
Uber has done some strange things.
"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."
These lithium batteries usually last longer when you don't fully discharge them and fully charge them regularly. 20-80%. No idea why manufacturers don't just call that range as 0-100%.
> Google today announced a “voluntary exit program” for employees working in the Platforms & Devices group.
As if to make my point.
Some folks have hooked up devices between the phone and charge cable that do the coulomb counting (or similar), and (the one case I saw) showed that the phone is only taking in about 40% of the watt-hours that it was doing before the OTA update.
From what I've seen, no one can point to any actual incidents with these phones being dangerously hot. But the google FAQ did have a "Yes you can still take the pixel 4a on flights", reminiscent of the samsung phone issue several years ago...
It seems to be unbelievable that none of this has become part of AOSP.
I should have a battery setting that optimizes either for battery longevity, or for maximum power delivery. These settings should incorporate best practice, such as you have outlined.
The last stable ACC release was in late 2023, and it appears to remain the best battery management tool for longevity.
Why is this so?
I rewrote your script slightly, and ran it on my Pixel 3.
find /sys/devices/platform |
grep battery/uevent$ |
head -1 |
xargs grep NOW
POWER_SUPPLY_VOLTAGE_NOW=3955800
POWER_SUPPLY_CURRENT_NOW=-222656
find /sys/devices/platform -name uevent |
grep battery |
head -1 |
xargs grep NOW
find /sys/devices/platform \
-path '*/battery/*' \
-name uevent |
head -1 |
xargs grep NOWNewer Pixels have a concept of "bed time" and charge slower overnight, for battery health.
1. https://social.treehouse.systems/@marcan/113914172433692339
Random Google engineer on personal machine trashes Pixel 4a batteries in GPL violation
How did this random engineer command that all previous firmware images be taken offline?
Alternate ROMs look much safer right now.
Should this be submitted to HN separately?
The whole of userspace will be replaced when LineageOS reformats all of the partitions.
It is possible that the new battery behavior has been injected into some deeper part of the hardware, but LineageOS is unlikely to make that worse.
I've loaded Lineage on the Nexus 6, Oneplus 3a & 5 & Nord N200, the original Pixel, and the Pixel 3a XL.
Pixels are the most forgiving, and the hardest to brick. They are also the best for VoLTE.
I also have an N100, which is not supported by Lineage.
They do this so that they don't have to reverse engineer and write the hardware drivers from scratch and simply use Android's user space drivers for them.
I haven't been involved in that domain for a while, but it basically meant reusing the contents of your device's /system and /vendor partitions and simply installing the Linux OS into /data.
>Users can delete an already downloaded (and not yet installed) update: Settings -> Apps -> All Apps -> Google Play Services -> Storage and cache -> Manage Space and from there on delete all data through the "Clear all data" button.
No, I don't think you can say that. If you're getting daily notifications about being out of date, then you clearly haven't gotten the update yet. There are two possibilities: (1) You have rebooted. In this case, the dev option must have worked, because you rebooted and didn't get the update, exactly what the dev option promised. (2) You haven't rebooted. In this case, the dev option doesn't apply, because it specifically refers to what happens after you reboot.
I wonder how you mean it. Is it that older products with good fundamentals are being replaced with younger quick-to-market technologies without those fundamentals, and different (possibly) wrong things get optimized?
Or is it experienced engineers with "well known" fundamentals are not involved in new products?
...
"Gramaci's Prison Notebooks that 'the crisis consists precisely in the fact that the old is dying and the new cannot be born; in this interregnum a great variety of morbid symptoms appear'"
"An interregnum is a period of discontinuity or "gap" in a government, organization, or social order."
With a Pixel, there is less bloat, so it is less of a factor with this particular device. However, you don't get the full suite of Chrome/Maps/Gmail/Drive/Photos/etc. installed by default, and what you have not installed will not drain your battery.
In any case, one would hope that Google's safeguards are equaled by ACC.
Data is cheap where I live, but also I dont use my phone to stream music/video.
Android's source code is a maze of branches and tags, unfortunately. The change can have been made in the generic cross-device kernel tree, or it could've been a separate module, or it could've been a binary.
One thing you could consider is checking out the kernel for a project like LineageOS: https://github.com/LineageOS/android_device_xiaomi_sm6150-co... They usually pull+filter changes from upstream. For instance, these changes may be of interest: https://review.lineageos.org/c/LineageOS/android_device_xiao... https://review.lineageos.org/c/LineageOS/android_device_xiao... These kernels are used for a variety of devices with similar hardware, so not all changes have anything to do with the Pixel 4a, but it could prove useful in your search.
Would changes to external closed-source binary files change the kernel image itself? There are kernel modules in that commit but it looks to me like they all come directly from here: https://developers.google.com/android/drivers
Google does provide detailed instructions for downloading all sources for the kernel, and I didn't see any changes since 2023 to any source files: https://source.android.com/docs/setup/
Thanks for the extra places to look. I'll check them out.
With the sunset of 3g, many devices that were not capable of 4g were retired.
That being said, Lineage still does support several Pixels that Graphene has desupported. In fact, I am typing this on a Pixel 3a XL which is in this category.
The original Pixel, Pixel 2 and 2XL are still supported by LineageOS:
https://wiki.lineageos.org/devices/#google
Graphene has explicitly removed everything prior to the Pixel 4, including:
Pixel 3a XL (bonito), Pixel 3a (sargo), Pixel 3 XL (crosshatch), Pixel 3 (blueline), Pixel 2 XL (taimen), Pixel 2 (walleye), Pixel XL (marlin), Pixel (sailfish).
Edit: This extended support does come at some risk. The chipsets used in Android can sometimes have showstopper bugs. Sometimes, these cannot be patched, although maintainers will go to great lengths to find solutions. The "firmware age" is reflected in the "vendor security patch" date in Lineage - the older, the more dangerous.
Graphene largely does not allow this.
The reason I don't choose a hotel 500 miles away is fairly obvious.
This also applies to parking lots for the same reason...
I think it's just cargo culting products. Apple made electronics sexy fashion accessories through their marketing, advertising and branding.
The problem is the misattribution of their success to the poor choices they have the customer loyalty to get away with.
Nobody has said "well thank God my new MacBook has no ports" or "I'm glad my battery isn't removable". The support column for these decisions is empty.
No, but they do say "thank god my device survived being splashed by water" or "I'm happy this teeny tiny thin device doesn't leave an unsightly lump in my pocket"
The de-featuring isn't capricious -- it's a result of optimizing for different tradeoffs. While it would be best for the customers if multiple vendors managed to tile the pareto frontier of feature combinations, allowing us all to pick a product that serves us best, for the vendors bunching up around a single point is a more stable equilibrium.
I use a panasonic wired headphone with a mic, $10. Airpods are $200. They wanted to increase their costs and frequency of purchase by hiding it behind accessories with higher profits and shorter longevity than the primary device.
Buying my last phone was a real challenge - even 6.5 inches long feels huge, and there were very few options under 7 inches.
I'm not hoping to argue, only to learn. This isn't my area of expertise.
> now I’m trying to think of what I can do to secure their devices if they’re not going to update
Did they? Immutable system images are a pretty solid feature to have. It's a lot less "fall over broken as shit randomly" than desktop Linux is...
1) Reduce the CPU speed so the phone did not crash 2) Not reduce the CPU speed and let the phone crash when the battery could not produce enough power.
I think Apple made the right choice.
I almost got completely screwed by my pixel updating right before a concert while I was already out of town. Luckily my wife was able to login to my computer and forward the tickets to someone else that I was with, but it was a close call because she was walking out the door to do something herself when I managed to get ahold of her.
In this case, if you don’t have a phone that can display Ticketmaster’s code, you’re just SOL, since they decided to break being able to just print out your code.
And you don’t see the difference?
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.
"Google Android on a Pixel 4a is vulnerable to remote code execution by arbitrary nearby wireless devices" is certainly a better reason to not use one than "security updates have ended".
Who knows, someone would need to write an actual exploit for these. Just quickly skim through the Android security bulletins at
https://source.android.com/docs/security/bulletin
and you'll see that every month lots and lots of CVEs are fixed with at least high or even critical severity in various stacks. If you're running a phone that hasn't received updates since August 2023, you can assume that you have dozens of remotely exploitable bugs on your system. The security track record of Android is absolutely terrible.
That phone hacking is not a big thing is simply because it's usually much easier for a hacker to get into the cloud services people use instead through targeted phishing attacks. If that makes you feel safe using a phone without updates, then good for you, but don't claim these updates aren't actually fixing serious bugs every month.
*Written from my 4a.
So if you release the feature branch every 3 months after a few years you will have a dozen maintaining branches to backport fixes to, and in which to carefully test that the fix actually works. The problem is linearly worse if you release the feature branch more often.
This has been solved by LTS releases for some time. You have a newest release branch that gets feature updates immediately and an LTS branch which has a full release e.g. once every two or three years, at which point it catches up on features to the then-current newest release branch. The newest release branch doesn't have long-term support and you're expected to take the latest feature update, the LTS branch gets only security updates, the user can choose between the two or three LTS releases currently in the support window or the newest release branch.
Select: Base version that will only receive security updates. No changes in features. OR All updates
Edit: By "Base version" I mean the first software version for that device.
Why? Because we have a counterfactual observation: in France there's a law against "planned obsolescence" and to comply Apple never pushed their update here. And not only French IPhone kept working, but everybody could disable the speed nerf by switching their location to France on their phone. And it turns out that the phones handled it without issue.
And if that were the case, how do you explain this as far as France?
https://www.theverge.com/2020/2/7/21127984/apple-iphone-batt...
TBH I think what Google did here is also bad, this should definitely trigger a system popup with an opt in/out.
However, Apple did exactly the same thing, initially denied it, and people are still defending them years later.
(edit):typo
So the pop up should be “Wouid you like your phone to shut off randomly?”
Just don't buy anything from Google, they've always screwed something up.
I liked Lineage, but an unlocked bootloader is a security non-starter for a device that's so personal and vital.
For those using the stock OS, Googles are nice because you "only" have Google's spyware built in to the OS.
But they're pretty clearly worse as phones and I'll go to my grave mad about the headphone jack.
pure evil
Sounds like you should move your AP? There's no way that communicating with an AP tens of feet away is going to require less power than communicating with a tower hundreds of feet away.
>I also find that on wifi data, apps constantly update and sync themselves - they don't do this on metered network data.
You can set wifi connections to "metered" on both android and ios. It doesn't allow you to cut off data entirely (like you can on cellular data), but should have similar effects to being on cellular.
They haven't said why they did this, like if it was a battery defect issue or what.
I ended up getting a 'regular' sized samsung only slightly larger than the one it's replacing, but at least modern phones seem to be getting longer software support periods (assuming there's no nasty surprises included).
I think they no longer do that since a while (a few years) ago, but don't ask me which phone model exactly was the last one affected.
Just updated to Pixel 8 and it fits the hand very well (including Spigen Liquid Air cover), and doesn't feel too heavy. Have a few friends who got Pixel 8 last month on sale as well and they all confirm.
Maybe from Google phones, for now? Possibly on smaller phones. But Best Buy sells 7 models with 5g and a headphone jack. There's almost certainly more if you shop a retailer with more variety, using Best Buy because they have decent filtering.
https://www.bestbuy.com/site/searchpage.jsp?_dyncharset=UTF-...
Unfortunately, unlockable bootloader isn't one of the parameters available, and I consider it essential.
The problem is the security industry has such a low signal:noise ratio that it makes sense to just ignore everything they say as a user. They're constantly lying and saying there are important security updates when there aren't, and that everything is high/critical severity when it isn't. In a corporate setting, you just unthinkingly update to check boxes, but as an individual, it makes no sense to do that. And with Android, you have to take possibly undesirable feature updates to get kernel or system library updates. For some products, security updates are to "secure" the device against its owner! Advisories are often lacking enough information to be able to evaluate impact, which further makes it clear that the people publishing them are to be viewed with a skeptical eye.
It should be immediately obvious whether this is exploitable by random passersby (if it actually is) without me having to go learn how bluetooth works at a protocol level. "Don't think about it and just update, install a new OS, or buy new devices" is not a useful attitude.
Things don't become end of life when they stop receiving updates. They become finished. Whether and for what purposes they continue to be useful requires ongoing judgement.
[0] https://learn.adafruit.com/introduction-to-bluetooth-low-ene...
But you missed the point that Android's system image is immutable and updates are atomic. A user can't screw it up. This is not an insignificant feature, and it's something you also get with something like Fedora Silverblue. Which then also doesn't let you pick and choose what updates to get.
Of course, they also fired a lot of their testers, and seem to have thought that testing was something end users do in prod, so...
Never mind the problem of if you started out on a non-LTS version.
And also the problem of not getting the actually nice updates, and perhaps losing app compatibility.
So, no, not solved at all.
(My Pixel 6 is rock solid on that by the way.)
This is the core problem - it is a roll of the dice whether your hardware will work five years from today.
I’m less concerned about the software but that is also a problem.
Meanwhile, my iPhone SE from 2016 still works as advertised.
Googles primary source of income is ads. All this stuff they do is the primary way they get money. People need to stop being surprised this is where they ended up.
My iPad is pretty naggy to install updates, moreso than my Pixel phone even. iOS doesn't automatically update like Android does, but if anything that seems less like it's because Apple disagrees with that and more because their update system is so shit they can't get away with it. It's inexcusably slow to apply updates.
> try to upsell me every time updates are installed
They are the only ones to have lost a lawsuit for doing literally this. Batterygate wasn't that long ago, surely you didn't forget about it already? Heck class actions about it are still happening in various countries!
I do my part to support Chinese factory workers by purchasing the latest iPhone™
https://securepubads.g.doubleclick.net/ https://news.google.com/swg/js/v1/swg.js - I found these on the Washington Post's web site.
https://fonts.gstatic.com/s/opensans/v20/cJZKeOuBrn4kERxqtaU... https://www.googletagmanager.com/static/service_worker/51n0/... - I found these on New Egg's home page.
https://cm.g.doubleclick.net/pixel?google_nid=a9&google_cm&e... - I found this going to Amazon's home page.
https://www.gstatic.com/recaptcha/releases/I0bG74fWAenNf3Z5n... https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LetQiEU... https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxK.... - I found all of these on democrats.org.
https://ad.doubleclick.net/activity;register_conversion=1;sr...? https://9323526.fls.doubleclick.net/activityi;src=9323526;ty...? https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LdJ810b... - I found these on www.gop.com.
Basically, Google tracks peopple everywhere. They track what news you read, where you shop, and what political party you support. Apple does none of this. No one tracks people on the Internet like Google. Facebook doesn't. Amazon doesn't. X doesn't. Microsoft doesn't (the own Bing). Apple certainly doesn't.
Also, I don't understand why you're linking to an article that contradicts you. It reminded me something I had forgotten though: that eventually Apple (partially). caved and made this behavior opt-out for everyone.
It wasn’t a theoretical concern. Phones were shutting down. Again this is physics.
Apple fanboys are really the best when it comes to defend the indefensible.
this dead simple warning message + a switch to toggle CPU throttling is all anyone ever wanted.
However that would require them to respect their users' intelligence - not Apple's style.
Both tracks you by forcing you to use their app that works as spyware.
I've done plenty of things without them. All Amazon devices do everything they do without them. Same with all Android devices sold in China.
Also, you missed the point of my comment. The comment I replied to basically was saying Apple and Google are equivalent because Apple sells ads (they sell search listings in the App store search and may run an optional advertising service for apps). My point was they are not equivalent because Apple does not track people around the web like Google does. The other things is Apple has released a lot of privacy features which interfere with the advertising spying machine.
At best, Google pretends to improve privacy. Google's business is basically building a profile on each individual so they can serve the most relevant ads to that person. They make more money when they serve relevant ads (ads people will see, and maybe buy something based on the ad). Google has no interest or incentive to protect privacy because their business depends on invading privacy.
That's a pittance of privacy. Apple sells your search results out to Google, cooperates with NSA surveillance and institutes online DRM for your apps. They do not care about protecting you from tracking because tracking users is official policy for Apple in both iOS and MacOS.
It is pathetic to watch people on this site rush out to defend Apple like they aren't part of the problem. If you have witnessed Tim Cook's behavior over the past 10 years and still hold hope for Apple, you are not paying close enough attention.
> At best, Google pretends to improve privacy.
Google still published AOSP source code. That's not "pretending" to improve anything, it's an outright statement about the transparent security of their product. I hate AdSense and consider it an anticompetitive scourge on the internet, but I don't see Apple making commitments to security on the level of Google. Last I checked they were still trying to sue security researchers...
If you think Google is "pretending" to improve privacy, how can you deny that Apple pretends too? The reason people drill down on this isn't to defend Google, it's to prove beyond a shadow of a doubt that you do not actually know what Apple's stance is on this and cannot confirm it with hard evidence. You are repeating marketing and whitepapers, hoping that it's correct.
No one has ever accused the EU of being tech literate.
And that feature is still part of iOS…
It did, shortly, then Apple got fined and then the feature was removed, yes, there's no contradiction whatsoever with anything I said.
> No one has ever accused the EU of being tech literate.
First it has no link with the EU, and then you said it wasn't about tech but “physics”. And surely Apple would hire lawyers familiar enough with physics to be able to explain it…
> And that feature is still part of iOS…
But now at least it's opt-out because Apple was forced to do something against the backlash. Nobody would have called that shady if they communicated clearly about the throttling and made it opt-out from the get go (or even better: wait before such a issue gets triggered once before throttling the phone, and explicitly tell the user when it happens…). And surely that's what company that cares about user experience as much as Apple would do … if they weren't trying to screw their customers.
So now are you back to saying that rechargeable battery degradation is not a thing? It is literally physics
https://gizmodo.com/scientists-solved-the-mystery-of-why-rec...
What I'm saying is that Apple's army of lawyer failed to justify how this behavior was indeed justified by laws of physics, and obviously you cannot do better than them. Your argument is just one of a fanboy coping against facts.
