GrapheneOS version 2025030700 released

GrapheneOS

GrapheneOS version 2025030700 released:

https://grapheneos.org/releases#2025030700

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

jet_silver

You can have no idea how much I appreciate the simplification the dev team aims for.

K8y

For what it's worth I am still on 2025030300, and went to settings, system, system updates, and clicked on "check for updates" but nothing happened. I also restarted my phone and same thing when I tried again.

augmented

K8y

Its in the Alpha channel currently. Then will go to Beta.
If all is good in the test channels it will hit Stable.

K8y

augmented oh OK, I saw a release for a 2025030500 version too and thought I might be missing out.
Thanks! : )

K8y

augmented If all is good in the test channels it will hit Stable.

Are notices put out when it goes stable?

collector

K8y there are no notices, unless there's a major issue, in which case the team will put a post saying there was a problem. Another way releases can be delayed in alpha or beta is if the team feels like they need more people to test.

Otherwise, if everything goes well, the release will hit stable either the same day or 1 - 2 days after.

de0u

K8y Are notices put out when it goes stable?

https://grapheneos.org/releases#devices

bbanzai

The fingerprint reader on my Pixel 9 seems to have disappeared system wide. It no longer shows up as an option to unlock the phone or to use within apps known to use it (e.g. Bitwarden).

other8026

bbanzai I just posted in the thread you started here https://discuss.grapheneos.org/d/20617-fingerprint-unlock-gone-after-latest-system-update/

There are reports of the same thing happening with phones running the stock OS after updating to QPR2, so this is not caused by GrapheneOS.

nulandroid

Pixel 8 Pro running smoothly (including fingerprint unlock) after install of release #2025030700. My thanks to Devs.

Finik

I've encountered a not-so-pleasant feature - the media player in the notification bar disappears and appears only for the duration of the animation of the transition to the "tiles" of quick settings, after which it disappears again

x-pve

Downloaded Komodo (Pixel 9 pro XL) install and Google stock install as well (still experimenting). Google has probably newer radio:
radio-komodo-g5400c-241205-250210-b-13036024.img
VS GOS radio:
radio-komodo-g5400c-241205-250127-b-12971716.img
It's intended? Do I have to flash GOS as is or is better to flash Google's radio partition?

sjaramillo

Has anyone tried the new linux terminal app, I just downloaded this update and enabled the terminal app. The app appeared but after it downloaded the required data the app keeps crashing.

GrapheneOS

sjaramillo It's not supported on GrapheneOS yet. We have to develop support for it, which was not part of an initial port to Android 15 QPR2 and then resolving the regressions.

GrapheneOS

x-pve You're comparing to the wrong stock Pixel OS release. You used the one labelled BP1A.250305.020.A2, Mar 2025, EMEA + TW instead of BP1A.250305.020, Mar 2025.

It's intended? Do I have to flash GOS as is or is better to flash Google's radio partition?

GrapheneOS provides all of the firmware images as part of flashing the OS and provides the updates to them. Not doing that would be completely broken and insecure.

Bourbass

For Pixel 9 the finger print does not work anymore (desappeared from the option).

spring-onion

Bourbass See this thread: https://discuss.grapheneos.org/d/20636-workaround-for-very-rare-fingerprint-firmware-glitch-with-android-15-qpr2

azureberthe

adevtool (Pixel Tablet): remove unintentional deviation from standard memory pinning configuration

Can you explain this change? I've been having a lot of problems with my tablet unloading apps and browser tabs and was wondering if this could have possibly been the cause.

Bourbass

spring-onion Thanks! I saw this a few minutes after posting, but I was unable to edit my post to refer this post.
Here is my update since yesterday: I first waited a few hours for an "auto fix" as a few posts in the thread suggested, but it didn't happen. So, I had to reboot my Pixel 9 about 8 times in a row, and it fixed the issue.