Android must expose gamepad input
GBA Play recognizes non-virtual gamepad or joystick devices reported by Android. It handles button and directional events from suitable controllers, whether the connection is Bluetooth or a supported physical connection.
The connection type alone does not prove compatibility. A controller using an incompatible mode may pair successfully while producing no usable gamepad input. There is no verified model-by-model list or supported-device count to publish yet.
What the app handles
- Game buttons
- A, B, L, R, Start, and Select, using standard Android button codes by default. Printed labels on a pad may differ from the action received by the app.
- D-Pad
- Directional key events and hat-style horizontal/vertical axes.
- Left stick
- Horizontal and vertical input converted to digital directions, including diagonals. Small movements below the app’s threshold are ignored.
- Optional shortcuts
- Fast Forward, Quick Save, Quick Load, and Menu can be assigned to controller buttons. They start unassigned.
Keep mapping expectations specific
Button Mapping stores one global mapping shared by connected controllers. It is not a separate saved profile for each controller model.
The remap flow captures button presses. The current directional motion handler reads the left stick and hat axes; this does not establish support for arbitrary right-stick or trigger-axis remapping.
Check the pad you already have
- Connect through Android and look for the device name in Settings → Controls → Controller.
- Test the default directions and game buttons in a safe moment.
- Remap a button if needed, then confirm each assignment independently.
- Test optional shortcuts only after preserving important progress.
Use the pairing and mapping guide for exact app steps. If a connected pad does not respond, follow the controller troubleshooting sequence.