Closed lbenini closed 4 years ago
E3V3A
commented
6 years ago Is this a problem that suddenly appeared (e.g. after an update/upgrade) or something that has been around since first install? If it appeared after update, please provide more info about your OS version and try to pinpoint what was updated when it started.
thooge
commented
6 years ago Same problem here with Iiyama ProLite T2252MSC. Tried with fresh install of Raspbian, Raspi 3B and Raspi3 B+.
$uname -a
Linux raspberrypi 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
$lsusb
Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 004: ID 2575:0401
Bus 001 Device 005: ID 046a:0011 Cherry GmbH G83 (RS 6000) Keyboard
Bus 001 Device 007: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub$cat /proc/bus/input/devices
I: Bus=0003 Vendor=2575 Product=0401 Version=0110
N: Name="Weida Hi-Tech CoolTouchR System "
P: Phys=usb-3f980000.usb-1.2/input0
S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:2575:0401.0001/input/input3
U: Uniq=
H: Handlers=mouse1 event2
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=2608000 3Tried on screen keyboard onboard. Unusable, seems not to send KeyUp events?
Same configuration with normal PC and Debian Stretch works as a charme.
JamesH65
commented
6 years ago JamesH65
commented
6 years ago Been taking a quick look at this stuff. It's a bit confusing how a driver is chosen, looks like the Quanta device uses the standard hid-multitouch.c driver, but not sure about the Wieda device. I don't think its the same driver though.
In the Quanta case, this driver is used by a LOT of different screens, so I would think it unlikely that it has any bugs this obvious. Since its also a different driver to the Weida, that sort of implies the issue is elsewhere, and the only elsewhere that comes to mind is the USB stack.
@P33M Any suggests on USB tweaks that might help here?
lbenini
commented
6 years ago I come back late, but I've been able to conduct more test only today:
thurban
commented
6 years ago I have the very same problem. The (2 tested) PROLITE T2252MSC monitors work fine on a Centos7/64 bit system, but shows the same issues on a Raspberry3 B.
trondjl
commented
6 years ago Hi, I have the same issue. I can trigger it by clicking with three fingers and fix it with two. It also seems to hang by itself sometimes when left alone, but also it might be the first click then is misinterpreted... Using evdev driver instead of libinput seems to be more stable in X, but still hangs with three fingers in my javafx app. Using rpi3b with updated Jessie and an 10 inch waveshare screen. Anyone found a good workaround or fix yet?
JamesH65
commented
5 years ago This issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested.
thooge
commented
5 years ago Still waiting for a fix...
thurban
commented
5 years ago I was able to fix it by adding the following text to the end of the /boot/cmdline.txt:
usbhid.mousepoll=0
The PROLITE T2252MSC and PROLITE T2454MSC both work just fine afterwards.
JamesH65
commented
4 years ago @thooge Did the above workaround fix your issue?
JamesH65
commented
4 years ago Closing due to lack of activity. Please request to be reopened if you feel this issue is still relevant.
We have found a particularly strange problem with RPI3 and a touchscreen. On a "macro" level the touchscreen stops to work "after a while" We have done quite a lot of tests that hopefully can help:
On Jessie the problem exists with and without X
(Qt application in eglfs mode has the same behavior); on Stretch we have not tested without Xorg
We have prepared a video that shows the situation. I cannot upload here so you can find it here: https://www.youtube.com/watch?v=PhPwJ6Vm40k The terminal on the left shows the touch events, the one in the middle show the mouse events and one the right the mouse events coming only from the USB mouse