WARNING

If you're going to attach the log files mentioned below be warned that those might include private information like phone numbers. If you're asked to share such log files you're free to not do this or share them with the asking person on a more private way than through launchpad/irc/..

Debugging procedure

Reporting a bug

When reporting a Bluetooth bug we need to include different things to make it easier for the developers to find a solution for the problem. Please use the following link to report bluetooth bugs:

https://bugs.launchpad.net/ubuntu-rtm/+source/bluez/+filebug

Please note/include the following things in your bug report:

• Which devices are involved? Exact model numbers if available are helpful.
• Which Bluetooth version do all involved devices support?
• Necessary log files (if possible with debugging information; see below)
  • /var/log/syslog
  • For Touch based devices:
    • /home/phablet/.cache/upstart/application-legacy-ubuntu-system-settings-.log
    • /home/phablet/.cache/upstart/dbus.log

List common information about current Bluetooth setup

• Adapter info

phablet@ubuntu-phablet:~$ hciconfig -a

• List of paired devices

phablet@ubuntu-phablet:~$ /usr/bin/bluez-list-devices

• If you have a system with BlueZ 5.x use bluetoothctl and execute the following commands

phablet@ubuntu-phablet:~$ bluetoothctl
[bluetooth]# show
[bluetooth]# devices
[bluetooth]# info <mac addr of any device you have problems with>

Generating log files with debugging information

As log files are normally just include warnings and errors it is quite helpful to have log files with additional debugging information. In the std. configuration of a Ubuntu system debugging informations are disabled to not pollute the system with a big log files. For Bluetooth we need to perform the following steps to enable verbose debug logging:

• If you're on a Touch based system you have to temporarily mount your system partition read/write.

phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /

• As next step we enable verbose logging for the Bluetooth daemon

phablet@ubuntu-phablet:~$ sudo sed -i 's/exec \/usr\/sbin\/bluetoothd \-c \/etc\/bluetooth\/touch.conf/exec \/usr\/sbin\/bluetoothd \-c \/etc\/bluetooth\/touch.conf -d/g' /etc/init/bluetooth.override

NOTE: If /etc/init/bluetooth.override doesn't exist use the following command instead

phablet@ubuntu-phablet:~$ sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf

• For additional logging information we also enable verbose logging of the PulseAudio daemon

phablet@ubuntu-phablet:~$ sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf

• For HFP or other mobile related Bluetooth profile debugging we also need to enable verbose logging for ofono:
  • Add '-d' to the exec line in /etc/init/ofono.override

NOTE: This is currently pretty specific to Touch and needs additional information for systemd based variants of Ubuntu.

Dumping send packages

At times its also interesting to dump the actual packages send from the host to the Bluetooth chip over HCI. This can be done with