GrapheneOS version 2025052000 released

GrapheneOS

GrapheneOS version 2025052000 released:

https://grapheneos.org/releases#2025052000

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

cirnolovetech

GrapheneOS
I'm on Stable branch atm so idk if it fixed or not but i haven't see any update logs in the past updates about the issue where Private space forcing you to unlock with fingerprint even with the option "Use for screen unlock" disabled. Will that be patch in the upcoming update or i just need to not sign a fingerprint on private space?

ScarletKing07

GrapheneOS Unlike WiFi, NFC doesn't turn off automatically if you are in a secondary user, actually even if you switch to the main owner profile it doesn't turn off if NFC was started on a secondary user.

Is this the intended behaviour? I am on 2025052000

364dev

GrapheneOS I can't find the "Pixel 9a" tag on this released version (or any other version). Am I assuming correctly that the 9a is not yet (I don't know how to say it)... ready for its tag to be included in a release ?

natoal

Private Space: make sure nested profiles in secondary users have their storage put at rest when the parent profile's session is ended

By nested profiles did you mean the Private Space in a secondary user profile?

GrapheneOS

natoal Yes, that's what it means.

looped_around

GrapheneOS
Silly question, but it's still only 1 private space per profile?
This is still an amazing add!

fid02

cirnolovetech I'm on Stable branch atm so idk if it fixed or not but i haven't see any update logs in the past updates about the issue where Private space forcing you to unlock with fingerprint even with the option "Use for screen unlock" disabled. Will that be patch in the upcoming update or i just need to not sign a fingerprint on private space?

I'm not clear on which situation specifically you are describing.

If the private space is locked and you have set up a fingerprint for the private space, then naturally it will let you unlock the private space with the fingerprint (except for when the private space is in a Before First Unlock state). That is an Android design decision and not a bug.

But perhaps you are talking about the following situation?

private space is set up with a fingerprint
private space's option "Use device screen unlock" is disabled
when the screen is locked and then unlocked, the user has to provide their fingerprint or PIN in order to open an app in the private space – even when the private space is already unlocked

That specific behaviour on GrapheneOS is identical to the behaviour on stock PixelOS, and I think we can safely assume that that is also an Android design decision. If you want to avoid that, currently you will have to enable the setting "Use device screen unlock".

iyanmv

Keyboard issue when having multiple layouts enabled is solved in this release, thanks! I think it still looks a bit weird to have the huge emoji key in that position, but I guess I will get used to. Perhaps the colorful background circle can be removed in a future release?

semi

iyanmv I do not like where the emoji button is now, and I can't see myself getting used to it. Who thought this was a good idea? Is there any way to go back to the other keyboard or are we stuck with this?

cirnolovetech

fid02 when the screen is locked and then unlocked, the user has to provide their fingerprint or PIN in order to open an app in the private space – even when the private space is already unlocked

This is not what i wanted to said. Sorry for bad English or poor choice of words but what i wanted to say is:

I don't want to use fingerprint to unlock private space at all. So i disabling the option "Use for screen unlocking" expected it to stop showing the fingerprint unlocking prompt like how work for screen unlocking but it didn't and the prompt for fingerprint unlock still show up when i want to unlock my private space.
I just want to use fingerprint unlock for some apps and nothing else.

So yeah i expected the option "Use for screen unlocking" to work the same way it work for normal screen unlocking. I think it is a bug or a misleading option that Android forgot to remove? Either way i don't know, but if that what it is ill have to completely disable fingerprint unlocking for now.

fid02

cirnolovetech So i disabling the option "Use for screen unlocking"

cirnolovetech I just want to use fingerprint unlock for some apps and nothing else.

Ah, I see. That feature has not been added to private space. The toggle currently only applies to the parent profile (Owner, secondary users). (Not sure if it applies to Work profiles).

cirnolovetech

cirnolovetech To anyone reading this. The problem is no longer there and you can now completely stop fingerprint being used for unlocking private space in the 2025052000 update with "Use for screen unlocking" disabled.

xxx

Thanks! Keyboard is back to normal.

other8026

ScarletKing07 This is a known issue and it's being worked on.

GrapheneOS

ScarletKing07 other8026 NFC auto-off for secondary users has been implemented for the next release after this one. We likely won't be avoiding moving this release to Stable due to this because it's a new feature and it does work properly in Owner already. It's not really a bug fix but rather extending it to support secondary users, although it was intended to work for them initially.

fid02

fid02 That feature has not been added to private space. The toggle currently only applies to the parent profile (Owner, secondary users). (Not sure if it applies to Work profiles).

Oh, I see that the toggle actually is present in the private space settings, so I was wrong. Although disabling the feature still mandates fingerprint authentication for me after locking the screen and then opening an app in the private space. Haven't tested on stock PixelOS yet.

W1zardK1ng

Could still see the dedicated language switch key in pixel tablet but in 6a its replaced with the emoji key.

matchboxbananasynergy

W1zardK1ng it's expected, we only removed the language switch key on phone layouts.

elliasdev

matchboxbananasynergy
So now the only way to change language is to press and hold space?
Very unconvenient, as for me. I use three languages, sometimes in the same conversations, it feels very awkward tbh. I would rather hold Enter for emoji than space bar for languages.
But, if majority is ok with it, well...

My first thought was it's a bug lol 😂😂😂
Seriously speaking: any way to customize it?

Fnmdnip

Tap to wake quit working on pixel 8 after update

GrapheneOS

Fnmdnip Tap to wake definitely still works on the Pixel 8.

fid02

Fnmdnip Tap to wake quit working on pixel 8 after update

Works on my Pixel 8.

Murcielago

Thanks for the great update, especially the extension of the Private Space features!

Short question:

Setup:
Parent user: Screen lock: Password
Private Space: Screen Lock: PIN

Is there a way to enable PIN scramble for Private Space in this setup? Not a feature request, just can't find it in the settings.

Pixelpioneer88

cirnolovetech Where is this option?

Shrunk836

Hey everyone,

Just wanted to report a weird bug I've been consistently experiencing with the Assistant (the Google one with Gemini enabled) on my Pixel 9 Pro.

Every time I reboot the phone, the swipe-from-bottom-edge gesture to activate the Assistant stops working properly. The phone vibrates, so it definitely recognizes the gesture, but the Assistant UI doesn't actually pop up. Nothing happens on screen.

The only way I've found to fix it temporarily is to go into Assistant settings, switch to a different default assistant (like "None" or any other one I might have), and then immediately switch back to the Google Assistant (Gemini). After doing that, the gesture works perfectly fine again, and the Assistant launches as expected.

However, the moment I restart the phone, the problem comes right back, and I have to do the assistant-switching dance all over again.

It's a bit annoying to have to do this after every reboot. Has anyone else run into this or have any ideas what might be causing it?

manhunt_shaft

I wish the toggles to "turn off <module> automatically" were in the main settings screen of Wifi, Bluetooth and NFC. It isn't intuitive to have to navigate to the Exploit protection screen, when the "Turn Bluetooth on again tomorrow" is right below the on/off switch.

adruld70

manhunt_shaft explanation as to why they are not placed on the individual settings or somewhere else:
https://github.com/GrapheneOS/os-issue-tracker/issues/5455#issuecomment-2892554489

chinook

manhunt_shaft eh, for me even "Turn BT on again tomorrow" doesn't even consistently works, so count your blessings :)

(I'm slowly gathering the breadcrumbs to raise an issue because it seems I'm the only one affected)