If I read previous articles right, Google has stopped shipping Pixel specific hardware drivers down to the android open source project, so any hardware support graphene figures out going forward has to be reverse engineered anyway.
I don't know about releasing an actual phone but they've released closed source patches for testing. They have the code but they can't opensource the code until google does so publicly, so yes they've got a OEM partner.
It's more that Google is making it significantly more difficult for non-Google sanctioned projects to operate on Pixel phones and there may come a time when it's no longer feasible to develop GrapheneOS for the Pixel
If I read previous articles right, Google has stopped shipping Pixel specific hardware drivers down to the android open source project, so any hardware support graphene figures out going forward has to be reverse engineered anyway.
So that's some additional motivation at least.
Sounds like Google is no longer giving security patches as quickly as the used to. I may be wrong.
I don't know about releasing an actual phone but they've released closed source patches for testing. They have the code but they can't opensource the code until google does so publicly, so yes they've got a OEM partner.
https://grapheneos.social/@GrapheneOS/115164133992525834
It's more that Google is making it significantly more difficult for non-Google sanctioned projects to operate on Pixel phones and there may come a time when it's no longer feasible to develop GrapheneOS for the Pixel
They said for at least a couple of years that they want to expand to other phone models or that they're partnering with a major OEM?