/e/OS is a complete, fully “deGoogled” mobile ecosystem
A privacy-focused Android variant called /e/OS, marketed as a “de-Googled” mobile ecosystem, draws mixed reactions: some users report it works well on devices like Fairphone and appreciate its friendlier UI and broad hardware support, while critics point to delayed security patches, reliance on microG, and defaults that still contact Google or even OpenAI for speech-to-text. Much of the debate contrasts /e/OS with GrapheneOS, LineageOS and Linux-based alternatives, weighing usability and app compatibility (especially banking and government apps) against stricter security models and faster updates. A recurring concern is whether replacing Google with Murena’s cloud services meaningfully improves user autonomy, and how feasible it really is to escape the Android/iOS duopoly given hardware constraints and app ecosystem lock-in.
Comparisons with GrapheneOS and other ROMs
- Many argue there’s “no reason” to use /e/OS if you can use GrapheneOS, citing better security, faster patches, and sandboxed Google Play.
- Counterpoint: GrapheneOS only supports Pixels (and possibly future Motorola devices), so /e/OS, LineageOS, iodéOS, etc. matter for non‑Pixel or older devices.
- LineageOS now supports signature spoofing, and there’s a LineageOS-for-microG fork; some see these or iodéOS as cleaner alternatives to /e/OS.
Privacy vs Security Trade‑offs
- /e/OS is positioned as “de-Googled,” but critics note:
- microG still talks to Google for device registration, push, SafetyNet, assisted GPS, etc.
- microG loads proprietary Google binaries with privileged access.
- /e/OS is described as privacy‑friendlier than stock Android but substantially weaker than GrapheneOS in security (delayed patches, old kernels, no strong hardware hardening).
- Several comments stress that privacy without security fails under real adversaries (border checks, protests, forensic tools).
Murena Ecosystem and Trust
- Murena account and cloud (Nextcloud-based) are deeply integrated; some like the convenience, others dislike “replacing Google with another central provider.”
- Some users ignore Murena services or self‑host; others distrust Murena’s privacy policy and lack of transparency around components like the “CleanAPK” app source.
OpenAI Speech‑to‑Text Controversy
- /e/OS speech‑to‑text has used OpenAI via a proxy.
- Initially this reportedly happened by default with inadequate consent; over months, they added and fixed an opt‑in dialog and anonymization.
- For some, any cloud STT is unacceptable; others see it as a reasonable interim compromise until on‑device models are good enough.
App Compatibility, Banking, and Attestation
- Real‑world experiences are mixed:
- Some report most banking and government apps working fine.
- Others hit hard blocks (Play Integrity, root/bootloader checks) and even utilities/banks that refuse to support “alternative OSes.”
- GrapheneOS is praised for systematically tracking app compatibility and for sandboxed Google Play that often works better than microG.
Updates and Technical Quality
- Historically, /e/OS lagged months behind on Android security bulletins; some say it’s now down to ~2 weeks and releasing monthly.
- Critics note not all patches are backported, and vendor firmware/kernels remain old, especially on devices like Fairphone 4.
Installer and WebUSB Friction
- The web installer relies on WebUSB, so Firefox users see a “browser not supported” message and are pushed toward Chrome/Edge/Opera.
- Many see this as ironic for a “privacy” OS and poor UX; they suggest clearly falling back to a simple supported-devices list and manual install docs.
User Experience Reports
- Several users report multi‑year daily use on Fairphone and other devices, describing /e/OS as stable, familiar Android with less Google tracking and extended device life.
- Others left /e/OS over bugs (e.g., call display issues), forced wipes on upgrade, or distrust over security posture, switching to GrapheneOS or Lineage instead.