Describe the bug
sometimes when launch service with adb, the controler can not access to touch the whole screen,only a small zone on the cornor is avilable.
To Reproduce
I use this macro to launch droidvnc from computer:
adb shell cmd appops set net.christianbeier.droidvnc_ng PROJECT_MEDIA allow
adb shell settings put secure enabled_accessibility_services net.christianbeier.droidvnc_ng/.InputService:$(adb shell settings get secure enabled_accessibility_services)
adb shell am start-foreground-service -n net.christianbeier.droidvnc_ng/.MainService -a net.christianbeier.droidvnc_ng.ACTION_START --es net.christianbeier.droidvnc_ng.EXTRA_ACCESS_KEY xxxxxxxxxxxxxxxxxxxx
launch droidvnc in the phone mannually, touch start physically.
connect to the android from the computer and touch stop from vnc.
run the above macro,
connect to the vnc again,and the screen can not be fully touched via the vnc client, they are not fully maped to eachother.
However, if you kill droidvnc app and run the macro, it works fine again.
Your environment (please complete the following information):
droidVNC-NG version:2.20
Android version: android 10 vision 72.20
Client-side OS and version: windows 10 22H2
VNC client and version: vnc (R) viewer 5.0.3 (r97046) 32 bit unicode
Describe the bug sometimes when launch service with adb, the controler can not access to touch the whole screen,only a small zone on the cornor is avilable.
To Reproduce I use this macro to launch droidvnc from computer:
Your environment (please complete the following information):