@markismus: about versions that 'work' on my kobo, I now have a clearer idea about what's happening: if I put my finger on the screen, I get
Code:
# tev fed| 558 | 291854 | 342 | 307 | 1 | Evt 0
# in tap state...
# set up hold timer
# hold gesture detected in slot 0
# in hold state...
# tev fed| 558 | 405127 | 341 | 307 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 504107 | 341 | 308 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 688109 | 340 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 872074 | 339 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 27735 | 339 | 310 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 225903 | 338 | 311 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 749673 | 337 | 311 | 1 | Evt 0
# in hold state...
# tev fed| 560 | 4570 | 337 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 560 | 13418 | 337 | 309 | -1 | Evt 0
# in hold state...
# hold_release detected in slot 0
which means that tev is populated with touch events from very close coordinates, as if I were moving my finger, except I'm not. There is no multitouch, no "two finger-tap" and so on, so I think the best think would be to put a threshold, like 5 points or so on this device, below which a touch event on hold state would be discarded?