New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no vibration over bluetooth #369
Comments
Usually, I'd say most of the symptoms can be explained by having "Steam Input" enabled. But (a) you state that it is disabled and (b) it won't affect the initial connection vibration. So let's look for some other clues:
If you used custom udev rules, please ensure that they don't affect the gamepad itself. If unsure, please post those rules. Our own rules only affect the gamepad itself. Actually, I believe v0.9.3 may fix your issues, it has fixes for both rumble throttling with 5.x firmware and SDL fixes to properly map all buttons: https://github.com/atar-axis/xpadneo/releases. You should ask AUR to bump to the latest version before trying other troubleshooting steps. |
I no longer have any custom udev rules that i've personally entered. I'll keep searching around and trying different things. Maybe i'll give it a whirl on a live usb and see if that works. If it works i can work through the differences between the 'clean' os vs one i've been working with for quite some time. Thanks a ton for your explanations and ideas! :) |
Sometimes i too got no vibration via BT, and that happen when i have new kernel update or some other package. Then i need reinstall xpadneo and all will work again. |
It must have been my distro was doing something funky. Reinstalled with vanilla arch on zen. Works perfectly as soon as I grabbed xpadneo from the AUR. Thanks a TON folks :) learned a whole lot |
Version of xpadneo
aur/xpadneo-dkms 0.9.1-1
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
properly search for the issue that i'm having to find relevant results.
Describe the Bug
While connecting over bluetooth, vibration does not work at all, not even on initial connection.
After plugging in the usb cable, all vibration works as expected.
Gamepadtester detects the controller while plugged in via usb as
"Microsoft Controller (STANDARD GAMEPAD Vendor: 045e Product: 0b12)".
After i unplug the usb cable to return to bluetooth, i get the connection vibration jingle, but nothing more.
On bluetooth, gamepadtester detects the controller as
"Xbox Wireless Controller (STANDARD GAMEPAD Vendor: 045e Product: 02e0)"
Steps to Reproduce
Expected Behavior
Vibration no different than plugged in via usb
Screenshots / GIFs / Videos
System Information
Controller and Bluetooth Information
xpadneo-btmon.txt
xpadneo-dmesg.txt
Additional Context
Aside the vibration, the controller works great over bluetooth. no disconnects, connects quickly.
Having previous issues with a t-rudder controller - could it possibly just be udev issues? The 60 rules are in place at the moment from install.
steam input checkboxes are all unchecked.
The text was updated successfully, but these errors were encountered: