Cant pair bluetooth headset, anyone can help me?

enkinambal

New Member


Messages: 4

FreeBSD 12.1

What configuration i have:

ASUSTek Computer, Inc. Qualcomm Bluetooth 4.1 integrated in motheboard.
JBL 500 BT Headset

Ok, what i tried to do:

1) scan with bluetooth-config always done, after i answer yes, new headset added to hcsecd.conf with nokey/nopin attributes. Looks like everything success, but headset always still blinking... Ok, after switched it off, and then turned on again, i see such thing: it is trying to search, 10-15 sec after it, is switching to blink/pairing mode again.

I ran hcsecd with -d key, and saw such picture:

Found matching entry, remote bdaddr 0:80:37:29:19:a4, name '****', link key doesn't exist

Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4

Headset start blinking, and nothing else happens, until i restart the bluetooth stack.

What am I doing wrong?
 

eternal_noob

Aspiring Daemon

Reaction score: 425
Messages: 651

It depends on the Bluetooth version if it's supported or not.
Bluetooth V3 and V4 aren't supported afaik.

For more information, look here: Thread 64797
 

asherikov

New Member


Messages: 1

Try with
Code:
hccontrol -n ubt0hci write_authentication_enable 1
hccontrol -n ubt0hci write_encryption_mode 1
My headset does not bind by default as well.
 

sdalu

New Member


Messages: 5

I need to run virtual_oss once connection established with hccontrol -n ubt0hci create_connection BT_ADDR. sdbpd and hcescd need to be running

Code:
virtual_oss -S -C 2 -c 2 -r 48000 -b 16 -s 1024 \
    -R /dev/null -R /dev/null -P /dev/bluetooth/SE7 \
    -T /dev/sndstat -d dsp.bt

Also I'm using in hcescd.conf a pin value of "0000"

Note that my headset say's "connected" only when virtual_oss has been run
 

christhegeek

Well-Known Member

Reaction score: 66
Messages: 252

Have you solved the problem ?
I remember my headset had no problems pairing with my freebsd, if you still have problems respond.




FreeBSD 12.1

What configuration i have:

ASUSTek Computer, Inc. Qualcomm Bluetooth 4.1 integrated in motheboard.
JBL 500 BT Headset

Ok, what i tried to do:

1) scan with bluetooth-config always done, after i answer yes, new headset added to hcsecd.conf with nokey/nopin attributes. Looks like everything success, but headset always still blinking... Ok, after switched it off, and then turned on again, i see such thing: it is trying to search, 10-15 sec after it, is switching to blink/pairing mode again.

I ran hcsecd with -d key, and saw such picture:

Found matching entry, remote bdaddr 0:80:37:29:19:a4, name '****', link key doesn't exist

Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4

Headset start blinking, and nothing else happens, until i restart the bluetooth stack.

What am I doing wrong?
 
Last edited by a moderator:
OP
enkinambal

enkinambal

New Member


Messages: 4

I need to run virtual_oss once connection established with hccontrol -n ubt0hci create_connection BT_ADDR. sdbpd and hcescd need to be running

Code:
virtual_oss -S -C 2 -c 2 -r 48000 -b 16 -s 1024 \
    -R /dev/null -R /dev/null -P /dev/bluetooth/SE7 \
    -T /dev/sndstat -d dsp.bt

Also I'm using in hcescd.conf a pin value of "0000"

Note that my headset say's "connected" only when virtual_oss has been run

Please check, am I doing right things?

The result is:
Code:
root@free:/home/noname # hccontrol -n ubt0hci create_connection 5c:fb:7c:72:26:91
BD_ADDR: JBL_TUNE500BT
Connection handle: 6
Encryption mode: Disabled [0]

root@free:/home/noname # kldload cuse                                                                                         

root@free:/home/noname # virtual_oss -S -C 2 -c 2 -r 48000 -b 16 -s 1024 -R /dev/null -R /dev/null -P /dev/bluetooth/5c:fb:7c:72:26:91 -T /dev/sndstat -d dsp.bt
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
backend_bt: Could not connect to HC: 13
backend_bt: PSM=0x19
 
Top