Thanks for posting this. I spent some time looking at how "de-Googled" GrapheneOS is. If you define "de-Googled" as meaning the phone makes no connections to

Thanks for posting this. I spent some time looking at how "de-Googled" GrapheneOS is. If you define "de-Googled" as meaning the phone makes no connections to Google servers that you do not explicitly acknowledge/permit, then GrapheneOS is still far from "de-Googled". Just to give one example, SUPL. There are also plenty of unGoogled-Chromium patches GrapheneOS doesn't apply. I'm not saying GrapheneOS isn't way better than the Android that ships on phones, but it's misleading to pretend they care about de-Googling as a first tier priority. GrapheneOS does do some privacy oriented work, but it's far more focused on hardening. I look forward to examining /e/ and CalyxOS since their focus is more heavily on privacy. For my use cases, I'm less worried about hardening than privacy. Also, it's a lot of work to keep Android both up-to-date and de-Googled. I started patching GrapheneOS and realized I did not have the bandwidth to maintain the patchset. And still had no good answer for SUPL. Hopefully CalyxOS and /e/ have maintainers with the bandwidth.