zlacker

>>skille+(OP)
I feel like the elephant in the room is that there's no phone battery that's going to stay useful in anywhere close to that time frame, and replacing phone batteries is usually a losing proposition. I've tried, several times. Fake, low-quality batteries are rampant (usually degrading within weeks), and genuine ones are prohibitively expensive -- usually a significant fraction of the cost of a new phone.

>>wheels+B7
I have a nexus 6p with a battery charging to 60% and the battery is on year 4 right now, runs android 11, and seems to have no end in sight for the battery. The phone itself is 2015 I got from a relative who bought a Pixel 3.

So battery if handled properly will last a very long time. So while battery issues can't be dismissed, at least it often can be replaced or otherwise worked around. The bigger issue is storage errors and being permanently locked out.

The Google Pixel 3 phone he bought died after 2 years due to the operating system not properly handling errors in the non-volatile storage, which is a very common error in Pixel 3/3XL/4 and maybe future ones as well. Google doesn't offer the firehose so owners are out of luck not able to reformat or recover the phones at all and completely locked out by the qualcomm bootloader with phones stuck in EDL mode.

Google Pixel 3 EDL to see how prevalent the problem is, and google just doesn't care to help people fix the issue.

>>moltic+3z
I woke up one day thinking I had that problem with my Pixel 3. Literally all the things described were going on and I was about to throw in the towel and rage post to reddit, but then I had a brief showerthought that maybe the battery was bad and the charging firmware was being retarded. Pixel 3 had this habit of autobooting when charging from dead when it thinks the battery has made it far enough to survive boot... it boots into this "battery charging" mode and then it will boot up when that's gotten far enough. But when its wrong (because the battery is dying) it never has enough power to make it past some initialization stage. Ultimately I "fixed" it by draining the battery completely (until the phone would not respond to anything) and then plugging it in to charge and watching it like a hawk to jump in and long-press power to force shutdown immediately when it tried to boot to keep it in powered-off charging (not the mini-boot it does where it shows you battery charge). It happened a second time and after rescuing it again, I replaced the battery and all was good.