Reconnect an Android controller in RetroArch without losing the player port
Pause first, reconnect the same controller in Android, then verify its RetroArch device index and Port 1 Controls assignment before touching a game remap. If Android does not report the device, RetroArch cannot repair it. If the device returns under a new index, reselect it for the intended port and test navigation plus one authorized game before saving any profile.
Do this in order
- 01
Pause and record package, core, connection type, controller name, player port, device index, and whether Android still shows the device.
- 02
If Android lost it, reconnect USB or Bluetooth there first; do not save a new RetroArch profile while the OS device is absent.
- 03
Return to Settings > Input and confirm the controller appears, then inspect the device index assigned to the intended port.
- 04
In Quick Menu > Controls, confirm the port maps to the intended RetroPad and that an old game remap did not swap it.
- 05
Test menu navigation, directions, one action button, hotkey isolation, and the touch overlay if it remains enabled.
- 06
Cold-reconnect once, repeat the same test, and save only the narrow remap or autoconfig change that proved necessary.
Decision and diagnostic table
| Observation | Layer | Next check |
|---|---|---|
| Absent in Android | OS/transport | Reconnect or re-pair |
| Present, wrong player | Device index/port | Reselect port device |
| Menu works, game wrong | Core remap | Inspect Quick Menu Controls |
| Buttons trigger menu | Hotkey binding | Repair hotkey enable binding |
Reconnection can change enumeration
A controller can return with the same visible name but a different device index. Port assignment, autoconfiguration, and per-game remapping are separate records.
Touch is a useful control
Keep the overlay available during diagnosis when practical. If touch drives the game while the physical pad only drives menus, the content and core are running and the fault is in the controller mapping path.
Save after a cold repeat
A one-session repair may vanish after Bluetooth sleep or app restart. Repeat the physical reconnection before persisting a profile.
Use only games, firmware, artwork, music, and media you created, dumped lawfully, or received under permission covering your use. Emulator compatibility does not grant content rights; never use an unauthorized ROM, BIOS, CHD, media pack, or mirror.