devicefarmer / minitouch Goto Github PK

I have problems with implementing the coordinate mapping for my Pixel 3a. (I am not using stf, that's why I have my own implementation).

The problem is: my Pixel 3A is switching the max-x and max-y coordinates when I reconnect my device.
Any ideas what's going on? How should I deal with this? My mapping does not account for device specific transformations...

Pixel 3a (max-x and max-y switch places)

Landscape
^ 10 2220 1080 0

Portrait
^ 10 1080 2220 0

Tab2 (max-x and max-y stay the same):

Landscape
^ 10 1535 2047 255

Portrait
^ 10 1535 2047 255

minitouch cannot be used on non-rooted Android 14 models and will report a permission error. How can I solve it?
The error message is as follows：

open: Permission denied
Unable to open device /dev/input/event0 for inspectionopen: Permission denied
Unable to open device /dev/input/mice for inspectionopen: Permission denied
Unable to open device /dev/input/mouse1 for inspectionopen: Permission denied
Unable to open device /dev/input/event5 for inspectionopen: Permission denied
Unable to open device /dev/input/mouse0 for inspectionopen: Permission denied
Unable to open device /dev/input/event2 for inspectionopen: Permission denied
Unable to open device /dev/input/event3 for inspectionopen: Permission denied
Unable to open device /dev/input/event1 for inspectionopen: Permission denied
Unable to open device /dev/input/event4 for inspectionUnable to find a suitable touch device
connecting socket: Connection refused

Hello, guys,

I have noticed that the current version of libevdev being used in the minitouch project is outdated. The latest version available for libevdev is 1.13.1, which includes new features, performance improvements, and potential security updates.

Updating the libevdev dependency in minitouch would help ensure that the project stays up-to-date and continues to benefit from the latest developments in the libevdev library.

Thank you for your attention to this matter, and I look forward to seeing minitouch continue to evolve and improve.

Best regards,
Yucheng Song

I have found out that touches can also be sent via ADB.
https://adbinstaller.com/commands/adb-shell-input-tap-5b67dc5ee7958178a295553f

Am I correct about my assumption that this would render minitouch obsolete?

I am using stf and while enrolling the realme device with android 14, minitouch is failing and giving below error logs:

open: Permission denied
Unable to open device /dev/input/event4 for inspectionopen: Permission denied
Unable to open device /dev/input/event2 for inspectionopen: Permission denied
Unable to open device /dev/input/event3 for inspectionopen: Permission denied
Unable to open device /dev/input/event0 for inspectionopen: Permission denied
Unable to open device /dev/input/event1 for inspectionUnable to find a suitable touch device
connecting socket: Connection refused

it will retry thrice and then will get failed.

what could be the potential issue here?

Hello, guys,

I would like to request the addition of Windows-specific installation steps and instructions for Minitouch. As a Windows user, I believe that having clear guidance for installing and running Minitouch on Windows would be beneficial. This would help expand the accessibility of Minitouch to a wider user base.

Thank you for your attention to this matter.

Best regards,
Yucheng Song

Hi,

Is there a way to integrate the minitouch to the AOSP build ? Including libevdev or directly by copying the executable.

Thanks

There was a problem starting the server on magisk 21.2 on version 20.4 working fine.

D/MinitouchSocket12: Note: device /dev/input/mice is not supported by libevdevType B touch device NVTCapacitiveTouchScreen (1080x2160 with 10 contacts) detected on /dev/input/event1 (score 2109) binding socket: Address already in useUnable to start server on minitouch

I am using AutoIt, and i believe you can use the the minitouch to inject touches into android emulator examples below

Is there a guide or tutorial on how to use it in AutoIt?

Any help will really be appreciated

Example
r
d 0 300 590 50
d 1 560 590 50
c
w 50
m 0 325 590 50
m 1 535 590 50
c
w 50
m 0 350 590 50
m 1 510 590 50
c
w 50
m 0 375 590 50
m 1 485 590 50
c
w 50
m 0 400 590 50
m 1 460 590 50
c
w 50
m 0 425 590 50
m 1 435 590 50
c
w 50
m 0 430 590 50
m 1 430 590 50
c
w 50
u 0
u 1
c

WARNING: linker: /data/local/tmp/minitouch: unsupported flags DT_FLAGS_1=0x8000001
opendir: Permission denied
Unable to crawl /dev/input for touch devices

Hello guys,

I was going through the minitouch documentation and noticed a potential typo in the section title. The section currently titled "Running minicap" seems to contain information relevant to "minitouch" rather than "minicap."

Given the context and content, it appears that the section title might be a typographical error and could potentially be corrected to "Running minitouch." This would align the title with the information presented in the section.

This could be found in the README.md file or directly at this link.

Thank you for your attention to this matter, and for your continuous efforts in maintaining this valuable project.

Best regards,
Yucheng Song

Hi, i'm facing a problem to use minitouch on Android 11 devices. I know there are some security policies that make it difficult to use, but on the readme it wrote that we can use it with the STFService.

But i well followed instructions to run the STFService. It seems to works well, when i start the agent, it print bin jp.co.cyberagent.stf.Agent Starting minitouch agent Listening on @stfagent

But when i send command through netcat to this socket, nothing happens, and when i build and use minitouch, it doesn't works too (got the normal error /dev/input/event )

What did i missed ?

Thanks for your answer.
Regards, Bastien

Description:

Gestures ignored when the device is stored on its right-side w/ landscape mode on, as soon as the device is rotated to its left-side gestures work correctly again.

Noticed on devices w/ versions: Android 11, Android 12 (Android 12 also has a problem with minicap in the landscape mode).
Minitouch consumer/environment: STF

Steps To Reproduce

• Connect an Android 11/12 (sdk 30/31?) to the STF
• Start using the device in portrait mode
  • If autorotate is off - switch on
  • Open Settings (or any application supports landscape mode)
• Rotate the actual device on its right-side (the window should be in landscape mode)
  • Try to manipulate via the browser - commands not reflected
• Rotate the actual device on its left-side (the window should be in landscape mode)
  • Try to manipulate via the browser - now it works

Hi, guys,
I've encountered an issue where minitouch does not terminate properly when I send a SIGINT signal (using Ctrl+C) in the Win-PS terminal. After terminating minitouch with Ctrl+C, attempting to run it again results in a "binding socket: Address already in use" error. This suggests that the previous instance of minitouch did not release the port it was using.

Steps to Reproduce:

1. Start minitouch on an Android emulator/device using the command: adb shell /data/local/tmp/minitouch.
2. Terminate minitouch using Ctrl+C.
3. Attempt to run minitouch again using the same command.

Expected Behavior:
Minitouch should terminate gracefully upon receiving a SIGINT signal and release any resources it was using, including the port.

Actual Behavior:
Minitouch does not seem to release the port it was bound to, leading to a "binding socket: Address already in use" error upon attempting to run it again.

Environment:

• Operating System: Windows 10
• Android device/emulator model: emulator-5554
• Android version: Android 7.1.2

Additional Information:

• Running adb -s emulator-5554 shell ps | findstr minitouch confirms that the minitouch process is still running after attempting to terminate it with Ctrl+C.
• Temporary workaround: Manually killing the process using adb shell kill [PID] allows minitouch to be run again.

I believe this might be a bug with how minitouch handles the SIGINT signal. Any assistance or insights into this issue would be greatly appreciated.