Wi-Fi does not auto-reconnect after reboot on M1 10.1 All-in-One: weak 5 GHz signal causes Android to skip saved network

Android

If your M1 10.1 All-in-One device doesn't automatically reconnect to your Wi-Fi network after reboot, weak 5 GHz signal strength may be the cause. This article explains why this happens and how to fix it.

Understanding the issue

After you reboot your device—either through the Esper Console or by power-cycling—it may fail to automatically reconnect to a saved Wi-Fi network, even though the network is visible and saved with valid credentials. You can manually reconnect by opening the Wi-Fi settings overlay (6-tap the top-right corner → Wi-Fi), selecting the network, and returning to your kiosk app. However, the issue returns after every subsequent reboot.

This happens because Android's built-in network selection logic filters out Wi-Fi networks with weak signal strength during startup. On 5 GHz bands, a signal strength below approximately −78 dBm may fall below Android's automatic connection threshold, even though the network is valid and saved on your device.

Before you begin

Check your current Wi-Fi signal strength at your device's location:

Open the Esper Console and navigate to Devices & Groups → Device Details → Wi-Fi Settings
Look for your network SSID and note the signal strength (RSSI value in dBm)
If the value is around −78 dBm or lower on 5 GHz, signal strength is likely your issue

Step 1: Improve your Wi-Fi signal strength

The primary fix is to ensure your device receives a stronger signal. Try one or more of the following:

Move your access point closer to the device or reposition the device to reduce obstacles
Add a Wi-Fi extender or mesh node to increase coverage in your device's location
Target signal strength of −65 dBm or better for reliable automatic reconnection

Step 2: Consider switching to 2.4 GHz band

If you cannot improve 5 GHz coverage, switch your device to your network's 2.4 GHz band instead. The 2.4 GHz band has greater range and is less susceptible to signal degradation over distance.

If your router broadcasts separate SSIDs for each band, connect your device to the 2.4 GHz SSID and verify it is saved on the device.

Step 3: Provision Wi-Fi credentials via Blueprint (optional)

To ensure consistent Wi-Fi credential deployment across multiple devices, you can add your network to a Blueprint:

In the Esper Console, navigate to Blueprints → [Your Blueprint Name] → Connectivity → Wi-Fi Access Points
Add your target SSID and credentials
Assign the Blueprint to your device or device group

Note: Blueprint provisioning improves credential management but does not override Android's signal-based filtering. You still need adequate signal strength for automatic reconnection to work.

Step 4: Verify the fix

Confirm your signal strength has improved (≥ −65 dBm on 5 GHz or ≥ −70 dBm on 2.4 GHz)
Reboot your device via the Esper Console: Devices & Groups → [Device] → Actions → Reboot
Wait 60–90 seconds for the device to reconnect
Check the device tile in the Esper Console—it should show "Online" status without manual intervention

If the issue persists

If your device still fails to auto-reconnect after signal strength is confirmed adequate (≥ −65 dBm on 5 GHz), try the following:

Collect a bug report immediately after a failed reboot (before manually reconnecting) and check the logs for entries containing Networks filtered out, No candidates, or WifiConnectivityManager to determine the root cause
Verify the network is still saved—if the network disappears from your saved network list after reboot, the issue may be related to credential storage rather than signal strength
Test with a factory reset and fresh enrollment to isolate whether the issue is specific to your device configuration

Still need help?

If you've followed these steps and your device still doesn't auto-reconnect to Wi-Fi contact Esper Support and include your device model, Wi-Fi signal strength reading, and the bug report logs from your device.