I run /e/OS on FP3 and I’m quite satisfied. Support and overall status is not perfect, but reasonably good (and to be completely fair, my experience with stock phones from big brands like Samsung, LG, etc isn’t perfect either).
On the FP3 support side: after using the phone during a few weeks I only found 1 issue, which is not a major one anyway (easy to work around). Everything else works perfectly.
On the general /e/OS side:
- My biggest problem is with location services not working as reliably as with gapps one (I opened a topic to ask advice about UnifiedNlp backends, with no feedback so far; I also suggested use of Mozilla Stumbler to help mitigate the problem)
- You might also run into some apps that don’t work, either because they are rigged to only work on gapps phones (SafetyNet) or usually other compatibility reasons related to microG. You can search your apps in this list and see if they’re affected.
- Depending on how Google-dependant was your typical usage before, it might take some effort getting used to. /e/ provides a few Cloudy services like email and whatnot. For me, this isn’t a big deal as I already was mostly detached from Google before and didn’t even have a Google account in my phone (I used things like Davx5 to sync calendar and contacts, Syncthing to sync files, K9 with self-hosted provider, etc).
- I was positively surprised that replacing Google Play wasn’t a problem at all, given there are many high-quality alternatives available (native Apps manager, Aurora, F-Droid…).
- In my experience, replacing Google Maps is a bit challenging because the alternatives aren’t as much userfriendly. But then again, nothing stops you from installing Google Maps on your /e/ if you really want it.
- Personally I didn’t like the default launcher, so I installed OpenLauncher which works perfectly for my needs. But well, I dislike the default launcher in many other phones anyway so I really can’t hold this against /e/
Well that’s all. On the upside, battery consumption is quite good.
P.S. with its ultra-long life cycle and because of the large overlap of their user target with /e/ user target, I have a feeling that FP3 will become the focal point when it comes to /e/ support (and non-google roms in general), so I would recommend going this route as hardware support is quite good already and will most likely get better in the future.