GrapheneOS version 2025090800 released

GrapheneOS

GrapheneOS version 2025090800 released:

https://grapheneos.org/releases#2025090800

See the linked release notes for a summary of the improvements over the previous release.

Eirikr70

GrapheneOS For my understanding as a non native English speaker (I'm French, you know ... the French and the English, ...), in the present context, what does the word backport mean ?

GrapheneOS

Eirikr70 Taking the Android 16 QPR1 Pixel firmware releases and integrating them into Android 16. We already did it for the SoC and cellular radio firmware. We also already did it for all of the kernel drivers. We still need to finish doing it for the most important driver libraries/services and then we can do it for the Android 16 QPR1 device-related code as a whole.

It would be much better if Android 16 QPR1 was pushed to the Android Open Source Project (AOSP) as it's supposed to be but this is what we're doing before that happens. We do have an OEM partner with partner access they can share with us but that does not enable us to publish the source code for major releases earlier than Google. It would enable us to port before code is pushed to AOSP and we could publish public releases with special release channels based on the new OS releases prior to it reaching AOSP within the rules for it. We cannot publish the sources before they do unless they allow OEMs to start doing that on the release publication date.

Eirikr70

GrapheneOS Thanks for that very clear answer. Sorry that you have to dedicate to such tasksinstead of developing new features for GrapheneOS.

xxx

Have sideloaded. All fine so far [P6 no gXXgle].

GrapheneOS would be much better if Android 16 QPR1

Perhaps it would be better to fork away from AOSP? I really don't know.

graphuser

GrapheneOS thanks for all the work done. Hats off for a wonderful OS. A small question on this and what you mentioned in the social media posts on this topic.

Am I right to understand that the "binaries" of the releases (QRP or security patches) can be released before Google pushes to AOSP but not the source and since GOS normal release channel publishes the code, that is why it cannot be updated before Google pushes to AOSP?

If that is right, than could OEM, at least in theory, release security patches before Google if they don't release the code?

raccoondad

GrapheneOS It would be much better if Android 16 QPR1 was pushed to the Android Open Source Project (AOSP) as it's supposed to be but this is what we're doing before that happens

Do we know when that will be?

n3t_admin

xxx Perhaps it would be better to fork away from AOSP?

That is not even remotely feasible. Aside from the monetary and personnel aspects, it would also introduce incompatibility between regular Android and a potential fork. This is pretty much out of the question.

xxx

graphuser theory, release security patches before Google if they don't release the code?

That's how I understood the posts. I think Samsung has done such things a couple of times.

GrapheneOS

graphuser

If that is right, than could OEM, at least in theory, release security patches before Google if they don't release the code?

Yes, that's the new approach. The embargo does not include binary patches. We plan to take full advantage of it with new release channels providing patches 3-4 months early. It will take some time before we can deal with the current mess and begin doing that.

GrapheneOS

xxx It was not previously allowed for Samsung to be doing that, they were breaking the embargo against the rules. However, it's now permitted to release binary-only patches early such as releasing the December 2025 patches right now.

franc

Thanks for the continued hard work team.
Working pretty smooth on Pixel 6a

Hopefully Google releases the full AOSP so you can continue with what's left.

Pocketstar

2025090800 is working fine so far on my P6a P7, Pixel Tablet and P9PXL. (I did not test cellular connections nor Play Services)
Awesome! Thank you!

x-pve

Pocketstar On tablet, battery is charged to 90 % instead of 80 %; anyone else has this experience?

twitheatrophonic

GrapheneOS who is the OEM partner?

xxx

twitheatrophonic who is the OEM partner?

Time will tell.

Aru

I have an issue with my Mi Band 3 bracelet since Android 16. I suppose it's from upstream. It won't reconnect automatically if I go to far from my phone. Are there logs I can provide to help solve this issue? It's not related to this release but A16 ones. Since there is a new BT firmware update with this GrapheneOS, can I expect a fix?

de0u

Aru If the issue is not related to this release please use a different thread.

lunchtime8317

I just got the update a few hours ago. Since them I have been unable to send any RCS messages. I can still receive them though.

EndoPlant

lunchtime8317 Same situation here

blackcat8

lunchtime8317 I'm also having this problem on my Pixel 8a.

cvsickle

lunchtime8317 I also just noticed this behavior. On 7a.

Minami-o

Hi,
I have one physical SIM with Fonus and one eSIM with French carrier Free mobile and, after applying the latest version (via OTA) and rebooting, my eSIM was disabled and I had no way to enable it (it would silently fail).
I tried to navigate system logs and noticed something about Google Play not being available (I have it permanently disabled, along with GP Services), so I tried to enable GP and the GP services, but to no avail. I then opened my private space, which has GP and services enabled, with an active google account attached, but this didn't work any better.
Physical SIM still worked flawlessly, btw.
I eventually rebooted, short of any other solutions, and the problem was gone.
Also, don't know if related, but I didn't see the usual app optimization routine notification after the initial reboot.
As it's the first time in a year or so running GOS that I'm experiencing such behavior, I thought it might be useful to mention it here...
Also, thanks to the team for the great work!

Freedomain

Minami-o

This same behavior happened to me on an 8a.
Noticed esim somehow got switched off, switched it on, rebooted, now my phone does not want to connect to mobile network in "LTE only" mode . (shows no connection and exclamation mark after a few seconds of it showing bars in LTE) but will work in 5G. Also the choice to disable esim is back on the SIM unlock screen where it was gone before.