I got my FW12 in batch 9 and I’ve been working on my Arch setup on it since then. However, I’m not quiet sure when the problem started over the last few weeks, but my touchscreen stops responding a couple of minutes after a fresh boot. The display still works, but touch events stop registering.
When it goes unresponsive, libinput still lists it. However, debug-events shows no events for the corresponding channel. On a fresh boot, I can see events come through, then after a minute or so they start to lag behind input before events stop coming in all together. There’s no dmesg or journalctl errors either.
I’m up to date on my kernel version, and iio-sensor-input. I’ve also tried booting off a usb device, but I get the same behavior.
I have also tried reseating the touch controls to no success.
I’ve had an open support ticket for a couple of days, but after searching the forms here and not seeing anything else here, I thought I should at least ask.
So, have you seen or hear of this issue? Do you have any advice for me? Please, I want to read my ebooks on my new 12” portrait screen
Hi, I got my FW12 back in batch 1. I have had an open support ticket on touch issues (I think in my case related to the stylus) since 01.08.25 (yes 4 months, still not resolved…). So far I have no advice except that it most likely isn’t a Hardware issues (my complete display unit was replaced with no change and I’m running Ubuntu 25.10 and also tried Fedora). From the amount of trouble shooting done in my case I also can’t imagine this being a one-off issue, it must be wide spread.
I didn’t update here because the thread didn’t have any traction.
I did end up going through a bunch of troubleshooting steps, similar I imagine to you, about my display when my touchscreen was not working back in October. they did issue me a new touchscreen.
however, while I was doing their troubleshooting, my display went out entirely not just the touch portion of it. I also thought it was very odd that for the touch portion being out and the display working they wanted to rep replacing the entire display and not the EDP cable, so I asked them to also issue a new EDP cable and they said let’s try to touchscreen first.
since I was already going to have to take the entire panel apart, I went ahead and bought an EDP cable and I replaced the entire EDP cable and touchscreen at the same time and that fixed my issue.
it’s been working great ever since. However, I believe in taking it apart I understood the issue. the EDP cable and the antenna are routed together around the right hinge and they can be disturbed during assembly (there’s no warnings for this) and the antenna puts pressure on the EDP cable if it gets out of the channel and that causes the EDP cable to fail, which would cause a touch module to fail.
if you replaced your screen, and it started to work again, then it could just be that reseating the EDP cable entirely (not just unplug and plug it back in) in the channel fixed the problem.
Thanks for posting this. My touchscreen wasn’t working, I found your post, and tried reseating the EDP cable connector on the mainboard. Voila! Touchscreen is back. For now anyway.
Definitely a pain but at least I have a workaround.
Thanks for posting this. I had my 12 for about 4 or 5 days when the touchscreen stopped working. Found your post, so I identified the EDP cable from the replacement walkthrough and re-seated it as you describe. Working fine now.
What I don’t get is why that mm adjustment is the difference between working and not working. I didn’t actually re-seat a connection that I could tell, which makes me worry my fix is temporary.
I can’t say if the cables are good or not after they show signs of failure. I haven’t thought to cut/strip my old one open till now. I might. If I do, I’ll report here.
in the mean time, if your experience makes you anxious about a future failure, eDP cables are only $12. Could grab one to have on hand.
Please, I want to read my ebooks on my new 12” portrait screen 