![cambridge silicon radio bluetooth dongle driver cambridge silicon radio bluetooth dongle driver](https://user-images.githubusercontent.com/690187/159580072-a144c9ab-6314-438c-be27-1e1edfd846f1.jpg)
Is this problem known, and even more, is there a solution? ( I will need an automated solution / a solution that can be automated, so physically re-connecting the dongle is no solution for me. When the dongle is plugged in again, VBox grabs the device before Win can. I played with Bluetooth on/off and (de)activating the dongle driver of the host system, but Win10 seems to keep its fingers on the dongle somehow and does not release it to the box, once it got it. how to setup a Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Ask Question. It appears in the list, and when I click it, it is immediately attached to the guest system, and the enty is checked. 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. On the other hand, I tried a USB-to-UART interface, which works as expected.
![cambridge silicon radio bluetooth dongle driver cambridge silicon radio bluetooth dongle driver](http://cf.ppt-online.org/files/slide/l/lOm53pzs8PJ1AonbVGMr2WXNDLyq0vucg4RktK/slide-13.jpg)
The already plugged-in dongle is not attached to the guest automatically, but when I remove and plug it in again, it is immediately. When I configure a USB-Filter, it is about the same. Had to use ofono to get HSP/HFP to work and use the mic. When I plug it in again, the dongle is immediately attacked to the guest system, and is operational (scanning for other bluetooth devices works). Working, tested, can detect devices and connect to them including controllers and phones. First, listing my Bluetooth USB type gave me the following information: mhsabbaghryzenpc: lsusb. When I remove the dongle, the unchecked entry is still in the list. When I click it, nothing happens! The entry in the list stays unchecked, and the dongle does not appear in the guest system (dmesg, lsusb, neither android nor openSuse)Ĭlicking it again gives the "Device busy with previous request" error. When I plug in the dongle, it appears in the list of USB devices of the VBox instance as usual. My desired Guest system is Android x86, but the same problem occurs with openSuse 42.1 Uninstall > Reboot the computer > The driver will be installed automatically when you restart. Click Properties > Go to Driver tab > If there is rollback option, click it. My host is Win10 with VBox 5.1.22 r115126 with the extension pack installed. Windows Key+X > Click Device Manager > Expand Bluetooth > Right click on entry below >. Code: Select all Cambridge Silicon Radio, Ltd CSR8510 A10