GrapheneOS version 2025073000 released

Drue3

Is there a reason my phone can't find the release while checking for updates? It just keeps saying it's up to date but still shows 71900 in settings even after restart. My update is set to the "stable" channel.

de0u

Drue3 071900 is the stable release at present, see the table for your device, e.g., https://grapheneos.org/releases#lynx

ChrisRoosh

Drue3 Also still on the same version on my 8 Pro. I have not yet understood when (or if at all) an announced new version will be pushed onto the devices.

Drue3

de0u Oh so that's why. So when a release is announced here it doesn't mean it's been released as stable. There was my wrong thinking. Thank you.

de0u

ChrisRoosh The status link for your device: https://grapheneos.org/releases#husky

Releases can't be staged on a schedule, because the point of staging is testing, and testing can uncover problems. Though this is rare, some releases are yanked and never reach stable.

ChrisRoosh

Drue3 Ah, got it. Made the same mistake.

Stephan-P

And every time again we are ending up in this same series with (new) users asking why their device hasn't yet updated to the newly announced release.

Two cents' suggestion:
It would make things so much clearer if the release announcements would include an extra line or two explaining about the release staging system, as well as include a link to https://grapheneos.org/releases where each can quickly check the release staging status for their particular device(s).

Psyonico

Stephan-P It would make things so much clearer if the release announcements would include an extra line or two explaining about the release staging system, as well as include a link to https://grapheneos.org/releases where each can quickly check the release staging status for their particular device(s)

Even just "X version has been released to the Alpha staging channel" or something like that.

nandohyphen1

Just got the update on my 6a to 2025073000. Everything's working great! Appreciate everything the GrapheneOS team does to keep us all updated and running GOS! Keep it up!! ;)

HecticHector

Pixel 8 Pro 🤌 No issues

cdflasdkesalkjfkdfkjsdajfd

Just updated (P7Pro) and rebooted.
It's normal that device showing the boot animation for 1:30-2 mins?
Finally boot sequence has ended, but never ocurrered this.

supersonic

cdflasdkesalkjfkdfkjsdajfd I had this experience as well, maybe about 3 minutes.

MartiMarto

Hello! Just installed it on my Pixel 6 Pro. I had the same weird behavior of the boot animation stuck for about 3 minutes (instead of the usual 10 seconds).

But the real problem is it doesn't charge anymore. It could just be a coincidence, but it was charging alright before the update and as soon as it was rebooted, charging stopped working. As soon as app optimization is finished, I'm going to shut it down, boot it back up, try to charge it and look at logs. I'll keep you updated. Please let me know if you know for sure that it isn't linked to the upgrade and I should just create a dedicated post on the forum.

other8026

MartiMarto Please let me know if you know for sure that it isn't linked to the upgrade and I should just create a dedicated post on the forum.

It doesn't sound related. We'd be getting a lot of reports if it was.

I'd try turning the phone completely off, leave it for several minutes, then power it on, and check again to see if it still won't charge.

GrapheneOS

MartiMarto

Hello! Just installed it on my Pixel 6 Pro. I had the same weird behavior of the boot animation stuck for about 3 minutes (instead of the usual 10 seconds).

That's expected unless you were already on 2025072700 or later which haven't gone to the Stable channel until 2025073000. It's covered in the 2025072700 release notes:

temporarily disable asynchronous pre-reboot OS update app optimization (dexopt) added in Android 16 to avoid the Finalizing step completing before apps are recompiled which can then result in it causing a very long initial boot of the new OS version if the user reboots before the background app optimization completes (this will not apply to updating to this release but rather only updating to future releases from this one and onwards)

Byku

GrapheneOS After the update (stable channel) apps can no longer use wireless debugging. It's like it is not detected at all. Pairing again won't work either. The usual schtick of rebooting or clearing app cache also doesn't work. It worked ok just before the update. I can still manually connect to wireless debugging via termux-adb command so it is there, just not accessible to apps for some reason.

Byku

Byku To clarify, the problem is with detecting the wireless debugging service once it's been paired. It is still possible to connect by manually typing the IP and to pair apps.

GrapheneOS

Byku Byku We didn't receive any reports of issues during the lengthy Alpha and Beta testing for the recent changes. Are you using a VPN with VPN lockdown enabled? Did you try in a profile without it?

nashgraph

Yeah it took a long time. I was a bit worried at some point.

Byku

GrapheneOS
I got same results with lockdown mode disabled.
When I disabled VPN completely I've managed to get one app to detect wireless debugging (Shizuku). The other app I've tried is Automate and it still failed to detect wireless ADB service throwing JavaScript internal error. So you're right that this behavior seems to be related to VPN. Maybe the new leak protections are interfering with discovering wireless debugging? I should mention that before the update all the apps could detect wireless debugging even when VPN with lockdown mode was running.

GrapheneOS

Byku Try connecting to it from another profile without a VPN.