-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUIDE: Fixing touch issues with Android 11 & 12 #105
Comments
Genius! |
Thanks for this... But now. The screen is ok.. controller work on Android .. but all button didnt work when i launch a game.... Idea ? |
yes this fixs the mouse clicks not working, but keyboard key presses still not functioning..? And Ideas there? |
Sorry, no idea about keyboard issues.. This guide is focused around gamepads and touch issues. |
I updated Android 12 and then I couldn't use the touch screen, I solved it according to your solution, however it still doesn't map properly. Now decided to downgrade Android version |
Please make sure you did not turn off USB debugging afterward. It needs to stay on at all times if you want to use the app. |
Hello, currently on a Edge e20pro with android 11 on it. I tried the fix, didn't work. |
سلام |
How to restore this setting? |
Hello there,
I'm writing this for anyone who might have touch issues when using the app on newer android versions.
The problems:
Why is this happening?
Android keeps on adding extra security with newer updates, and they added one in Android 12 (and some A11 devices) which prevent any untrusted apps from simulating touch inputs, such as Panda Gamepad.
The solution:
You must allow untrusted apps to simulate touch inputs or add Panda Gamepad as a trusted app. Here's how:
prerequisites:
Doing it yourself (you need to be in an ADB environment, since you will be running ADB commands):
adb shell settings put global block_untrusted_touches 0
Using the .bat file I attached to this issue:
Fix_Touch.zip
The text was updated successfully, but these errors were encountered: