HDMIT Touchscreen on RP5 - not calibrated - mousepointer far away from my finger,

[bullemer]

Firstly, i want to say thank you for the great work - nice project and i think there is a huge demand for a good working Bootloader, as there is no good tool at the moment, which is a big surprise.

I tested Raspberry5 with variouse HDMI displays. the original DSI displays are not supported by now - so tested several HDMI Toch with usb support - all work, but with a big streching between mouse pointer and finger, so it is almost not possible to use it.

I worked on this 3 days, and it seems that this has something to do with QT touchscreen setup. I created a calibration file and tried to setup it with http://www.tslib.org/ but maybe my skills are not good enough to integrate this tool with the current setup.

This video shows the behaviour.
https://github.com/user-attachments/assets/4eb2e302-9ce8-48bf-826e-be85e91d44a5

I am happy to test and support this development - if you need some financial sponsorship i am also happy to contribute, as i think that especially a good touch implementation especially for RP5 would be very important.

[procount]

I think the first step is to check the touchscreens work ok in Raspberry PiOS and then try to identify which USB touchscreen drivers they are using. These drivers may need adding to PINN,

[bullemer]

In normal raspos the touchscreen works fine.

[procount]

Which drivers?

[xxxajk]

Same issue here. No problems with it in raspios or lineage android 16, pointer tracks OK.

[Flhuub]

Hi, same here! I have a touchscreen (Waveshare, 7", HDMI, USB) whose display works perfectly. However, the touchscreen is completely off on PINN and Moode (see the video)… On LibreELEC, it works very well, though. If anyone has any idea…

4_5870472106034076545_1764752728086.mp4

[xxxajk]

I actually found the reason and a workaround for it as far as android, which could apply here.
The touchscreen chip for some stupid reason comes up as a mouse and keyboard... yep, a keyboard...
My solution ignores the keyboard endpoint entirely.
The other thing with respect to raspios, is that somehow, the VID/PID actually changes, which is annoying. The only way to get the original vid/pid back is to powercycle it.

I'll attach the Android Linux kernel diff here, in the hope that it is useful.

mtouch.patch