Only problem, i cant turn it into a HSP\HSP profile but i think its another story(even after the ofono gambiarra). I still run the bredr_setup() but bypass the clear event filter step. Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Couldnt open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1. Maybe the "#define lmp_bredr_capable(dev) 0" also work. Hci_req_add(req, HCI_OP_WRITE_CA_TIMEOUT, 2, ¶m) hci_req_add(req, HCI_OP_SET_EVENT_FLT, 1, &flt_type)
Hci_req_add(req, HCI_OP_READ_CURRENT_IAC_LAP, 0, NULL) Hci_req_add(req, HCI_OP_READ_NUM_SUPPORTED_IAC, 0, NULL) Have installed 5.17.1-051701-generic on Ubuntu 22.04.1 and still have the problem lsusb: Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Have tried with 6.0.7-060007-generic and still same output 3.776546 Bluetooth: Core ver 2.22 3. Hci_req_add(req, HCI_OP_READ_VOICE_SETTING, 0, NULL) ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Couldnt open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2. Hci_req_add(req, HCI_OP_READ_LOCAL_NAME, 0, NULL) I have a bluetooth device and with lsusb I can find it here Bus 001 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). Hci_req_add(req, HCI_OP_READ_CLASS_OF_DEV, 0, NULL) Hci_req_add(req, HCI_OP_READ_BUFFER_SIZE, 0, NULL) * Read Buffer Size (ACL mtu, max pkt, etc.) */ static void bredr_setup(struct hci_request *req) Besides the link I shared above, if you just google the line I quoted you will find lots of references to issues and. It seems something in about 4.15 kernel broke these adapters and it has never been corrected. I solved my problem by comment the lines 296 and 297 of hci_core.c(plus patches). Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The problem is this is a 'troublesome' adapter in Linux in modern kernels. I don't know how to do that #define lmp_bredr_capable(dev). bluetooth Some of them could be used to debug your setup, if you use a non. "Changing the #define lmp_bredr_capable(dev) in hci_core.h to return false did the trick." Cambridge Silicon Radio, Ltd BlueWhile some of the required software modules. I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusbīut even after patch, I'm getting the error below via hcidump: HCI Event: Command Complete (0x0e) plen 4
I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb If I understand though, when you have a properly-matching USB filter, and you plug the device in while the guest is running, Virtualbox gives the host a dummy device and diverts the device into the guest. I've got a fake dongle BT 4.0 from china and try the procedure from this thread: Bluetooth dongle problem Distributor ID: Ubuntuĭevice: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) That would be up to the host OS, drivers, etc.