Controls
Android sees the controller, but Xbox Remote Play does not respond
Connect the controller to the device running XBPlayer and check input separately in Android, the client interface and the game. Save the current setup before changing mappings.
On this page
If Android sees your controller but the game in Xbox Remote Play through XBPlayer does not respond, first check which device the controller is connected to. To send commands through XBPlayer, it must connect to the phone, tablet or Android TV running the client. Then check buttons and sticks separately in Android, the app interface and the game: menu navigation does not confirm that every game command is delivered.
First check the connection and a live picture
Make sure the streamed picture is updating—for example, an animation continues in a familiar scene. If the stream has frozen, the lack of a visible response does not let you judge the controller.
For Bluetooth, open connection settings on the device actually running XBPlayer and check the controller’s current status. An entry among previously paired devices does not mean it is connected now. With a console, phone and TV box nearby, it is especially easy to confuse the active connection. A controller connected directly to the Xbox does not test command delivery through Android and XBPlayer.
For a multi-mode controller, consult the manufacturer’s instructions for its Android mode. Record the original mode before switching. USB requires a compatible data cable and USB peripheral support on the phone or tablet: a light confirms only power. The connection procedure is in the Xbox controller on Android guide.
Find the last stage where input works
To check without streaming, save your progress and end the current session. Then open “Settings → Controls → Controller profile” and “Live virtual gamepad”. Press buttons, move both sticks and pull triggers in turn. Record which readings change, then compare the same commands in a new game session.
| Observation | What is known | Next step |
|---|---|---|
| No current connection to the intended device | A previous pairing record or USB power does not confirm input. | Restore the Bluetooth/USB connection. |
| Connected, but the required reading does not change in XBPlayer’s profile | The client is not yet showing the command being tested. The cause may involve the connection, mode, mapping or processing. | Check the model’s mode; for USB, check the data cable. Also compare a familiar local app. |
| The profile reading changes, but the game does not respond | The client sees processed input; delivery and the in-game action are not yet confirmed. | Check the active game and open panels. |
| The failure began after a profile change | There is a specific last change to reverse for a test. | Save the setup and undo that mapping. |
| A different command or two actions occur | This differs from completely missing input. | Check incorrect mappings and duplicate actions. |
The panel shows the virtual gamepad state after XBPlayer processing, not raw OS events. A working D-pad in menus does not prove that both sticks and triggers work either. Be specific: “The left stick changes in the panel; the right stays still.”
To separate Android from XBPlayer, you can additionally test an already installed app with controller support. A single system screen may not accept the commands you need. If no suitable app is available, mark this test as not completed—the remaining troubleshooting is still useful.
Return from menus to the active game
Close system windows and panels over the stream. Return to the game screen and perform an action available right now: open pause, move the character or turn the camera. No gunfire in a menu does not test a trigger. If the game asks you to select a profile or join a session, follow the on-screen instruction first.
On a phone or tablet, you can also compare the same command using an XBPlayer touch button. If it works but the physical button does not, this narrows the search to physical input and its processing. If neither works, that still does not prove the controller is faulty: return to checking the stream and game screen.
When the problem affects only one game, check its control settings and, after saving progress, repeat the test in another installed game. If no game responds, save progress by an available method, end the streaming session and connect the controller before the next Remote Play launch. Repeat the same commands and record whether the result changes. Do not assume disconnecting the stream saves the game.
Save the setup before checking remapping
Investigate mappings after checking the connection and active screen. Recall where controls changed before the failure appeared: the controller’s own profile, its companion utility, a third-party app, XBPlayer or the game.
- First record the current mappings and settings at the layer being tested. Save a separate profile if available; otherwise, take screenshots of settings or write them down. Do not overwrite the only working setup.
- Temporarily disable the last added remapping or choose a default setup at that layer only. Do not reset all device or app settings.
- Repeat the same command in the same scene. If nothing changes, restore the original setting and move to the next layer. If the command works, correct the identified mapping separately.
XBPlayer supports control profiles and physical-button remapping. The button remapping article explains how to avoid conflicts between several schemes.
Prepare details for support
If input is not restored, record the controller model and mode, connection type, Android and XBPlayer versions, game name and controller firmware version if known. Add the last successful stage, another-game test result and what happens when the controller connects before streaming starts.
A useful description is: “XBPlayer on a phone, Bluetooth connection; the D-pad works in menus, but buttons and both sticks do not respond in two games; connecting before the session starts changes nothing.” Include only your observations. Exclude sign-in codes and personal data from screen recordings. If commands arrive but perform different actions or trigger twice, use the incorrect mapping and duplicate input checks.
Send us the controller model and these results at hi@hetko.eu or through the form below. Include model and mode, Bluetooth/USB, Android and XBPlayer versions, game, last working command or stage, and a touch comparison if available. This description helps us locate the stage where input is lost; fill in only what you know.
Need help with this setup?
Sources and further reading
- XBPlayer — Xbox Remote Play and cloud gaming — Compatible Bluetooth/USB controllers, physical-button remapping, profiles and phone/tablet touch controls.
- Find your screen and controller setup — XBPlayer — Connection to an Android TV device, separate navigation and game-command checks, and saved profiles.
- Handle controller actions — Android Developers — Official Android documentation: button and axis events differ, and their handling depends on the active view and app; menu navigation is not a test of every game command.
- Xbox on Mobile — Xbox — Bluetooth or a wired controller connection to a compatible phone/tablet.
Get the key points
Open a summary request with this article’s link. For Gemini, the request is copied — paste it into the chat.