• General

  • Updater seems to try to check updates before signing in to a public WiFi.

pappee pappee Our System Updater uses a scheduled job with internet access set as required. It only runs once the OS detects internet access is already working. This is already a feature it provides, not something it needs to implement.

pappee It's an issue with the VPN app that you're using, not with GrapheneOS or our update client. It's not properly using the VPN API to let the OS know when it's connected.

GOS2023 GOS2023 The connectivity checks are working fine according to what you've reported. It's the VPN that's not working correctly. Connectivity checks do not bypass airplane mode. Airplane mode means cellular disabled and doesn't block enabling Wi-Fi. If your VPN switches to Wi-Fi and presents the network as up when it isn't yet, that's a VPN app issue.

              GrapheneOS pappee It's an issue with the VPN app that you're using, not with GrapheneOS or our update client. It's not properly using the VPN API to let the OS know when it's connected.

              GrapheneOS
              I am using a Mullvad VPN and you are saying that the VPN is causing the errors?

                  GOS2023 I'll switch to google connectivity check for testing.

                  I am using Google connectivity check and I get the error.

                      GrapheneOS

                      Sorry but it seems I (we ?) don't understand your logic.
                      You wrote here : https://discuss.grapheneos.org/d/1839-disabling-connectivity-checks-on-grapheneos/29
                      If the OS isn't performing connectivity checks, it doesn't know which networks are working and doesn't know when internet access is available. [...] If the OS doesn't know when it's available, the jobs will run when any network is available even if there's no internet access through it at the moment. You will get errors from multiple app background jobs instead of a single notice that no network access is available.

                      According to this post, I was assuming that :

                      • "OS connectivity check" has the job to
                        1/ verify if internet is available (internet is not available when airplane mode is trigerred and wifi is not re-activated after (*)),
                        2/ if it's not available, postpone jobs like "System Updates"

                      • "OS connectivity check" is not disturbed by the presence of a VPN because it bypass the VPN

                      (*) Mullvad VPN app and Wireguard app don't re-activate wifi after airplane mode is triggered. I think that many users can confirm this.

                      So, why blame the VPN whereas "OS connectivity check" is not supposed to interfere with it ?

                        pappee Thanks, I had indeed the same errors this morning with google connectivity check.
                        It would be interesting to see if a Pixel phone with stock OS (without GrapheneOS) has the same errors (with an app like Auditor, which can be installed without GrapheneOS) when a VPN + airplane mode are used.

                        I also tried to tweak different OS settings like "Alwyas-On VPN", "Block connections without VPN", and allow "Unrestricted" battery usage for the VPN app, but it does not seem to change anything regarding the errors in airplane mode.

                          • [deleted]

                          • Post #18

                          I use Proton VPN and have not encountered this issue when airplane mode is enabled.

                            [deleted] Thank you for your input .
                            I guess you use default VPN settings set by Proton : "Always-on VPN" and "Block connections without VPN" are both "on" ?

                            I just installed Proton VPN app on a new profile, activated airplane mode, and I'm waiting for GOS app "Apps" next update. (*) So far apps like Vanadium act exactly like with Mullvad VPN app : they have no clue that connection is down and try to connect until reaching timeout.

                            (*) Edit : and it's done : problem reproduced with Proton VPN app. "Apps" app triggered the usual error while trying to update while airplane mode was activated and Proton VPN used.

                            The more I dig this subject, the more I think it's an upstream problem, and that "OS connectivity check" is almost useless when using a VPN... because even if it checks connectivity, the information is not handed down to apps, or maybe overruled by apps' own network detection process (which can be shortened as "If VPN present : internet is UP")

                                • [deleted]

                                • Post #20

                                GOS2023 Yeah. I have both "Always-on VPN" and "Block connections without VPN" enabled.

                                  I guess I have only 2 options now :

                                  • completely silence the offending error notification, for each app involved. (But I may miss legit errors)
                                  • OR, each time I enable/disable airplane mode (for a long time), disable/enable the VPN in GOS settings (too cumbersome for me, I will probably forget to re-enable)

                                  • [deleted]

                                  • Post #22
                                  • Edited

                                  GrapheneOS Our System Updater uses a scheduled job with internet access set as required. It only runs once the OS detects internet access is already working. This is already a feature it provides, not something it needs to implement.

                                  What would have to be the circumstances for this notification to appear on a users' device?

                                      5 days later

                                      [deleted]
                                      If it's a question for me, I think I have explained it here : https://discuss.grapheneos.org/d/5439-updater-seems-to-try-to-check-updates-before-signing-in-to-a-public-wifi/9

                                      By the way, the statement you quote from @GrapheneOS is just false when you use a VPN. At least with the (probably) 2 most mentioned VPNs on this forum : Mullvad and Proton.

                                      As a VPN user, I recommend to :

                                      • "silence" the network error notifications from "System Updater", "Apps", "Auditor", and forget about the battery wasted by the useless connection attempts.
                                      • And also completely disable "OS connectivity check" because until a fix is implemented, it adds no value in our situation. It only discloses information about an Android / GrapheneOS user being present on the network (as explained on Android issue tracker : https://issuetracker.google.com/issues/250529027 )