How to Inspect Shared Connectivity and Instant Hotspot Services on Android Using ADB dumpsys shared_connectivity

Modern multi-device ecosystems allow laptops, tablets, and mobile phones to coordinate connectivity seamlessly. Introduced in Android 14 (API level 34), the Shared Connectivity framework powers Google’s Cross-Device Services, enabling features such as Instant Hotspot, Wi-Fi credential synchronization, and seamless internet handoffs between Android devices, tablets, and Chromebooks signed into the same Google Account. Rather than requiring users to manually toggle portable hotspot switches and enter WPA passwords on secondary devices, the shared_connectivity system service negotiates secure Bluetooth Low Energy (BLE) handshakes and orchestrates Wi-Fi tethering automatically. This article explains how to inspect Shared Connectivity states, registered client devices, and instant hotspot handshakes on Android using adb shell dumpsys shared_connectivity.

Understanding Android Shared Connectivity Architecture

The Shared Connectivity architecture operates as an abstraction bridge between low-level hardware radios (Wi-Fi, BLE, Cellular telephony) and cross-device intelligence daemons. Governed by com.android.server.connectivity, the service coordinates several operational layers:

• Service Implementation Binding: Android binds to an authorized system-level connectivity provider (typically implemented within Google Play Services under CrossDeviceServices).
• BLE Advertisement & Proximity Detection: Companion devices (such as a Pixel Tablet or Chromebook) detect nearby host phones via encrypted Bluetooth Low Energy proximity beacons.
• Cryptographic Device Verification: When a secondary device requests connectivity, the service verifies cryptographic keys established through the user’s Google Account or local device grouping.
• Automated SoftAP Activation: Once authorized, the service instructs the Android Wi-Fi framework to spin up a dynamic Wi-Fi SoftAP hotspot, transmits the SSID and transient pre-shared key over the encrypted BLE channel, and connects the client without prompting the user.
• Battery and Thermal Safety: If the host phone experiences high thermal loads or drops below critical battery thresholds, the service suspends hotspot advertisements to preserve battery health.

Connecting to ADB and Querying dumpsys shared_connectivity

To inspect Shared Connectivity telemetry, enable Developer Options and USB debugging on your Android device, connect it to your computer, and verify authorization with adb devices. Then execute the service dump:

adb shell dumpsys shared_connectivity

To save the output for diagnostic analysis or offline filtering, redirect the terminal stream to a text file:

adb shell dumpsys shared_connectivity > shared_connectivity_dump.txt

If executed on devices running Android 13 or earlier, or on minimal AOSP builds that do not include cross-device frameworks, the command returns Service shared_connectivity does not exist.

Inspecting Active Service Bindings and Provider Status

At the top of the dumpsys shared_connectivity output, review the core service initialization parameters:

adb shell dumpsys shared_connectivity | grep -A 10 "SharedConnectivityManagerService:"

Key provider indicators include:

• mSharedConnectivityService: Confirms whether the system service has successfully established an active IPC binding to the underlying cross-device provider package (e.g. com.google.android.gms/.nearby.sharing.crossdevice.SharedConnectivityService).
• mServiceBound: A boolean flag (true or false) confirming active IPC communication.
• mCallbackList: Lists registered client applications and system settings listeners waiting for hotspot availability updates.

Auditing Known Companion Devices and Network States

The dump details all companion devices associated with the active account and their current connectivity posture. Query the device list:

adb shell dumpsys shared_connectivity | grep -A 20 "Client Data:"

A representative entry for a connected tablet or laptop displays structured parameters:

Device: Pixel Tablet (ID: dev_74820a1)
  DeviceType: TABLET
  ConnectionState: CONNECTED
  HotspotNetwork:
    Ssid: AndroidHotspot_9821
    SecurityType: WPA3_SAE
    BatteryPercentage: 84%
    NetworkProvider: Vodafone UK (5G)
    SignalStrength: 4/4

Reviewing these parameters clarifies how the connection is managed:

• ConnectionState: Reports whether the remote companion device is currently DISCONNECTED, CONNECTING, or CONNECTED.
• SecurityType: Confirms that modern encryption standards (such as WPA3-SAE) are enforced for transient SoftAP credentials.
• BatteryPercentage & SignalStrength: Reflects the host device’s operational metrics as advertised over BLE to client devices.

Monitoring Instant Hotspot Handshakes and Failures

When an Instant Hotspot connection fails to establish, the service records diagnostic event tokens. To inspect recent connection attempts, run:

adb shell dumpsys shared_connectivity | grep -A 15 "Historical Events:"

Common failure modes identified in this section include:

• ERROR_HOTSPOT_TIMEOUT: The client device failed to associate with the SoftAP within the negotiated timeout window (typically 30 seconds).
• ERROR_TETHERING_DISALLOWED: The cellular carrier or enterprise Mobile Device Management (MDM) profile blocked mobile hotspot activation.
• ERROR_LOW_BATTERY: Hotspot activation was rejected because the device was in Battery Saver mode.

Tracing Real-Time BLE Handshakes via Logcat

To watch cross-device discovery and tethering handshakes in real time as a companion tablet or laptop triggers an Instant Hotspot request, filter logcat output alongside the dump:

adb logcat -s SharedConnectivityService:V CrossDeviceManager:V TetheringManager:V

By reviewing adb shell dumpsys shared_connectivity, Android developers and system engineers can verify cross-device synchronization, diagnose Instant Hotspot negotiation failures, and validate secure Bluetooth and Wi-Fi handshakes across Android 14+ devices.