06-12-2025, 02:25 PM
(06-10-2025, 09:30 PM)Merc Wrote: I have never experienced something like this. It happening right after a system upgrade is when you'd expect something like this could happen software wise but it persisting across installs is of course not expected. I'm sorry I can't help but I can say that I have not had this happen ever and my PPP works just fine on a fully updated Arch Linux ARM system. Just recently I've been testing various distributions and in none of them did touch inputs stop working which leads me to believe that this is not software/bug related but rather hardware related. The coincidence that it happened right after an upgrade is a head scratcher!
I just did a bit of searching and the input of the touchscreen can abstractly be seen using
Code:cat /dev/input/touchscreen
When touching the screen while running this command it should fill the terminal with a bunch of indiscernible symbols and text, if nothing shows up, well that's a problem.
As it turns out for me, I looked at dmesg output for an old pinephone and a L5 that I have working touch screens. Neither have this file when running and both dmesg outputs show output for a touchscreen.
Code:
PP dmesg output:
[ 17.563932] Goodix-TS 1-005d: ID 917S, version: 0200
[ 17.564204] Goodix-TS 1-005d: Direct firmware load for goodix_917S_cfg.bin failed with error -2
[ 17.586362] cedrus 1c0e000.video-codec: Device registered as /dev/video3
[ 17.588872] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input2
L5 dmesg output:
[>> 8.514985] edt_ft5x06 2-0038: using DT '/soc@0/bus@30800000/i2c@30a40000/touchscreen@38' for 'wake' GPIO lookup
[>> 8.515000] of_get_named_gpiod_flags: can't parse 'wake-gpios' property of node '/soc@0/bus@30800000/i2c@30a40000/touchsc>
[>> 8.515015] of_get_named_gpiod_flags: can't parse 'wake-gpio' property of node '/soc@0/bus@30800000/i2c@30a40000/touchscr>
[ 8.515027] edt_ft5x06 2-0038: using lookup tables for GPIO lookup'touch' was not found in the dmesg output for my PPP.
I'm still looking at software solutions, but it's looking more like a hardware problem every day.
Thanks for your help.
