Send rumble to the controller, not the phone

Browse Source

Rumble always went to the phone's own motor: the vibrator lookup asked
the system service and never considered the connected pad. On a handheld
that is the wrong motor outright, and on a phone-plus-controller setup it
buzzes the device sitting in a dock while the pad in hand stays still.

Prefer the first connected gamepad or joystick reporting a working motor,
falling back to the phone. The target is resolved per state change rather
than cached for the pump's lifetime, so connecting or disconnecting a pad
mid-session moves rumble with it; the motor that was last started is
tracked separately so unplugging mid-rumble cannot leave one buzzing.

Add a 'Vibrate the phone' toggle gating only that fallback, so playing on
a pad need not mean the phone rumbles along with it. Touch haptics stay
on the phone deliberately -- the finger is on the phone's screen.

Closes #89

...

This commit is contained in:

jpolo1224

2026-08-23 01:39:03 -04:00

parent daed55c427

commit 06b33abf27

10 changed files with 105 additions and 16 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

3rdparty/discord-rpc/discord-rpc

Vendored

+1 -1

Submodule 3rdparty/discord-rpc/discord-rpc updated: fb04b1766b...3dc2c326cb

3rdparty/libsdl-org/SDL

Vendored

+1 -1

Submodule 3rdparty/libsdl-org/SDL updated: 147a8ee32d...f87239e71e