The stuff Hacker News actually recommends.

Phones · Google Pixel

Google Pixel 4a

96owners with an opinion
58%of verdicts positive
47/33positive/negative since 2024
5 yrslongest happy owner
4happy after 3+ years

Praised for reliability and battery; criticized for support.

What owners wrote

Likes itOwned 5 years
> if you enable battery changes, a current gen device can easily last a decade), people will care. Modern batteries last surprisingly long. I assumed my 5yo pixel 4a was at 50~60% capacity based on feels and the adb batterystats printout estimated the same (with 1600 charge cycles). But when I actually measured the screentime / wattage consumed while charging, it was still at 80% capacity. Even confirmed this by replacing the battery and running the same tests. I think part of the reason the old battery felt worse is that it would read 100% when it was only ~85% full then trickle charge at like 2w for another 90 minutes.
Likes itOwned 5 yearsStill going
I use ACCA[0] to select my charge rate and limit. This can also set battery idle mode (power from USB without using the battery) when the charge limit is reached if the hardware supports it. I usually limit it to 60%, and charge at 500mA when I'm not in a hurry. Maybe that's too much fuss for most people, but I'm still using a five year old Pixel 4A on the original battery and its showing no signs of reduced battery performance. I probably wouldn't put in the effort if it was easy to replace the battery, but it is not. I might be a little less aggressive about it if I liked any current phones, but I do not. [0] https://f-droid.org/packages/mattecarra.accapp/
Doesn’t like itOwned 3 years
At this point I believe google is personally trying to rub it in my face that they can do what they want. I have been a user of android for 15+ years and have had a pixel 4a for the past three years and was happy with it. In january they had a cryptic announcement that some 4a's needed a software update to deal with an unspecified battery issue. The three options provided weren't described well and once you choose you can't change your mind. The software really nerfed the battery on the phone and it often refuses to charge or lies about the level of charge, and it needs to be charged five times a day. I opted to go with the $100 discount and I was going to get an 8a (list $499). At the time the google store had it on sale for $100. They took three weeks to issue the discount code, just after the sale ended, so it was kind of a charade. Fine. I go to redeem it ... and they won't just accept my credit card which they have on file and routinely charge things against it. It turns out, to use the code you have to send a picture of your credit card and front and back of your driver's license! Last night I bought an 8a without the discount code because I don't want to send that info. And today they announce the 9a at the same price. F me. This has pushed me to degoogle my life more. I'm going to install grapheneOS and I'm seriously considering dropping google fiber and go back to spectrum (which is its own horror show, but doesn't have the power of google).
Doesn’t like itOwned 3 years
I have a Google Pixel 4a and planned to use the phone until it physically no longer worked. I loved it, especially with its wired headphone jack and small size. 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.
Likes itOwned 3 years
It’s great that Google is extending the support, and that GrapheneOS can benefit from it. I bought a Pixel 4a specifically for installing GrapheneOS. I used it happily for almost 3 years, until EOL firmware support. The phone worked fine, but I wanted the reassurance of firmware security updates. I was going to get a Pixel 6/7 (I forget which was available at the time) to use GrapheneOS again, but I was so annoyed at Google for only supporting firmware for 3 years, that I decided to switch to an iPhone SE. Shortly after this, I believe the next Pixel came out with 5+ years support. I had some regret, but the iPhone SE is OK, and I didn’t want to buy a new phone just for the sake of it. I will probably switch back to GrapheneOS for my next phone, as it really is a great mobile OS. Hopefully the project is still going strong by then.
Doesn’t like itOwned 3 years
It's not even just downstream vendors. Google itself only supports its devices for three years. I bought a Pixel 4a on release in 2020 and next month will be my last security update. https://support.google.com/nexus/answer/4457705 Can you imagine if Apple or Microsoft stopped making OS updates for CPUs more than three years old?
Likes itOwned 2 yearsStill going
If you're not a phone power user, you can get by on old low end stuff. When my pixel 4a died of a bad screen crack a couple years ago, I replaced it with a random used 4a on ebay for $80. Two years later and it's still completely fine for all my purposes (texting, phone calls, chrome browsing, tolerable camera, etc.), although I still haven't accepted google's deal for a free battery swap yet from sheer laziness. I've learned that I can accept a 90 minute screen-on phone battery, though it's an odd adjustment to make. Again, not a power user.
Likes itOwned 2 years
I had a two phone lifestyle as well for different reasons: I needed car play but don't like iOS, and also needed to know Android and iOS quite well for my job. One iPhone that was wifi only, had my entire music library local, used for car play and a few exclusive apps. One android with a sim that had my communication apps, social media, and some custom tinkering stuff that doesn't exist on iOS. I did this for about two years. The main takeaways: -I 100% could have just had the iPhone with a sim for communication apps and been fine. The social media was just annoying enough to swap to that I never felt that draw and barely used it on 2phones. -even though I despise how little customization iOS lets you do, without social media or game apps, the only actual pain point with it was the nightmare of managing notifications/alert/vibration/screen wake settings* -god it made me miss small phones so much. The android was a pixel 4a, the last real phone with real hardware that released at the actual ideal size for my hands(that has an unlocked bootloader, I really can't do the Samsung hellOS experience again). Now Im on a pixel 8 only, with Glider for this site and no other social media or games. It's fine. Phones too big, car doesn't have AAuto, and Google is trying to rot the foundation of android, but for now it's fine and better than the two phone experience because it's less juggling.
Likes it
I've considered this before, but the short software support timeframe given by device manufacturers makes this a costly endeavour. I still have a perfectly functional Galaxy Tab S2 9.7, but even the third party ROMs have dropped it. I have a pixel 4a, and although it works beautifully running a supported version of lineage it's very likely that the modem baseband has a significant vulnerability that Google isn't patching. I don't think running banking or crypto wallet software on those devices is any smarter than running it on my daily driver pixel 8.
Likes it
I was secretly hoping they'd stop supporting the Pixel 4a so I would have a reason to get a new phone, but no, still there in the list of supported devices. So I guess I'll just keep using that thing another year... Anyway: big thanks to the Lineage maintainers, keeping so many phones from landfill!
Neutral
I did a lot of research in this field and additionally in audiobooks. While I still think that the iPod Nano 7 is the perfect device for me, I recently got my hands on a HiBy R1. For 60 bucks it is a remarkable non Android device (in fact it is buildroot based with a publicly available toolchain and a modding community). I have to prepare for my iPod nano collection slowly dying over the next years. I also use an old Android GrapheneOS phone (Pixel 4a) along with some apps as a backup: Substreamer APP (cross platform) DSub Navidrome (Backend) Audiobookshelf (Backend) Prologue (iOS) Voice (Android, Paul Woitaschek) Navidrome backend even supports smart playlists while Substreamer App supports Offline Sync, this is very handy to use. My workflow is: 1. Obtaining Audio CDs (cheap, high quality) 2. Ripping flac with EAC [1] 3. Tagging with beets music organizer 4. Convert inplace to mp3 v1 with beets 4b. Archive the flac (on disk and bluray) 5. Add to navidrome 6. Star / rate in navidrome 7. use a smart playlist to sync top titles and New Albums offline 8. use a shell script to download to USB for my old car without Bluetooth Works pretty well and after the ripping step pretty much full auto. The only reason i still prefer iPod Nano 7 over Android is the limited remote of my cable headphones (longpress is not detected on Android) and the near flawless UX. 1: https://pilabor.com/blog/2022/10/audio-cd-ripping-hardware/
Likes it
> Approximately nobody is throwing away phones because the OEM stopped providing security patches. They're doing it for more practical reasons, like the phone getting slow, the battery wearing out, or wanting a better camera. I did this just last year because my Pixel 4a stopped getting security updates and some app I needed to use for work (I think Duo?) refused to install or run because of it. The phone was otherwise running perfectly fine and I had no reason to change it. I'm on a Pixel 8 now which is supposed to have 7 years of security updates, and I don't see myself replacing it until then.
Doesn’t like it
My experience with Google hardware is that they shipped an update for Pixel 4a that crippled the battery. In Australia, they announced a safety recall due to a discovered battery safety issue, but in the rest of the world, it seems they wanted to save money by crippling people's phones of their own volition without much explanation. But no worries, they're offering 3 methods of compensation: free battery replacement to restore it, $50 cash, or $100 credit for another Google phone. I went to redeem my compensation - free battery replacement unavailable in your country, $100 credit unavailable in your country. I guess I'll take the $50 cash...? I fill in the form with my IMEI, full name, address, etc etc. After a week they send a response saying unfortunately after thoroughly looking into my case, I'm not eligible, and no further explanation is offered as to why. In effect it's as if they hacked into my phone and installed a virus that cripples the battery and there's nothing I can do about it, like this is just a normal way to do business now. You don't really own your phone after all...
Doesn’t like it
>I've had to turn off a lot of features. On my pixel 4a, I had to turn off a "call 911" feature that I think was initiated by shaking the phone. I took a couple of walks with the phone in my front pocket, and the movement from my leg called 911 (which I would only find out when the police would call me back to ask if everything is OK).
Likes it
I recently upgraded my 4a to a 10 two months ago. Besides getting security updates again, it feels like a downgrade in every way that matters to me. Can't lie flat due to camera bulge. No headphone jack. Fingerprint sensor on the front that screen protectors interfere with. No sim slot. Ai bullshit triggers if i keep my thumb to close to where you touch to switch apps. Ai bullshit also replaces the old power menu, which now requires a combo button press. Such a let down.
Likes it
Same. The Pixel 4a was the perfect phone for me: Light, screen exactly the right size to navigate with a single thumb whilst holding the phone in one hand, enough battery life, small enough to fit in my jean pockets comfortably. But people buy big phones in preference to small ones, so that’s what Google & Apple manufacture. Nobody (from the POV of Apple/Google decision makers) buys these smaller phones.
Doesn’t like it
> I dont think Google is gimping your device to sell you new ones. I'm not sure. Last year they ruined my Pixel 4a by pushing that battery patch to everyone (even to end of life devices). Their official repair center replaced the battery as per Google's guidelines and offer but during the battery swap they managed to physically break other parts of the phone over the course of multiple visits. Each visit broke a new component. Google support didn't do anything in the end, eventually ignoring me. This went on for almost 6 months with an email chain over 100+ replies. Eventually the repair center gave me enough credit towards a new phone (this 9a) but only after I mentioned I was going to small claim's court since they left me with a device that didn't function in the way it used to function before I visited them.
Likes it
I've been using it for more than 2 years, and I can't think of ever going back to a stock OS. I had to send my phone for a screen repair, in the meantime I picked up my old Samsung, and the sheer amount of apps I didn't want, notifications and dark patterns to tricking me into handing over my data made me anxious. I couldn't finish setting the phone up and drove to my parent's home to pick up their old, remotely nerfed by Google, Pixel 4a so I could install GrapheneOS into it and use it while I waited for my repaired Pixel 8.
Doesn’t like it
As someone who never comments on HN, I would like to voice my absolute disapproval of this new policy. As these decisions are not made in a vacuum, I have no doubt the recent developments in the political landscape have contributed to this decision (e.g. UK Online "Safety" Act, EU Chat Control, EU Age Verification solution, probably others). Coupled with the recent "mandatory" (read: forced) upgrade of my Pixel 4a, I get the impression Google's attitude towards phones has become equivalent to Apple's: namely, the illusion of choice. Since there are no viable alternatives, I guess it's time to go back to owning a cheap corporate/government approved phone for official business (i.e. banking), and another one that I actually use. As an aside, the presentation[0] doesn't really go into the details how they will enforce this (on-device? Remotely? If the latter, can I just remove Play Services from my device to sideload whatever?), but you can apparently submit feedback about the verification process here[1]. [0]: https://goo.gle/play-console-android-developer-verification [1]: https://docs.google.com/forms/d/e/1FAIpQLSdpZbsJCS-f7CtMbZPn...