Hacker News new | ask | show | jobs
by paulmd 1216 days ago
It's really not uncommon to see ROMs with known bugs like "camera doesn't work" "3.5mm port doesn't work". When I was looking for a phone in 2018 I was looking at the Pixel series and that was the bug list for most of the ROMs at the time - and pixel was basically the best-case scenario that everyone was pointing me at as far as support.

It was still in official support at that time but I got burned by my first android phone going EOL within 6 months of when I bought it and I wasn't going to leap again without knowing there were actually ROMs that worked without major feature loss.

It probably would have worked out, being a pixel and all, but I specifically ran into bumps on my previous phone (Moto G Falcon) with features being lost on custom ROMs. Eventually I found one that worked OK but that's just not acceptable to lose official support 6 months after purchase and deal with custom ROMs where random shit is broken.

1 comments

That's right, and that's why you should choose your phone based on the ROM you want. Of course if you choose a phone that is not supported, it probably won't work well.

Try running the Samsung S23 ROM on a Nokia 7 plus and tell me how it goes: that's the same problem.

I have been using /e/ OS on a Fairphone for 2 years, and it is absolutely great. I just use it like a normal Android, no need to fiddle with it _at all_. Some apps don't work because I'm de-Googled (no Play Services), but you don't need that (or you can accept that some apps don't work).