I know the generall guidance for private phones was Pixel with graphene OS. I was financially planing on buying a 10th gen pixel when they come out later this year to only put gos on it. However with the recent news, I am wondering if this is still the recommended best practice from this community.
I am worried that if the gos team needs to spend tonnes of ressources on maintaining basic drivers and stuff then they won’t have any time to work on the privacy and security features they are best known for.
What is your oppinion?
Also does anyone have a way to dpam feedback to google? I couldn’t finf a generall feedback form, but if they know that people aren’t buying their hardware because of this decision, they might back down. (I really fell in love with gos researching it lately so I would hate to have to switch to something like /e/ os or calyx or something)
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
much thanks to @gary_host_laptop for the logo design :)
In the GrapheneOS development room there’s a lot of talk about finding an OEM to get security partner status from and/or to design a grapheneos specific device. I saw they were tentatively chatting to the CEO of Mecha (currently crowdfunding for a Linux handheld called the comet) as well as another anonymous Android OEM lead. So I’d say be patient, wait and see. I’m confident the project will continue, hopefully with full support for pixels via a partnership but potentially on their own hardware.