Controllers, Touch Overlays, Gyro Aiming & USB-C OTG Input on Android Ports

How Native Android Ports Handle Input Under the Hood

Unlike console emulators that force every game through a single generic virtual controller pad, native Android game ports wire input directly into the game’s internal action system. Most community decompilations, static recompilations, and source ports on Android use SDL2 (libsdl2.so) or Android’s Native AInputEvent / GameActivity API to poll touchscreens, physical gamepads, inertial measurement unit (IMU) gyroscopes, and hardware keyboards.

On every game page in the DroidPorts catalog, the Controls & Input specification panel breaks support down into four distinct capabilities:

1. On-Screen Touch Overlay
2. Bluetooth & USB-C Native HID Gamepad
3. Gyroscope Motion Aiming
4. Mouse & Keyboard (Bluetooth / USB-C OTG)

Understanding how each input pipeline works helps you eliminate input latency, fix swapped A/B buttons, and choose the right control scheme for each genre.

1. USB-C Direct Controllers vs. Bluetooth Gamepads: Input Latency Breakdown

Physical gamepads connect to Android devices through one of three hardware paths, each with a measurable difference in polling interval and end-to-end button-to-photon latency:

Fixing Bluetooth Controller Lag on Android

If you notice sluggish analog stick response on a Bluetooth controller (particularly Nintendo Switch Pro controllers or older 8BitDo firmware), check two common culprits:

• Input Mode Selection (X-Input vs. D-Input vs. Switch Mode): On 8BitDo and GameSir Bluetooth controllers, always pair in X-Input (Xbox) mode (Start + X on 8BitDo) or D-Input (Android) mode (Start + B) rather than Nintendo Switch mode. Android’s Bluetooth stack negotiates faster HID connection intervals with Xbox/Android profiles than with Switch Pro profiles.
• Bluetooth Audio Coexistence: Using legacy SBC Bluetooth earbuds simultaneously with a Bluetooth controller shares the same 2.4 GHz radio time-division scheduler on older phones, which can double gamepad jitter. Switching to wired USB-C controls or low-latency 2.4 GHz dongle earbuds eliminates radio contention.

2. SDL2 gamecontrollerdb.txt and Fixing Swapped A/B & X/Y Buttons

Android handhelds and controllers are split between two physical face-button conventions:

• Xbox Layout (West = X, North = Y, South = A, East = B): Used by Xbox controllers, Backbone One, Razer Kishi, and Steam Deck.
• Nintendo Layout (West = Y, North = X, South = B, East = A): Used by Nintendo Switch controllers, 8BitDo SN30 Pro, and by default on many retro handhelds (Retroid Pocket and AYN Odin).

Why Buttons Sometimes Swap in Native Ports

SDL2 identifies physical buttons by positional semantics (SDL_CONTROLLER_BUTTON_SOUTH is always the bottom face button, and SDL_CONTROLLER_BUTTON_EAST is always the right face button) using an internal database of controller GUIDs (gamecontrollerdb.txt).

When you toggle the system-wide controller style on an AYN Odin 2 or Retroid Pocket between Xbox mode and Retro / Nintendo mode, the handheld changes the Android keycodes emitted by the South and East buttons (KEYCODE_BUTTON_A vs. KEYCODE_BUTTON_B):

• In Ship of Harkinian and 2Ship2Harkinian: Open the in-game Enhancements > Controls or Controller Mapping menu (accessible via the top-left corner tap or Select/Minus button) and bind the N64 A, B, and C-Buttons directly to your preferred physical positions.
• In SDL2 Source Ports (OpenMW, DevilutionX, Sonic Mania, Hollow Knight): If confirm/cancel feels inverted, either flip your handheld’s quick-settings tile from Retro to Xbox while playing that port, or drop an updated gamecontrollerdb.txt file into the port’s data directory if your newer USB-C controller GUID is not recognized by an older APK build.

3. Native Gyroscope Motion Aiming

One of the standout advantages of native Android ports over console emulators is 1:1 gyroscope motion aiming.

In a traditional console emulator, mapping a phone’s gyroscope to a virtual analog stick feels floaty because the emulator must convert angular velocity into a clamped 8-bit joystick deflection value, complete with the original game’s deadzone and acceleration curve.

In a native port with built-in gyro support (such as Ship of Harkinian, 2Ship2Harkinian, Delta Touch / GZDoom, Quad Touch / Quake, idTech4A++, and Half-Life 2), SDL2 reads your device’s 3-axis MEMS gyroscope sensor (SENSOR_TYPE_GYROSCOPE) at up to 200 Hz and feeds raw angular delta radians directly into the camera yaw and pitch matrices, just like mouse look on a PC.

Recommended Gyro Configuration for Handheld & Phone Play

1. Combine Right Stick + Gyro: Use the right analog stick (or touch swipe) for broad 90-degree turns, and use subtle wrist tilts for precision reticle adjustments (such as bow aiming in Ocarina of Time or railgun shots in Quake).
2. Enable “Gyro Only When Aiming” (Where Supported): In Zelda and Metroid ports, setting gyro to activate only when holding Left Trigger (Z-Target or First-Person Aim) prevents involuntary camera drift during normal platforming.
3. Roll vs. Yaw Axis: When holding a phone or handheld horizontally in front of you, turning the screen left/right like a steering wheel corresponds to the sensor’s Roll axis, whereas pivoting flat corresponds to Yaw. Modern ports combine both axes (“Player Space” or “Local Space” gyro) so aiming feels natural regardless of how reclined you are.

4. Mouse, Keyboard & Touch Overlays for Strategy and CRPG Ports

Classic PC strategy games, city builders, and isometric RPGs (Fallout 1 & 2, Morrowind, Diablo, Heroes of Might and Magic II & III, RollerCoaster Tycoon 2, Theme Hospital, and OpenTTD) were designed around high-precision mouse cursors and keyboard shortcuts.

Native Android engine recreations adapt these controls in three ways:

Direct Touch vs. Virtual Trackpad Mode

• Direct 1:1 Touch (DevilutionX, fheroes2, VCMI, OpenRCT2, Balatro): The engine rewrites the UI layout with enlarged 48dp+ hit targets so tapping directly on units, inventory slots, or dialogue choices works naturally with a finger or active stylus (such as a Samsung S-Pen).
• Relative Trackpad Touch (fo2.exe, OpenMW, Source Engine): Dragging your thumb anywhere on the screen moves the cursor relatively (like a laptop trackpad), tapping once performs a Left Click, and tapping with two fingers performs a Right Click. This prevents your finger from obscuring small loot items or dialogue lines on a 6-inch screen.

USB-C OTG and Bluetooth Mouse & Keyboard (“Desktop Mode”)

Every port marked Mouse & Keyboard: Supported in the DroidPorts catalog accepts standard USB HID mice and keyboards through a USB-C OTG hub or Bluetooth pairing.

On devices that support USB-C DisplayPort Alt-Mode (such as Samsung Galaxy S/Ultra devices with DeX, Motorola Ready For, Pixel 8/9 Pro, AYN Odin 2, and Retroid Pocket 5), you can connect your device to a 1080p/1440p monitor, pair a wireless mouse and keyboard, and play OpenMW, Half-Life 2, GZDoom, Quake, or OpenTTD as a silent, fanless desktop PC consuming less than 6 watts of power.