Closed Haxorzz closed 3 months ago
Previously hidraw5 had correct permissions (still showed xbox 360)
The controller should not expose any hidraw permissions to user-space, this is currently incompatible with SDL and Steam Input. xpadneo shows all controllers as Xbox360 controllers, that's normal and not an issue.
but after using the git version, now hidraw5 is almost forced to have wrong permissions (user has no rw) after the controller connects?
Yes, this is intended behavior.
After connect, the controller should only play a short rumble. If it doesn't, some quirk flags may be needed for motor masking and/or pulse parameters. Unload the module and try loading the module with
rmmod hid-xpadneo && modprobe hid-xpadneo quirks=98:b6:ea:4a:21:a4+7
Does it fix rumble? You can confirm the quirk flags via dmesg output (it should change from 0x00000083
to 0x00000087
. You already tried that before according to your report, but the quirks flags were wrong. So please double-check you've put the options correctly, and it's not set twice with different options. You controller OUI should already default to quirks 7 with the version of xpadneo you're using.
If you actually want to run with hidraw, do not use xpadneo. The controller will be supported via hid-generic and hidraw in SDL. Even if hid-generic won't support rumble, rumble is provided via hidraw in SDL. This would also fix the cosmetic issue with the controller being shown as "Xbox 360 controller". The downside is: Non-SDL games probably won't support rumble.
There's a test program for hidraw in misc/examples/c_hidraw
: run make
to build it (ncurses-dev is needed), then run it as root and the dev-path of your current hidraw device. It will open a simple GUI for programming and sending raw rumble commands to the controller. Try playing with the parameters to find which one your controller ignores.
Version of xpadneo
v0.9-168-gbe25f7b
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
Steps to Reproduce
(Android mode or X-input mode) Pair Gulikit kk3 max to computer Open steam -> settings -> controller Controller classified as an xbox 360 controller (X-input mode only) Pair gulikit kk3 max to computer As soon as connection is made, controller won't stop vibrating setting quirk 7 to controller's mac address does not apply/does not work (x-input mode only)
Expected Behavior
Controller is detected as a modern controller in steam Controller does not vibrate forever (x-input mode only)
System Information
Controller and Bluetooth Information
xpadneo-btmon.txt
xpadneo-dmesg.txt
no dongle = no lsusb entry
Additional Context
Running the controller on firmware 3.8 Previously hidraw5 had correct permissions (still showed xbox 360), but after using the git version, now hidraw5 is almost forced to have wrong permissions (user has no rw) after the controller connects?