/e/OS is not fully degoogled, as DNS connectivity checks, hardware attestation provisioning, and eSIM activation all go through Google.
It is often many weeks or months behind on security updates, especially in the WebView, which makes it easy to exploit.
It doesn’t support bootloader locking on many devices, and if you lock the bootloader on a phone that does support it, it could brick if /e/OS is on an older security patch than the stock ROM was.
It doesn’t use a lot of the hardening in GrapheneOS such as hardened_malloc which prevents memory corruption exploits, even if the hardware supports it.
And finally, /e/OS’s text-to-speech sends what you say to OpenAI, despite local options being available.
If you want a properly secure Android phone, the best option is GrapheneOS, however it only supports Pixel phones and future Motarola phones due to its high security requirements.
If you can’t get a Pixel then iOS in lockdown mode is the next best option, however if you can’t replace your phone, LineageOS is much worse than Graphene although it is still much better than /e/.
/e/OS is not fully degoogled, as DNS connectivity checks, hardware attestation provisioning, and eSIM activation all go through Google.
They are working on some of this, at least eSIM activation. Also do you have a source for DNS connectivity checks? AFAIK they have used their own for a while
It is often many weeks or months behind on security updates, especially in the WebView, which makes it easy to exploit.
This is a serious problem, however their update speed is comparable to a lot of default ROMs
It doesn’t support bootloader locking on many devices, and if you lock the bootloader on a phone that does support it, it could brick if /e/OS is on an older security patch than the stock ROM was
/e/os supports boot loader relocking on most official devices, however the community builds don’t support it. The bricking part has nothing to do with /e/os, it’s a hardware security feature of some devices. This would happen with any ROM including the official one
And finally, /e/OS’s text-to-speech sends what you say to OpenAI, despite local options being available.
I assume you mean speech-to-text? Anyway the feature is opt in and they have since updated it to include a prompt to inform you about what it will do. Their reasoning for a cloud option was that local options either are bad or have too high ressource usage (important as /e/os supports a lot of underpowered devices). Overall a stupid move, but they adjusted the feature to let users make an informed choice
If you can’t get a Pixel then iOS in lockdown mode is the next best option, however if you can’t replace your phone, LineageOS is much worse than Graphene although it is still much better than /e/.
Lineageos might have quicker updates, though it is even more connected to google, except for not including microg. However a lot of people will need google play services so they will have to install it anyway
As someone who bought a Murena FairPhone 5 with /e/OS preinstalled because I had the option to pay a reasonable price for a decent phone that isn’t Google branded, and have been enjoying the experience with it for a while now, I don’t think I’m going to fall for that very obvious rage bait that’s been copy-pasted from an aggressive forum post.
I’ll give GrapheneOS my attention when it works on more than one phone. I hear Motorola is building a second phone for it to be compatible with.
Booooriing. (Written fro e/OS phone)
OpenAI feature is called Murena Voice to Text, so users don’t know, it’s OpenAI. They use tracking ids in their own update process. They ignore critique.
Graphene is currently only available for Google devices and therefore no alternative.
Lineage contains connections to Google as well.
Recommending iOS is ridicolous.
OpenAI feature is called Murena Voice to Text, so users don’t know, it’s OpenAI. They use tracking ids in their own update process. They ignore critique.
Graphene is currently only available for Google devices and therefore no alternative.
Lineage contains connections to Google as well.
Recommending iOS is ridicolous.
what has prompted this, I wonder.
Is it already time for the lead GrapheneOS developer’s annual crash out? Where do the years go?
the fun thing is like, I use grapheneOS on a pixel 10 pro, though I find it kind of difficult to fess up to given the cringeworthy escapades of the graphene community.
who pissed in their cereal? does the mere presence of other ROM projects attack their identity in some way? have they claimed to be more secure than GOS and others?
Wrong about everything + no arguments award 🏅
Sorry but this sounds again like the typical e/Os bashing from GrapheneOS users.
Those two system are not the same. One is focused on security and the other on privacy.
Yes I know about the issues of e/OS, but it is still better than using Google or Apple.
For me personally I moved cause I don’t want to support american companies. So Graphene was no option, as I would need to give google some money or buy one 2nd hand. But Pixels are still quite expensive compared with others.
Why do you always need to attack other systems, they can coexist. We should be happy people have more options to break free from Big Tech companies.
This is honeslty a shameful post. A personal rant with just a nasty agenda
People or projects attacking other privacy focused projects working on good faith intent to help us escape the duopoly are just sad. If a project doesn’t fit your personal needs, so be it, move on
As a whole we need as many of these projects to succeed & elevate as possible. Shooting at others because you got your feelings hurt elsewhere is childish and self-defeating for all. Last thing we need is creating a monopoly of privacy focused options
Security is very important.
