Skip to content
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

Open
KolhozniiSniper opened this issue Jul 3, 2024 · 0 comments
Open

Mirrored half of the touchscreen along the X axis #237

KolhozniiSniper opened this issue Jul 3, 2024 · 0 comments

Comments

@KolhozniiSniper
Copy link

KolhozniiSniper commented Jul 3, 2024

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:

../tools/fwtool -c firmware.fw -m 1680 -w 1525 -h 2035 -f track,swap,yflip -t 10 silead_ts.fw

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:

[    6.071315] gslx680_ts_acpi: loading out-of-tree module taints kernel.
[    6.071328] gslx680_ts_acpi: module verification failed: signature and/or required key missing - tainting kernel
[    6.462631] gslx680 i2c-MSSL1680:00: gsl_ts_probe: got a device named MSSL1680:00 at address 0x40, IRQ 68, flags 0x0
[  129.004891] gslx680 i2c-MSSL1680:00: gsl_ts_probe: got a device named MSSL1680:00 at address 0x40, IRQ 68, flags 0x0
[  147.298737] gslx680 i2c-MSSL1680:00: gsl_ts_probe: got a device named MSSL1680:00 at address 0x40, IRQ 68, flags 0x0
[  179.398072] gslx680 i2c-MSSL1680:00: gsl_ts_probe: got a device named MSSL1680:00 at address 0x40, IRQ 68, flags 0x0

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 of WB_PADV10_3692_L_X64_230705_ZT.h supplied by the manufacturer. With

../tools/untscfg WB_PADV10_3692_L_X64_230705_ZT.h firmware.fw

and

../tools/fwtool -c firmware.fw -m 1680 -w 1525 -h 2035 -f track,swap,yflip -t 10 silead_ts.fw

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant