While the cans were charging I looked at the Amazon page for the adapter here and noticed that it said for Windows and "Not work with Mac OS, car stereo systems or TVs". I dropped down to the Customer questions & answers section and input Linux and found nothing. I figured at worst my wife will have a Bluetooth adapter for her Win10 machine, but still thought I'd give it a try.
Once fully charged, I first ran lsusb to make sure the adapter was recognized:
Code: Select all
scott@scott-HP ~ $ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1acc:3c01 Midiplus Co, Ltd.
Bus 003 Device 002: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code: Select all
scott@scott-HP ~ $ dmesg | tail
[374567.799925] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374583.796900] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374599.798951] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374615.796918] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374631.798973] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374644.794043] Bluetooth: hci0: last event is not cmd complete (0x0f)
[374787.881957] Bluetooth: RFCOMM TTY layer initialized
[374787.881965] Bluetooth: RFCOMM socket layer initialized
[374787.881975] Bluetooth: RFCOMM ver 1.11
[374907.790163] Bluetooth: hci0: last event is not cmd complete (0x0f)
Code: Select all
scott@scott-HP ~ $ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
scott@scott-HP ~ $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-12-30 00:12:12 EST; 25min ago
Docs: man:bluetoothd(8)
Main PID: 9071 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─9071 /usr/lib/bluetooth/bluetoothd
Dec 30 00:21:00 scott-HP bluetoothd[9071]: a2dp-sink profile connect failed for FC:58:FA:52:EF:54: Protocol not available
scott@scott-HP ~ $ sudo hciconfig hci0 voice 0x0060 <---- found this in another post on here, no idea if it helped in any way
[sudo] password for scott:
scott@scott-HP ~ $ pulseaudio -k
apt install pulseaudio-module-bluetooth
followed by pactl load-module module-bluetooth-discover
(cannot remember if I removed the device and searched for it again at this point) and suddenly there was a slight hum in my ears.Last step was to fire up
pavucontrol
and change the output on the Playback tab to the now listed headphones and BAM! SUCCESS! Eat that, Mac OS users and car stereo systems or TVs!Hope this helps save someone some frustration in the future.