-
Notifications
You must be signed in to change notification settings - Fork 203
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
Mirrored half of the touchscreen along the X axis #237
Comments
Hi, i am experiencing the same problem, if possible, upload the file with the correct driver |
Unfortunately, I have not yet been able to achieve success with this task. I'm still working on it, but I'm running out of ideas. |
I guess I am in the same boat. My touch screen is responding in different places. Also I have tried the driver provided from the official Chinese website and still having same error. Any updates? |
Hello, will this method works on windows OS? If not can you provide me your working copies plz. I really appreciate it. |
Hi, i have some several copies Jumper EzPad V10, and touchscreen drivers from the manufacturer for touchscreen.
On 3 copies everything was installed quite normally and works. But on 1 copy, with exactly the same touchscreen model, half of the panel is mirrored along the Y axis.
I create with command:
Which works quite well on several copies.
It's the same problem in the wrong touchscreen driver or something different?
UPD:
I tried several other drivers, they all with the same result.
Then I went back to the manufacturer's driver, and after restarting the touch stopped responding.
I use gslx680-acpi
Dmesg:
UPD 2:
I managed to get him to respond with the old result again.
The problem was that I was collecting from
SileadTouch.sys
, instead ofWB_PADV10_3692_L_X64_230705_ZT.h
supplied by the manufacturer. Withand
touch started reacting again.
UPD 3:
I experimented with extreme values. If we set the driver parameter to X = 100, we obtain a zone of 100 pixels in the center, with a border that is equal to the border of the display.
The text was updated successfully, but these errors were encountered: