Diagnose and Fix Android Wi‑Fi Direct Connection Problems

Why Wi‑Fi Direct can be flaky on Android

Wi‑Fi Direct (also called Wi‑Fi P2P) lets two Android devices talk to each other without a traditional Wi‑Fi network. It’s handy for quick file swaps, multiplayer games, or sharing a screen. However, the feature depends on a combination of hardware, firmware, and software settings. A mismatch in any of these layers can cause the connection to stall, drop, or never form.

This guide walks you through a logical troubleshooting workflow. By the end you’ll know exactly where the problem lies and how to fix it—no rooting required.

Before you start

• Battery: Keep both devices above 30 % to avoid power‑saving interference.
• Wi‑Fi: Turn on regular Wi‑Fi on both phones (Wi‑Fi Direct uses the same radio).
• OS version: Note the Android version on each device; some bugs are version‑specific.
• Permissions: Ensure the “Location” permission is granted to any app you’ll use for testing (Android 10+ requires location for Wi‑Fi scans).
• Tools: Have a computer with adb installed and a USB cable ready for log capture.

Understanding Wi‑Fi Direct basics

Wi‑Fi Direct works by electing one device as the Group Owner (GO). The GO acts like a miniature Wi‑Fi hotspot, handling DHCP and routing. The other device becomes a client. The election process is automatic, but you can force a specific device to be the GO via developer options or third‑party apps.

If the GO fails to start DHCP, or the client cannot obtain an IP address, the connection will appear to succeed but data transfer will never happen.

Step‑by‑step troubleshooting workflow

Settings → Network & internet → Wi‑Fi → Wi‑Fi Direct

ip addr show p2p-wlan0

Using ADB to capture Wi‑Fi Direct logs

When the UI shows “Connected” but the transfer fails, the underlying cause is often visible in the system log. Follow these steps:

1. Enable Developer options on both phones (tap Build number seven times in Settings → About phone).
2. Turn on USB debugging (Settings → System → Developer options → USB debugging).
3. Connect the phone to your PC via USB and verify connection with adb devices.
4. Start a filtered logcat session that focuses on the Wi‑Fi P2P service:

   adb -s DEVICE_SERIAL logcat -b main -v threadtime | grep -i "p2p"

5. Re‑create the failure (try to connect or transfer a file) while the log is running.
6. Stop the log (Ctrl‑C) and copy the output to a text file for analysis.

Typical error strings you may see:

• p2p_supplicant: Failed to start GO – indicates the device cannot become Group Owner.
• p2p_supplicant: DHCP server failed – the GO’s DHCP service crashed.
• p2p_supplicant: Peer connection timeout – the client never received the GO’s beacon.

Common error scenarios and fixes

Troubleshooting checklist

• Restart the Wi‑Fi stack: Toggle Wi‑Fi off/on on both phones.
• Clear cached data for the “Wi‑Fi Direct” system app (Settings → Apps → Show system apps → Wi‑Fi Direct → Storage → Clear cache).
• Reset network settings if the problem appears after a system update.
• Test with a different pairing method: Use a third‑party app like “Files by Google” that internally handles the GO negotiation; if it works, the issue is likely UI‑related.
• Check for battery‑optimisation blocks: Some OEMs disable background Wi‑Fi Direct when battery‑saving mode is on. Disable battery optimisation for the “Wi‑Fi Direct” service (Settings → Battery → Battery optimisation → All apps → Wi‑Fi Direct → Don’t optimise).

Alternative approaches when native Wi‑Fi Direct refuses to cooperate

If you’ve exhausted the steps above and still cannot establish a stable link, consider these work‑arounds:

1. Use a local hotspot: Turn one device into a regular Wi‑Fi hotspot and connect the other device to it. Transfer files via standard Wi‑Fi, which is more robust on older chipsets.
2. Bluetooth file transfer: Slower but universally supported; good for small files.
3. Third‑party P2P apps like “SuperBeam” or “Send Anywhere”. They fall back to Bluetooth or internet when Wi‑Fi Direct fails, giving you a reliable path without extra configuration.

Safety warnings

When hardware is the culprit

Some low‑cost devices ship with a Wi‑Fi chip that supports only infrastructure mode (regular Wi‑Fi) and lacks the P2P firmware. In such cases, no amount of software tweaking will enable Wi‑Fi Direct. The only reliable fix is to use an external accessory (e.g., a USB‑OTG Wi‑Fi dongle that advertises P2P support) or switch to a different transfer method.

By following the workflow above you’ll be able to pinpoint whether the problem is a mis‑configuration, a software bug, or a hardware limitation, and apply the appropriate remedy. Wi‑Fi Direct is a powerful tool—once it works, you’ll have a fast, ad‑hoc network at your fingertips.