Android emulator controller not working
Pair the pad in Android Bluetooth settings, then check the emulator shows one device per pad instead of merging two controllers into Pad 1.
A pad that works perfectly on a PC can fail on Android for reasons that have nothing to do with the pad. Android’s input layer reports HID devices its own way: it can expose the same controller under a generic name, merge two controllers into one entry, or hand the app a stale handle after the phone sleeps. Emulators then show a “Pad 1” that ignores every button.
What you actually hit
| Symptom | Likely cause |
|---|---|
| Pad pairs in Android settings, emulator lists nothing | Emulator launched before the pad connected, or the app never sees the HID node |
| Two pads control the same player | Android reports identical descriptors, so both land on Pad 1 |
| Worked once, dead after sleep or reconnect | The device handle was not re-acquired on resume |
| Wired pad will not map on a tablet | USB host / OTG not enabled or a charge-only cable |
| Pad appears under a generic name like “Xperia Play” | Android’s input layer is reporting a shared descriptor |
Fix the common cases
-
Prove the pad works outside the emulator firstPair it in the system Bluetooth menu and press buttons in any browser gamepad tester. If the system cannot see the inputs, no emulator setting will help — re-pair the pad and clear the old pairing entry on both sides.The system test page lights up for every button and stick.
-
Connect the pad before launching the emulatorMost Android emulators enumerate input devices when the activity starts. A pad connected mid-session may never appear until you restart the app. Connect, then open the emulator.The pad's real name appears in the emulator's device list, not "none".
-
Check the emulator's own device list, not the gameIn PPSSPP use the control settings' analog and button test; in RetroArch open Settings, then Input, then Port 1. This tells you whether the emulator sees the device at all, which is a different question from whether the game binds it.Pressing a button highlights the matching entry inside the emulator's input screen.
-
Separate pads that collapse into oneWhen two controllers both drive Player 1, unpair the unused one or assign players explicitly instead of relying on auto-detect. This is a known Android reporting quirk, tracked upstream rather than caused by your pad.Each connected pad moves only its own player.
-
Fix wired pads on tabletsEnable USB host / OTG if the tablet has the option, swap to a cable that carries data rather than charge only, and accept the Android USB permission prompt. A pad that never triggers the prompt is usually the cable.The pad appears in the system input list after plugging in.
Tracked issues, not your setup
These are open or closed reports that match the symptoms above — worth checking before you spend an hour reinstalling:
- Xbox Series X/S pad reported not working on Android: PPSSPP #14617
- Switch Pro pad only partly working: PPSSPP #13027
- Two different pads read as the same “Pad 1”: PPSSPP #18602
- Wired pad cannot be mapped on a tablet: PPSSPP #21056
- Bluetooth pad on Android 11: PPSSPP #16158
- Every Bluetooth pad shows up as the same “Xperia Play”: RetroArch #18348
If your pad model is not listed, report it with the Android version, the pad’s Bluetooth name as Android shows it, and the emulator build — that trio is what maintainers need.
If the pad is fine but the screen buttons fight it
Physical pads and on-screen touch controls are two separate mapping layers, and changing one does not change the other. See touch control mapping on Android for that side. Pad connected on a PC instead? That is a different input stack — start with Xbox controller connected but not working. Running Switch titles on the phone? The platform caveats are in running Switch games on Android.