GrapheneOS version 2025070800 released

Eirikr70

Don't want to ruin the bug party, but everything runs smoothly for me (P6a).

Gsuajsj

AccXess i am also having this same issue. Have played with all the notification settings but not been able to get it working. Has anyone found a fix for this?

Bimmy

Multiple Pixel 8s running fine. Thank you very much for the milestone of Android 16 at GOS stable channel.

Naturally, tens of thousands of new "testers" in production and their diverse configurations will inevitably discover issues not covered by developer tests, alpha and beta. I'm confident, GOS will become better than ever.

I'm curious what further releases of Android 16 and beyond will bring.

DeletedUser370

indigomadelin Could you please take a look at this reply here? https://discuss.grapheneos.org/d/23700-no-internet-on-secondary-profile-when-main-uses-nextdns-private-dns/2

othemad

P9P Fold here, everything working fine. Great job on addressing the Android 16 update issue with Google! Your skills and capabilities are truly impressive, and this just proves it.

huberto

User Profile changes crash everytime since the latest update.
Formerly a feasable workaround was to lock the profile before switching resp. termination a session, but this doesn't work anymore, leaving a unusable device for me. It crashes everytime I return to #0.
Unfortunately I didn't discover this severe regression during my initial tests and I messed up my spare phone too.
There's hunderds of reports about the keygard timeout crash - hopefully devs are aware and can finally get the fixes back in as GOS had at late Android 14 days. The crashes returned with Android 15 but I could live with the lock-workaround. This workaround isn't available with Android 16 anymore.

Bimmy

huberto

If it's crashing so badly, that it becomes unusable, I wonder if booting into safe mode (s. https://support.google.com/pixelphone/answer/2852139 ) allowed to find a temporary solution/workaround. If it enables to single out problematic apps, it might at least restore a somewhat working device -- though not with apps apparently in conflict with A16 -- instead of a (quasi-)brick.

Would that be an option for you? Have you maybe tried already?

stewartyara29

GrapheneOS Hello admin, I updated from gos a15 to a16 via OTA, and now I want to clean flash. Is there any difference between these two methods? 1: Factory restore directly on the current gos a16 2: Switch back to stock firmware and flash gos a16 again

de0u

stewartyara29 I updated from gos a15 to a16 via OTA, and now I want to clean flash.

In order to achieve what?

Both the OTA process and the installation process result in the system partition having the same contents. It is possible to cryptographically wipe all user data and settings via "factory reset".

grayway2

It is now available on stable branch ? I would personally suggest to remove it from stable as there is still a lot of things that needs to be corrected.

DeletedUser370

grayway2 I would personally suggest to remove it from stable as there is still a lot of things that needs to be corrected.

Any major issues you were concerned about?

grayway2

DeletedUser370 yes , such as the lockscreen and I see a lot of complaints from others. It's probably related to AOSP but the fact is that Android 16 is not yet ready despite being distributed by Google on stockOS

semi

semi The wallpaper dim is not happening every time, but I've noticed that it is in fact happening on secondary profiles as well.

It happened on a secondary profile that I never set up sleep mode on. The only way I could undim the wallpaper on that profile was to set up sleep mode with the wallpaper dim on, then shut the sleep mode off.

Edited to add: Pixel 6a

Dav3

p7a and tablet on stable, Since Wednesday night (updated to a16) both are running fine without any issues noticed. Pixel tablet has a second profile and switches fine without crashing.

stewartyara29

de0u Ok, I thought it would be different, thought a clean restart would be better, but there is no difference between my factory reset and reinstall?

de0u

stewartyara29 Better in what way?

Lilac6044

stewartyara29 I am not a mod of the forum but I would suggest sticking to only one thread per issue, and I do not believe this question really pertains to the release this thread concerns. So I would continue this discussion on your dedicated thread:

https://discuss.grapheneos.org/d/23929-a15-to-a16-clean-flash-issue

Bimmy

SirMixAlot

I wonder whether this is a side-effect of the temporary removal of NFC auto-turn-off (s. https://grapheneos.org/releases#2025070800 > last bullet point? (Pure speculation.)

Have you tried disabling the feature, reboot, re-enabling it, maybe with slightly different time to increase chance of fresh configuration in that area?

(Forgive me, as I can only offer laymen error analysis atm.)

other8026

Bimmy I wonder whether this is a side-effect of the temporary removal of NFC auto-turn-off

Unlikely. Looking at the change to remove NFC auto-off feature, other auto-off features shouldn't be affected.

Bimmy Have you tried disabling the feature, reboot, re-enabling it, maybe with slightly different time to increase chance of fresh configuration in that area?

Agree that this is worth trying to see if it helps.

Also, looking at how WiFi auto-off works, it will also not automatically turn off if the wifi state is connecting, authenticating, or obtaining an IP address, and it looks like the timer will automatically reset if the state changes. So if the device tries to connect over and over again for any reason, auto-off might just not get a chance to run.

Rasta9

Been running A16 on my P7Pro for a little bit now and I've started having cellular network issues. My network connection just intermittently drops out for no apparent reason and turning the esim off and back on or rebooting are the only ways I've found to fix it.

« Previous Page Next Page »