Many Android users encounter a situation where the device either refuses to join a Wi‑Fi network, drops the connection repeatedly, or shows "No internet" even though the router works fine. The cause can be a mis‑configured network, a software glitch, driver issues, or an obscure setting that only appears on certain manufacturers. This tutorial walks you through a systematic, reproducible process that starts with the easiest built‑in checks and progresses to using adb logcat to read the underlying system messages.
Why this approach? Instead of blindly resetting the phone or flashing a custom ROM, we first gather concrete evidence (log entries, Wi‑Fi configuration files) so we know exactly what is failing. This saves time, preserves data, and often uncovers a simple fix that would otherwise be missed.
Settings → About phone.Build number seven times until you see "You are now a developer".Settings → System → Developer options (or directly under Settings on some OEM skins).USB debugging on.Settings → Network & internet → Wi‑Fi.If you can connect to a different Wi‑Fi network (e.g., a neighbor’s hotspot) without issues, the problem is likely specific to the original router rather than the phone.
Settings → Network & internet → Wi‑Fi, tap the three‑dot menu (⋮) and select Advanced → Wi‑Fi diagnostics. If you don’t see this option, skip to Step 3.Run diagnostics. The tool will perform a quick scan of signal strength, frequency band, and basic connectivity.If the built‑in diagnostics don’t reveal the cause, we need to look at the system logs. Android writes detailed Wi‑Fi events to logcat, and we can filter them for the WifiManager tag.
adb devices
You should see a line with your device’s serial number and the word device.adb logcat -b wifi -v time *:S WifiManager:D
Explanation: -b wifi reads the dedicated Wi‑Fi buffer, -v time adds timestamps, *:S silences all other tags, and WifiManager:D shows debug‑level logs from the Wi‑Fi manager.
08-12 14:23:45.123 1234 5678 D WifiManager: Connecting to SSID "MyHome" (BSSID 00:11:22:33:44:55)
adb logcat -b wifi -v time *:S WifiManager:D > wifi_log.txt
Now we have a concrete log that we can analyze. Look for lines that contain the words Failed, Authentication, DHCP, or Network not found. The exact wording varies by Android version, but the pattern is usually clear.
| Log snippet | Typical cause | Suggested fix |
|---|---|---|
WifiManager: Authentication failure for SSID "MyHome" |
Wrong password or WPA2‑Enterprise mis‑configuration. | Re‑enter the password. For enterprise networks, verify the EAP method and certificates. |
WifiManager: DHCP failed, error code -1 |
Router not handing out an IP address. | Restart the router, or assign a static IP on the phone (Settings → Network → Wi‑Fi → Network name → Advanced → IP settings → Static). |
WifiManager: Network not found |
SSID hidden or out of range. | Make sure the router broadcasts the SSID, or manually add a hidden network via Add network and enter the exact name. |
WifiManager: Unsupported frequency 5GHz on device |
Device hardware does not support the 5 GHz band. | Switch the router to 2.4 GHz or use a dual‑band router that also offers 2.4 GHz. |
WifiManager: BSSID mismatch |
Router’s MAC address changed after a firmware update. | Forget the network (Settings → Wi‑Fi → Forget) and reconnect to refresh the BSSID. |
If you spot any of these patterns, apply the corresponding fix and then try to connect again. Often a single change resolves the issue.
If the logs don’t give a clear clue, or you have tried several fixes without success, resetting the network stack can clear corrupted configuration files.
Settings → System → Advanced → Reset options → Reset Wi‑Fi, mobile & Bluetooth. The wording may be Reset network settings on some OEM skins.All saved Wi‑Fi passwords, paired Bluetooth devices, and VPN configurations will be removed. Make sure you have the necessary passwords before proceeding.
Manufacturers occasionally release patches that fix Wi‑Fi driver bugs. Even if you don’t see a brand‑new Android version, a security patch can contain relevant fixes.
Settings → System → System update (or Software update on Samsung, OnePlus, etc.).Check for updates. If an update is available, download and install it.
After updating, repeat Steps 1–4. The log may now show a different error code, or the problem may be gone.
For power users who have root access, you can inspect the /data/misc/wifi/wpa_supplicant.conf file. This is rarely needed, but it can reveal malformed entries that survive a network‑reset.
adb root
(Note: many production devices refuse adb root. In that case, you need a custom recovery or a rooted ROM.)
adb pull /data/misc/wifi/wpa_supplicant.conf
network={} blocks for the same SSID, or missing psk fields.
adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
Then set correct permissions:
adb shell chmod 660 /data/misc/wifi/wpa_supplicant.conf
adb reboot
Modifying system files can brick the Wi‑Fi stack. Only attempt this if you are comfortable restoring a full backup (e.g., via TWRP) or have a working ADB sideload recovery plan.
After applying any of the above solutions, perform a quick verification:
https://example.com). The page should load within a couple of seconds.Settings → Network & internet → Wi‑Fi → tap the connected network → Advanced. Confirm that the IP address, Gateway, and DNS fields are populated.adb shell ping -c 4 8.8.8.8
You should see four replies with low latency.If any of these checks fail, return to the relevant step and double‑check the details. Often a missed typo in the password or a forgotten router reboot is the culprit.
Some VPN apps install a virtual network interface that can confuse the Wi‑Fi stack.
Battery optimization for the Wi‑Fi service via Settings → Battery → Battery usage → Wi‑Fi → Don't optimize.If you have exhausted all steps and the phone still cannot connect to any Wi‑Fi network (including mobile hotspots), the issue may be hardware‑related – for example, a failed Wi‑Fi antenna. At that point, contact the device manufacturer’s support or visit a service center.
By following this structured approach you turn a vague “my Wi‑Fi stopped working” complaint into a clear diagnosis, apply the right fix, and avoid unnecessary resets or data loss. Happy troubleshooting!









