GrapheneOS version 2025060200 released

GrapheneOS

GrapheneOS version 2025060200 released:

https://grapheneos.org/releases#2025060200

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

iyanmv

I noticed a regression in the fingerprint reader to unlock the screen. I have a Pixel 8 and I have the two-factor fingerprint unlock enabled.

After updating to this release, sometimes the fingerprint reader does not work. The light turns on when placing the finger, but there is no haptic feedback and it does nothing. Turning off the screen and on again, solves the issue. The reader works and I'm asked the pin.

Emerald

iyanmv
I noticed the same. The biometric unlock was working very reliably for me until the recent update on a Pixel 6a.

iyanmv

iyanmv I have not observed this issue for two days now. Weird. I guess it was a temporary glitch after the update. I did not reboot the phone or changed anything.

JustBeginnez

No problem with Pixel 7a & 8a.

upstage4186

Pixel 8 here and my fingerprint reader is working fine, I'm not using two factor though.

nashgraph

Using two factor on Pixel 8. Works as usual. Did not notice anything off so far.

Murcielago

Pixel 9 Pro no problem with fingerprint so far.

Wadder

Since the update, my device is only using LTE for my network and in some cases doesn't have a signal at all.

I should note that I have data on the sim so no issue on that, and I've checked to see if the network has gone down, which it hasn't.

Lilac6044

Wadder My first suggestion would be going to settings, system, reset options, reset mobile network settings

Wadder

Lilac6044 thanks that did the trick. Seems the obvious thing silly me. Thanks again

hubblehead

This update came through for me and since then my physical sim card has not been recognizable on my pixel 9 pro XL. I have tried resetting the mobile network settings and re-seating the sim card a few times. I have also tried the sim card on another phone and it works fine. The Sims menu in network options only allows me to tap "add a new sim" with no result, so i assume the sim card detection is totally failing and mobile options aren't related as i cannot set them, though i reset them and nothing changed.

I'm not sure what other trouble shooting steps to follow, or how to attempt rolling back an update to double check the cause is the update for that matter... have not installed any new apps in the last couple weeks either, and the same issue is present on every profile. So i'm stuck on "emergency calls only" at the moment.

Michiel

hubblehead It is unlikely that this is caused by the update. Pixels appear to be a bit picky about physical sim cards. I once had to replace an old sim card because often calls did not come through. Did you try another sim card in your Pixel? I guess you already tried rebooting your phone a few times.
Rolling back to a previous version is not possible in GOS. Thus you'll have to do a factory reset or install PixelOS if you want to explore this further.

hubblehead

Michiel

I just fixed it in a very odd way that does suggest it was update related, though i am not sure, someone else will have to tell me. I saw that the "eSIM support" option was toggled off below the nonfunctional Add sim button. I tried toggling esim to the on position, and after the phone restarted with eSIM support on, it worked, my mobile connection was back using the physical sim network and i started recieving texts immediately.

This is after restarting the phone about 5 times over the day with no joy, so it was indeed specifically toggling the esim support that fixed the physical sim, not just restart. I don't remember whether esim support was previously on or off (it was likely off) but perhaps the update either toggled it off, or something changed with it needing to be on for the physical sim to work.

TrustExecutor

Michiel
This is interesting. I have this issue sometimes on my P8 Pro with a rather old physical SIM card. My primary eSIM never has this issue. Did it happen for you sporadically or did it die completely?

Michiel

TrustExecutor it happened once in a while, not always.

natoal

I've been wondering for a while now, it might be a stupid question but since the device list does not include the 9a (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, emulator, generic, other targets), does that mean that the Pixel 9a will be running an old version for a while?

I checked https://grapheneos.org/releases#devices and it says that Pixels runs 2025060600 though. I thought that it was YY/MM/DD but there are two more numbers at the end

Dumdum

natoal does that mean that the Pixel 9a will be running an old version for a while?

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

thought that it was YY/MM/DD but there are two more numbers at the end

The two numbers are specifically for when a change/hotfix gets made on the same day. So if 2025060600 had an issue and its fixed, there would be a version 2025060601 that gets released afterwards. And if it happened again, version 2025060602 would release etc.