We need to contact the linux kernel maintainers for bluetooth support, but before we do that we need more people than me to confirm that it works. So the dongle is using a fake CSR chip made by Barrot as previously mentioned. It was possible to make a patch that makes the dongle work in Linux, but we have some work to do before we get it into the kernel. LMP Subversions currently unknown for products 1 and 2 below. LMP Subversion ( BXL - product 3 in image below): 0x1712 Images found on the Internet that matches specific 'BQB 75270' LMP Subversions ( identified by user): Note: I was asked by to create this as a separate question to avoid that my previous comments (added as an answer in the question referred to in the start) will get deleted. Jan 26 21:10:38 some-computer systemd: Reached target Bluetooth. Jan 26 21:10:38 some-computer systemd: Started Load/Save RF Kill Switch Status. Jan 26 21:10:38 some-computer systemd: Starting Load/Save RF Kill Switch Status. Jan 26 21:10:38 some-computer kernel: usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Jan 26 21:10:38 some-computer kernel: usb 1-1.3: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 Jan 26 21:10:38 some-computer kernel: usb 1-1.3: config 1 interface 1 altsetting 0 endpoint 0x83 has wMaxPacketSize 0, skipping Jan 26 21:10:38 some-computer kernel: usb 1-1.3: config 1 interface 1 altsetting 0 endpoint 0x3 has wMaxPacketSize 0, skipping I get this when inserting the Bluetooth USB dongle: jan 26 21:10:38 some-computer kernel: usb 1-1.3: new full-speed USB device number 6 using ehci-pci Blueman is not recognizing the Bluetooth devices. It works fine in Windows 10, but not in Ubuntu 18.04 (also not with kernel 5.3). After the patch you wont see the event/command in the output of hcidump. You will only see the last HCI Event for Error: Unsupported Feature or Parameter Value as long as you have not applied the patch. > HCI Event: Command Complete (0x0e) plen 6ĭelete Stored Link Key (0x03|0x0012) ncmd 1Įrror: Unsupported Feature or Parameter Value Manufacturer: Cambridge Silicon Radio (10) LMP Version: 4.0 (0圆) LMP Subversion: 0x1113 HCI Version: 4.0 (0圆) HCI Revision: 0x810 Read Local Version Information (0x04|0x0001) ncmd 1 > HCI Event: Command Complete (0x0e) plen 12 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 TX bytes:368 acl:0 sco:0 commands:30 errors:0įeatures: 0xff 0xff 0xc5 0xfa 0xdb 0xbf 0x7b 0x87 RX bytes:574 acl:0 sco:0 events:30 errors:0 I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb If anyone can help a very simple to follow step by step guide for a novice would be fantastic, I'm running latest debian 10.Like Bluetooth dongle problem.(probably regarding the driver) I experience the same problem that the bluetooth device won't initialize properly: $ lsusb | grep Bluetoothīus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The criticality of using this particular usb device is because its class 1 with better range than the more standard class 2 dongles the intention is to run "Home Assistant" as an upgrade to my current setup using a RPI 4, included within my home assistant install is many bluetooth temperature sensors and hence the requirement for bluetooth at an extended range. So the device is detected, i've spent literally every evening this week searching "0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" in an attempt to find a suitable guide and solution that i can understand but to date i've failed. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 002: ID 80ee:0021 VirtualBox USB Tabletīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub