- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
The killswitches are great, but if it is not based off GrapheneOS it is not really worth using.
Having great looking hardened ROMS would be so great! And as Android already so secure and GrapheneOS doesnt reinvent the wheel, it should just work.
Using LineageOS as base, I suppose
- SUPL
- captive portal
- connectivity check
- device authentification
Will still all run through Google. And if you need Google services or even the store, you need to install them unsandboxed, unlike on GrapheneOS.
/e/OS fixes captive portal and connectivity checks as far as i know
Opt-in should not be the standard, but thats good news
csprive pırtal is modified by /e/OS not to use google, and I am pretty sure you can modify others
It’s a good first step imo. It maintains compatibility with Google apps, which as the author notes, would be needed for it to not be a dead project. It’s a pretty good balance.
That said, I’m not familiar with Graphene, so I could just be wrong.
Dont know how this should help “maintaining compatibility with Google apps”. Has no impact here. GrapheneOS does that by shipping normal play store and services, but with a compatibility layer to be able to run in a sandbox
Does Murena 2 still use microG?
