# Debugging logs

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

## Bluetooth technology on, off or pairing

See the following logs for issues related to Bluetooth technology ON/OFF or pairing:

- Logcat log with log level 6.
- Snoop log
- OTA log

## A2DP sink – Split mode

- Bluetooth technology host and multimedia audio: Contains information of stack for
          Bluetooth technology host and audio HAL logs.
- Split A2DP debug information of Bluetooth technology SoC: Provides the details related
          to issues with audio data scheduling caused due to Bluetooth technology firmware. The
          details include, but, are not limited to, CxMdetails, late Tx, and
          time since the last A2DP packet sent over the air and so on.
- Audio data logging for LPASS: Provides the data related to enable audio for logging before and after the encoding through QXDM.

## A2DP sink – Nonsplit mode

- Overflow detection: Provides the details related to A2DP ring buffer overflows. This enhanced logging feature is enabled for user-debug build. The OverflowCount parameter is generated whenever every two successful A2DP Tx durations are longer than the threshold.
- Audio dump from snoop: The PCM dump on the FTS tool is not possible because split A2DP is an interaction between audio DSP and WCD3990, and the UART bandwidth is not sufficient.
- Delay from LPASS detection: If there is no audio data received from LPASS for at least
          30 ms, this enhanced log message is generated by Bluetooth technology firmware. This can
          be a normal occurrence when audio is either paused or stopped.
- Audio dump point of LPASS
- PCM or compressed data can be dumped on each highlighted point
    - [0x1535] encoder input – PCM
    - [0x1536] encoder output – packetized compressed data.
    - [0x152E] decoder input – packetized compressed data
    - [0x1586] AFE logging – PCM
    - [0x14D2] aDSP log – not an audio dump but required for debugging aDSP
- Log messages: Search for underrun or overrun messages in QXDM to find if there are underrun/overruns at runtime.

**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
OTA logs](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/88_OTA_logs.md) [Next Topic
Debug user space](https://docs.qualcomm.com/bundle/publicresource/80-88500-3/topics/90_Debug_userspace_.md)