So unless we can find out how to make the AVD properly interpret a touchpad as a touchpad, and not a touchscreen, using a mouse seems like the best solution.įor reference, I'm including this link to the AVD manual: So it suggests to me that it is indeed properly interpreted as a SOURCE_MOUSE controlled pointer and not a SOURCE_TOUCHSCREEN controlled pointer. However, with the mouse it only responds to clicks. I plugged in a mouse and tested the pointer up/down movements over the screen, which this part of the document suggests should register as a press. Unfortunately, I don't have a solution as much as a workaround: In reading that, I've come to believe this may actually be the default behavior due to touchpad events being interpreted through the SOURCE_TOUCHSCREEN method, rather than SOURCE_TOUCHPAD or SOURCE_MOUSE. Some devices permit touches outside the display area so the effective range may be somewhat smaller or larger than the actual display size. Use getMotionRange(int) to query the range of the pointing device. Pointer down/up indicated when the finger touches the display or when the selection button is pressed/released. A MotionEvent should be interpreted as absolute coordinates in display units according to the View hierarchy. Examples: SOURCE_TOUCHSCREEN, SOURCE_MOUSE. The input source is a pointing device associated with a display. Looking at the documentation, I came across the SOURCE_CLASS_POINTER method, which states: I hate tap-to-click, so having an ultra-sensitive-to-touch Android screen emulated on my laptop is beyond frustrating. I am new to the Android Emulator, but am experiencing the same issue in Ubuntu, even though I have tap-to-click disabled in the OS.
I think it appeared after updating to Monterey, but not 100% sure of the exact timing correlation. I have tested and tested this again to make sure I'm not biasing the results, but there really is a difference, and it's driving me nuts. If I try the same in some other app (tested with the "System Preferences" window), it catches 100% of the taps. If I tap the "Enable clipboard sharing" toggle, it misses about 50% of the taps.
What's more, it's not only the emulator window itself that has this issue, but the emulator settings window as well. I don't even know how this is possible, is there even such a thing as app-specific tap-sensitivity? So, it seems that the emulator window is somehow less sensitive to tapping than all other apps. The tap sensitivity in the Trackpad settings is set to "light". If I click hard instead of tapping, it catches every click. But somehow, when the emulator window is active it seems to miss almost every other tap. I have "tap to click" enabled on my Macbook Pro (Mid 2015 15"), and it works fine in all other apps.
I'm experiencing a really weird and frustrating issue with the Android Emulator on macOS Monterey.
0 kommentar(er)
