GamepadButton.dpadUp/.dpadDown inverted for Android

[fescrb]

Pressing the DPad's Up button on a connected controller produces the following NormalizedGamepadEvents:

I/flutter (20397): GAMEPAD EVENT: button="GamepadButton.dpadUp" axis= null value=0.0
I/flutter (20397): GAMEPAD EVENT: button="GamepadButton.dpadDown" axis= null value=1.0

And vice-versa for the Down button.

---

Checked on the following environment:

• Device: SM-G781B
• Android Version: 13
• GamePad: GameSir G8 Pro

$ flutter --version
Flutter 3.44.6 • channel stable •
https://github.com/flutter/flutter.git
Framework • revision ee80f08bbf (3 weeks
ago) • 2026-07-08 15:02:06 -0700
Engine • hash
d3a3293399556a85388faf8c6f0723a7a5597aa8
(revision 83675ed276) (30 days ago) •
2026-06-30 16:59:03.000Z
Tools • Dart 3.12.2 • DevTools 2.57.0

  gamepads:
    dependency: "direct main"
    description:
      name: gamepads
      sha256: bc2b4368f7f01e0390187f63c063f1fa26f420224e159fed1aaa2c449f5a1125
      url: "https://pub.dev"
    source: hosted
    version: "0.1.10+5"
  gamepads_android:
    dependency: transitive
    description:
      name: gamepads_android
      sha256: "8d8430deab5c35bafee3124bec0db19d3df605bb8f42da9ba188e826fda551e2"
      url: "https://pub.dev"
    source: hosted
    version: "0.1.8+2"

[fescrb]

For what it's worth, I think the cause is simple:

1. The EventListener inverts the value of the AXIS_HAT_Y axis before calling onGamePadEvent.
2. The AndroidMapping maps the values to normalized buttons without taking the inversion into account.. Ie. it still uses the values as described in the AXIS_HAT_Y MotionEvent, 1.0 for down and -1.0 for up.

[spydon]

@fescrb would you be interested in submitting a PR with a fix?

[fescrb]

@spydon I'd be happy to submit a PR but would need some advice about where to apply the fix:

1. EventListener.kt: Removing the inversion. OR
2. android_mapping.dart: Handling the inverted values correctly.

The difference between the two options being the values reported by unnormalized GamepadEvent. If option 1 is applied, the values of the axis will be consistent with Android's convention of of 1.0 == DOWN. If option 2 is applied, the values reported will follow the library's convention of 1.0 == UP.

[fescrb]

Ah, though my project only uses the d-pad inputs, I've performed a test of the analogue inputs and I believe the Y-axis are also inverted: UP on the left or right joysticks produces the following normalized event:

I/flutter (18695): GAMEPAD EVENT: button="null" axis= GamepadAxis.leftStickY value=-1.0
I/flutter (18695): GAMEPAD EVENT: button="null" axis= GamepadAxis.rightStickY value=-1.0

I can add a fix for these too.

[gavinliu]

When can we merge this code? On Android, the direction of movement is reversed.

[spydon]

When can we merge this code? On Android, the direction of movement is reversed.

Since the PR was just opened yesterday it will take us a few days to review etc before it is released.