I did more test today and I have to say this seems to be a problem specific to my iPega controller. Some findings:
1. This happens in a lot of other apps including Chrome, Play store, Google map, etc. but not in PPSSPP.
2. My iPega controller has two modes, one is called direct play mode, which doesn’t have this issue but I need to use a separate key mapping app to simulate screen touch which is not very easy to use. The other one (which is the one I’m currently using) is called Android standard mode which doesn’t require additional app but has this issue.
3. I also tried some other devices including Dualshock 4 and a normal bluetooth keyboard, none of them have this issue.
But since PPSSPP doesn’t have this problem I guess this can be fixed by correctly handling some event?
Did more investigation today and I think I’ve figured out where the problem is.
I created a simple Android app and captured all config changes, compared them one by one and found out when my game controller is connected a “navigation” config change is triggered (changed to NAVIGATION_DPAD). Not sure why it’s recognized as a d-pad device, but does it make sense to capture this event so game won’t be reset?
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.