acroFPV

Android radio setup

Fly an FPV simulator on Android Chrome with an EdgeTX radio.

If Gamepad Tester sees throttle, roll, and pitch but yaw is dead on Android, the fix is usually in EdgeTX Advanced USB Joystick mapping.

What this fixes

Desktop Chrome may show all four radio axes while Android Chrome only shows axes 0, 1, and 2. In that case the cable, browser API, and radio are partly working, but Android is not exposing yaw as a usable gamepad axis.

acroFPV cannot calibrate yaw until Android Chrome exposes a fourth moving axis. Confirm the browser side first with Gamepad Tester.

EdgeTX settings

  1. Create or select a simulator model on the radio.
  2. Open Model Setup, not Radio Settings.
  3. Find USB Joystick and switch from Classic to Advanced.
  4. Set Interface mode to Gamepad.
  5. Set Circular cutout to None while testing.
  6. Map only the main stick channels as axes first. Add switches/buttons later.

Recommended axis map

Radio control Usual channel Advanced mode Axis
Roll / Aileron CH1 Axis X
Pitch / Elevator CH2 Axis Y
Throttle CH3 Axis Z
Yaw / Rudder CH4 Axis rotZ / RZ

The important Android-specific part is yaw on rotZ / RZ. Classic desktop joystick mapping can put channel 4 on a rotation axis that desktop Chrome accepts but Android Chrome may not surface.

Acceptance test

  1. Fully unplug USB from the phone and radio.
  2. Reconnect the radio to Android Chrome.
  3. Reload Gamepad Tester.
  4. Move each stick axis by itself.
  5. Confirm four axes move: throttle, roll, pitch, and yaw.
  6. Open acroFPV and run the controller wizard.

If yaw still does not move

Try Joystick interface mode

Keep the same X, Y, Z, and rotZ/RZ channel assignments, switch Interface mode from Gamepad to Joystick, then unplug and reconnect USB.

Check the radio monitor

Move yaw on the radio channel monitor. If the channel does not move there, fix the model mixes before testing Android.

Use desktop as a control test

If desktop Chrome sees all four axes and Android does not, the remaining issue is Android/browser HID mapping, not acroFPV calibration.

Keep switches out at first

Extra axes, duplicate axes, or switch channels can confuse browser mappings. Get the four stick axes clean, then add buttons later.

FAQ

Do I need a special OTG adapter?

If Gamepad Tester already sees some stick axes, the phone is already acting as a USB host. A missing yaw axis usually points to Android HID mapping, not a missing OTG adapter.

Does this work on OpenTX?

OpenTX usually exposes a fixed USB joystick layout. The Advanced USB Joystick screen described here is an EdgeTX setting, and it may not exist on OpenTX.

Should I calibrate acroFPV before Gamepad Tester shows four axes?

No. First confirm Android Chrome sees four moving axes. Then run the acroFPV controller wizard and map throttle, roll, pitch, and yaw.

Official references