Google Pixel 5a

Same here; had a Pixel 5a with Google Fi. The 1 year old Pixel randomly died one day, totally bricked. Google phone support requires them calling you (after you request it online), and the browser-based “Fi phone” was unable to receive calls from Google phone support. No other callers had this issue. When I finally got in touch with them via my wife’s phone, they wanted me to drive 1.5 hours outside of SF for a phone diagnostic. I said no thanks and switched to iPhone with AT&T.

I had this happen twice with pixel 5a's as well. Older, but just to say I'm not sure this is limited to the 8 line. One of them literally just died in my hand and was unfixable.

I got badly burned by the Pixel 5a, but especially with Google's support. My wife and I both had 5a, and both died spectacularly right around the end of warranty period. Mine ultimately got replaced under warranty and that replacement died the same way when I was on vacation less than a year later... which they refused to repair under warranty. They put up such a shit show and had us run through so many hoops with my wife's phone that it ended up being out of warranty by the time they agreed it was broken and needed repaired. The support experience was so painful I reluctantly let them get away with their bullshit, bought a new phone (oneplus) for my wife, and swore not to buy another Pixel phone despite having a strong preference for them and the pure Android experience.

I built it circa 2012 or 2013 and still have the physical win8 disc. I considered futzing with linux on it. The extent of my linux experience is via SSH to a raspberry pi kludging some docker containers for this and that. SSH/linux terminal feels like fumbling in a dark room flipping random switches until something works. >scrcpy I also have a pixel 5a whose screen doesn't work, but I think functions otherwise. Would this allow me to interface with it?

My Google pixel 5a randomly requires the pin/password every couple of days and will not accept biometrics. I have always assumed this was to heavily discourage using long passwords for this very reason.

The sad part is even security updates stopped for my pixel 5a.

I've yet to notice a substantive difference between my current Moto g 5g, which cost ~150 USD and my previous phone, a Pixel 5a which cost ~450 USD. I balked at the price of the pixel at the time, but figured that's just the price of admission these days. It is now useless since the screen/mobo failed soon after I switched. After it was obsoleted, I just opted for the cheap Moto and will probably never spend more than 200 USD on a phone again.

Was there a point to this story? I have a pixel 5a with a dead screen that runs but can't be used because the dead part is part of the motherboard not the screen. It's a known problem with this model. So it still runs, but I can't recover any pics or texts from dead people from it because I can't respond to the screen prompts to allow the USB connection. I don't see how I'm any better off.

I'm still salty about my Pixel 8 dying out because of the "green screen" bug (basically, screen just progressively turns greener until it stops working). Very common according to reddit, and the ubreakitifixit guy acknowledged it's a common problem as well. My Pixel 5a also had some shenanigans and my dad's pixel 6 as well No idea why they don't do proper Q&A. Looks like a good phone but yet fails in ways my work iphone never has.

> This is a limitation/downside/flaw of "VA" LCD panels. OLED panels will not experience this... I don't know what to tell you, man. I'm seeing this behavior on a Pixel 5a. Purchased _directly_ from Google's store. Google says this model of phone has a OLED display... an HDR one, at that. [0] Not even the worst color transitions for my my VA monitor (a BenQ EWE3270U) streak this badly. [0] https://blog.google/products/pixel/pixel5a-with-5g-new-googl... >

> ...if you're getting smearing of any kind it wasn't an OLED I have a Pixel 5a. It has _comically_ slow switching times between dark-ish colors and blacks that's most obvious with dark blue-family colors. If you have such a phone, go check out the "Gunnerkrigg Court" webcomic ( https://gunnerkrigg.com >), scroll down to the border between the comic and the blog part, and jostle the viewport up and down. If you go check out today's episode (comic 2929), you get an especially long trail of slow-transitioning pixels in the art that is particularly noticeable in the bottom panels of the comic, itself. (Examine the black borders of the people's hair, as well as the black frame of the comic panels. If you're not noticing it, scroll at a rate of travel of roughly one-quarter of the screen's height per second.)

Manufacturers quote those response times, but worst-case response times are often at least a full frame, and sometimes multiple frames. Unlike with CRTs, response time is a factor of what color you're switching to and from, and their intensity, it's highly-variable, and it makes me so sad whenever an otherwise-lovely game happens to put colors together that very obviously smear on my monitors. (Also, see above for my report on the laughably bad color smearing on my Pixel 5a.) RTNGS usually has more-detailed breakdowns of best and worst-case color transition times for the monitors they test, as well as over- and under-shoot reports... which is a phenomenon that's just as bad as slow transitions between colors.

FYI, my pixel 5a phone has also been really slow and acting out in the last month. Crashes and extreme sluggishness in apps. Sometimes when I pull up the app-switcher, I can't get out of it without rebooting the phone. I however am not on the Jan 2024 Google Play update detailed by this article. I am still on the recommended Nov 2023 one.

https://react.dev/learn is so slow on my phone, it takes 1.5s to open the burger menu, and about 1s to jump to a section. (Google pixel 5a). It must be some SPA that loads the whole documentation all at once I presume. A traditional MPA would probably work much better here. edit: and like the sibling comment noted, the history back button gets messed up. edit2: I mistakingly wrote nexus 5a instead of pixel 5a

Absolutely, but it being a pixel5a makes it much worse! But as you said, even a nexus 5 should be able to run a doc website.