It will start out being their regular phones with security and updates improved to meet the requirements of GrapheneOS. When we demonstrate there's a huge demand for it after the products launch, we can have more influence. Our focus would be adding some security features not available on Pixels. The current aim is preserving the security we get from Pixels, but the future goals are more ambitious.

The Sony Xperia XZ1 Compact was the perfect size phone and I hate the world for not having successors of the same size.

Seconded! Need a smaller phone! and video out means i can make screen biggger if i want!

Do you guys all have that small pockets? I have a 6.7" Smartphone and never had an issue with its size

> 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.

Pixel 10 will be supported by GrapheneOS provided it continues to meet our requirements - we'll know when it's out. It'll definitely take us longer than it has before.

A collaboration with an OEM doesn't mean we'll stop providing existing or future Pixels if they continue to meet our requirements.

> "As you're working with the OEM, I hope you'll consider a model which will come with either an IPS screen or is compatible with a 3rd party IPS replacement."

Ahaha, don't get your hopes up, friend. The possibility of an adequate, degoogled Android with picky requirements as GOS on good, ultramobile hardware (matte DCI-P3 IPS, 3.5 mm audio, USB-C 3.2 or better, dedicated, ideally quick-access mSD card slot, IP68 rating, good cameras, EMR pen compatibility, changeable battery, non-plastic case) is virtually nil. That would essentially be a modern hybrid between a Samsung XCover Pro 6 and one of the older Samsung Note phones, e. g. the Note 9. Days long gone... :(

Agreed, pixel oled (and iphone oled) make my eyes blurry and achy and ia ssume its the pwm. ips laptop, other phones never have this effect

for me a non-OLED screen would be a non starter. I love reading text (white text with black background) and watching HDR videos on OLED screens

The comment above was describing in great detail how this is not the case and after some initial effort should prove no difference at all.

Generic power-user here: I am going to guess without the backing of Google going forcefully open-source, "niche" hardware such as Google's Tensor will lose their attractiveness.

However one must note also that for now not even Snapdragon fulfills GOS requirements. If/when that changes, Snapdragon devices may have more open-source community momentum than Google's Tensor. Plus all the economy of scale, etc..

In terms of security, Microtek is even more far behind Snapdragon.

Again, not an Android dev here, take the text above with a grain of salt, YMMV, etc..