Why doesn’t rumble work when I stream my PC, and how do I get it back?

The game is on the TV, the pad is in your hands, and nothing shakes. Hits, engines, footsteps — the whole tactile layer is gone, and a racing game without it feels like driving on ice.

Or it half works: one dull buzz for everything, no difference between a trigger and the body, no force on the wheel.

You have tried the settings on both ends and the answer is always the same shrug: the streaming app does not do that, or does it only for one kind of pad.

Rumble is a command the game sends to the controller’s driver. In a stream that emulates a pad, the command lands on a virtual pad on the PC; some clients relay a simplified version of it back to the phone, others relay nothing. Trigger motors and force feedback need the real driver and are lost either way.

And there is a second catch with Bluetooth that nobody puts on the box: a pad can only vibrate over Bluetooth if its firmware exposes a motor to Android. Many pads — including plenty of third-party and Xbox-licensed ones — expose none. When that happens, what other streaming apps call “rumble” is the **phone’s own motor** buzzing in your hands; the pad itself stays still.

Over USB, ChimpDeck forwards the physical device, so the driver is the real one and the motor commands go back over the same link to the actual motors: left trigger, left body, right body, right trigger, each addressed on its own, with pressure-driven trigger feedback and force feedback on wheels. Over Bluetooth, ChimpDeck emulates like the others; pad rumble where the pad allows it, plus haptics on the phone, is about to launch.

1. 01

   Plug the pad in over USB

   USB into the phone, tablet or TV box running ChimpDeck. This is the whole fix: over USB the pad is the real device on the PC; over Bluetooth it is a virtual Xbox 360 pad with no rumble return today (Bluetooth rumble is coming soon).

2. 02

   Test the four motors

   Gamepad tools → rumble runs the left trigger, left body, right body and right trigger one by one, with patterns. A motor that never answers is a pad fault, not a streaming one — the other tools live in the same place.

3. 03

   Check the game sees the real device

   With the real driver loaded on the PC, games send their native rumble and trigger effects. If the game does not see the pad at all, start here.

4. 04

   Wheels: force feedback follows

   The same forwarding is why a racing wheel keeps its force feedback: the game talks to the wheel’s official driver.

5. 05

   Know the Bluetooth trade-off

   If you must go wireless, the pad still plays. Pick the Xbox identity on the PC for the right prompts; the PlayStation identity has no rumble return either, and the app says so. More Shield-side checks here.

• Four motors, addressed one by one

  Left trigger, left body, right body, right trigger, with pressure-driven trigger feedback.

• Force feedback on wheels

  The game talks to the wheel’s official driver, so every force it sends reaches the motor.

• A rumble test on the device

  Each motor on its own, with patterns, before the game starts.

• No extra software

  The pad uses its own official driver on the PC; nothing to install for rumble.