'Turn on Wi-Fi automatically' not working?

MetropleX

Could it be possible the network isn't being detected with a high enough RSSI (signal strength indicator) to meet the 'high quality' as Google defines it to trigger auto connect?

Turn on Wi-Fi automatically
Users may disable Wi-Fi for a variety of reasons (e.g. a connection to a bad network) and can then forget to re-enable it when arriving back home, resulting in a bad experience (e.g. not being able to control home automation devices). The Turn on Wi-Fi automatically feature, introduced in Android 9, solves this issue by automatically re-enabling Wi-Fi whenever the device is near a Wi-Fi network that is both a saved network (i.e. one which the user explicitly connected to in the past) and has a sufficiently high RSSI.

The feature can be enabled or disabled by the user using the Settings app at:

Settings > Network & internet > Wi-Fi > Wi-Fi preferences > Turn on Wi-Fi automatically

Wi-Fi Scanning (for Location) must be enabled for this feature to function. If Wi-Fi Scanning is not enabled the user is prompted for permission to enable it. Wi-Fi Scanning is required because scan results are used to determine whether the device is in the vicinity of a Wi-Fi network that meets the criteria to re-enable Wi-Fi connectivity.

The feature avoids re-enabling Wi-Fi immediately after a user disables it, even if the device observes a saved Wi-Fi network of sufficient quality. For example, if the user is in the office and is connected to the office Wi-Fi (a saved network) and then disables Wi-Fi, the feature will not re-enable Wi-Fi until the user arrives at a different environment with a different saved network that meets the re-enabling criteria.

From: https://source.android.com/devices/tech/connect/wifi-infrastructure

lbschenkel

MetropleX Maybe, but I have a number of saved networks (home, work, etc.) and the phone never turned on for any of them. I think that the probability of all of them being poor is very low.

Also: the phone is lying 20cm away from the router. RSSI = -23.

lbschenkel

Hmmm... I also found this in logcat:

W vendor.google.wifi_ext@1.0-service-vendor: setScanModeInternal(1) not supported
E WifiVendorHal: setScanMode(l.3312) failed {.code = ERROR_NOT_SUPPORTED, .description = }
W WifiConnectivityManager: Ignoring call from non primary Mode Manager ConcreteClientModeManager{id=381413462 iface=wlan0 role=ROLE_CLIENT_SCAN_ONLY}
W WifiConnectivityManager: java.lang.Throwable
W WifiConnectivityManager: 	at com.android.server.wifi.WifiConnectivityManager.handleConnectionStateChanged(WifiConnectivityManager.java:2228)
W WifiConnectivityManager: 	at com.android.server.wifi.ClientModeImpl$DisconnectedState.exit(ClientModeImpl.java:5838)
W WifiConnectivityManager: 	at com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler.invokeExitMethods(StateMachine.java:1022)
W WifiConnectivityManager: 	at com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler.performTransitions(StateMachine.java:878)
W WifiConnectivityManager: 	at com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:820)
W WifiConnectivityManager: 	at android.os.Handler.dispatchMessage(Handler.java:106)
W WifiConnectivityManager: 	at android.os.Looper.loopOnce(Looper.java:201)
W WifiConnectivityManager: 	at android.os.Looper.loop(Looper.java:288)
W WifiConnectivityManager: 	at android.os.HandlerThread.run(HandlerThread.java:67)
D WifiHandler.WifiScanningService: handleMessage Received message=159771 sendingUid=1000
D WifiScanningService: replySucceeded replySucceeded recvdMessage=159771
E SupplicantStaIfaceHal: Can't call listNetworks, ISupplicantStaIface is null for iface=wlan0
E SupplicantStaIfaceHal: removeAllNetworks failed, got null networks
E WifiClientModeImpl[wlan0]: Failed to remove networks on exiting connect mode
E WifiVendorHal: stopRssiMonitoring(l.2617) failed {.code = ERROR_NOT_AVAILABLE, .description = }
E SupplicantStaIfaceHal: Can't call setSuspendModeEnabled, ISupplicantStaIface is null for iface=wlan0
E SupplicantStaIfaceHal: Can't call setPowerSave, ISupplicantStaIface is null for iface=wlan0
E SupplicantStaIfaceHal: Can't call setBtCoexistenceMode, ISupplicantStaIface is null for iface=wlan0
V WifiNative: Interface status unchanged on Iface:{Name=wlan0,Id=2,Type=STA_SCAN} from true, Ignoring...
V WifiNative: Interface status unchanged on Iface:{Name=wlan0,Id=2,Type=STA_SCAN} from true, Ignoring...

and

W vendor.google.wifi_ext@1.0-service-vendor: setScanModeInternal(0) not supported
I vendor.google.wifi_ext@1.0-service-vendor: Adding interface handle for wlan0
I vendor.google.wifi_ext@1.0-service-vendor: Adding interface handle for aware_nmi0
I vendor.google.wifi_ext@1.0-service-vendor: Adding interface handle for wlan1
W vendor.google.wifi_ext@1.0-service-vendor: No active wlan interfaces in use! Using default
I wificond: Unsubscribe scan result for interface with index: 47
I wificond: tearDownClientInterface: erasing wiphy_index for iface_name wlan0
I wificond: remove channel type 0 support at wiphy index 0
I wificond: remove channel type 1 support at wiphy index 0
I wificond: remove channel type 3 support at wiphy index 0
D vendor.google.wifi_ext@1.0-service-vendor: Stopping legacy HAL
I vendor.google.wifi_ext@1.0-service-vendor: Legacy HAL stop complete callback received
D vendor.google.wifi_ext@1.0-service-vendor: Legacy HAL event loop terminated
D vendor.google.wifi_ext@1.0-service-vendor: Legacy HAL stop complete
I vendor.google.wifi_ext@1.0-service-vendor: Wifi HAL stopped
W AlarmManager: Window length 1152921504606846975ms too long; limiting to 1 day

I wonder if it is related?

MetropleX

lbschenkel RSSI is -23?

RSSI can be on a scale of 0 to up to 255
https://www.metageek.com/training/resources/understanding-rssi/

lbschenkel

MetropleX I am referring to how the RSSI is shown in the UI. It is customary to show signal strength as a negative number of dBm.

-23 RSSI is an excellent signal.

You are referring at how it is represented internally (unsigned byte) and I do not know the formula to map one scale to the other.

lbschenkel

https://github.com/GrapheneOS/os-issue-tracker/issues/1341

Automatically turning on Wi-Fi is not supposed to be working at the moment because this feature relies on a network location provider which is not implemented in GrapheneOS. So it is not a bug per se, and it is (not) working as intended.

de0u

JovialIntellect I believe the status in the GitHub issue that was linked to above (lbschenkel) is still accurate, and I suspect the workaround described above (hemlockiv) may well still be accurate.

The GrapheneOS project has expressed an interest in working with beaconDB on a fused geolocation provider which might well address this issue among others, but I am unaware of reportable progress on that front so far.

People are welcome to subscribe to the GitHub issue (via the "Subscribe" button), and also welcome to express interest via reaction buttons (e.g., "thumbs up"), but are requested to not add "me too" comments to the issue, because that accomplishes nothing beyond spamming the developers, who are likely to lock the issue. That said, pull requests with high-quality code are in scope...

Meanwhile, just leaving Wi-Fi on all the time works well for most people.

Matth

Bummer, I turned that on yesterday expecting it to be a nice privacy feature. But then I realized just now, that my Wifi was not back on after being home again.

pampur

I just realized too, that this not working. Very bad.

hemlockiv

With automation apps like Tasker or Macrodroid, you can set a geofence for where you want your wifi to turn on. Inconvenient to have to set up a 3rd party app, I know, but better than nothing.

JovialIntellect

Same problem here. A year later, is this working yet for anyone?