- Edited
other8026 Have you made any changes to settings in developer options?
No.
other8026 I have multiple profiles and VPNs set up in almost all of them. I have never had any issues with a VPN being disconnected while a profile is running in the background.
This is not exactly the situation I have described. What I'm experiencing consistently since I started using GrapheneOS years ago is the following:
I have two profiles: "O" (owner) and "S" (secondary). I have 3 apps installed in "O": Wireguard, WG Tunnel, and Mullvad (all of them use Wireguard in userspace). None of those are installed in "S".
What I expect to happen based on documented behaviour: I enable a VPN in "O", "S" is unaffected — it will access the network without going through the VPN.
What actually happens: I enabled a VPN in "O", "S" becomes offline — every single network connection gets "stuck" until it eventually times out. As long as I disconnect the VPN in "O", then "S" recovers immediately and regains access to the network.
To troubleshoot/diagnose this I have tried the same experiment in Wi-Fi, in mobile network, with and without enabling "Always-on VPN", tried rebooting the phone, and tried enabling the VPN before unlocking "S" or after "S" was already running. In every scenario "S" has inoperable networking as long as "O" has a VPN active.
However, this does not happen when the app is the Mullvad app. In that case "S" continues to have networking, without going through the VPN (as expected). Therefore I'm very intrigued as to (1) what are the other two doing differently to result in this difference of behaviour and (2) if there is an OS bug that these apps are triggering in the way they set up the VPN that is bringing down networking in other profiles — in this latter case, my understanding is that this should not be possible.