Vibration, motion & touchpad

Three possible reasons: the controller has no motors, Android does not expose vibration for that pad over the current connection, or the pad only accepts rumble from its own console. Device Info tells you which — if it says Vibration: Not supported, there is nothing for the app to drive. On pads that support both, USB is worth trying instead of Bluetooth.

It is a timeline editor for the two rumble motors, so you can build and feel your own patterns instead of only the fixed presets. Editing and the built-in presets are free; driving the motors with a custom pattern and saving it to My patterns are Pro.

No. Patterns and test records are stored on this device only, with nothing kept on a server. A full phone-to-phone transfer that includes app data will carry them over; a fresh install will not.

Reading a controller's gyroscope needs Android 12 or newer, and the pad has to publish its sensors to the system — in practice DualShock 4, DualSense and Switch Pro. Note that this reads the controller's sensors, not the phone's, so a pad without a gyro shows nothing even on a phone that has one.

Touchpad capture needs Android 8.0 or newer, and only pads that actually have a touchpad — DualShock 4 and DualSense — can be captured. Tap Start capture first, otherwise the touch data goes to the system instead of the app. Leaving the page releases the capture.

Yes — capture only redirects the touch surface, while buttons and sticks keep reporting as usual. It is released the moment you leave the page, so nothing stays locked to the app afterwards.