CalyxOS now supports Pixel 6 and Pixel 6 Pro
calyxos.org
calyxos.org
I don't know whether the maintainers have the bandwidth, tooling, processes and procedures, and vetting to ensure that an image doesn't get backdoored. Given the Venn diagram of "people who want to keep stuff private" and "people who will go through the trouble of installing and using CalyxOS" probably has significant overlap, I would assume some well-funded adversaries, including state actors, are motivated to sabotage it.
At least with the standard Google Pixel images, I have some degree of assurance from Google's robust source management and security infrastructure. The bar for backdooring an official Google product is much higher than the bar for backdooring a hobbyist project.
google hasn't posted a new image or ota for pixel 6(pro) since november. last i read it was held up by some breakage of the google assistant.
i don't know how much patching gets done via google play, but this seems really disappointing. no rces but loads of eops which now means the phone is only as secure as the weakest app supply chain?
With de-googled OSes that provide proper network controls, you can at least cut out commercial spying.
It means you no longer need to trust the infrastructure or machines being used to create the images, just the developer through their source code which, yes, while it's a daunting task to review, it's "just" a fork of AOSP.
I've been building a modified LineageOS for a while, and these posts always have me circle back around and question if I should just go back to stock, Graphene or Calyx.
I've spent some time in the corresponding IRC channels and... asking about the other OS and how things compare seems rather frowned on in both of them.
I also notice things like push notifications work just fine with Calyx, and not on Graphene, which I think is due to microG and/or Firebase.
I think there is some additional hardening that Graphene does as well.
If your goal is the most possible privacy and security, I'd go with Graphene. For a much-improved privacy, mostly non-Google experience, where you can still use Maps or your bank's app, I'd go with Calyx.
This is definitely superior to the mircog approach which means enabling signature spoofing for applications.
What if I do not want to run Google Play Services at all (or any proprietary code from Google)? Can Graphene sandbox microg instead?
It might be able to, but AFAIK microg works by pretending to actually be google services, so it's possible it depends on the system privileges that google services usually has?
Also, it is not as black and white, copperhead os did try to backstab him by selling his own work. Also, a secure OS is very much the same as cryto — you don’t roll your own. And while the enthusiasm is welcome in this space, it is simply a ridiculously hard domain which should not be done by novices.
Graphene does not.
Tl;Dr: If you want a privacy-focused no-compromises fork of Lineage OS, and the default hardening Google performs on their platform is enough for your personal threshold of safety (this is where most custom ROMs settle), Calyx is probably a good choice. If you're concerned about novel security vulnerabilities (read: more paranoid/vulnerable than most) affecting your device, choose Graphene.
Privacy-wise, Calyx is basically Lineage with most of it's headline features being provided via LOS or third-party apps available on F-Droid. It does a good job at de-Googling your experience and has good privacy-focused default settings and apps. I like the custom location provider. Their egress firewall feature is a nifty improvement on top of LOS's original implementation of a similar feature.
Security- and hardening-wise, it's not much better than Lineage, which isn't much better than AOSP. Zero to little runtime or kernel hardening to be found. Graphene, on the other hand, puts the effort into hardening as many aspects of Android and the kernel as possible. Graphene has a custom hardened `malloc` for helping prevent memory safety exploits, a hardened libc, toolchain, and app runtime, among all sorts of other difficult but valuable security changes. Functionality-wise: almost anything Calyx can do, Graphene can do with some F-Droid apps to help.
This might seem a bit harsh, but the reality is that Graphene has some a large number of deep security changes upon AOSP that Calyx isn't yet up to par with. As we've all seen, security in 2021 is difficult, and it takes decades or a lot of specialized experience to be a security expert. It's difficult enough for large companies to hire and retain security talent, and for hobbyist projects/small organizations even more so.
Does everyone need a hardened runtime? Probably not. Are there people who do and/or want one? Definitely
Edit: one concern of mine about Calyx is their bundled VPN serviced by Sprint (as per https://calyxinstitute.org/legal/terms-of-service). Third-party VPNs are always to be taken with a grain of salt for privacy depending on your activities online and the VPN's owners themselves. I suppose it's better to have a VPN than not, but you must also trust that party and their security with your highly valuable network traffic, which should be a very high bar. Obviously, nothing limits you from loading up OpenVPN, IPSec, Wireguard, etc and going your own route.
Nonetheless, the project has an absolutely stellar track record, where the main guy behind it even revoked the signing keys of the OS upon a failed for-profit company overtake attempt. The project doesn’t accept any for-profit company offers since then and is independent and open-source.
The possibility of expanded device support is encouraging. Pixel devices have always been the most accommodating of alternative Android distros, but as many people have noticed, it's unfortunate that a software project that tries to distance the user from Google services has a dependency on Google hardware.
Trust me, some wild-ass Pixel 6 hardware fault will emerge in the next twelve months.
Also, while the Pixel 6 (non-Pro) is competitively priced for its hardware features, I don't think the Pixel 1-5 (excluding the A-series phones) were the best-value products on the market at their launch prices. CalyxOS users would benefit from having support for high-end devices that are a better value for the money, and for entry-level devices for users with limited budgets.
CalyxOS does support the Xiaomi Mi A2, but the device's 4G band coverage is limited in some parts of the world, and the support seems to be expiring immediately after this update: https://calyxos.org/docs/guide/device-support/
As I understand it, Pixel phones do image processing in hardware instead of in software so CameraX can provide the same level of image quality as Google Camera.