Emulator Issues #13133


Issues when bluetooth headphones are connected: Wiimote fails to pair when game is running, gamecube games also hang on stop/exit when continuous scanning is enabled

Added by DevilFish303 11 months ago. Updated 11 months ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

N/A (reproducible with all Wii Games)

Game ID? (right click the game in the game list, Properties, Info tab)


MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)


What's the problem? Describe what went wrong.

When bluetooth headphones are connected, and while "Emulate the Wii's bluetooth adapter" and "Continuous Scanning" are selected, are connected I notice the following:

  • Wiimote fails to pair when in game, will pair when I disconnect bluetooth headphones
    • this does not happen when in desktop and only the dolphin GUI is open, it only happens when in game
  • Gamecube games tend to hang on stop/exit, the hang is cleared as soon as I turn off bluetooth headphones
    • this only happens when Gamecube games are launched via CLI with -b flag

I enabled logging and I did not see anything relating to bluetooth connection

What steps will reproduce the problem?

On Linux, with a single bluetooth adapter:

  1. Connect bluetooth headphones, does not matter what kind (I was able to reproduce this issue with Sony and Beats headphones)
  2. Make sure "Emulate the Wii's bluetooth adapter" and "Continuous Scanning" are selected in the controller config, set controller 1 to "real wii remote", do not attempt to pair yet
  3. Start any Wii game, as soon as you see the "Press A" splash screen, attempt to pair the wiimote by pressing 1 + 2, you should see the remote fail to pair
    • Workaround 1: disconnect headphones and try again, the wiimote should pair successfully
    • Workaround 2: pair wiimote in the dolphin GUI before launching the game, it should succeed regardless of state of the headphones
  4. To reproduce gamecube game bug, exit the Wii game, and exit out of dolphin, note that configuration from step 2 should still be set at this point
  5. Connect headphones again, when successful open a terminal and execute a gamecube game, does not matter which one: dolphin-emu -b -e <path to gamecube ROM>
  6. Play the game for a bit, maybe 10-30 seconds, now attempt to stop or exit the game with whatever hotkey you use, you will see a black screen where the game is hanging
    • Workaround 1: disconnect headphones, the window should immediately close
    • Workaround 2: wait, sometimes a somewhat ridiculous amount of time, my record is ~7 minutes, the window eventually closed, at other times it never does not until I disconnect headphones

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.


What are your PC specifications? (CPU, GPU, Operating System, more)

OS: EndeavourOS
Kernel: 6.1.1-arch1-1
CPU: AMD Ryzen 5 5600X 6-Core
GPU: NVIDIA GeForce RTX 3080
RAM: 32 GB

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

I have no other useful information, I tried bluetoothctl logging and dolphin logging with error verbosity, and everything looked normal as far as I can tell.
Did not attach dolphin logs because they are not useful, they're identical to when I play without any bluetooth headphones.

Actions #1

Updated by DevilFish303 11 months ago

  • Gamecube games tend to hang on stop/exit, the hang is cleared as soon as I turn off bluetooth headphones
    • this only happens when Gamecube games are launched via CLI with -b flag

I forgot to mention, this is only problem when launching from emulationstation

However, good news! I found a workaround, I need to just disable continuous scanning when running the ROM:

/usr/bin/dolphin-emu -b -C Dolphin.Core.WiimoteContinuousScanning=False -e <path/to/rom>

So this is pretty much a non-issue with GC, I will leave it up to you devs, however the -C (and CLI options in general) should be better documented


Also available in: Atom PDF