# Enable logs for Bluetooth wireless technology

Source: [https://docs.qualcomm.com/doc/80-88500-3/topic/87_Enable_Bluetooth_logs.html](https://docs.qualcomm.com/doc/80-88500-3/topic/87_Enable_Bluetooth_logs.html)

## Host logs

The `adb` logcat collects system logs in the Linux user space. It can capture logs
        of Bluetooth technology applications and fluoride stacks.

To collect the logs with the timestamp enabled, execute the following command in an ADB
        shell:

    adb logcat -v threadtimeCopy to clipboard

Both `logcat` and `BluetoothSnoop` (Fluoride stack) logs can be
        captured as the initial logs for any reported issues related to Bluetooth wireless
        technology. The `hcidump` log is used to determine whether the issue is
        related to the application, host or SoC supporting Bluetooth wireless technology, or to a
        remote device.

To pull the snoop log file from target (`/data/misc/bluetooth/btsnoop_hci.log`),
        execute the following command:

    adb pull /data/misc/bluetooth/btsnoop_hci.logCopy to clipboard

## GAP and core stack logs

1. Enable GAP/core stack logs.

        adb root
        adb pull /etc/bluetooth/bt_stack.conf
        Copy to clipboard
2. Open `bt_stack.conf` and add the following values.

        TRC_BTM=6
        TRC_HCI=6
        TRC_L2CAP=6
        TRC_RFCOMM=6
        TRC_SDP=6
        TRC_BTAPP=6
        TRC_BTIF=6
        adb push bt_stack.conf /system/etc/bluetooth/
        Copy to clipboard

## Linux kernel log

To capture a Linux kernel message, run the following command:

    adb shell cat /proc/kmsgCopy to clipboard

## Enable QXDM Professional™ Tool logs

1. Launch the QXDM Professional.
2. Go to Options > Communication. The communications
          window is displayed.
3. Select the target port and click OK.
4. To begin logging, open File > Load Configuration
          to load the correct mask file (.dmc) with the required log mask
          enabled to begin the logging.

## UART logs

The UART logs are required for turn on or off related issue or transport layer issues. Run the
        following commands to collect the logs.

    adb shell cat /sys/kernel/debug/ipc_logging/78b2000.uart_pwr/log_cont >
    c:\temp\uart_pwr.txt
    Copy to clipboard

    adb shell cat /sys/kernel/debug/ipc_logging/78b2000.uart_state/log_cont >
    c:\temp\uart_state.txtCopy to clipboard

    adb shell cat /sys/kernel/debug/ipc_logging/78b2000.uart_rx/log_cont >
    c:\temp\uart_rx.txtCopy to clipboard

    adb shell cat /sys/kernel/debug/ipc_logging/78b2000.uart_tx/log_cont >
    c:\temp\uart_tx.txt
    Copy to clipboard

**Parent Topic:** [Debug connectivity logs](https://docs.qualcomm.com/doc/80-88500-3/topic/86_Connectivity_logs_and_debugging_.html)

Last Published: Sep 26, 2023

[Previous Topic
Debug connectivity logs](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/86_Connectivity_logs_and_debugging_.md) [Next Topic
OTA logs](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/88_OTA_logs.md)