I also did some USB packet capturing using Wireshark.
When reconnecting a paired remote which I turned off and back on again within the same session, I get:
Rcvd Connection Request (HID-Control, SCID: 0x0054)
Sent Connection Response - Success (SCID: 0x0054, DCID: 0x0040)
followed by a bunch of communication
while after an emulation restart with the same genuine remote I get:
Rcvd Connection Request (HID-Control, SCID: 0x0057)
Sent Connection Response - Refused - security block (SCID: 0x0057)
I would be willing to share whole captures aswell but it looks like there is no more useful information in there as the connection is promptly refused.
I was able to get it working.
I blacklisted the btusb driver which blocked the driver from loading between emulation restarts.
My guess is that loading the driver and having the OS access the module changed the remembered devices somehow.
I tested this on two systems and it fixed the problem on both.
Remotes are now remembered across restarts of Dolphin as well as System Restarts.
This of course has the downside of all USB BT devices not receiving a driver now so a more fine-grained approach would be preferable.
I tried some things with udev rules but so far I have not found a working solution.
(07-31-2022, 07:35 AM)TheOnly1IKnow Wrote: [ -> ]I was able to get it working.
I blacklisted the btusb driver which blocked the driver from loading between emulation restarts.
My guess is that loading the driver and having the OS access the module changed the remembered devices somehow.
I tested this on two systems and it fixed the problem on both.
Remotes are now remembered across restarts of Dolphin as well as System Restarts.
This of course has the downside of all USB BT devices not receiving a driver now so a more fine-grained approach would be preferable.
I tried some things with udev rules but so far I have not found a working solution.
Hi TheOnly1IKnow, just chiming in to concur with everything you've said to this point. I'm also using a real Nintendo Bluetooth module with passthrough and have been having the same trouble with getting the devices to stay paired on Linux using 5.0-16380.
I've also confirmed that blacklisting the `btusb` kernel module fixes the problem, but like you mentioned this prevents other Bluetooth adapters from working as well, so sadly it's not a permanent solution for me either.
I'm going to spend more time trying to find a solution or workaround after work today, but wanted to post in the meantime so that any devs who may be browsing here can see that the issue may be widespread for Linux users.
Let me know if there's any additional info I can share or troubleshooting steps I can take which might help illuminate this issue!