nostr:npub1kl8e7s48j6cfr6zrmn53n5l0fsxustszj3fwmu9ahn0tnm9e8euq80u2uq nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk 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.
nostr:npub1kl8e7s48j6cfr6zrmn53n5l0fsxustszj3fwmu9ahn0tnm9e8euq80u2uq nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk We don't think the story is real or makes sense. It's a bunch of unsubstantiated assumptions repeated by many tech sites. There has been no reliable source claiming it and it wouldn't be specific to phones since many other devices also have radios. OEMs we're in contact with aren't aware of anything stopping them supporting alternate operating systems in Europe.
Discussion
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.
Each time you buy a pixel you support financially google and make it even more powerful.
Working towards OEM partnership always seemed like a good idea for graphene long term instead of depending on one hardware partner (a known privacy bad actor) playing ball.
Glad to see the issue being forced so Graphene can take this huge next step!