GrapheneOS version 2026062300 released

Developer-Dude

Only complaint with A17 is the stupid separate toggle for WiFi and data. Its was way more organized before in one toggle and I liked it way better. Not complaining to GrapheneOS though, since this is an AOSP (and likely stock as well) thing. Thanks @GrapheneOS for getting us to another Android version smoothly!

r134a

Many thanks to the team and all the people in the testing pipeline! 🥳

ClickClickDrone

Developer-Dude
You do realise that you can remove the cellular quick tile and toggle the cellular network from the Wi-Fi toggle instead, right?

Cyanide77

Updated fine here pixel 7 pro.. Only thing I've just realised my daily backup hasn't ran since the 7th June!
Not sure if that was the date of the last GOS update...is set to trigger when charging but hasn't in nearly 3 weeks ..
Will see if it starts again overnight.

Developer-Dude

ClickClickDrone oh, I CAN! Well thats good! I never clicked it at all today since I had no need to, just saw the two separate ones. Well thats perfect!

GazelleInitial

ClickClickDrone Yeah I just ignore the other one and continue as before.

Byku

Stable version rolled into Pixel 10s. So far only good impressions. The driver/Vanadium crash is no more. Wifi and mobile data have separate tiles again. I was afraid of new bugs being introduced with how things have been going with Google lately but so far so good. Congratulations to the GrapheneOS team!

0xC0DED0D0

0xC0DED0D0 Up and running. Looking good, so far! 👍

andrej567

GrapheneOS
It would be good if there would be a button "set proper permissions for google services" if there isnt already

MrLinux

P9a updated everything is working good so far no issues.

hnn8

Pixel10pro256GB works

de0u

andrej567 It would be good if there would be a button "set proper permissions for google services" if there isnt already

This forum thread is for users to report issues (or successes) specific to the 2026062300 release. A suggestion for a possible feature should be made in a fresh thread.

SouthernPolish99

Thanks! I didn't even have time to realize RCS was broken yet. Back working per the texts that just came through.
Working great on pixel 9 Google Fi

bake

RCS running and functional, but I am having issues with it disconnecting in text conversations with iPhone users. I will send a RCS message then the reply from an iPhone will come back as SMS and so on. Anyone else having this issue?

noodle_panda

Hi. Just got the 2026062301 update from the stable channel. Kudos for the quick port!

One thing I noticed: I have two secondary user profiles with "Allow running in background" enabled for them. Both have the Mullvad VPN app running with "App battery usage" set to Unrestricted, "Always-on VPN" and "Block connections without VPN" enabled. Whenever I switch the foreground profile, I see that Mullvad VPN has been disconnected, it is briefly in the state "Blocking internet (device offline)" then suddenly it changes state to "Connecting..." and then it connects.

That is, Mullvad VPN is disconnected for the profile that is running in the background. When I switch to that profile to bring it to the foreground, then Mullvad VPN starts to connect. This effectively means at any given time I only have internet access in just the single profile that is in the foreground. This was not the case before Android 17.

As I have instant messengers running in both of these profiles that might receive texts at any given time, it means texts are going to get missed :/

Is this a bug in the Mullvad app (incompatibility with Android 17), or a regression in AOSP? Or am I simply misunderstanding something?

Johnnyloans

noodle_panda

This probably explains your observations -- WiFi disconnecting.

https://discuss.grapheneos.org/d/36689-grapheneos-version-2026062200-released/62

noodle_panda

Johnnyloans I see. Thanks for the link.

Is there an adb command or developer setting I can tweak so that wi-fi works in all running profiles? I don't mind having to configure the SSID once for each profile. Otherwise this change seriously limits the utility of having multiple profiles.

Or is the workaround to get a non-kyc eSIM and have the background profiles use mobile data? Is that how it is envisioned to be used now? Foreground profile using wi-fi and background profiles using mobile data? Really weird... Ideally I would want to keep the phone in airplane mode though as usual :)

EDIT: oh and I see in the DHCP leases of my router that every time I switch profiles a new lease gets added. That's fun. While I was trying to figure out what's going on, just switching profiles back and forth this past hour, apparently I already added 50 DHCP leases just with this phone, lol.

GrapheneOS

noodle_panda

Is there an adb command or developer setting I can tweak so that wi-fi works in all running profiles? I don't mind having to configure the SSID once for each profile. Otherwise this change seriously limits the utility of having multiple profiles.

Wi-Fi should still work fine in secondary users as long as you don't disable sharing the networks with other users, but it will reconnect when you switch users since it clears the state to make sure the separation between users is secure. Users can now define their own private networks not shared with other users, but existing networks are all shared. Look at your saved Wi-Fi networks and you'll see toggles for sharing it with other users and allowing other users to edit it. The disconnect when switching users is just because they have per-user state now and need to make sure they switch over to it. It could probably skip that if it detects the configuration is 100% the same between the users but they didn't implement that.

oh and I see in the DHCP leases of my router that every time I switch profiles a new lease gets added. That's fun. While I was trying to figure out what's going on, just switching profiles back and forth this past hour, apparently I already added 50 DHCP leases just with this phone, lol.

That's because GrapheneOS uses per-connection Wi-Fi MAC randomization and DHCP state by default. You can set it to per-network randomization instead to have it work the same way as the stock OS. If your router properly flushes out the least recently used DHCP table entries then it shouldn't be an issue and per-connection MAC randomization is nice. It's mainly meant for connecting to networks which aren't your own though and you can turn it off for your home network with little downside.

noodle_panda

GrapheneOS

Wi-Fi should still work fine in secondary users as long as you don't disable sharing the networks with other users, but it will reconnect when you switch users since it clears the state to make sure the separation between users is secure.

Ah I see. Thanks. So in that case my only remaining remark is re answering e.g. Signal calls from another profile (I just tested this with an old phone from a drawer and indeed it works exactly like you describe and as I would expect from that):

a call comes in on the background profile, the phone starts vibrating and shows the GrapheneOS notification "Notification from Signal for ProfileXX"
I switch to that profile and accept the call
now the internet is disconnected
apparently Signal has a really long timeout so the call will not get disconnected but no packets are flowing for cca 10 seconds
internet is reestablished and now the call works

Worst case, I will just have to call back people most of the time. I can live with that.

That's because GrapheneOS uses per-connection Wi-Fi MAC randomization and DHCP state by default.

Yes, I am aware. I just found it funny that now even switching profiles triggers a reconnect.

Thanks for the answers and time :)

GrapheneOS

noodle_panda We'd like to avoid Wi-Fi having to reconnect by default but it has to happen in the general case to make the features work properly. It's likely tricky to implement skipping it when the configuration is the same which is why they didn't do it.

If you're not already using a Private Space, consider using one as a nested user to replace one of your secondary users. Private Spaces are nearly the same as a secondary user but nested within another user from a user interface perspective with support for explicitly sharing files between them. The clipboard is shared by default but GrapheneOS adds the option to make it fully separate or only shared in 1 direction. Unfortunately only 1 Private Space can be created per user. We added creating them in secondary users so you can have multiple but not within the same user. A work profile can be used as a 2nd nested profile in Owner but it's not as cleanly separate as Private Space including not having the fully separate encryption support.

« Previous Page Next Page »