Arch Linux

Seooo

Member

Registered: 2020-04-01

Posts: 9

Bluetooth headset errors

Hi everyone. I have installed Arch recently and I am trying to understand the problem I have with my bluetooth headset. In order to activate the microphone I need to switch to HSP/HFP while in order to have good audio quality (but no microphone) I need to switch back to A2DP codec. The point is that I have noticed that sometimes the connection interrupts during the switches and other times the microphone still does not activate even after the HSP/HFP selection (the only way that always work is to use the "Echo/Sound Test Service" of skype, it magically activates the mic). I have catched some logs regarding the bt headset connection showing the detected errors. Does anyone of you know to what the errors could be related?

[18730.035451] audit: type=1130 audit(1585831290.115:138): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[18730.356002] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[18730.356005] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
[18735.041563] audit: type=1131 audit(1585831295.122:139): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[18739.091161] input: Philips SHB3060 (AVRCP) as /devices/virtual/input/input24
[19029.670486] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19029.670489] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19029.670490] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19029.680503] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19029.680506] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19034.721802] Bluetooth: hci0: SCO packet for unknown connection handle 257
[19034.721805] Bluetooth: hci0: SCO packet for unknown connection handle 257
[19034.721806] Bluetooth: hci0: SCO packet for unknown connection handle 257
[19069.882418] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19069.882420] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19069.882422] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19069.882423] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19069.892408] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19117.105234] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19117.105237] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19117.115197] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19117.115199] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19117.115201] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19123.655297] Bluetooth: hci0: SCO packet for unknown connection handle 257
[19139.645973] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19139.645975] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19139.655945] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19139.655948] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19139.655949] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19139.665947] Bluetooth: hci0: SCO packet for unknown connection handle 0
[19143.495364] Bluetooth: hci0: SCO packet for unknown connection handle 257

The debugfs errors are printed during the bluetooth initial connection with the headset, the hci0 instead during the switching between the two codecs.

Last edited by Seooo (2020-04-02 13:07:48)