Using wireshark to monitor the usb traffic, we'll find the touchscreen becomes abnormal after systems sends the IDLE command to it.
But the touchscreen could revive after sending some other commands, such as GET_DESCRIPTOR.
I'll build a test driver soon, but I need to build a list for the affected usb id.
On this bug, there are 2 IDs
06cb:1d10
and mine is
06cb:0af8
Please reply if your borken touchscreen ID is not listed above.
Using wireshark to monitor the usb traffic, we'll find the touchscreen becomes abnormal after systems sends the IDLE command to it.
But the touchscreen could revive after sending some other commands, such as GET_DESCRIPTOR.
I'll build a test driver soon, but I need to build a list for the affected usb id.
On this bug, there are 2 IDs
06cb:1d10
and mine is
06cb:0af8
Please reply if your borken touchscreen ID is not listed above.