Dedoimedo: Fairphone 6 with /e/OS - The perfect un-Android experience?

[Gandalf_The_Grey]

Do you remember the old days of phones? You would "set up" your device and be on your way. No cloud accounts, no thousand toggles, no excessive profiling. Simple life. Is this possible in 2026? Maybe. Unlikely, but there's a potential candidate. Android with minimal Google-ness, called /e/OS. Sounds cool. But hey, installing firmware on smartphones is a complicated procedure. Huh, you're in luck. Fairphone ships with this alternative option, no need for any tinkering. Great! I've already tested the phone a while back. A solid, mid-range phone that offers a bit more soul than the mainstream choices. Sure, there's an emotional element, but then, don't you feel all loved and pampered by the big tech every time you pick up your phone? Just recently, I also wrote about my ongoing endeavors with the Fairphone 6 in the first long-term report. Therefore, it makes sense to expand my experimentation.

What I would like to do today is show you what Android feels like - without being too Android. You've seen my take on this matter many times before. Every single time, it was the classic setup, with a Google account and many hours of tweaking spent trying to make each and every device slightly less stupid and annoying. If only there was a way to skip that ... Perhaps there is. Let me show you how I fared with /e/OS. The name seems funny, but don't let that stop you. After me.

Fairphone 6 with /e/OS - The perfect un-Android experience?

Long, detailed review of the /e/OS de-Googled Android operating system, tested on Fairphone 6, including usage model and differences from stock Android, MicroG service and potential security implications and considerations, first run and setup, look and feel, default applications and...

www.dedoimedo.com

 

[Bot]

Fairphone 6 with /e/OS - The perfect un-Android experience?

Long, detailed review of the /e/OS de-Googled Android operating system, tested on Fairphone 6, including usage model and differences from stock Android, MicroG service and potential security implications and considerations, first run and setup, look and feel, default applications and...

www.dedoimedo.com

/e/OS on a Fairphone is one of the more “mainstream” ways to get an Android experience with much less Google integration, mainly because it avoids the usual bootloader/ROM DIY risk and still stays relatively close to stock Android in day-to-day use.

That said, it’s worth framing it as a set of trade-offs rather than a return to the “old phone days.” You get less Google account dependency, but you don’t automatically get privacy or security “for free,” because apps, networks, and update practices still matter.

What /e/OS actually changes (in practical terms)

• No mandatory Google account during setup, and generally fewer Google components baked in.
• Typically relies on microG (an open-source re-implementation of some Google Play Services APIs) to keep many apps functional without official Google services.
• Includes a curated app store experience (often via third-party sources) plus support for F-Droid-style installation, depending on the build and configuration.

The biggest real-world pros

• Less Google tie-in: fewer Google apps/services by default, and less pressure to sign in everywhere.
• Cleaner baseline: starting from a more minimal setup can reduce the “hours of toggles” problem.
• Fairphone angle: if you value repairability and longer device support, Fairphone is one of the few vendors that even tries to make that a selling point.

The biggest real-world cons (and where people get surprised)

• App compatibility isn’t guaranteed: anything that depends on Google Play Services heavily (push notifications, maps APIs, certain DRM) can behave differently under microG.
• Banking/streaming/work apps may fail: some apps use Play Integrity/SafetyNet-style checks; functionality can break or be limited, and this can change over time.
• Security posture depends on update cadence: what matters is how quickly the OS ships Android security patches and firmware updates for that specific device. This is not something anyone should assume—verify it from the vendor’s documentation/changelog.
• Privacy is still largely “app-driven”: even without Google, many apps (especially social/media/ads SDK-heavy apps) profile users aggressively on their own.

Security notes that matter on any de-Googled Android

• Keep the OS fully updated (monthly security patches are the baseline expectation).
• Use only reputable app sources, and prefer F-Droid for open-source apps when possible.
• Be cautious with “random APK” installs—this is one of the easiest ways to turn a privacy-focused phone into a compromised phone.
• Consider DNS-based tracking protection (from a reputable provider) as a *supplement*, not a replacement for good app hygiene.

Low-risk way to evaluate it before committing (recommended)

• List your “must-have” apps (banking, authenticator, work MDM, streaming, transit, etc.) and test them first.
• Check the OS vendor’s published security update policy and recent patch history for your exact model.
• If you want an objective signal on app behavior, run with minimal apps for a week and only add what you truly need.

If the goal is “less Google without becoming a tinkering project,” /e/OS on Fairphone is a reasonable candidate—but the deciding factors should be (1) update reliability for your model and (2) whether your critical apps still work under microG/without Play Integrity dependencies. The safest next step is to verify the device’s patch cadence and test your must-have apps before migrating your digital life over.

 

[LinuxFan58]

Well, I am interested in a more private phone, but not willing to pay twice as much for this phone than my Samsung A56 (while teh A56 marginally beats the gen 6 fairfone in secs)