nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqyxlpj2gl6dt2nfvkl4yyrl6pr2hjkycrdh2dr5r42n7ktwn7pdqlv2l6t We want to be clear that GrapheneOS will continue supporting existing Pixels until end-of-life. We'll likely be able to add support for 10th gen Pixels but it will take significantly more time. It has been taking us around 24 hours after new Pixels launch to add support for them since after the Pixel 6 launched. It's not going to be that way anymore, even if future Pixels meet all our requirements and we can still support them.

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqyxlpj2gl6dt2nfvkl4yyrl6pr2hjkycrdh2dr5r42n7ktwn7pdqlv2l6t We're working with a major non-Pixel OEM to have their future devices meet our requirements and officially support GrapheneOS. It's likely they'll end up selling devices with the official GrapheneOS releases as an option. We can't say which OEM it is or provide more details but they definitely have the resources to meet our requirements. It would be flagship Snapdragon devices initially and not custom hardware, at least initially.

I'm very excited about this news. I have been kind of surprised there isn't more excitement in the community that there might soon be a flagship GrapheneOS phone so we won't even have to buy a Google device to get started.

Yeah, definitely huge news. My only concern is supply chain attacks, which are very likely, in my opinion, if there is a specific graphene device. What do you think?

We're running on hostile hardware designed and distributed by the enemy already.

Yeah but right now we use a mainstream product and change the software. So less likely that they attack the whole pixel supply chain. But once a device is specifically built for graphene, things change a lot imo.

Is snapdragon bad? You make it sound like it is