Android 16 QPR3 Rolling out to (stock) Pixel devices

tinymonster

https://9to5google.com/2026/03/03/android-16-march-update-pixel/

If I remember correctly, GrapheneOS won't get Android 16 QPR3 due to the recent AOSP code release changes, right?

userofgos

tinymonster If I remember correctly, GrapheneOS won't get Android 16 QPR3 due to the recent AOSP code release changes, right?

Where did you hear this? Please provide a source. AFAIK this is incorrect. See here: https://discuss.grapheneos.org/d/28869-grapheneos-version-2025121000-released/9

Until Android 16 QPR3, our workload for security preview patches will be lower than it was for porting them to QPR1 but then QPR3 will be a pain for that again.

This is the only mention of Android 16 QPR3 I've seen mentioned by the GrapheneOS project, which implies that we will get QPR3

Also see here about device trees: https://discuss.grapheneos.org/d/31185-question-regarding-the-pixel-series-10-and-going-forward/7

wizoatk

userofgos which implies that we will get QPR3

I believe the context there was security patches associated with QPR3. I don't believe there was an AOSP Android 15 QPR3 source release. I wouldn't be surprised if there wasn't an AOSP Android 16 QPR3 source release either this year.

userofgos

wizoatk believe the context there was security patches associated with QPR3.

Correct, hence why I was asking for a source since this was the only mention of 16 QPR3 I found on the forum.

wizoatk I don't believe there was an AOSP Android 15 QPR3 source release.

I believe you are correct here as well.

wizoatk I wouldn't be surprised if there wasn't an AOSP Android 16 QPR3 source release either this year.

Based on the above, I would agree. My issue was more with the reason why we would/wouldn't get QPR3. OP said due to the AOSP source code changes, but I don't believe that is the reason.

phospmph

userofgos Correct, hence why I was asking for a source since this was the only mention of 16 QPR3 I found on the forum.

Check https://source.android.com/docs

Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4.

Android 16 QPR3 is a Q1 2026 release. Google may not publish source code for this.

tinymonster

GrapheneOS has confirmed that unless Google decides to release the Android 16 QPR3 source code, the Android 17 release will be the next release used by GOS, skipping QPR3 entirely.

https://grapheneos.social/@GrapheneOS/116183048843338718

harp

tinymonster GrapheneOS has confirmed that unless Google decides to release the Android 16 QPR3 source code, the Android 17 release will be the next release used by GOS, skipping QPR3 entirely.

That's completely the opposite and misinterpretation of the linked statement:

Only if Google decides to release it for use beyond the stock Pixel OS. Otherwise, Android 17 will be the next release used by GrapheneOS and then Android 17 QPR2. Only the yearly and QPR2 releases are currently being made available for other OEMs to use and for AOSP.

https://grapheneos.social/@GrapheneOS/116183048843338718

That means, if Google would push QPR3 to AOSP (which means releasing the source code) - or make it available for OEMs - GOS will get QPR3 too. But as things stand now that won't happen.

Johnnyloans

harp

I read both quotes as the same.

¯\(ツ)/¯

harp "GrapheneOS has confirmed that unless Google decides"

Open source or 'source available to OEMs' both match tiny monster's quote

"release the Android 16 QPR3 source code"

harp

Johnnyloans I read both quotes as the same essentially.

You're right, my bad! I was apparently briefly lost in translation. Also sorry to @tinymonster. ;)

tinymonster

harp Also sorry to @tinymonster. ;)

No worries!

Probably9857

OTOH...

...we've been focused on hiring multiple additional full time developers and porting to the new Android 16 QPR3 Pixel code

https://grapheneos.social/@GrapheneOS/116184520815309996

👀

Byku

Hmm. My Pixel 10 device is on stable version. It's showing Android version 2026030201. Despite that I seem to have firmware fixes working already. The PowerVR gpu stopped crashing. The wireless charger started to work.