[epikao]

Hello, I have several USB HID Multi-Touchscreen which are not working with Kodi (respectively OSMC).
The Forum OSMC cannot help.
In the Internet it looks I am not the only one with that problem but unfortunately no solution available.
(if touch, only mouse on the top left corner is showing)
I have also a I2C to USB Multitouch screen converter where I would be able to change something on the USB Describtor. But I don't know the rules and criteria that Kodi needs to properly implement a USB Touch??

The only one USB Touchscreen that I know is working is from Atmel mXTouch.

My question: Can someone help guide me what I can do next to find a solution? It's very very important for me.

And please note: The mentioned Touchscreens are working on Raspbian, Ubuntu Mate, Windows IOT 10, Ubuntu 17.04, Windows 10, Mac without problem.
And anyway today I expect that a USB Touchscreen is Plug&Play like a USB Mouse.

BTW: With for example: "sudo sh ts_calib.sh" I can see that touch is working. So it looks that driver are loaded but the GUI cannot understand the touchdata?

[epikao]

no help? Are more infos required? Is it the wrong forum?

[Sam.Nazarko]

We have covered this here in extensive detail.
https://discourse.osmc.tv/t/osmc-touch-s...blem/54865

It doesn't work with GLESv2.

[epikao]

We have covered this here in extensive detail.
https://discourse.osmc.tv/t/osmc-touch-s...blem/54865

It doesn't work with GLESv2.

I think I have find now a driver that should work with Kodi =>
http://www.eeti.com/touch_driver/Linux/2...-ma.tar.gz

But my problem now is, that I have really no idea how to install that driver correctly.

with evtest I get following:
/dev/input/event0:      Teensyduino Keyboard/Mouse/Touchscreen
/dev/input/event1:      Teensyduino Keyboard/Mouse/Touchscreen
/dev/input/event2:      Teensyduino Keyboard/Mouse/Touchscreen
/dev/input/event3:      Teensyduino Keyboard/Mouse/Touchscreen
Select the device event number [0-3]: 3
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x4d4 version 0x111
Input device name: "Teensyduino Keyboard/Mouse/Touchscreen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value   8671
      Min        0
      Max    32767
    Event code 1 (ABS_Y)
      Value  14035
      Min        0
      Max    32767
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 47 (ABS_MT_SLOT)
      Value      0
      Min        0
      Max        9
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max    32767
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max    32767
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max    65535
    Event code 58 (ABS_MT_PRESSURE)
      Value      0
      Min        0
      Max      255
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
***********************************************
  This device is grabbed by another process.
  No events are available to evtest while the
  other grab is active.
  In most cases, this is caused by an X driver,
  try VT-switching and re-run evtest again.
  Run the following command to see processes with
  an open fd on this device
 "fuser -v /dev/input/event3"
***********************************************
^C
osmc@osmc:/$ 


so I get data from touchscreen, but what's the reason that this data are not seeing from OSMC GUI ? Is it definetly the driver - and I cannot do anything without driver?

[ultraman]

According to ABS_X/Y values (which are very high indicating uncalibrated) you need to calibrate touch: https://kodi.wiki/view/advancedsettings.xml#touchscreen
But even then I'm not sure it will work. At least you should see pointer moving.