Most gamepads work on the Android Loudplay app — Xbox controllers, PlayStation controllers, generic XInput pads, all detected automatically. If yours isn't being seen by the game, the fix is usually about when you connect it, not what you connect.
The single most useful tip
Connect or reconnect the gamepad during an active session, not before.
If you connect the gamepad before starting the session, the streaming protocol sometimes initialises without registering the controller properly. The game then doesn't see your inputs even though Android does.
Procedure that works reliably:
- Start the Loudplay session, get to the Game Catalog or game.
- Connect the gamepad (Bluetooth pair, or plug in USB).
- Wait 2–3 seconds for the device to register.
- Press a button — the virtual PC should respond.
If it doesn't respond, briefly disconnect and reconnect. The first reconnect during an active session almost always fixes it.
What's supported
- Bluetooth gamepads — Xbox Wireless Controller, DualSense (PS5), DualShock 4 (PS4), 8BitDo Pro 2, most generic Bluetooth pads. They all appear inside the virtual PC as Xbox controllers, regardless of the actual brand. Games that support Xbox controllers see them; games that look for specific PS-button glyphs may show Xbox prompts.
- USB gamepads via USB OTG — if your phone supports USB OTG (most modern Android phones do), you can plug in a wired Xbox or generic USB controller through an OTG adapter. Same caveat: connect during the session.
- Multiple gamepads — if you connect two pads, the virtual PC sees them as one controller. We don't currently support local multiplayer with two distinct controllers.
What's not supported
- Racing wheels (Logitech G29, Thrustmaster, Fanatec) — the streaming protocol doesn't pass through wheel and pedal axes correctly. Same for force feedback.
- Flight sticks and HOTAS systems (Thrustmaster Warthog, etc.) — same reason.
- Side mouse buttons. Mice work as keyboards/mice fine, but the side buttons (back/forward) aren't passed through the protocol.
- Vibration / rumble. Most gamepads connect for input only. Force feedback is hit-or-miss depending on the protocol — assume it won't work.
- Native triggers as analog axes. L2/R2 work as buttons; the analog pressure value isn't always passed through. This affects driving games particularly.
Bluetooth pairing — common problems
Phone says paired but game doesn't see input. Most often this is the "connected before session" issue above. Disconnect, start session, reconnect.
Pad keeps disconnecting. Bluetooth gamepads have a battery; they sleep when idle and sometimes don't wake fast enough for the streaming protocol to keep them. Make sure the pad is charged. If the issue persists, try a USB OTG connection instead — wired is more stable.
Two paired pads, app uses the wrong one. Android's Bluetooth gamepad handling is system-level. Open Android Settings → Connected devices → forget the pad you don't want, then re-pair only the one you want for this session.
Xbox Wireless Controller refuses to pair. The original Xbox Wireless Controller (with the older non-Bluetooth dongle) doesn't pair with Android over Bluetooth. The Xbox Wireless Controller series 2 (Xbox One S+) does. If you have the original, you'll need a USB OTG cable instead.
Testing the gamepad outside Loudplay first
If you're not sure whether your gamepad works on Android at all, install Gamepad Tester (free, on Google Play) and check that all buttons and axes register. If they don't show in Gamepad Tester, the problem is between the pad and Android — solve that first before bringing Loudplay into the picture.
On Desktop, gamepads "just work"
This article is Android-specific because Android is where pairing complexity lives. On Desktop (Windows, macOS), connect the gamepad to your computer the same way you would for any local game — Loudplay passes the input through without needing to be told.