GrapheneOS based on Android 16 has been through extensive public Alpha/Beta testing and should reach our Stable channel today. We'll continue fixing various upstream Android 16 regressions such as the back button issue impacting the stock Pixel OS we fixed in our latest release.
July Android Security Bulletin will likely be published today. We obtained early access to the signed partner preview and confirmed no additional patches were required, so we set the 2025-07-01 patch level last month after we backported Pixel 2025-06-05 driver/firmware patches.
Tomorrow will likely be the first monthly update of Android 16 with a new Android Open Source Project and Pixel stock OS release. We won't need to backport Pixel driver/firmware patches since we're on Android 16 and can simply incorporate and ship the monthly update within hours.
It can be extraordinarily difficult to backport driver/firmware patches due to dependencies on the new major release. We were only able to backport everything required for the 2025-06-05 security patch level because Android 15 QPR2 is much closer to Android 16 than Android 15.
After our Android 16 port was completed yesterday, we started fixing an Android tapjacking vulnerability disclosed last month:
We have a fix implemented and it will be included in our next release, likely with the monthly Android 16 update tomorrow.
This vulnerability was disclosed to Google in October 2024 and Android still hasn't fixed it. Security researchers should report vulnerabilities to GrapheneOS in addition to Google. This now joins our many other GrapheneOS exclusive fixes for serious Android vulnerabilities.
We've decided to make another release today with our fix for the Android tapjacking vulnerability because we need to fix a DisplayPort alternate mode regression specific to 8th generation Pixels which doesn't impact 9th generation Pixels.
I'm confused--I thought google was halting AOSP or somehow making its dev impossible for android 16?
Did the graphene team find a way around the halting issue?
They reverse engineered as needed. I am on AOSP 16 from GOS
They changed the reference device to no longer be pixel devices. So basically they are publishing AOSP buy no linger the device tree for pixels. So basically the drivers for pixels are no longer open source and that makes it harder for the graphene devs to port.
If google stopped publishing AOSP, then the only android device on the market would be Pixels from then on. All other manufacturers rely on AOSP to build their OS afaik.
Just explaining how I understand it, could be wrong. Essentially, the theory is Google is scared that they'll be split up. To this end to try to protect themselves somewhat they are still publishing AOSP, but only as an online image. This makes it harder to find the commits needed to build ROMs, but it is still possible. Just more time consuming.
Again, just what I understand, could be wrong
This makes sense and provided some greatly needed motivating logic that I've been without for a few weeks now.
Many thanks to the GOS team and the piwakawakas lol
I think the source is released after android 16 is, plus they removed support for pixel devices from the source