touchscreeh doesn't accept input

[henrythemouse]

The original problem started with an upgrade in April 2025 that installed 600 packages on my PPP, which failed to complete. I reran the the upgrade, which ended up completing, but it failed to boot. I saw several "core" files in the root dir.  So, I decided to install from a new img.

Installing mobian phosh (mobian-rockchip-phosh-20250525.img.xz).

I installed the new OS image on my PPP using the suggested method (dd). I placed the installation img file on a micro sdcard which had that same OS on it. I installed that sdCard in my PPP and booted it.

I then used dd to transfer that img to the eMMC per instructions.

Code:

dd if=IMAGE.img of=/dev/mmcblk2 bs=1M status=progress conv=fsync

I rebooted the PPP. 

All was well, the system was working. I installed some software. After a few days, I decided to upgrade the system. After rebooting the touchscreen would not accept input. The login screen would appear, but would not respond to my touch. I plugged in a usb mouse via a pine64 usb multi port hub. The mouse pointer appeared and I could login. 

I tried booting the micro sdCard, but was confronted with the same situation.

I decided to go to an earlier img (20250618). After installation it booted fine, but would not respond to my touch. I tried booting from an arch img (20241223) on an sdCard. Still, touch did not work. 

First, I'd like to know if anyone else is experiencing this issue. And, if so, have they found a solution for it. 

Second, if no one has experienced this, does anyone have a clue as how to go about debugging the problem?

Thanks for any help.

[Merc]

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.

[henrythemouse]

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.

[Merc]

Code:

input: Goodix Capacitive TouchScreen as /devices/platform/ff130000.i2c/i2c-3/3-0014/input/input0

Appears in the dmesg of my PPP.

It's looking like a hardware issue for sure. 

[henrythemouse]

Code:

input: Goodix Capacitive TouchScreen as /devices/platform/ff130000.i2c/i2c-3/3-0014/input/input0

Appears in the dmesg of my PPP.

It's looking like a hardware issue for sure. 

Each day I upgrade this phone, reboot and check dmesg for 'touch'.
Today grep came back with this (never having reported anything previously)

Code:

grep touch 2025-06-14-dmesg.output

[    4.222506] vcc3v0_touch: Bringing 1800000uV into 3000000-3000000uV

Still no response from the PPP ui. I'm checking into what this might mean.