mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2024-11-15 22:09:19 -07:00
e9a696b160
There seems to be a race condition between a peripheral device connecting to the bluetooth controller and it being ready to use. It's very short and it depends upon the controller, some appear to connect synchronously and block until the device is ready, others report the device upon discovery but do not allow communication straight away. I don't know which is the correct behaviour, or whether it depends on the peripheral, controller or both. Anyway, Dolphin waits for a remote to appear and immediately attempts to open the communication channels, this can fail because the device isn't ready yet, delay, try again, and it works. There are other (unlikely) chances the device is busy at random moments after this initial race condition so it loops around try to reconnect. This was inspired by an earlier patch, see here: https://bugs.dolphin-emu.org/issues/5997#note-20 I can confirm that it works perfectly for me on a bluetooth controller where otherwise it's impossible to connect (Dell 380 Bluetooth 4.0). |
||
|---|---|---|
| .. | ||
| Android | ||
| Core | ||
| DSPSpy | ||
| DSPTool | ||
| PCH | ||
| UnitTests | ||
| VSProps | ||
| .clang-format | ||
| CMakeLists.txt | ||
| dolphin-emu.sln | ||