Bug 216218
Summary: | Nintendo Switch Pro Controller randomly disconnects with force feedback (bluetooth only) | ||
---|---|---|---|
Product: | Drivers | Reporter: | tinozzo123 |
Component: | Input Devices | Assignee: | drivers_input-devices |
Status: | NEW --- | ||
Severity: | normal | CC: | richbergert |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.18.5 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
tinozzo123
2022-07-07 23:13:48 UTC
I have the same issue, but not exclusively with my Switch Pro Controllers. The Sony DualSense has a really weird manifestation of this. The DualSense shows up in Dolphin as three controllers: Wireless Controller, Wireless Controller Motion Sensors, and Wireless Controller Touchpad. When I'm playing in Dolphin with the Switch Pro controllers with rumble on, they will disconnect after a while and need to be reconnected and refreshed. When I'm playing with the DualSense with rumble on, after a while, only the Wireless Controller Motion Sensors disconnects, while the Wireless Controller stays connected. Also interestingly, I'm using the virtualized Pointer (which emulates a Wii pointer using the motion controls). When I have rumble on, the pointer jumps all over the place when the rumble is active. I wonder if the rumble is overloading the motion sensor, sending more data than the Linux bluetooth stack can cope with. On the Switch Pro Controller, because the motion sensors are registering on the same device as the buttons, it just knocks out the whole pad. On the DualSense, because it's showing up as a different device, it only knocks out the motion sensor device. |