Unable to get CSR Bluetooth dongle to pair with headset

Strykar · 07-22-2019, 12:43 AM

I've spent two days trying to get this Cambridge Silicon Radio USB Bluetooth dongle to pair with my JBL T460BT headset without success.
I've tried every option on the Arch linux Bluetooth and BT headset wiki pages with no change.
I've tried setting a GATT profile to headset and audio sink, and also tried Blueman which also fails to pair/connect irrespective of previously setup trust for the MAC.

I believe the issue is that there is no Pulseaudio sink for Bluetooth in spite of the module-bluetooth-discover being loaded.
pavcontrol does not show BT audio.

Code:

[strykar@i-5 ~]$ lsusb
Bus 002 Device 007: ID 2357:010c TP-Link TL-WN722N v2
Bus 002 Device 005: ID 04f2:0833 Chicony Electronics Co., Ltd KU-0833 Keyboard
Bus 002 Device 004: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[bluetooth]# list
Controller 00:1A:7D:DA:71:10 i-5 [default]
[bluetooth]# show
Controller 00:1A:7D:DA:71:10 (public)
	Name: i-5
	Alias: i-5
	Class: 0x000c0104
	Powered: yes
	Discoverable: no
	DiscoverableTimeout: 0x00000000
	Pairable: yes
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0532
	Discovering: no
Advertising Features:
	ActiveInstances: 0x00
	SupportedInstances: 0x05
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
[bluetooth]# devices
Device 5C:FB:7C:FC:DE:67 JBL T460BT
[bluetooth]# pair 5C:FB:7C:FC:DE:67
Attempting to pair with 5C:FB:7C:FC:DE:67
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]#

Hardware and sound info:

Code:

[strykar@i-5 ~]$ pacmd list-cards|grep blue
[strykar@i-5 ~]$ pactl unload-module module-bluetooth-discover
[strykar@i-5 ~]$ pactl load-module module-bluetooth-discover
31
[strykar@i-5 ~]$ pacmd list-cards short
2 card(s) available.
    index: 0
	name: <alsa_card.pci-0000_01_00.1>
	driver: <module-alsa-card.c>
	owner module: 6
	properties:
		alsa.card = "1"
		alsa.card_name = "HDA NVidia"
		alsa.long_card_name = "HDA NVidia at 0xf7cfc000 irq 17"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:01:00.1"
		sysfs.path = "/devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1"
		device.bus = "pci"
		device.vendor.id = "10de"
		device.vendor.name = "NVIDIA Corporation"
		device.product.id = "0fba"
		device.product.name = "GM206 High Definition Audio Controller"
		device.string = "1"
		device.description = "GM206 High Definition Audio Controller"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
	profiles:
		output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no)
		output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no)
		output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no)
		output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no)
		output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no)
		output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no)
		output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no)
		output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no)
		output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no)
		off: Off (priority 0, available: unknown)
	active profile: <off>
	ports:
		hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "video-display"
		hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "video-display"
		hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "video-display"
    index: 1
	name: <alsa_card.pci-0000_00_1b.0>
	driver: <module-alsa-card.c>
	owner module: 7
	properties:
		alsa.card = "0"
		alsa.card_name = "HDA Intel MID"
		alsa.long_card_name = "HDA Intel MID at 0xf5ff8000 irq 37"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:00:1b.0"
		sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"
		device.bus = "pci"
		device.vendor.id = "8086"
		device.vendor.name = "Intel Corporation"
		device.product.id = "3b56"
		device.product.name = "5 Series/3400 Series Chipset High Definition Audio"
		device.form_factor = "internal"
		device.string = "0"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
	profiles:
		input:analog-stereo: Analog Stereo Input (priority 65, available: no)
		output:analog-stereo: Analog Stereo Output (priority 6500, available: unknown)
		output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6565, available: unknown)
		output:analog-surround-21: Analog Surround 2.1 Output (priority 1300, available: unknown)
		output:analog-surround-21+input:analog-stereo: Analog Surround 2.1 Output + Analog Stereo Input (priority 1365, available: unknown)
		output:analog-surround-40: Analog Surround 4.0 Output (priority 1200, available: unknown)
		output:analog-surround-40+input:analog-stereo: Analog Surround 4.0 Output + Analog Stereo Input (priority 1265, available: unknown)
		output:analog-surround-41: Analog Surround 4.1 Output (priority 1300, available: unknown)
		output:analog-surround-41+input:analog-stereo: Analog Surround 4.1 Output + Analog Stereo Input (priority 1365, available: unknown)
		output:analog-surround-50: Analog Surround 5.0 Output (priority 1200, available: unknown)
		output:analog-surround-50+input:analog-stereo: Analog Surround 5.0 Output + Analog Stereo Input (priority 1265, available: unknown)
		output:analog-surround-51: Analog Surround 5.1 Output (priority 1300, available: unknown)
		output:analog-surround-51+input:analog-stereo: Analog Surround 5.1 Output + Analog Stereo Input (priority 1365, available: unknown)
		output:analog-surround-71: Analog Surround 7.1 Output (priority 1200, available: unknown)
		output:analog-surround-71+input:analog-stereo: Analog Surround 7.1 Output + Analog Stereo Input (priority 1265, available: unknown)
		output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown)
		output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:analog-stereo+input:analog-stereo>
	sinks:
		alsa_output.pci-0000_00_1b.0.analog-stereo/#0: Built-in Audio Analog Stereo
	sources:
		alsa_output.pci-0000_00_1b.0.analog-stereo.monitor/#0: Monitor of Built-in Audio Analog Stereo
		alsa_input.pci-0000_00_1b.0.analog-stereo/#1: Built-in Audio Analog Stereo
	ports:
		analog-input-front-mic: Front Microphone (priority 8500, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-input-microphone"
		analog-input-rear-mic: Rear Microphone (priority 8200, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-input-microphone"
		analog-input-linein: Line In (priority 8100, latency offset 0 usec, available: no)
			properties:
				
		analog-output-lineout: Line Out (priority 9900, latency offset 0 usec, available: yes)
			properties:
				
		analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-headphones"
		hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: unknown)
			properties:
				device.icon_name = "video-display"

[strykar@i-5 ~]$ sudo pacman -Ss bluetooth|grep installed
extra/gnome-bluetooth 3.32.1-1 [installed]
extra/sbc 1.4-1 [installed]
community/blueman 2.1-1 [installed]
custom/bluez-firmware 1.2-9 [installed]
custom/bluez-git 1:5.50.r470.g79bf51dbb-1 [installed]
custom/pulseaudio-bluetooth-a2dp-gdm-fix 0.1-1 [installed]
custom/pulseaudio-modules-bt-git r139.99aa1fe-1 [installed]

Bluetooth service log:

Code:

Jul 21 15:23:27 i-5 systemd[1]: Stopped Bluetooth service.
Jul 21 15:23:27 i-5 systemd[1]: Starting Bluetooth service...
Jul 21 15:23:27 i-5 bluetoothd[4681]: Bluetooth daemon 5.50
Jul 21 15:23:27 i-5 systemd[1]: Started Bluetooth service.
Jul 21 15:23:27 i-5 bluetoothd[4681]: Starting SDP server
Jul 21 15:23:27 i-5 bluetoothd[4681]: Bluetooth management interface 1.14 initialized
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to clear UUIDs: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to set privacy: Rejected (0x0b)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to add UUID: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to add UUID: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to set device class: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to add UUID: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to add UUID: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to add UUID: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Failed to set device class: Busy (0x0a)
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSource/VENDOR/APTX
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSource/AAC
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSource/SBC
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSink/VENDOR/APTX
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSink/AAC
Jul 21 15:23:27 i-5 bluetoothd[4681]: Endpoint registered: sender=:1.588 path=/MediaEndpoint/A2DPSink/SBC
Jul 21 15:38:36 i-5 bluetoothd[4681]: 5C:FB:7C:FC:DE:67: error updating services: Connection timed out (110)
Jul 21 15:39:37 i-5 bluetoothd[4681]: Pair device timed out for hci0

I'm currently on bluez-git and could use some help.
I'm using Gnome with lightdm on Arch linux.

Shouldn't the output of pacmd list-cards have bluetooth in there?

business_kid · 07-23-2019, 09:10 AM

Welcome to the club. Bluetooth is a bitch.

I ended up using 'bluetoothctl' in a kernel console as root, which has some useful commands. You can scan for it, pair/unpair it, trust it etc.Restart bluetooth before you do. Watch out for microscopic icons on your taskbar in the most unseen places. Then open blueman if you need to.

Strykar · 07-25-2019, 03:28 AM

I tried it as root, I get the same errors:

Code:

[root@i-5 ~]# bluetoothctl 
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# quit
[root@i-5 ~]# systemctl restart bluetooth
[root@i-5 ~]# bluetoothctl 
Agent registered
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 00:1A:7D:DA:71:10 Alias: i-5
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# list
Controller 00:1A:7D:DA:71:10 i-5 [default]
[bluetooth]# devices
Device 5C:FB:7C:FC:DE:67 JBL T460BT
[bluetooth]# pair 5C:FB:7C:FC:DE:67
Attempting to pair with 5C:FB:7C:FC:DE:67
Failed to pair: org.bluez.Error.AuthenticationFailed
[bluetooth]#

business_kid · 07-25-2019, 11:15 AM

Quote:

[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady

I'd investigate firmware for your bluetooth device. What does bluetooth on your box?

Strykar · 08-10-2019, 12:23 AM

Quote:

Originally Posted by business_kid

I'd investigate firmware for your bluetooth device. What does bluetooth on your box?

From every post I read about this BT dongle, it appears that this does not need firmware unlike some of the Asus/Broadcom Windows specific devices, how would I confirm this?

business_kid · 08-10-2019, 01:21 PM

Quote:

Originally Posted by Strykar

From every post I read about this BT dongle, it appears that this does not need firmware unlike some of the Asus/Broadcom Windows specific devices, how would I confirm this?

Google <your exact device> +firmware. Firmware is usually a way to get themselves out of an expensive recall.

A company I was with in the 1980s had to fix a bug, and that involved sending off a mass of eproms to their English outfit. They had to stick them in boxes under trucks, then reprogram the ones they rescued and visit again when more trucks were back at base :-/. That was expensive!

Strykar · 08-11-2019, 01:14 PM

Spent some googling results for "0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle firmware" and found none that relate to the CSR BT chipset.
Also confirmed the headset pairs fine to a Sony notebook running Ubuntu with a Broadcom BT chipset. I've ordered another USB BT dongle to see if a different chipset will make a difference, will report back in a few days.

Strykar · 08-12-2019, 11:50 PM

The new Kinivo BTD400 USB dongle works and pairs immediately with my JBL headset, I had to change the HSP/HFP profile to Pulseaudio's A2DP sink and did have to install its firmware via an aur package. I'm just going to return the older CSR dongle which I couldn't get to work on my Odroid C2 either. I won't waste any more time on it.