8bitdo pro 2 analog/direction buttons not working

[natsoy]

Game or games this happens in

Trails of the sky, God of war etc

What area of the game / PPSSPP

Hi, just tried to use my pro 2 on my poco f3 with a ppsspp gold version of 1.11.3 and the direction and analog controls doesnt work. I've tried remapping them but the app doesnt detect the buttons, the other ones such as x, y, start, l, r are working fine. But the direction and analog controls doesnt. But the controller works fine outside the app and no problems encountered using in on epsxe and drastic. Any workaround fix for this?

What should happen

.

Logs

No response

Platform

Android

Mobile phone model or graphics card

POCO f3

PPSSPP version affected

v1.11.3, v1.12.2

Last working version

No response

Graphics backend (3D API)

Vulkan

Checklist

• Test in the latest git build in case it's already fixed.
• Search for other reports of the same issue.
• Try resetting settings or older versions and include if the issue is related.
• Try without any cheats and without loading any save states.
• Include logs or screenshots of issue.

[turbo420]

Not sure if this will help but in Android 11 there seem to be a bug. I had to turn ON One-handed mode to get my controllers to work.

[KerrangR]

having this issue as well on a different controller, seems like MIUI has to go through additional steps as just disabling accesability stuff isnt fixing the issue.

Im also assuming this might be a PPSSPP problem using old or outdated control APIs because literally all other emulators I have tested have no issues when it comes to this so it just makes me think that its something PPSSPP devs will have to find a fix for

[hrydgard]

I really wish I could find a combination of hardware that has this issue but everything I try just works. We are using the Java APIs for input, unlike many other emulators that instead use the nativeactivity APIs, so that might be related, or we might be handling something wrong... Manually remapping the buttons in control settings doesn't help, right, they just don't do anything? Can you use these buttons to navigate the UI?

[KerrangR]

I really wish I could find a combination of hardware that has this issue but everything I try just works. We are using the Java APIs for input, unlike many other emulators that instead use the nativeactivity APIs, so that might be related, or we might be handling something wrong... Manually remapping the buttons in control settings doesn't help, right, they just don't do anything? Can you use these buttons to navigate the UI?

Just to reply to you: No, I actually made a post you can check it out #15763 where I detail my issue, will post how I fixed it there as well for people to see.

I just found a fix, not sure if its a full fix but I noticed that my buttons were being used for navigation (B would take me out of apps, Select would act as Menu button). I had completely given up on PPSSPP when I booted up redream which I had actually struggled to set up initially but then quit using (because BT controller input lag for sonic is a hard pill to swallow.). Anyways, I noticed how my controller wasnt working for navigating redreams menues which were working just a few days ago. More so, noticed how Select would take me to the running apps view. That moment I realized I had seen an option were the Menu button would Either do that or just pull the App's menu. Now at this point I minized redream and did 2 things so I dont know what actually fixed it exactly but im leaning into #2:

1.- re-disabled One handed mode which I was told to disabled due to the Android 11 glitch but since I actually use it some times, and seeing that it didnt help me fix PPSSPP nor other older android games I gave up and enabled it again. I remembered the fix so I disabled it
2.- Set the navigation keys to always disable within redream (Settings>Additional Settings>Button Shortcuts>Automatically disable navigation buttons) and BAM, redream started reading my inputs normally. Inmediately went in again and did the same for PPSSPP and it was fully recognizing my inputs and I tested it working perfectly within my couple of PPSSPP games.

No Idea what behind the scenes thing affects controllers negatively but my previous point stands. Due to the massive ammount of emulators/apps that work and you confirming you use a different API than other devs means that that API is whats creating the incompatibility with the settings I mention above. I hope this can get fixed someday because I also reckon google loves breaking stuff and not fixing them on newer revisions of Android.