Three1989

  1. Turn off block connection's without VPN.
  2. Toggle airplane mode.
  3. Connect to VPN
  4. Go back to settings and turn "block connection's without VPN" back on

      Fhggyy5767

      Even that doesn't get me to connect to MobileData w/VPN. I've been no-VPN since getting my 6a onto Graphene. WiFI+VPN works fine. The workaround did work, briefly (5min or so) right when A13 was released, but no longer.

      TMobile (40000000018.7) + Mullvad + 6a + GOS 1016build

      ... AlwaysOnVPN set to NO (so block-connections option is greyed-out/ isn't an option)

      ... sure would like to find that the upstream issue were trackable. Being on mobile data is > half of my use, and I don't take measures like running Graphene to walk around without a VPN.

          Three1989 Sorry to hear that. It drives me crazy having this problem. It sucks listening to Spotify or doing anything for that matter that needs data and it shuts off and has to be reset. I don't understand how Google could make a feature like this and then send it out broken. I'm blown away by this broken feature.

            10 days later

            with VPN Lockdown turned off entirely, I am getting No Mobile Data when VPN enabled. Mobile Data works fine when I turn VPN off.

            ... is anyone else ITT seeing the same?

            DesktopCloneLanguage Fhggyy5767 OpenSource-Ghost Three1989

            Please try the latest build (select Alpha/Beta Channel if required):

            • backport many upstream fixes for clat including a more complete set of fixes for the compatibility issue impacting all Android 13 operating systems between VPN lockdown and certain IPv6-only mobile data configurations along with fixing other issues with these setups

            Test and report any issues to our Alpha/Beta Room on Matrix: https://matrix.to/#/#testing:grapheneos.org

                    Wow! This is awesome! All problems gone, even after rebooting and trying different mobile data/wifi constellations.

                    10 days later

                    MetropleX

                    ... now that those of us affected have altered APN configurations to attempt workarounds for the last few months ... So, what "should" the Access Point Name settings be, as best practice?

                    ipv4-only/ipv6-only/ipv4-6, etc

                    Thanks.

                      3 months later

                      MetropleX since two weeks i am having this issue with carrier. I wanted to change the apn setting but then i saw it was already set to ipv4 and still has problems.