Controls
Swapped buttons and double presses in Xbox Remote Play: find the cause
Save a working layout and test one short press. Separate mismatched labels from wrong commands, input repeating while a button is held from duplicate actions, and picture faults from input faults.
On this page
If Xbox Remote Play buttons are swapped or one press triggers twice, save your current control setup first. Then check one short press: is only the letter different, does another command occur, or does the game actually perform two actions? After that, check controller mode and mappings separately—in the controller, Android, XBPlayer and the game.
Before making changes, record the active profile, controller mode and connection method, and take screenshots of mappings. Save a profile copy if settings allow. Choose a menu or training scene where a mistake will not cause a purchase, an exit without saving or lost progress.
First establish what is repeating
Briefly press one button and release it fully. Wait for the result instead of pressing again because of a delay. Repeat the test several times from the same starting position and record what happens.
| Observation | What to check next |
|---|---|
| The action is correct, but the controller’s letter differs | Match the button’s physical position to the game prompt. This is not yet an input error. |
| A different action occurs | Go to mode and mapping checks. |
| A short press moves the selection by two items instead of one | Open the two-actions-after-one-short-press checks. |
| The picture freezes or movement looks repeated, but the action occurs once | Check the stream: visual repetition alone does not prove two presses. |
Identical adjacent frames in a recording do not mean the game received a command twice. Judge the outcome: how many menu items were crossed or how many times the game state changed. Lag alone does not prove a button was registered twice. If there is one action but it arrives late, start with input lag troubleshooting.
Match the label, command and action
Controller types use different letters and symbols. For example, Android may recognize the bottom face button as A even when a Switch-layout controller labels it B. Remapping changes that relationship again. A label on the controller therefore does not show which command the game receives.
Record three things: the button’s physical position, its mapping in the XBPlayer profile, and its action in the current game scheme. Check confirm and back in a safe menu, then a familiar action in a game scene. If the actions are correct, there is no need to swap buttons just for an on-screen letter. Client remapping should not be treated as a way to change game prompts.
Check the mode for your exact controller model
Some controllers have several connection modes. Find the exact model’s manual and check which mode the manufacturer recommends for Android and your chosen connection. Do not choose X-input or D-input based on universal advice: capabilities depend on the model. The device name in the Bluetooth list may not be enough to identify its mode.
Record the current mode before changing it. Pair again if the instructions require it, then retest the same button. If the result worsens, return to the saved setup. For an Xbox controller connection, use the Android connection guide.
Separate controller, Android, client and game mappings
Start with the most recently changed layer. The remapping simulator gives a visual example of successive mappings; two transformations do not by themselves mean two presses.
- Controller. Check the active hardware profile and mappings in its companion app. If the model supports macros or turbo, make sure they are not enabled for the button being tested.
- Android. Check any remapping utility, manufacturer’s gaming mode or app that converts buttons into touches. Not every device has these features.
- XBPlayer. Open “Settings → Controls → Controller profile” → “Button mapping” and the relevant control’s row. Check the entire “Sends” list: one physical button can have several output commands, including app actions.
- Game. Check the action assigned to that Xbox command, including separate menu, vehicle or other game-mode schemes if provided.
Start with the layer changed most recently. Temporarily restore only the mapping being tested to its default, or disable the corresponding transformation, then repeat the same test. If this does not help, restore the saved value before the next attempt. Do not reset all profiles together: that makes it harder to understand what changed the result.
When you find a setting that affects it, build the mapping you need and check the whole result. Where possible, perform the same swap in one place. Examples of the “button → Xbox command → action” chain are in the remapping guide.
If the game really performs two actions
- Check the button’s complete mapping list. Create a separate profile with “New profile”, open the problem button’s row and leave one required output command for the test. Save and repeat the action. Two different mapped commands are not the same command being sent twice; restore the previous setup by selecting the original profile.
- Separate holding from a short press. Holding a direction in a menu may trigger repeats. Compare a short press with a hold and release the button fully between attempts. Test another button too.
- Leave one input source. Temporarily disconnect a second controller, avoid touching the screen and stop any input-conversion app you use. Its presence does not prove the cause: what matters is whether the result changes when it is disabled and enabled again.
- Compare another game in the same stream. If the error occurs only in one game context, check its scheme and action rules.
- Check input without streaming. Use a compatible local Android app. If the same button repeats there, check the controller profile, system input transformations and the controller itself. One test is not enough to declare a button faulty.
If only a trigger is affected, say so separately. Some controllers report it as both an axis and a button; Android documentation says apps should account for this. When contacting us, include the controller model and trigger behavior in the game: a simple event count in a tester, without considering event type, can be misleading.
Check the fix after reconnecting
Save the setup you found and retest after reconnecting the controller and starting a new session. Check required combinations as well as individual buttons, such as moving while jumping. Keep a working profile copy to return to.
If you have not found the cause, record the controller model and mode, Bluetooth or USB, Android device model, Android and XBPlayer versions, game name and one action that reproduces the problem. Say whether it repeats without streaming and whether there are two actual actions or only a visual stutter. If all input disappears, use the guide for a controller that Remote Play does not respond to.
When contacting hi@hetko.eu, add three details: the physical button position, expected Xbox command and actual action with its count. For example: “D-pad down → D-pad down; I expect selection to move down one item, but it moves two after one short press.” This is a description template—substitute your own results.
Sources and further reading
- XBPlayer — Xbox Remote Play and cloud gaming — Physical-button remapping, profiles and compatible Bluetooth or USB controllers.
- Android Developers — Handle controller actions — Differences in button labels and mappings, press/release handling and trigger-event behavior.
- Android Developers — KeyEvent — Holding can produce repeated ACTION_DOWN events; pressing and releasing are distinct. This supports separate tests for a hold and a short press.
- 8BitDo — Pro 2 Wired Controller FAQ — Example of primary manufacturer documentation: X-input/D-input modes, profiles, remapping, macros and turbo. The information does not apply to every controller.
Get the key points
Open a summary request with this article’s link. For Gemini, the request is copied — paste it into the chat.