DPAD triggers no longer work in 4.0+

[jambl3r]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

There have been several reports of DPAD triggers not working in 4.0+

I activated the key mapper and entered the game. However, when I pressed a button on the down D-pad that I had mapped to a button using the key mapper, it didn't work. The other buttons worked, but not the right, down, left, up D-pad. I turned off the key mapper, and the D-pad works fine. So it's not a problem with my controller, but with the key mapper, since when I activate it, the button I configured in the application doesn't work. Please help me. If you don't understand, here's a better explanation of the problem:
Error configuring/mapping button. The command is not executed on screen.
When attempting to assign an action to a specific physical button, the mapping is saved visually in the application, but it does not produce any response within the game or the system when pressed.

Hello, just got the 4.0.5 update and while using the dpad on a connected 8BitDot Zero 2 controller was working previously, even though it works with phone control, the dpad is suddenly not registering with KeyMapper - try and record trigger input and it does not register, what could be the reason for this ? Is there an easy fix or is it a bug Yeah using KeyMapper keyboard and was working before, only stopped registering dpad key presses after new update. This update is also messing with the AB buttons of the controller, in that when the application is running any A/B pressing can be registered in KeyMapper, but they do not do their usual enter/back functions in any apps. And when the application is paused, they work completely fine. Basically my whole workflow is currently compromised, is there any chance of this being fixed/errors reverted ? Thanks for any help you can give ! Ok I've rolled back to 3.2.0 131 and the capabilities are working again, I can export at some point but will have to remake the keymap in this version first, but everything from now back to 3.2.1 didn't work with this dpad FYI

What did you expect to happen?

No response

What would the developer need to do to reproduce the bug?

No response

App version

4.0+

Android version

?

Device model and manufacturer

?

Extra info

• My device is rooted