[UWP] Gamepad navigation RB/LB is broken on ROG Ally Xbox

Question

[UWP] Gamepad navigation RB/LB is broken on ROG Ally Xbox

60856927 111

I am developer of UWP apps. UWP apps support gamepads natively well. But I noticed that gamepad support in UWP apps on Rog Ally Xbox is totally broken. For example RB makes 'A' press instead of navigation in Navigation View. On regular Windows 10 an 11 it works well as always. The problem persists on ROG Ally Xbox.

1 answer

Your answer

Answer 1

Danny Nguyen (WICLOUD CORPORATION) 4,160 Microsoft External Staff Moderator

Hi,

Thanks for sharing the details. Since you’ve confirmed that gamepad navigation works correctly on standard Windows 10 and 11 systems, this behavior on the ROG Ally Xbox sounds like a device-specific mapping issue rather than a UWP framework regression.

Here are a few things you could check to narrow it down:

Game Controller Settings (Win + R → joy.cpl): Verify RB/LB register correctly. If RB appears as A (or both), it’s below the app.
Raw UWP reading: Poll the first gamepad (Gamepad.Gamepads.FirstOrDefault()?.GetCurrentReading()) and log reading.Buttons to see if RB includes A.
Cross‑app test: Try a simple UWP sample from the Store. If it reproduces, it’s system-wide.
Disable remap layers: Turn off Armoury Crate profiles, Steam Input, reWASD, etc., then retest.
Firmware / updates: Ensure BIOS, controller firmware, Windows build, and drivers are current.

If the button mapping appears incorrect at the system level, it’s likely related to the ROG Ally’s firmware or input translation layer. In that case, you may want to report it to ASUS Support. Hope this helps.

60856927 111 Reputation points

2025-10-27T10:18:36.64+00:00

I found what is the problem. On ROG Xbox for some reason the 'Control Mode Auto' detects it as Desktop while I am in Full Screen Xbox Experience. I expect my app be detected as gamepad mode. Do you know how to set it be detected as Gamepad but not Desktop app while in FSE?
Danny Nguyen (WICLOUD CORPORATION) 4,160 Reputation points Microsoft External Staff Moderator

2025-10-27T10:47:31.1766667+00:00

Can you check if there's a gamepad driver update on Armory Crate? I saw some recent thread suggesting that that should work.

Also if you think there might be driver conflict with other drivers or the driver is faulty, consider reinstalling them.
Danny Nguyen (WICLOUD CORPORATION) 4,160 Reputation points Microsoft External Staff Moderator

2025-11-06T02:18:43.39+00:00

Hi, just checking in, is there any update on your end on this issue?
60856927 111 Reputation points

2025-11-06T06:35:34.6+00:00

As I mentioned above, it is not a driver issue, it is control mode issue. The question is how to set the app manifest by default to detect is gamepad supported.
Danny Nguyen (WICLOUD CORPORATION) 4,160 Reputation points Microsoft External Staff Moderator

2025-11-06T07:59:37.2633333+00:00
According to the TargetDeviceFamily documentation (TargetDeviceFamily element), the only manifest-level hint you can really provide is to include the Xbox device family if your app is compatible:

<TargetDeviceFamilies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22621.0" /> <TargetDeviceFamily Name="Windows.Xbox" MinVersion="10.0.17763.0" MaxVersionTested="10.0.22621.0" /> </TargetDeviceFamilies>

Beyond that, there is no manifest flag (based on current published schemas) that explicitly forces “Gamepad mode” classification. You can try enabling gamepad detection early at startup (subscribe to Gamepad.GamepadAdded immediately and read a GetCurrentReading() right away).

Since there is no documented, direct way to declare gamepad-first UWP app beyond targeting Xbox and designing for controller input, I suggest opening a ticket here under UWP tag https://support.serviceshub.microsoft.com/supportforbusiness/create?
60856927 111 Reputation points

2025-11-06T10:52:26.99+00:00

I think you are not familiar with the device. Control mode on ROG means if it acts as gamepad or desktop mouse simulation. It is ok that in Desktop control mode it doesn't acts as normal gamepad. But, it I believe it is windows uwp responsibility to report if the app supports gamepad. For example the xbox app is detected as gamepad supported. My uwp app is not detected as gamepad supported and therefore ROG stays in Auto control mode that acts as desktop control mode. May be I need to declare something in the app manifest that will tell to the system that the gamepad is supported.
Danny Nguyen (WICLOUD CORPORATION) 4,160 Reputation points Microsoft External Staff Moderator

2025-11-17T03:09:37.8033333+00:00

Yes, I get what you're saying and I think it is unfortunate that your app is experiencing this issue. Though, from what I can confirm in the UWP documentation, there isn't a specific manifest entry or capability to explicitly declare "gamepad supported" at the package level. The closest is targeting the Windows.Xbox device family in the manifest, which signals compatibility with Xbox-like environments and implies controller optimization. Beyond that, gamepad support is handled at runtime through the Windows.Gaming.Input APIs.

Share via

[UWP] Gamepad navigation RB/LB is broken on ROG Ally Xbox

1 answer

Your answer