> Because you said discussion are being done with an OEM, will GraphaneOS switch from pixels to a different device?

Pixels will be supported until end-of-life. Future Pixels will be supported if they continue meeting our requirements.

> You also said that not having the device tree won't be a major hurdle in building GraphaneOS for the future, does that mean we can expect the pixel 10 to have GraphaneOS or it's too early to know ?

We expect 10th gen Pixels to meet our requirements and we should be able to add support for them. It's not going to happen in 12 to 48 hours from the official launch of the devices as we did for around the Pixel 6a and later. It will be more work. We've automated most of the device support for existing Pixels now and have removed nearly all of the Android 15 QPR2 device trees rather than manually updating them. We're continuing to automate more and will use that approach for supporting new Pixels.

The devices with an OEM partner are further in the future than the Pixel 10. We need Qualcomm's new SoC with hardware memory tagging support to launch because a flagship Snapdragon is the best fit other than the current lack of hardware memory tagging. Some things need to be addressed by the OEM including licensing extra things like Qualcomm and filling in some missing features. There needs to be a clear, workable plan for updates including Linux kernel LTS branches.

Makes sense, thanks for the reply!

I've never owned a pixel, but I'm planning on getting the pixel 10 so I can use the new android 16 Linux terminal with graphical support. I hope the pixel 10 will still fit your requirements and it won't be a hurdle to port GOS without the device tree. I see no other OEM supporting the level of virtualization with kvm and vergil Google is bringing to the pixels. Good luck!