Definitely on this boat. CalyxOS feels like it strikes a good balance between security/privacy and practical usability--the locked bootloader and app-specific firewall options are a huge plus, while MicroG ensures that I can still use every app I used to with the old Pixel-specific OS without ceding all of my data to Google Play Services.
Invariably people bring up the signature spoofing needed for MicroG as some huge security hole, but from what I've seen it's really a non-issue--CalyxOS has tight restrictions to specifically allow only MicroG to use this, it's disabled for any other app.
Same. It feels like the "have the cake and eat it" situation for me who switched over from iOS.
I was worried that some apps might not work but that is not the case. Everything from banking apps to password managers just works fine with the only exception being NPR One (which is hilarious).
They are really doing an outstanding job and I do not miss anything on here besides a Apple/Google Pay NFC solution. But that is quite ok.
Can I expect CalyxOS to support the Pixel 6 rather soon? Is e.g. camera performance dependent on closed source Google code/firmware? What are the limitations there?
I was going for GrapheneOS, but tbh seeing that one main developer's personality issues turned me off big time. I don't care about technical advantages, if I have to trust in that guy's impulse control. Too small a project for that.
You can expect a dedicated team to start working on it once they're able to get their hands on some Pixel 6 devices. They don't get them early from Google you know, there's no cooperation there. They buy them when they're released just like we do, and it hasn't been released yet so work hasn't started.
The general attitude towards GCam seems to be... Calyx isn't going to ship it but it's generally understood most people will be using it. The recommendation I got when I switched was to install the apk and disable all network access via Datura before I launched it for the first time. That works well, the pictures look great too. A recommendation I heard after I did that which I will be following next time is to extract the gcam apk from your new phone before you flash calyx and install that one (to avoid apkmirror or whatever).
GrapheneOS’s main dev can come across as paranoid, but it is sort of understandable given the history of the project. Nonetheless, they are doing a spectacular job and I think using GCam with properly set permissions is the best of both words.
Paranoia is not the problem. The problem is general hostility and not being open to other viewpoints and ideas. Also I feel some kind of power hunger, which makes me feel really uncomfortable surrendering basically full control over my phone to these people.
From what I’ve seen, he gets summoned, and angry when things like “Calyx pays great attention to usability, while GrapheneOS gives more focus to security at the price of usability” gets mentioned, which is just false.
Also, do note that it is indeed a dangerous business — false sense of security is the worst. And there are plenty of companies taking advantage of people wanting something “privacy-oriented”.
Nah, it's not about having strong options. I've been around nerds forever, that doesn't bother me. Yours might be the impression on recent HN, but if you look around he is all over the place, attacking people on various platforms, while promoting some conspiracy narrative; derailing, gaslighting and manipulation. Whatever is going on with that guy, something is definitely going on. He doesn't inspire trust, he probably needs therapy.
Micay started working on the project and got some funding from copperhead os, with the plan being that the company could provide paid support and the like.
But copperhead os broke its promises and basically hijacked the project - but Micay being a professional, he invalidated the validation keys so that existing users would not get served code not associated with him.
Afterwards he continued working on the open source project without any partnership, while copperhead os continues to take the code, add some questionable modifications to it and sell it, while badmouthing GrapheneOS.
I wouldn’t go as far as to make psychological advice on someone based on a few interactions, but seeing how people in the industry can burn out from some rude comments, being totally backstabbed does explain his behavior. Also, do note that he is a professional security expert (the upstream android project routinely takes commits from his project) and unfortunately even with the best intentions, one can create absolutely shitty distros regarding security. Being critical of them may look “competitive”, but he only wants end users safe.
That's what I believed until I had a direct (online) conversation, which got unpleasant very quickly. Maybe there is a grain of truth in there, but I am more inclined to think it might at least be exaggerated by a lot.
