Start with the device state
Open Controllers, select the intended device and move one control at a time. In the Universal Controller update, detection is separate from receiving events and activation. A selected name without changing raw values does not prove a working input path.
| What you see | What to check next |
|---|---|
| Device is absent | Connection mode, data cable, USB-host support or Android Bluetooth pairing |
| Detected, no usable input | Move controls; inspect joystick/HID mode and whether the OS exposes actual events |
| Raw values change, flight channels do not | Run mapping or correct the selected axis/button/key bindings |
| Calibrated neutral drifts | Correct centering/calibration, then use a small per-channel dead zone |
| Receiving input but inactive | Complete all four flight channels and explicitly activate with safe sticks/released actions |
| Active input disconnects | Gameplay pauses; reconnect, activate and confirm Resume |
Nothing arrives over USB or Bluetooth
Use a data-capable cable and the radio's data port. Check the phone supports USB-host/OTG and that the radio is in joystick/HID mode. Storage, charging, serial and DFU connections do not provide this game's generic joystick path.
For Bluetooth, pair the exposed joystick in Android settings. A radio needs a compatible BLE joystick module/firmware; ordinary RF transmission is not Bluetooth controller input. If the OS exposes no usable inputs, manual mapping cannot invent them. A proprietary device may need an adapter. Follow the radio connection guide for the specific path.
The wrong channel moves
Use raw diagnostics to find which axis actually changes. Map one requested control at a time and return it to its starting position during the wizard. Verify the radio's channel mixes if a single movement drives several channels. Do not assume Xbox axis order for a transmitter.
For a reversed channel, use inversion and retest. Hats may appear as directional buttons, and a trigger can be exposed as an analog axis or button. Choose a binding based on the events received from your actual device.
Calibration is rejected or sticks drift
Sweep every mapped analog flight axis through its full travel during the seven-second stage. Each must show at least 0.1 normalized movement. Cancellation or insufficient movement leaves previous measurements intact. Digital-only channels do not need analog calibration.
Choose throttle centering to match the mechanism. Release spring-centered axes during rest sampling. If raw input is unstable, check the controller/radio's own calibration and mechanics. If raw values are steady but output is wrong, inspect mapping, inversion and response settings before increasing dead zones. See calibration.
Activate Controller will not complete
Confirm that actual input events have arrived and all four flight channels are mapped. Center yaw, pitch and roll, then use the correct throttle position: low/motor-off in manual modes, neutral in assisted modes and active 3D. Release all buttons, keys and action switches.
An activation request can wait up to ten seconds for those conditions. If it expires, correct the values and request activation again. A held arm switch should be returned to its inactive position; activation and arming are separate actions. The flight-mode guide explains why the wrong throttle position can block activation.
Wi-Fi is visible but never receives input
Confirm the phone is on the intended local network and the entered IPv4 address belongs to the transmitter or adapter. ExpressLRS firmware must implement Wi-Fi joystick, not only its configuration web page. Choose Connect Wi-Fi to request the stream.
A custom adapter must send the expected protocol to the phone's UDP port 11001 from the explicitly selected peer address. Incorrect schema, stale sequence numbers, changed identity or another sender cannot refresh its heartbeat. A 500 ms gap disconnects input. Check the adapter interface if you built the sender yourself.
Touch works but the controller will not resume
After a disconnect or profile change, reconnection alone does not restore ownership. Select the controller, verify safe inputs and activate it, then Resume. To use touch instead, choose Use Touch / Keyboard first. Moving another controller will not take over the paused session.
What to include in a support report
Record the game version/build, phone model, Android version, exact controller model, firmware/module, connection method, reported device name, selected profile and the steps that reproduce the problem. Include which raw controls move and the calibrated/output values that look wrong.
A screenshot of diagnostics is more useful than a model name alone. Send it through the official support route. Browser input-lab success only proves browser input; it does not establish native Android hardware compatibility.