Emulator

Thanks for trying to reproduce. It is a bit disappointing that you didn't succeed :-)

I'll double check at my side and get back to you soon. (within a couple of days)

Ok, here is some news.

I have updated bluez to 5.10 and after that removed dolphin from the system (checked with updatedb; locate dolphin). Next I downloaded latest trunk and compiled and installed dolphin again.

In /var/log/messages the bluetooth daemon doesn't complain anymore.

Still, dolphin doesn't find any compatible device. I tried:

• bluetoothd not running
• bluetoothd running, but device not paired and not connected
• bluetoothd running, device paired, but not connected
• bluetoothd running, device paired, connected and trusted

What is the advised way to connect?

In the last option, /var/log/messages logs:

Oct 16 20:47:59 localhost kernel: input: Nintendo Wii Remote Accelerometer as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/bluetooth/hci0/hci0:21/0005:057E:0306.0007/input/input27
Oct 16 20:47:59 localhost kernel: input: Nintendo Wii Remote IR as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/bluetooth/hci0/hci0:21/0005:057E:0306.0007/input/input28
Oct 16 20:47:59 localhost kernel: input: Nintendo Wii Remote as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/bluetooth/hci0/hci0:21/0005:057E:0306.0007/input/input29

Isn't it possible to have dolphin search and use those devices as input for real wiimote controller?

I have more or less the same issue. Dolphin used to work with my noname wiimotes, but since the last gnome and dolphin update (moved to bluez 5), it doesn't work anymore. I don't know what changed, but just wanted people to know that this is probably not an isolated case.

Unpair the device from the system. I thought dolphin paired it a different way o_O

I already tried that. Actually, the way it used to work was with the device unpaired and the bluetooth service stopped. It's doesn't work anymore.

Just to be sure, I tried it again: not paired, no bluetooth daemon running. No luck.

It is a pity that I don't have original wiimotes.

In my opinion, things are different now with bluez5 and the new in-kernel driver. As posted before, for one wii mote 3 new devices are created. I believe that dolphin should make use of that.

Today I got an original wiimote and tried to use it. Using dolphin 4.0-305. Stopped bluez daemon, set wiimote to real wiimote and started scanning. Pressed button 1+2 at the same time.. wiimote not found.

I have also tried with bluez daemon running, and I have also tried with user root.

Downgraded bluez5 to bluez4 and recompiled dolphin-emu-3a28afd8d5d5.

bluetooth daemon running + original wiimote: works!

no bluetooth daemon running, or with 3rd party wiimote: no wiimote found.

I'm having this issue as well, even with first party wiimotes. I'm running the latest git build of dolphin, the latest bluez in the official arch repo (tried with the bluetooth service running and not running), and dolphin just shows.

I can connect my wiimote manually but that doesn't work. My computer seems to treat the wiimote like a keyboard, assigning keyboard buttons to each wiimote button. It doesn't work at all in Dolphin.

I would try using bluez4 but I can't compile it. The configure script can't find my copy of DBUS even though it's installed.

Let me clarify this with a screenshot, just in case my explanation wasn't clear.

For me it works fine nowadays with bluez 5.

I'm running Gentoo Linux, bluez 5.18, latest git build of dolphin and using 2 official wiimotes with motion plus inside.

This is what I needed to do:

1. make sure bluetooth dongle is running in hci mode (and not HID). You can verify with lsusb or read your dmesg output. There is a tool hid2hci that can be used to switch to hci. For my current dongle I had to apply this patch: http://comments.gmane.org/gmane.linux.bluez.kernel/42209 (for my previous dongle it was important to have atheros firmware in /lib/firmware, by default it was already in hci mode).

2. first compile bluez, then compile dolphin.

3. do not run the bluez daemon.

4. check if the device is available: "hcitool dev". If not, power on the bluetooth dongle: "hciconfig hci0 up".

5. startup dolphin, configure wiimote and enable scanning

6. press buttons 1+2 together to connect the wiimote to dolphin

Thank you so much, it works now! What I was missing is "hciconfig hci0 up" to turn the device back on after shutting down the bluetooth service.

Thanks again!

I can confirm the issue and with latest git disabling bluetooth service and manually turning on "hciconfig hci0 up" does the trick. With latest stable my rev.20 wiimote+ doesn't work at all no matter if above steps have been done.

Please add bluez5 support!
openSUSE 13.2

Sorry for another comment but I guess soon all Linux distributions will be affected by this issue why is the issue "questionable"?

At least a workaround is available.

ps: Thanks for the program, I love dolphin-emu!