xpadneo module not loading correctly when connecting Bluetooth Controller about xpadneo HOT 5 CLOSED

Did you reboot the system? This sounds like the module aliases and/or udev rules may not be loaded properly.

from xpadneo.

Yes, I have rebooted a number of times. I also installed and reinstalled the driver a few times. Same result.

from xpadneo.

So I tried installing the xpadneo on my other sdcard with a cleaner RaspberryPi OS installation.
And it seems to work fine. The controller pairs, rumbles about three times, then stops.
Running jstest shows that the input events all register. I do not have any games on that installation as it is the sdcard I insert when my kids have to use the Pi for their school projects.

Linux raspberrypi 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

Thus I am thinking something is messed up on my RetroPie sdcard.
I had xpadneo v0.9.5 installed from Retro-Pie Setup. This morning I uninstalled it and installed xpadneo from git. Then the issue started. If I uninstall the git version and install the RetroPie Setup version again, the problem is still the same.
I am only able to use the controller if I completely remove xpadneo drivers by uninstalling.

Can I somehow do I "fresh" install of xpadneo? Remove every trace of it? Also reset the udev rules?

from xpadneo.

I managed to get it to work.
This seemed to be the issue:
[ 530.435937] hid_xpadneo: sion invalid for parameter rumble_attenuation

under the ~/xpadneo/ directory I ran configure.sh -r 0. I set the rumble_attenuation to 0.
rebooted and removed the device via bluetoothctl and paired it from fresh.

Started emulationstation and it detected the controller. Tested in game, the rumble at first did not work, but I then just fiddled with the rumble setting on the controller (see Gulikit KingKong2 Pro Manual) then the rumble worked.

I do not know what messed up the rumble attenuation, but it is fixed now.

from xpadneo.

I do not know what messed up the rumble attenuation, but it is fixed now.

Me neither. Maybe an artifact of an old version of the configure script caused it which had a bug.

from xpadneo.