BT Passthrough, LIBUSB_ERROR_NOTSUPPORTED on two bt dongles

[mashakos]

As the title says. Have two bluetooth dongles, 
A generic CSR dongle from 2010
A new UGreen CSR8510 A10 dongle

Tried the ugreen dongle first with libusbk driver using the wiki guide. Libusb error. 
Decided to try winusb. Deleted sysconf  in dolphin folder, deleted libusbk driver, unplugged dongle, put back in to perform winusb driver replace etc. 
Converted PID and VID (0A12,0001) to decimal (2578,1) added to dolphin ini. Same result surprisingly, libusb error

Assumed it was the dongle so used an old dongle that I know can work as a libusb dongle with ScpToolkit
Same result, libusb not supported error

Is there no hope, or have I missed something? 

[mbc07]

Something is wrong. We have a lot of test results for CRS8510 based dongles and they indeed work. Make sure you're using libusbK driver and also make sure that ScpToolkit and similar apps are stopped before booting Dolphin...

[mashakos]

Is there a way to enable more detailed logs? I pretty much closed all input related processes/services but no luck

[mbc07]

You can enable Dolphin logs (View => Show Log and View => Show Log Configuration), but I'm not sure if it'll have relevant BT Passthrough info as it's failing super early on the boot process for you. LIBUSB_ERROR_NOTSUPPORTED on Windows means Dolphin is failing to get access to the BT Adapter (e.g. other program are using it or no BT Adapters with libusb drivers were detected).

By the way I'm currently using an Orico BTA-403 (which also uses CSR8510 chip) with libusbK and it's working fine here. Perhaps try running Dolphin as Administrator?

[mashakos]

this is what I'm seeing on log

06:27:308 core\ios\usb\bluetooth\btreal.cpp:109 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:1d26: LIBUSB_ERROR_NOT_FOUND
06:27:308 core\ios\usb\bluetooth\btreal.cpp:109 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:1d2d: LIBUSB_ERROR_NOT_FOUND
06:27:308 core\ios\usb\bluetooth\btreal.cpp:109 E[IOS_WIIMOTE]: Failed to get config descriptor for device 1b21:1042: LIBUSB_ERROR_NOT_FOUND
06:27:308 core\ios\usb\bluetooth\btreal.cpp:109 E[IOS_WIIMOTE]: Failed to get config descriptor for device 1b21:1042: LIBUSB_ERROR_NOT_FOUND
06:27:308 core\ios\usb\bluetooth\btreal.cpp:109 E[IOS_WIIMOTE]: Failed to get config descriptor for device 1b21:1042: LIBUSB_ERROR_NOT_FOUND
06:27:308 common\msghandler.cpp:92 E[MASTER]: Warning: Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED
06:28:344 common\msghandler.cpp:92 E[MASTER]: Warning: Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED
06:28:747 core\ios\usb\bluetooth\btreal.cpp:126 N[IOS_WIIMOTE]: Using device 0a12:0001 (rev 8891) for Bluetooth: CSR8510 A10

EDIT: I assume that the libusb error is for non bluetooth devices mistakenly being pinged, as dolphin runs games with passthrough enabled and the ugreen dongle. Sync doesnt work tho. That is, full sync with red button on back of wiimote while a game is running and hitting sync in controller options

[mashakos]

a few answers to some questions I should have mentioned:

Quote:[color=#000000] Perhaps try running Dolphin as Administrator?[/color]

I am testing this on a windows 7 partition with Admin as the main user. I have also unblocked all dll/exe files in the dolphin directory. No antivirus other than windows defender and dolphin folder is set as exempt

Quote:other input/HID applications I'm using?

DS4windows, SCPtoolkit, Whiteknight Autowhitelister, XOutput

Of the above only SCPToolkit and autowhitelister have services, the rest are exe processes. Closed/stopped all of them before testing dolphin

Quote:what are the devices that are getting failed descriptor in your log?

devices 8086:1d26 and 8086:1d2d are my motherboard's chipset USB2 Enhanced Host Controllers
the device 1b21:1042 is a 3rd party ASM1042 SuperSpeed USB Host Controller in the motherboard
to add: I think of myself as fairly adept at unpacking issues and finding the root cause but this time I'm stumped! 

[mashakos]

update:
So I moved the usb dogle from a port on my motherboard to a 4 port usb hub and now wiimotes pair
the only problem is that pairings are not remembered after I exit out of dolphin. so I have to open up each wiimote hit sync and use the sync button on dolphin every time I start a game

[mbc07]

Whether pairings will be remembered or not is completely dependent of your particular BT Adapter, some remember, most don't...

[mashakos]

(12-18-2019, 02:05 PM)mbc07 Wrote: Whether pairings will be remembered or not is completely dependent of your particular BT Adapter, some remember, most don't...

so, made a strange discovery. I have two wiimotes, a 1st gen white one with a motion plus dongle and a TR gen black one. I favour the black one so tested pairing with it and every time I tr to launch dolphin and pair the TR when a game just starts? nothing. but! If I try to pair the 1st gen wiimote first it pairs, whats even weirder is that after the 1st gen pairs the TR wiimote pairs! So pairings are remembered but I have to pair the older 1st gen wiimote first to get both working then switch their positions in the ingame wi home menu.

Is that a common thing?

[mbc07]

I wouldn't say it's common, but it's somewhat expected given how identical adapters can have wildly different results. I mean, look at how many CSR8510 test results we have on the wiki, some works perfectly while others barely work, there's even cases of a BT Adapter supporting only BT 2.1 while others support BT 4.0 even through they all share the same chip...