How to Inspect Bluetooth Adapter States and Connected Profiles on Android Using ADB dumpsys bluetooth_manager

Modern Android smartphones interact with an extensive ecosystem of wireless peripheral hardware, including wireless earbuds, smartwatches, vehicle infotainment systems, medical monitors, and smart home IoT beacons. These interactions rely on Bluetooth Classic and Bluetooth Low Energy (BLE) protocols managed by Android’s Fluoride/GD Bluetooth stack. When users encounter wireless connectivity drops, audio stuttering on Advanced Audio Distribution Profile (A2DP), pairing refusals, or rapid battery drain caused by rogue BLE scanning, inspecting the Bluetooth management subsystem is essential.

The Android Debug Bridge (ADB) provides comprehensive diagnostic access to the operating system’s wireless stack via the dumpsys bluetooth_manager service command. By querying this diagnostic endpoint, system engineers and mobile developers can audit adapter operational states, inspect bonded device profiles, analyze active RFCOMM socket handles, and review low-level event logs without rooting the device.

Understanding Android’s Bluetooth Service Architecture

In Android, Bluetooth connectivity is divided into multiple coordinated layers:

• BluetoothManagerService: The system server daemon responsible for coordinating the overall lifecycle of the Bluetooth adapter, handling user toggles, managing persistent state settings, and communicating with airplane mode services.
• Bluetooth App (com.android.bluetooth): A dedicated system application process hosting the native Fluoride/GD stack, GATT server/client engines, and profile service implementations (A2DP, HFP, PAN, HID).
• Bluetooth HAL: The hardware abstraction layer that communicates with the physical SoC Bluetooth controller via UART, PCIe, or shared memory interfaces.

Executing dumpsys bluetooth_manager dumps state from the high-level manager service, while also providing hooks into the active profile handlers.

Querying the Complete Bluetooth Manager Dump

Connect your Android device to a workstation with USB debugging enabled. In a terminal, run the primary diagnostic dump command:

adb shell dumpsys bluetooth_manager

The output presents a structured report detailing the adapter’s hardware MAC address, current power state, bound application listeners, and profile connections. To archive this diagnostic report for offline troubleshooting, redirect the output to a local text file:

adb shell dumpsys bluetooth_manager > bluetooth_dump.txt

Inspecting Adapter Power and Radio States

To verify the physical radio state and confirm that the Bluetooth controller is operating normally without firmware faults, inspect the adapter parameters at the beginning of the dump:

adb shell dumpsys bluetooth_manager | grep -E "(enabled|state|address|name)"

Key operational indicators include:

• State: Reflects the current state machine value (STATE_ON, STATE_OFF, STATE_TURNING_ON, or STATE_TURNING_OFF). A persistent “turning on” state indicates a firmware lockup in the Bluetooth SoC.
• Address: The factory MAC address of the device’s Bluetooth interface.
• Name: The public broadcast name presented during device discovery.
• AirPlane Mode: Indicates whether the system server is suppressing radio broadcasts due to flight safety policies.

Auditing Bonded Devices and Connected Bluetooth Profiles

To inspect paired wireless peripherals and understand which profiles are actively negotiating data, query the profile state machine section:

adb shell dumpsys bluetooth_manager | grep -A 25 "Bonded devices:"

For each paired peripheral, the dump displays its Bluetooth device address, device class (CoD), device name, and connection status across standard profiles:

• A2DP (Advanced Audio Distribution Profile): High-fidelity stereo audio streaming used by wireless headphones and speakers. The dump indicates active codecs (e.g., LDAC, aptX HD, AAC, or SBC) and buffer latency.
• HFP (Hands-Free Profile): Voice telephony and microphone routing for phone calls.
• HID / HOGP (Human Interface Device / HID over GATT): Bluetooth mice, physical keyboards, and game controllers.
• PAN (Personal Area Network): Bluetooth internet tethering.

If an audio device is connected but produces no sound, check whether the A2DP profile state reports STATE_CONNECTED or remains stalled in STATE_CONNECTING.

Auditing Active BLE Scans and Battery Drain

Bluetooth Low Energy background scanning is one of the most common causes of unexplained battery depletion. Applications often register continuous BLE background scans to locate beacons or wearables without specifying hardware filters.

To identify which applications are executing BLE scans, run:

adb shell dumpsys bluetooth_manager | grep -A 15 "Active BLE Scans"

The diagnostic section reveals:

• Package Name: The application initiating the scan.
• Scan Mode: Indicates power consumption settings (SCAN_MODE_LOW_POWER, SCAN_MODE_BALANCED, or SCAN_MODE_LOW_LATENCY). Low latency scanning keeps the radio receiver continuously active.
• Hardware Filtering: Indicates whether the scan offloads address matching to the controller chip or wakes the main CPU for every ambient advertising packet.

Reviewing Bluetooth Crash Logs and State Machine History

The bluetooth_manager service maintains a historical ring buffer of recent state transitions, pairing attempts, and disconnect reasons. To view the state machine event log, execute:

adb shell dumpsys bluetooth_manager | grep -A 30 "State transitions:"

Each entry records a timestamped transition alongside the triggering process ID (PID). If an external app repeatedly toggles Bluetooth or causes daemon crashes, the log reveals the exact sequence of system calls leading to the failure.

By leveraging dumpsys bluetooth_manager, engineers and system administrators can isolate audio codec negotiations, troubleshoot pairing failures with automotive consoles, and identify battery-draining BLE background applications with precision.