How to Inspect Wi-Fi Direct and P2P Connections on Android Using ADB dumpsys wifip2p

Modern mobile operating systems rely heavily on ad-hoc device-to-device wireless networking to enable local data sharing, peripheral connections, and multimedia streaming without requiring an intermediary Wi-Fi access point or internet connection. On Android, this capability is powered by the Wi-Fi Direct (Wi-Fi P2P) specification developed by the Wi-Fi Alliance. Core Android features—such as Quick Share (formerly Nearby Share), wireless screen projection (Miracast), Wi-Fi Direct printing, and peer-to-peer multiplayer gaming—operate on top of this P2P framework.

When peer discovery fails, group owner negotiations stall, or wireless projection sessions disconnect unexpectedly, diagnosing the issue through standard user settings is virtually impossible. By connecting the Android device via the Android Debug Bridge (ADB) and using dumpsys wifip2p, developers, QA engineers, and network administrators can inspect internal P2P state machine transitions, discoverable peers, Group Owner (GO) negotiation intent, and persistent network credentials.

Architecture of Wi-Fi Direct (Wi-Fi P2P) on Android

Wi-Fi Direct operates through a coordinated framework comprising the Java API (WifiP2pManager), the system service (WifiP2pService), the vendor Wi-Fi HAL, and wpa_supplicant. Key architectural concepts include:

• Group Owner (GO): When two devices establish a Wi-Fi Direct connection, one device negotiates to become the Group Owner (acting essentially as a soft access point providing DHCP and network addressing), while the other joins as a client.
• Group Owner Intent: During connection handshake negotiation, each device advertises an intent value (an integer between 0 and 15). The device with the higher intent value becomes the Group Owner.
• Peer Discovery (Find Phase): Devices scan specific social channels (channels 1, 6, and 11 on the 2.4 GHz band) and exchange Probe Request and Probe Response frames containing P2P Information Elements (IEs).
• Persistent Groups: Android caches group configurations, security keys, and network names (SSIDs) in local storage, allowing paired devices to reconnect instantly without repeating WPS PIN or push-button authorization.

Inspecting Wi-Fi P2P Service State with dumpsys

To inspect the status of the Wi-Fi Direct subsystem, connect your device with USB debugging enabled and execute dumpsys wifip2p via ADB:

# Query the Wi-Fi P2P system service diagnostics
adb shell dumpsys wifip2p

The command dumps the internal state machine hierarchy, active network interfaces, and device hardware details:

WifiP2pService:
  mP2pStateMachine:
    Active State: P2pEnabledState
    Interface: p2p-wlan0-0
    Device name: Pixel 8 Pro
    Device address: 42:2a:18:90:bc:11
    Group Owner Intent: 7

The output displays the active state of the state machine (such as P2pEnabledState, InactiveState, or GroupCreatedState), the assigned virtual network interface name (typically p2p0 or p2p-wlan0-0), and the randomized MAC address used for P2P advertisements.

Auditing Discoverable Peers and Signal Quality

When searching for nearby devices using Quick Share or screen casting, you can verify which peer devices Android has discovered and parsed by inspecting the peer list within the dump:

# Query currently discovered Wi-Fi Direct peers
adb shell dumpsys wifip2p | grep -A 10 "Peers:"

The terminal lists all discovered devices within wireless range, including their device names, primary device types, and connection status:

Peers:
  Device: Smart TV [Living Room]
    Address: 98:02:11:ff:34:20
    Primary type: 0007-0050F204-0001 (Display)
    Status: 3 (Available)
  Device: Samsung Galaxy S24
    Address: 7a:89:12:34:ef:01
    Primary type: 000A-0050F204-0001 (Smartphone)
    Status: 3 (Available)

Status codes represent the peer’s availability: 0 (Connected), 1 (Invited), 2 (Failed), 3 (Available), or 4 (Unavailable).

Inspecting Active Group Owner Connections and IP Addressing

When a P2P session is actively connected, dumpsys wifip2p exposes the established network topology, negotiated frequency, and assigned IP addresses:

# Inspect active group details and client connections
adb shell dumpsys wifip2p | grep -A 12 "mGroup:"

The output reveals complete group parameters:

mGroup:
  network name: DIRECT-ab-Pixel_8_Pro
  passphrase: **********
  is group owner: true
  frequency: 5240 MHz (Channel 48)
  Group Owner IP: 192.168.49.1
  Connected Clients: 1
    Client [0]: 42:2a:18:90:bc:11 (IP: 192.168.49.125)

This information confirms whether your device is operating as the Group Owner (hosting the 192.168.49.1 subnet) or connected as a client, along with the precise 5 GHz channel being used for high-bandwidth streaming.

Auditing and Clearing Persistent Groups

Over time, Android accumulates cached credentials for dozens of previously paired peer devices. If a peer device updates its security firmware or re-keys its network, stale persistent group entries can cause connection handshakes to fail repeatedly.

You can inspect all saved persistent groups:

# List persistent group records
adb shell dumpsys wifip2p | grep -A 8 "Persistent Groups:"

To delete a corrupt or stale persistent group, identify its network ID (such as netId: 2) and remove it using the native wpa_cli or p2p shell control:

# Delete saved persistent group
adb shell wpa_cli -i p2p0 p2p_group_remove DIRECT-ab-Pixel_8_Pro

Using dumpsys wifip2p provides mobile engineers and system testers with comprehensive diagnostic visibility into local device-to-device wireless networking, ensuring rapid resolution of discovery and pairing anomalies.