Live data from Hacker News

/e/OS is a complete, fully “deGoogled” mobile ecosystem

e.foundation

21–30 of 415 posts

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#21
post #8
post #2

There's absolutely no reason to use /e/ when GrapheneOS exists. https://eylenburg.github.io/android_comparison.htm

But GrapheneOS doesn't exist. It works only on a few devices created by Google, so their claim of being degoogled is a bit funny.

I must agree, you are right, GOS is only on Pixel phones.

But we have to keep in mind that /e/ has a lot of problems, the only one solved is sending data to Google. The security aspect of the OS is problematic and some key elements of a privacy seem questioning (AI integration, commercial collaborations, ...).

Fix: IA => AI typo and various English errors.

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#22

Tweaking user-hostile OSes into user-friendly ones is impressive, but not sustainable. Even worse, it slowing us down from leaving Android entirely. Look at the AdBlocker crackdown of Google Chrome. Every single chrome-fork has shut down MV2 extensions, even Brave is about to do it, because it is impossible to maintain features that complex on a browser that Google spends >$1B/year to develop. Same story for /e/ and…

> We should focus our efforts on truly open platforms.

But currently AOSP is very much open. That's also what the GrapheneOS devs say and why they want to continue using Android. Until it becomes clear that they will completely stop releasing the source code under a free software license i dont see why one should not use Android.

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#23
post #8
post #2

There's absolutely no reason to use /e/ when GrapheneOS exists. https://eylenburg.github.io/android_comparison.htm

But GrapheneOS doesn't exist. It works only on a few devices created by Google, so their claim of being degoogled is a bit funny.

GOS is degoogled in all the ways that I care about - it's about the data they can gather. Among all the smartphone options that I consider usable day to day (leaving only Android and iOS at the moment), GOS is the most private and secure.

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#24

Tweaking user-hostile OSes into user-friendly ones is impressive, but not sustainable. Even worse, it slowing us down from leaving Android entirely. Look at the AdBlocker crackdown of Google Chrome. Every single chrome-fork has shut down MV2 extensions, even Brave is about to do it, because it is impossible to maintain features that complex on a browser that Google spends >$1B/year to develop. Same story for /e/ and…

Chrome did not crack down on adblockers in Chrome. In fact the chromium team worked together with adblockers on mv3.

>it is impossible to maintain features that complex on a browser

While Chromium is complex, it is modularized which does make it possible for teams to maintain features.

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#25
post #8
post #2

There's absolutely no reason to use /e/ when GrapheneOS exists. https://eylenburg.github.io/android_comparison.htm

But GrapheneOS doesn't exist. It works only on a few devices created by Google, so their claim of being degoogled is a bit funny.

/e/OS is Android, meaning it's still critically dependent on goodwill of Google to continue releasing their work as part of AOSP.

So if you're trying to be a silly purist, then /e/OS doesn't fit either. If you're not, getting a Pixel will significantly enhance your safety since they're better supported for security patches and better designed in hardware when it comes to security.

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#26

Tweaking user-hostile OSes into user-friendly ones is impressive, but not sustainable. Even worse, it slowing us down from leaving Android entirely. Look at the AdBlocker crackdown of Google Chrome. Every single chrome-fork has shut down MV2 extensions, even Brave is about to do it, because it is impossible to maintain features that complex on a browser that Google spends >$1B/year to develop. Same story for /e/ and…

> Every single chrome-fork has shut down MV2 extensions, even Brave is about to do it

Source?

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#28

Tweaking user-hostile OSes into user-friendly ones is impressive, but not sustainable. Even worse, it slowing us down from leaving Android entirely. Look at the AdBlocker crackdown of Google Chrome. Every single chrome-fork has shut down MV2 extensions, even Brave is about to do it, because it is impossible to maintain features that complex on a browser that Google spends >$1B/year to develop. Same story for /e/ and…

> We should focus our efforts on truly open platforms. But currently AOSP is very much open. That's also what the GrapheneOS devs say and why they want to continue using Android. Until it becomes clear that they will completely stop releasing the source code under a free software license i dont see why one should not use Android.

AOSP dev went private, and Google is slower and slower at releasing the source, now twice a year. Worse, many stock apps like the Dialer and Gallery went closed-source years ago.

But the source isn't the point, it's the governance. Just like Chrome, having the source is not enough to guarantee an open platform. Sure you can disable telemetry flags. But you cannot afford to maintain an important feature Google wants to remove, like MV2.

https://arstechnica.com/gadgets/2025/03/google-makes-android... https://www.androidauthority.com/android-16-qpr1-source-code...

Re: /e/OS is a complete, fully “deGoogled” mobile ecosystem

#30
post #8
post #2

There's absolutely no reason to use /e/ when GrapheneOS exists. https://eylenburg.github.io/android_comparison.htm

But GrapheneOS doesn't exist. It works only on a few devices created by Google, so their claim of being degoogled is a bit funny.

Google's hardware is just hardware. It is not locked down like the hardware of many other manufacturers. Moreover, it's the only such hardware which also allows you, the user, to lock it down for your own security. GrapheneOS is not just focused around avoiding Google, it's more accurately focused around security and user choice.

The goal is to give you the option to avoid needing to rely on Google's spying or services while not having to compromise on security.

None of these other solutions regularly get included in Celebrite's documentation as being an explicit benchmark of their software's ability to break into phones. And that's almost certainly due to the fact that unless you leverage hardware security features like what GrapheneOS (and stock Android on a Pixel, and iOS on an iPhone) utilises, you have no chance of going against any actual adversaries.

And I'm not just talking about state actors here, even drive-by opportunistic attacks are likelier on a random other phone running some other Android build.

So yeah, you are running Google hardware, that doesn't make you "googled". It's just a sad reflection on the reality of the hardware landscape. If you want the same security as what GrapheneOS offers, you will currently need to use a Pixel.

I'd be curious to see what comes out of their Motorola partnership though.

Post reply on HN