Dorian Stoll

> Is there any way I could test if this problem is actually originating in the hardware or the driver? Maybe a report comes in late or all zeros or...

You could try enabling the `BlockOnPalm` option. iptsd will then disable the touchscreen if a single palm is detected somewhere (default behaviour is to filter out the palms and forward...

There are two different versions of iptsd. The one in the master branch is the stable one that uses a very simple algorithm. Then we have the `libqzed` branch which...

> More importantly, it's really sluggish. (Really smooth movement, but very noticable delay of maybe even a second.) The code heavily relies on optimization, which are disabled by default. Additionally,...

You can reset the touch sensor with `sudo iptsd-sensor-reset`. This issue can be caused by faulty auto-calibration of the touchscreen. The command will delete that calibration data and restore the...

> That's a bit tricky. IIRC we can't do anything other than polling the hardware by checking the doorbell due to how it used to work before Intel restructured their...

Yes, indeed! This looks pretty awesome, thank you! I will try to implement something based on this when I have some time for it. Already have an idea that should...

> My Theory: While on the Surface devices the Touchscreen controler is managed by the ME (which this driver is for) und the NUC M15 the controler is directly accessed...

Well, the IPTS protocol can also transport HID reports instead of raw sensor data. I wouldn't rule it out that an OEM could do the processing in the touch controller...

> I rechecked and realized that the /dev/ipts/X devices are only there when I manually modprobe the ipts driver. The iptsd was started after that. When I start it before,...