Oddbean new post about | logout
 Speaking of which, I tried Graphene a few weeks ago, and it was painful. CalyxOS > GrapheneOS

nostr:nevent1qyw8wumn8ghj76r0v3kxymmy9e3k7unpvdkx2tn5dahkcue0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uqsuamnwvaz7tmwdaejumr0dshsqgz2z0yaudrp6j2vf75mgfw6k0nxrel3u4zx0nlk5afqq23fqncqcq5l2ymg 
 I can't confirm this. 
 interested to hear more! what was of note in the difference?  
 I think something about the way graphene emulates google play services stuff introduces a ton of latency. The same phone is buttery smooth on calyx, but so so bad on graphene. There were lots of other weird little UI bugs too, just things not working as expected. 
 It's because graphene has a lot of security stuff and calix don't.
Calix is less secure than stock android specially if you still use gapps 
 I figured it was probably to do with the security layer. Less secure you say, in what way? 
 If you install gapps it will be system applications in calyx
They also failed to deliver security updates a lot of times, sometimes for months 
 😬 
 I would like to try one of those Motorola receiving support from calyx, pixel phones are so expensive. And calyx has a much longer support 
 Buy a pixel 4 on ebay, $100 
 It will have maybe only one more year of updates. 
 But graphene with its hardened features may be better against govt and 3L agencies attack. 
 Yes, but I still use Google Maps, so I'm not sure that matters much for my purposes 
 Heretic!!!! 
 😂 
 I use cashapp on my graphene phone, and it works flawlessly.  Pixel 6a 
 I respectfully disagree. 
 Rare L. Massive one too. 
 So it seems. I'm getting edjumacated today. Graphene has to improve its UX though if it wants to win. 
 Idk, I think Graphene UX is pretty damn good. Maybe I just haven't tried out any other ROMs? 
 Sounds like mileage varies. My install was basically unusable 
 Respectfully, this is a bad take. GrapheneOS generally works very well and is considerably more secure than CalyxOS or the stock Android distro, both of which sacrifice security for performance.

I do agree that GrapheneOS needs to improve UX, especially the stock AOSP apps which all need to be replaced with modern Kotlin + Jetpack Compose apps.

GrapheneOS makes Google entirely optional. Instead of replacing the first party privileged code with less battle-tested third-party privileged code in the form of MicroG, GrapheneOS coerces the real Google services to run unprivileged in a normal application sandbox, and therefore under the user's full control. There may be some performance issues currently as a result of this workaround for Google's horrible software practices.

Using MicroG is probably why others have called CalyxOS less secure than stock Android, and this may be true. MicroG still communicates with Google and, unless I'm severely mistaken, is still privileged code. The only thing you're gaining is transparency into the code of MicroG. There isn't any additional security, and as I noted above, this approach is considerably less battle-tested than Google Play, meaning that in fact it probably is less secure than stock Android. It may also have more compatibility issues with apps than the approach used in GrapheneOS.

I'm not saying you're wrong for using a less secure OS, but please try to understand the differences before calling one better than the other. You're sacrificing a lot of security for those small performance gains, and I haven't even started describing the plethora of other security hardening GrapheneOS adds. Ultimately, use what meets your needs, but don't discount what GrapheneOS offers. It's an incredible project.