Diagnosing and Fixing Android Wi‑Fi Connectivity Issues

18 min read Step‑by‑step guide to identify why your Android device won’t connect to Wi‑Fi and fix it using system logs, ADB commands, and built‑in settings. September 26, 2026 20:00 How to Diagnose and Fix Android Wi‑Fi Connectivity Problems with ADB and Built‑In Tools

What problem are we solving?

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.

Before you start

  • Charge the phone to at least 50 % (some Wi‑Fi drivers behave oddly on low battery).
  • Connect the device to a stable mobile data connection or have a computer with internet access ready – you will need to download Platform‑Tools (adb) if you haven’t already.
  • Enable Developer options and USB debugging:
    1. Open Settings → About phone.
    2. Tap Build number seven times until you see "You are now a developer".
    3. Go back to Settings → System → Developer options (or directly under Settings on some OEM skins).
    4. Toggle USB debugging on.
  • Have a USB‑C or micro‑USB cable that supports data transfer (charging‑only cables won’t work).
  • If your device is locked with a PIN, pattern, or biometric, keep it unlocked while you run the commands – otherwise ADB will refuse connections.

Step 1 – Verify the basic Wi‑Fi setup

  1. Open Settings → Network & internet → Wi‑Fi.
  2. Make sure Wi‑Fi is turned on. If the toggle is greyed out, the device may be in Airplane mode – turn that off first.
  3. Locate the network you want to join. Tap it and enter the password if prompted.
  4. Observe the status message:
    • Connected – you should see a check mark and the network name at the top of the screen.
    • Connecting… – wait up to 30 seconds. If it stays stuck, proceed to the next step.
    • No internet – the device is associated but cannot reach the router. This often indicates DNS or DHCP problems.

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.

Step 2 – Use Android’s built‑in Wi‑Fi diagnostics (Pixel & most AOSP devices)

  1. In 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.
  2. Tap Run diagnostics. The tool will perform a quick scan of signal strength, frequency band, and basic connectivity.
  3. Review the results. The app will flag common issues such as:
    • Weak signal (RSSI below –70 dBm).
    • Incompatible band (e.g., 5 GHz only on a 2.4 GHz‑only device).
    • DHCP lease failure.
  4. Follow any suggested actions – often simply moving closer to the router or restarting the router resolves the flagged issue.

Step 3 – Capture logcat output with ADB

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.

  1. Connect the phone to your computer via USB. When prompted on the phone, allow the computer’s RSA key for debugging.
  2. Open a terminal (Command Prompt, PowerShell, or a Linux/macOS shell) and verify the connection:
    adb devices
    You should see a line with your device’s serial number and the word device.
  3. Start a filtered logcat session that captures Wi‑Fi‑related messages:
    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.
  4. Re‑attempt to connect to the problematic network on the phone. Watch the terminal – you will see a series of lines such as:
    08-12 14:23:45.123  1234  5678 D WifiManager: Connecting to SSID "MyHome" (BSSID 00:11:22:33:44:55)
  5. When the connection either succeeds or fails, press Ctrl+C to stop logcat. Save the output to a file for later reference:
    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.

Step 4 – Common log patterns and their fixes

Log snippetTypical causeSuggested 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.

Step 5 – Reset network settings (safe fallback)

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.

  1. Open Settings → System → Advanced → Reset options → Reset Wi‑Fi, mobile & Bluetooth. The wording may be Reset network settings on some OEM skins.
  2. Confirm the reset. The device will reboot automatically.

    All saved Wi‑Fi passwords, paired Bluetooth devices, and VPN configurations will be removed. Make sure you have the necessary passwords before proceeding.

  3. After reboot, reconnect to the Wi‑Fi network using the correct password.
  4. If the connection works, the issue was likely a stale configuration. If it still fails, continue to Step 6.

Step 6 – Check for system or driver updates

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.

  1. Open Settings → System → System update (or Software update on Samsung, OnePlus, etc.).
  2. Tap 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.

Step 7 – Advanced: Manually edit the Wi‑Fi configuration file (root required)

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.

  1. Open a terminal on your computer and start a root shell on the device:
    adb root
    (Note: many production devices refuse adb root. In that case, you need a custom recovery or a rooted ROM.)
  2. Pull the configuration file for inspection:
    adb pull /data/misc/wifi/wpa_supplicant.conf
  3. Open the file with a text editor. Look for duplicate network={} blocks for the same SSID, or missing psk fields.
  4. If you spot an error, you can edit the file locally and push it back:
    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
  5. Reboot the device:
    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.

Step 8 – Verify the fix

After applying any of the above solutions, perform a quick verification:

  1. Open a browser and load a lightweight site (e.g., https://example.com). The page should load within a couple of seconds.
  2. Open Settings → Network & internet → Wi‑Fi → tap the connected network → Advanced. Confirm that the IP address, Gateway, and DNS fields are populated.
  3. Run a ping test from ADB to ensure the device can reach the internet:
    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.

Troubleshooting checklist

  • Signal strength – Move closer to the router; avoid thick walls or metal furniture.
  • Frequency band – Ensure the router broadcasts a 2.4 GHz network if the device is older.
  • MAC address filtering – Some routers block unknown devices. Add your phone’s MAC (Settings → About phone → Status → Wi‑Fi MAC) to the allowed list.
  • VPN or proxy interference – Disable any active VPNs before testing.

    Some VPN apps install a virtual network interface that can confuse the Wi‑Fi stack.

  • Power‑saving mode – On some devices, aggressive battery optimizations turn off Wi‑Fi during sleep. Disable Battery optimization for the Wi‑Fi service via Settings → Battery → Battery usage → Wi‑Fi → Don't optimize.

When to seek external help

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!

User Comments (0)

Add Comment
We'll never share your email with anyone else.