Before you begin

These steps describe the Universal Controller update, built and checked on 4 October 2026. Google Play publication of this update has not been confirmed. If your installed game does not show these controls, check its version and the update status.

Touch controls remain available. For physical input, use a device that Android exposes as a joystick, gamepad or keyboard, or one of the supported Wi-Fi paths. A connected name alone does not establish usable input.

1. Connect and select a device

Connect a USB data cable through a supported phone USB-host/OTG connection, pair a Bluetooth controller in Android settings, or connect a supported Wi-Fi joystick. Open Controllers from Settings, pre-flight or the paused flight hub. Choose the device by its name.

Move a stick and press a button while watching diagnostics. Detected with no input means the device was found but has not delivered usable events. Receiving input confirms events are arriving. Neither status automatically activates the controller.

2. Assign the four flight channels

Run the setup wizard. Follow the on-screen prompt for throttle, yaw, pitch and roll; move only the requested control, then return it to its starting position before continuing. The radio's channel order may differ from a gamepad's, so map the controls you actually see moving.

Analog axes work for sticks and exposed triggers. Buttons, hats and keyboard-style inputs can form opposite digital directions when available. Digital directions have no intermediate stick travel. Avoid assigning one analog axis to two different flight channels.

If capture picks the wrong input, cancel with Back or Escape and start again. Manual binding controls let you edit individual channels afterward. Cancelled capture restores the previous mapping.

3. Assign flight and menu actions

Continue through arm/disarm, reset/emergency cut, Take Off, camera switching, pause, settings, menu confirm/cancel and menu directions. Press the desired button/key or move an exposed analog switch/trigger when prompted.

Skip an action to keep using its touch control. An analog-only radio can finish after the flight channels using the option to leave the remaining actions on touch. Take Off is a separate command: assigning it does not bypass the aircraft's flight-mode or arming rules.

Analog arm switches disarm when released. Enable the latching-switch option for a button/key that represents a physical arm switch. Leave it off for ordinary gamepad buttons that should toggle arm/disarm. Test both positions while grounded.

4. Calibrate, then tune

Choose whether the throttle returns to centre. Start calibration, hold spring-centering axes at rest for 3 seconds, then sweep every mapped analog flight axis through its full travel for 7 seconds. A non-centering throttle uses measured travel to establish its midpoint. Insufficient movement or cancellation keeps the previous calibration.

Check inversion and neutral values before changing dead zones, sensitivity or response curves. Read the calibration guide for drift checks and the flight-mode guide for the correct throttle position.

5. Save a profile and activate

Save a named profile such as “Pocket USB · Mode 2”. Return yaw, pitch and roll to neutral. Put manual throttle at motor-off, or assisted/3D throttle at its neutral point. Release buttons, keys and action switches, then choose Activate Controller.

An explicit activation request can wait up to ten seconds for safe inputs. Activation chooses the input source; it does not arm the aircraft. Use your arm command only after confirming that the throttle and other channels are correct.

6. Make a grounded check

Move each channel separately and inspect raw, calibrated and output values. Test arm/disarm, reset and camera controls. Reconnect the device and verify the expected saved profile. Make a gentle simulator takeoff only after these checks.

If the active controller disconnects, flight disarms and pauses. Reconnect, confirm safe inputs and activate again, then Resume. To continue with touch, explicitly choose Use Touch / Keyboard before resuming. Editing a profile or changing flight-input semantics also requires a fresh activation.

DJI validation

DJI controllers use model-specific input paths. The game retains its dedicated DJI setup where applicable; this general wizard does not certify every DJI remote. USB launch prompts and historical packet captures are separate from a physical flight test. No new DJI FPV model certification is claimed by these guides.

Use the compatibility record and DJI explanation before choosing a connection. If a device is visible but no raw channels move, follow troubleshooting.