After update windscribe won't connect. Cam anyone try and confirm? Pixel 6a

    twitheatrophonic After update windscribe won't connect. Cam anyone try and confirm?

    Does it happen on both WiFi and mobile data, or only one of them?

      I pushed the update through on my P6 and have lost all cell service. Wifi and Bluetooth work great.

      I have tried:

      1. switching airplane mode on and off
      2. turning phone on and off
      3. reset network settings
      4. pulled sim card and tried in another phone - works fine

      Any other thoughts on how to remedy this?

        It seems that all works with my pixel 8a. No errors. VPN (Proton) works perfect...

        winniethebish I pushed the update through on my P6 and have lost all cell service.

        Works for me on Pixel 6.

          winniethebish just because the release is still in alpha status. It need to be tested before it will push to stable

            Regarding the following statement in the change log, I have a question:

            "extend standard Android eBPF filter to prevent apps sending multicast packets outside of the VPN tunnel either directly or indirectly via kernel-generated multicast traffic (IGMP, MLD) when leak blocking is enabled (2nd generation implementation with improved app compatibility)"

            Does the phrase "when leak blocking is enabled" translate to mean "Block connections without VPN" setting is selected on under network settings?

            If "Block connections without VPN" must be on for kernel-generated multi-cast traffic to be prevented from leaking outside the VPN, would a user running a firewall application like RethinkDNS benefit from this new protection, given that these apps are usually run with this setting disabled?

            Thanks

            Working good on Pixel Tablet. Protonvpn tested.

            spacecicada The update is first released to the Alpha channel before it is shortly moved to Beta for additional testing. It can take about 2 days to reach Stable.

            There have been cases, including a recent one, where a buggy update reached Stable due to lack of testing. If you want the update sooner or want to help with testing, you can switch to the Alpha or Beta channel.

              spacecicada That entirely depends on what (as well as how serious), if anything, is caught during Alpha and Beta channel testing. As stated on the GrapheneOS website: "Releases are tested by the developers and are then pushed out via the Alpha channel. The release is then pushed out via the Beta channel shortly afterwards. Finally, the release is then pushed out via the Stable channel after being tested by some users using the Beta channel. In some cases, problems are caught during Beta channel testing and a new release is made via the Beta channel to replace the aborted one. In general, it's not possible to downgrade unless a downgrade update package is generated, so use the Stable channel if you cannot tolerate dealing with temporary issues while a new release for the Beta channel is being created."

              https://grapheneos.org/releases#about-the-releases

                We usually don't ever do more than 24 hours of public testing before Stable. In this case, we already previously tried to ship these multicast leak blocking improvements in our 2024091900 release and then had to roll them back due to a flood of issue reports after it reached Stable after around 24 hours of public testing (4 hours in Alpha, 20 hours in both Alpha/Beta). We're being very cautious with it this time around and might even have it in public testing for 72 hours in total. It's currently around 43 hours since it entered Alpha. Automatic update checks are done every 6 hours but it can be delayed up to another 6 hours for idle devices with no other jobs, which is unusual, so nearly everyone gets updated within around 8 hours without manually doing anything, but people do need to reboot into the new version unless they use the opt-in post-update idle reboot toggle or their device is locked/idle so the default 18 hour auto-reboot after locking kicks in.