For future reference: the cover setting is irrelevant here, we get the hardware events regardless
.
On the Forma, the SleepCover *will* send KEY_REPEAT events (every 80ms after a 400ms delay), so, that won't help, and while fairly stupid, that's at least not mysterious
.
EDIT: See
this KO issue for more details
. And a bonus picture in case you were looking for the hall sensor position ;p.
Now, regarding those weird touch events on the H2O, I'm a bit stumped.
That *looks* like an EV_KEY -> KEY_DOT
Code:
E: 1.412001 0004 0004 458807 # EV_MSC / MSC_SCAN 458807
E: 1.412001 0001 0034 0001 # EV_KEY / KEY_DOT 1
E: 1.412001 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +1412ms
:E: 1.468005 0004 0004 458807 # EV_MSC / MSC_SCAN 458807
E: 1.468005 0001 0034 0000 # EV_KEY / KEY_DOT 0
E: 1.468005 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +56ms
(That's from my actual keyboard, hence the stray : (AZERTY layout here) ;p)
Except that doesn't make any sense for a Touch input device, and that final 0x20 byte doesn't make sense either.
The only other event with a 0x34 code is ABS_MT_ORIENTATION, but that's an EV_ABS, and should never happen on those devices.
It is the final link in the event chain on a Forma, though, but that looks like this:
Code:
E: 41.149809 0003 0034 0125 # EV_ABS / ABS_MT_ORIENTATION 125
E: 41.149809 0000 0002 0000 # ++++++++++++ SYN_MT_REPORT (0) ++++++++++
E: 41.149809 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +11ms
(That's output from evemu-record, of which I have a Kobo build
here).