There are no `ABS_MT_POSITION_X` and `ABS_MT_POSITION_Y` sent from the tincore_mt device

21 views
Skip to first unread message

Ulysses Zhan

unread,
Jul 22, 2022, 11:56:08 PM7/22/22
to Tincore
After tincore_mt is selected as the touchscreen where touches are emulated, if you look into it by using `getevent` command from ADB shell, you can see events like these:
```
[   35421.844780] EV_ABS       ABS_MT_SLOT          00000000            
[   35421.844780] EV_ABS       ABS_MT_TRACKING_ID   00000452            
[   35421.844780] EV_KEY       BTN_TOUCH            DOWN                
[   35421.844780] EV_SYN       SYN_REPORT           00000000            
[   35427.736954] EV_ABS       ABS_MT_SLOT          00000001            
[   35427.736954] EV_ABS       ABS_MT_TRACKING_ID   00000453            
[   35427.736954] EV_SYN       SYN_REPORT           00000000            
[   35432.260998] EV_ABS       ABS_MT_TRACKING_ID   ffffffff            
[   35432.260998] EV_SYN       SYN_REPORT           00000000            
[   35434.277339] EV_ABS       ABS_MT_SLOT          00000000            
[   35434.277339] EV_ABS       ABS_MT_TRACKING_ID   ffffffff            
[   35434.277339] EV_KEY       BTN_TOUCH            UP                  
[   35434.277339] EV_SYN       SYN_REPORT           00000000
```
As can be seen, there are no `ABS_MT_POSITION_X` or `ABS_MT_POSITION_Y`, which makes it purely useless.
The only way of working around this is to use the physical touchscreen instead of tincore_mt. However, this will conflict with physical touch events and have strange problems like [this](https://groups.google.com/g/tincore-contact/c/27QzLkaR7MY).
I hope the developers team can look into this bug and make tincore_mt useful again.
Reply all
Reply to author
Forward
0 new messages