Replying to Avatar GrapheneOS

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqkl8e7s48j6cfr6zrmn53n5l0fsxustszj3fwmu9ahn0tnm9e8euqmwdfch nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzssxadyp There are things happening which are concerning and harmful to us. Google is taking actions which cause further harm to AOSP-based projects. We're worried about some of what's happening and we may have to end up entirely focused on OEM partnerships for future devices. We're not sure if we can support future Pixels so the OEM partnership could become the only option.

I hope that a solution can be found to keep the same quality OS, on Pixel or other devices. To be honest I would even prefer if you could work on your own hardware with design optimized for security and privacy but I guess it would require much more ressources.

Reply to this note

Please Login to reply.

Discussion

We're already working with another major OEM to produce a GrapheneOS device but we can't discuss further details at this time.

Long term this sounds like a better solution than pixels