2 Controllers detected when emulating controller in hidraw mode

[markubiak]

Here's my issue: I use hidraw mode on Arch Linux, which is fine because BlueZ is new enough. My main problem is that, when paired over bluetooth, 2 controllers are created by the system. Here is Dolphin Emulator's controller configuration page using raw bluetooth mode: and under hidraw mode: Now, this may not seem to be an issue, but in Borderlands 2, it crashes the entire game. Yup. Pretty bad bug, and I much prefer hidraw mode (by the way, you should submit a kernel patch for led support when you get the chance). I'll see if I can find a workaround for Borderlands, but the long term solution would be to solve this double controller nonsense. Yay linux.

[benmoran56]

For Dolphin and Borderlands 2, it's not necessary to use ds4drv anymore. Just pair them normally, and stop ds4drv. In Dolphin, the only thing you have to do is manually choose the axis for "Triggers", since the kernel driver creates button inputs and axis for the triggers. For Borderlands 2, just lauch it from within Steam Big Picture mode one time, and it will inherit the correct controller config.

Personally I only use ds4drv when necessary (to emulate x360 controllers), and only then in raw mode. Normally I just use the native kernel driver these days, since most games are using SDL2 and don't need to emulate the xbox controller anymore.

[markubiak]

Ah, thank you very much! It works wonderfully!

Regardless, I like using ds4drv quite a bit, I got used to the profiles and trackpad... If we could get this fixed, then maybe I could use it full-time!

[benmoran56]

I just wanted to comment here, since this report is still open: I came across a comment from someone a while back that found a workaround to this problem. The initial roadblock is that it's not possible to delete the original hidraw device. However, the user discovered that he could simply copy the new virtual one over top of the original, so that it was no longer picked up by applications. I haven't looked into it at a technical level, but it sounds like a feasable solution.

[Mernst1]

Have the same problem. A lot of games especially for games from steam but also for some emulators. There is no input recognizable i think because it grabs the wrong one "wireless Controller"

[Ryochan7]

Another workaround that can probably be used is to change the permissions on the system created evdev device after grabbing it in order to disable all read access for new processes. That way, no application launched after ds4drv will have access to that device. Running chmod 000 <device> is a workaround that comes in handy under various circumstances. You can always reset the file permissions if you want to undo the change and allow other applications to have access to the device again; that probably wouldn't be desired in this case though.

[Mernst1]

I tried the workaround above. It's really working when I change the permissions on the real hidraw evdev device. The bad thing is that you always must repeat this steps to work again, when you disconnect the controller. Can someone maybe tell me how I can create a udev rule that always writes the permissions to 000 when the controller plugs in or gets connect. Or is this a bad idea?

[Ape]

Closed as a duplicate of #45.