Replies: 1 comment 2 replies
-
|
Hi, thank you for pointing out that. Tiny details like this help the project improve for everyone.
I will add a warning, but some users might not read it, so I'm also going to add detection in the code for that property. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
-
Hii everyone! (〃▽〃)
I’m writing this because I’m a bit embarrassed... As a relatively new Waydroid user, I spent some time struggling with a tiny detail that I didn't know was causing trouble.
I remember suggesting a feature to the amazing developer on YouTube, and he was so kind to fix the functionality for "Aim Mouse" (instead of WASD)! But, silly me, I didn't realize that my own Waydroid settings were interfering with it.
I had previously enabled this property to log into Mobile Legends:
waydroid prop set persist.waydroid.fake_touch "*"
I didn't know that xtmapper already emulates touch perfectly on its own without needing that property enabled! (。>ㅅ<。)
It turns out that for the Mouse Trigger and movement to work flawlessly, this must be disabled! Once I cleared it, everything became so smooth and wonderful~ ✨
Could we please add a small "Warning" or a tiny note in the Guide? I’d love for other users to know they should disable fake_touch if they want to use the mouse movement properly. I don't want anyone else to go through the same confusion I did!
Thank you so much for all the hard work on this project! You guys are the best! 💖
Beta Was this translation helpful? Give feedback.
All reactions