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. It appears in the list, and when I click it, it is immediately attached to the guest system, and the enty is checked. On the other hand, I tried a USB-to-UART interface, which works as expected. 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. When I plug it in again, the dongle is immediately attacked to the guest system, and is operational (scanning for other bluetooth devices works). 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 My host is Win10 with VBox 5.1.22 r115126 with the extension pack installed. So my question is, do you know how I can get it to accept and use older drivers?Īlso, could there be another explanation, for why a system cannot search for and detect other bluetooth devices, but can be seen by other bluetooth devices, but no device can connect to it? I don't know for sure that it is the drivers, it's just one thing I was going to try and check before seeing if there was anything else I could think of.Code: Select all Cambridge Silicon Radio, Ltd CSR8510 A10 I tried it once again and the same thing happened?! 5512 versions, and the same filesize as the original 5512 versions. However, when I rebooted the computer and reinserted the dongle, they had all magically reappeared again as version 5512! All the files which I overwrote with 2180 versions had somehow managed to come back to being original. Some of the files were a slightly different file size. I overwrote the above mentioned 5 files with older versions from the other PC. ![]() I thought that if I overwrote all the driver files on this newer XP system with the older drivers from the other XP system (which I know do work with the device), then this might fix it. If you go in to "Driver details." it tells you the names of 5 files (bthport.sys, bthusb.sys, bthprops.ctl, fsquirt.exe, bthenum.sys) and their locations. įor the newer and more updated SP3 machine, which isn't working with the dongle, the drivers are newer: version. On the (older) machine, which IS working with the dongle, the drivers are version. I went to see if my two XP machines were both using the same drivers, and found that they weren't. But I want to use the dongle with my main machine, not these other two! That also worked! It can see other devices, it pops up a message when a phone tries to connect to the computer, etc. I then dug out an old laptop with XP SP2 on it. Vista did the same thing as XP, it found and installed generic drivers all by itself automatically, but on Vista it worked fine. I plugged the dongle in to my mums Windows Visata machine to see if the Dongle itself was faulty, but everything worked perfectly. Iif you try to get the phone to connect to the computer, nothing at all happens at the computer end, even though all the options are set to allow connections, show as visible, etc. It does allow the PC to be seen by other devices (like my mobile phone) as a bluetooth device though, so it's not completely dead! It does not allow connections though. When instructing the computer to search for new Bluetooth devices, using the "Add Bluetooth Device Wizard.", no devices are found, despite several being in range. When I plugged it in to my XP Professional SP3 machine, Windows automatically installed generic drivers for it, and then said the device was ready for use. The only clue as to who made it is the company name "Cambridge Silicon Radio Ltd.", which is listed as the manufacturer for the "Generic Bluetooth Radio" under the Hardware tab in the Bluetooth Devices section of Control Panel. The dongle did not come with any drivers disk. The purpose was to transfer photos from my bluetooth-enabled phone to my computer. I have purchased an unbranded USB Bluetooth dongle from eBay.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |