If you manage to identify the device in a udev rule you could try to attach ID_INPUT_TOUCHSCREEN=1 to extend the result of udevs own checks with the right result. Meanwhile I will look how to extend the detection logic inside systemd/udev to get this fixed.
I believe the problem here is not limited to this device. Looking through the exposed keys it also sends BTN_TOUCH which should be enough for udev to detect it..
If you manage to identify the device in a udev rule you could try to attach ID_INPUT_ TOUCHSCREEN= 1 to extend the result of udevs own checks with the right result. Meanwhile I will look how to extend the detection logic inside systemd/udev to get this fixed.
I believe the problem here is not limited to this device. Looking through the exposed keys it also sends BTN_TOUCH which should be enough for udev to detect it..