| > I used it for a year and it was not very smooth GrapheneOS isn't any less 'smooth' than the stock OS. You should read https://grapheneos.org/usage#exec-spawning about the optional secure spawning feature which requires additional time for cold start application spawning. It doesn't really sound like you've used GrapheneOS > I used it for a year and it was not very smooth CalyxOS isn't a hardened OS. It substantially reduces security rather than improving it. It recently didn't ship half of the August security patches until part of the way into October including critical remote code execution vulnerabilities. They currently have missing security patches. They roll back the security model. It sounds like you're coming here from that community. A typical pattern from their community is pretending to be GrapheneOS users unhappy with it and spreading misinformation about it, which is obvious to people who know about it and have used it themselves. > Besides the phone bricked due to frequent updates. Which now I see happened to many people with Pixel phones, custom ROM or original. > I did not find a easy way to delay or disable the updates. https://grapheneos.org/usage#updates-disabling This has been near the top of the usage guide for years and if someone asked on the discussion forum, Matrix chat room, Twitter community or elsewhere they'd almost always be told about it or linked to it. There's absolutely no common issue with Pixels being bricked on updates. It definitely doesn't happen outside of extremely rare cases with GrapheneOS. It's unlikely that it happened here. Sometimes users do think their device isn't booting since it can take ~20 minutes after certain kinds of updates, but it does boot fine, and if they power it off it will just trigger rolling back. > And they immediately upgrade everything not just security updates, so something will probably break, apps stops working, and your workflow in general, because a lot of things change across android versions. We follow along with the stable releases of Android. These go through months of public betas. It's not possible to delay upgrading the major release on Pixels without going months without providing full security updates like LineageOS and LineageOS derivatives like CalyxOS. Not providing critical remote code execution patches for literally months as was the case this year from August until part of the way until October for CalyxOS is a serious problem. This occurs for them regularly with the browser engine and other patches too. > Lets be real most people are not tying running away from the 3 letters agencies. We want as most privacy and security possible, but we also want a fast phone, usable, compatible with apps, and customizable. This OS looks more like a exercise in security, prioritized over privacy and usability This is not at all accurate. GrapheneOS is highly usable and has broad app compatibility. It has far broader app compatibility than the OS you're trying to promote (CalyxOS). If you've used GrapheneOS, then you're aware it has the sandboxed Google Play compatibility layer (https://grapheneos.org/usage#sandboxed-google-play) allowing using nearly every app on the Play Store without giving any additional access to Google Play than it would have through the SDK / libraries included in those apps. > The developers, I am sure they are trying to do what they think is best, but they come across a bit arrogant. I think what comes across as arrogant is someone who is clearly unfamiliar with GrapheneOS and what it provides pretending they know all about it and other projects they haven't used or familiarized themselves with either. Typical for Hacker News though. > I don't care if root is an insecure vector, I will 100% root my phone. And use Google camera app. And use f-droid and whatever insecure app I wanna use Google Camera works fine on GrapheneOS without anything special. Google Play works fine on GrapheneOS as regular apps in the full standard app sandbox with all the GrapheneOS improvements to the app sandbox and permission model, and absolutely no special access or privileges. If you've used GrapheneOS or just read our features page and usage guide, then I'm sure you know all this already and don't need me to tell you here. > Especially to other open source communities, like Bromite, F-droid, CalyxOS, deciding to just do everything alone, which sounds unsustainable Unlike those projects, we do a substantial amount of collaboration with upstream projects. We do upstream work on AOSP, the Linux kernel, LLVM and other projects. We work with DivestOS, ProtonAOSP and other projects on areas where we have aligned goals. We won't work with people who engage in spreading misinformation about our project and targeting our developers with bullying/harassment like many of the people involved with Calyx. > Their built in browser still sends data to Google to increase privacy, by blending in, but I think I prefer Bromite model of blocking everything. This is not accurate. Vanadium doesn't send any user data to Google. |