Bluetooth connection issue with headphone

[offroadUser]

Dear community,

currently I’m hanging on the configuration of my Teufel headphone. Here what I'm doing:

root@mini:~ # hccontrol -n ubt0hci Create_Connection Teufel
BD_ADDR: Teufel
Connection handle: 12
Encryption mode: Disabled [0]

Then I check for the status of the connection

root@mini:~ # hccontrol -n ubt0hci read_connection_list
Remote BD_ADDR    Handle Type Mode Role Encrypt Pending Queue State
Teufel                12  ACL    0 MAST    NONE       0     0 OPEN

OK. Looks fine for me. Now I'm trying to create the OSS device

root@mini:~ # virtual_oss -T /dev/sndstat -S -a o,-4 -C 2 -c 2 -r 48000 -b 16 -s 1024 -R /dev/dsp0 -P /dev/bluetooth/Teufel -d dsp -t vdsp.ctl
hw.snd.basename_clone: 0 -> 0
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 5
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 5
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 5
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 5

I'm landing here in a endless loop with the backend_bt message. What's wrong here? Thanks in advance


This is the message from hcsecd -d command from a different shell session:

root@mini:~ # hcsecd -d
hcsecd 51785 - - Restored link key for the entry, remote bdaddr 00:11:22:33:44:55, name 'Dummy'
hcsecd 51785 - - Got Link_Key_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', link key doesn't exist
hcsecd 51785 - - Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', PIN code doesn't exist
hcsecd 51785 - - Sending PIN_Code_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', PIN code doesn't exist
hcsecd 51785 - - Sending PIN_Code_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', PIN code doesn't exist
hcsecd 51785 - - Sending PIN_Code_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', PIN code doesn't exist
hcsecd 51785 - - Sending PIN_Code_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 78:5e:a2:00:83:a0
hcsecd 51785 - - Found matching entry, remote bdaddr 78:5e:a2:00:83:a0, name 'Teufel', PIN code doesn't exist
hcsecd 51785 - - Sending PIN_Code_Negative_Reply to 'ubt0hci' for remote bdaddr 78:5e:a2:00:83:a0
^Chcsecd 51785 - - Got signal 2, total number of signals 1

and this is the configuration from hcsed.conf

# Default entry is applied if no better match found
# It MUST have 00:00:00:00:00:00 as bdaddr
device {
        bdaddr  78:5e:a2:00:83:a0;
        name    "Teufel";
        key     nokey;
        pin     nopin;
}

 

[ksolowoniuk]

Hi OffroadUser,

Did you ever get this issue solved? I am having similar problems with a Logitech K380.

hcsecd 65962 - - Found matching entry, remote bdaddr f4:73:35:93:82:39, name 'Keyboard K380', link key doesn't exist

This is after configuring the device with bluetooth-config scan. It will work fine until I disconnect and try reconnecting. That's when I get the above message about the link key. Does the documentation for your headphones specify a default PIN that you could put in /etc/bluetooth/hcsecd.conf?