I have been struggling with automatically turning on Wi-Fi as soon as the device is within range of an access point without turning on the screen. It has been very frustrating to test and figure out a solution, especially since different devices have completely different results.
Base Test
Keep the screen turned off during this test. The application should hold a WifiLock.
- Walk out of WiFi coverage and stay there for a minute.
- Walk back into coverage.
Result : The Wifi is not reconnected immediately and thus app does not reconnect to server. Depending on the device and settings, sometimes it would not reconnect at all until the screen was turned on.
Forcing the Wi-Fi to reconnect
Ok, this time my application calls WifiManager.Reconnect() at an interval if Wifi is disconnected.
Repeated the test. Results : Worked for the S3, failed for other devices.
Tried adding some other calls
Tried different combinations of WifiManager.Scan(), WifiManager.Reassociate(), ...etc. Eventually it was working for most devices(HTC, S3) except the S4.
Code that seems to work for all devices
NetworkInfo wifiInfo = _androidConnectivityMgr.GetNetworkInfo(ConnectivityType.Wifi);
if (!_wifiManager.IsWifiEnabled || _wifiManager.WifiState == WifiState.Disabled || _wifiManager.WifiState == WifiState.Disabling)
{
// Make sure the Wi-Fi is enabled, required for some devices when enable WiFi does not occur immediately
_wifiManager.SetWifiEnabled(true);
}
if (!wifiInfo.IsConnectedOrConnecting)
{
// Do not wait for the OS to initiate a reconnect to a Wi-Fi router
_wifiManager.PingSupplicant();
if (_wifiManager.WifiState == WifiState.Enabled)
{
try
{
// Brute force methods required for some devices
_wifiManager.SetWifiEnabled(false);
_wifiManager.SetWifiEnabled(true);
}
catch (Java.Lang.SecurityException)
{
// Catching exception which should not occur on most devices. OS bug details at :
// https://code.google.com/p/android/issues/detail?id=22036
}
}
_wifiManager.Disconnect();
_wifiManager.StartScan();
_wifiManager.Reassociate();
_wifiManager.Reconnect();
}
I am not even sure all this code is necessary as I was unable to find much information online. WifiFixer did help some. But this does seem to work for the devices I have tested on.
The Question
- Is there a better way of doing this?
- Do the manufacturers really modify the base Android where I can be seeing this much of a difference?
- Is this completely the wrong way to approach this?
Thanks for reading through all this :)
Additional Notes
- Code runs during 10+ second interval initiated from the AlarmManager. WakeLock is held only for the duration of this call.
- Before this final scary looking solution/hack the "Wifi Sleep Policy" affected the results. This confused me since I am holding a WifiLock the entire time, which I thought was equivalent of "Never".
- Changing the "Wifi Sleep Policy" programmatically does not work for the S4, can anyone else confirm?
- Yes, we have a specific need to do this and are aware of battery implication.
The approaches by Alex and Mr_and_Mrs_D were close but not entirely consistent under Android 4.4 KitKat (Nexus 4). This may have to do with Google's more aggressive power saving policies starting in KitKat. I used a combination of their approaches with modifications.
The general idea is that during a periodic WiFi check, explicitly start a scan, then in the scan results handler call reassociate() and reconnect(). Additionally in the NETWORK_STATE_CHANGED_ACTION callback, check whether the connection is established before releasing the wake lock. The key is to hold onto the wake lock long enough for the WiFi connection to properly establish (and obviously not any longer than necessary).
Periodic WiFi check that kicks things off:
Register for WiFi broadcasts
And the WiFi event handlers
You'll need to declare the necessary variables (e.g. mWakeLock is a partial, non-reference counted wakelock; WiFi_Mgr is an instance of WifiManager; etc...).
My scenario is slightly different - I do not hold a wifi lock to begin with (and I am on regular android so I had to translate your method).
Screen off, CPU off, radio dies. Alarm wakes my (wakeful) service up - I hold a (partial) wake lock.
What I want is - if wifi is enabled to connect to the access point it was connected before the radio died - I acquire a wifi lock and I call your function -
wakeWifiUp()
. When the radio has died (!wifiInfo.IsConnectedOrConnecting
is true) I get a network unreachable when I try to connect. I workaround it as in :Btw not all the tricks in
wakeWifiUp()
are needed (in my case) and all the!_wifiManager.isWifiEnabled()
may be ommited - as I only use the net if enabled by the user. I leave it for completeness.Recap : in my scenario your method was not enough (if I translated correctly to java and didn't make some silly mistake, which always applies - see also my
connection()
). I needed to wait for connection to be established - but then all was fine. Not sure still how exactly you were using it - if as I do then the difference might be that you were holding a wifi lock all alongHTC Nexus 1, 2.3.7, Cyanogen mod (don't shoot I've been given it to test).
Will keep you posted
Had a second go around in the area. While the above solution did work for all our qualified devices, there were too many calls that might have been unnecessary. Plus we got new device for which the solution did not work. Here is a much better solution:
At every interval this code is called
When the Wi-Fi scan is finished