Privacy Guides post vs /e/OS

Please see discussions here:


Github: A case for /e/OS as a first step away from Google Android for beginners · Discussion #479 · privacyguides/ · GitHub

Edit: Privacy Guides’ take in the Github discussion linked above on /e/OS is quite damning:

"In short, /e/OS will not be recommended until they at least:

  1. Support verified boot for devices that do support verified boot with third party OSes.
  2. Ship firmware updates for devices that have not reached EOL.
  3. Not have any major security regression over the stock OS.

While there is no “anti recommendation” against /e/OS, it is not recommended either because it does not meet basic security requirements…I don’t want to recommend options that I know are bad/questionable."

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone


I would love to see this addressed. If you look at the comments on Github and on Reddit, they make /e/ look like a bad option from a security standpoint.

1 Like

Yes they do, but are they wrong? :wink:

nothing damning about it, it’s tradeoffs. /e/ is not foremost about security. While elitists on Pixels fly high about AvB, /e/ (or Lineage) users on old phones do live a bit more freely off an analytics industry that is very much unimpressed by boot verity and firmware updates. Encrypt your user partition and if your device gets lost cycle credentials fast.

1 Like

I just leave this here:


This topic was automatically closed after 13 days. New replies are no longer allowed.