@kaihengfeng  I was just having an "attack" of these events as I started writing this post! I guess it DOES come in clusters for me, after all. :|  I tried `sudo rmmod i2c-hid hid-multitouch && sudo modprobe i2c-hid hid-multitouch`. Almost immediately afterwards I still had the problem.

Today I left `sudo evtest /dev/input/event16 |grep EV_KEY` running, to try and catch the trackpad in the act. It acted up, but when I switched to the desktop with that terminal on it (with the keyboard), it had already resolved itself. It quickly acted up again, however. At present it seems like it just wants to prove me wrong, that it CAN happen in clusters. :|

Here's the output. I'll annotate as we go along. You can see some normal mouse activity here, with the timestamps incrementing by a second or more between event clusters.

Event: time 1509044426.298980, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044426.298980, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044426.434514, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044426.434514, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044427.045093, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1509044427.137465, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1509044427.164803, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044427.164803, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044427.350292, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044427.350292, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044427.704242, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044427.704242, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0

Right here, it begins. I don't know if the first event is real or not, but now we're getting BTN_TOUCH and BTN_TOOL_FINGER flickering on and off about every 10000 microseconds.

Event: time 1509044429.679735, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044429.679735, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044429.706049, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044429.706049, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044429.720705, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044429.720705, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044429.833727, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044429.833727, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044429.841380, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044429.841380, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044429.855022, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044429.855022, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044429.862632, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044429.862632, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044429.968564, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044429.968564, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044429.976200, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044429.976200, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.387279, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044430.387279, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.394908, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044430.394908, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.430921, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0

Right about here comes my next mouse gesture, which gets read as a repeated BTN_TOOL_DOUBLETAP, because it thinks there's already a finger on the trackpad. Don't let the name fool you, BTN_TOOL_DOUBLETAP only indicates there are two fingers on the trackpad. It's not a click of any kind. I have touch-to-tap disabled, otherwise I would expect this to react like a rapid fire right click. Anyone experiencing that?

Event: time 1509044430.430921, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044430.480311, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.480311, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044430.487841, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.487841, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044430.494734, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.494734, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044430.502024, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.502024, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044430.508762, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.508762, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044430.608509, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.608509, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044430.615126, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.615126, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044430.771653, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.771653, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044430.778310, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.778310, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044430.791841, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044430.791841, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0

I guess I realized it was acting up, and headed too the other desktop. 

Event: time 1509044430.806529, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044430.806529, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.820205, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044430.820205, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.827792, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044430.827792, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.848595, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044430.848595, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044430.856310, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044430.856310, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044430.862821, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044430.862821, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0

This continues for several seconds. Here are some other interesting bits:

Event: time 1509044433.205526, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044433.205526, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044433.220142, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044433.220142, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044433.297457, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044433.297457, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044433.716618, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044433.716618, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044436.405294, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044436.405294, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044438.066387, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044438.066387, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044440.017091, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044440.017091, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044440.358260, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044440.358260, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044441.783929, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044441.783929, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044442.508233, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044442.508233, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044442.586907, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044442.586907, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 1


The timestamps jump. There was a good second and a half, between 1509044436 and 1509044438, that it stopped "flickering" input like this. And again right afterwards, from 30-40 seconds. Then it's back in action again, albeit at a slower pace it seems. But don't worry, it picks up again. I _think_ that there I left my finger off the trackpad for a second to see if it stopped. Honestly the events go by too quickly for me to correlate very well. :( Note the tripletap where I tried to scroll my way out of the lock. (didn't work).

I thought I captured the end of the sequence there, but it started up again so quickly, it's possible I was mistaken. So I started the capture again, and this time definitely caught it ending:

Event: time 1509044461.318212, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044461.318212, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 0
Event: time 1509044461.964355, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044461.964355, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 1
Event: time 1509044462.247519, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 1
Event: time 1509044462.247519, type 1 (EV_KEY), code 334 (BTN_TOOL_TRIPLETAP), value 0
Event: time 1509044463.206013, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1509044463.368917, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1509044463.417782, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044463.417782, type 1 (EV_KEY), code 333 (BTN_TOOL_DOUBLETAP), value 0
Event: time 1509044463.772504, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044463.772504, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0
Event: time 1509044469.045093, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1509044469.045093, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 1
Event: time 1509044469.534121, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1509044469.534121, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), value 0

One hard click that counted as BTN_LEFT. My reading of this is that I left my finger on there for a split second, and that's the BTN_TOOL_FINGER=1 at 1509044463.417782. DOUBLETAP is released at the same time as that finger is registered, and a third of a second later, TOUCH and TOOL_FINGER are simultaneously released. The next events come 6 seconds later, and don't look like "flickering" anymore. That's a solid half second movement, which I think is "real."  

IF that interpretation is correct, there's a similar pattern the first time, and I _did_ catch the ending of the episode... it just restarted. But I'm not confident enough to say that's the case.

But for now, here's what I take away:

* The episodes DO come in clusters.
* It's a rapid-firing of BTN_TOUCH/BTN_TOOL_FINGER that flicks on and off about 8 times a second.
* A hard left click reliably ends it for me. It's possible that's because I tend to leave the finger on the trackpad for a split second after the click, long enough to register a new BTN_TOOL_FINGER. 

I've saved a txt of my terminal output. It's one long normal session where an episode starts, and I suspect ends. Then a second capture that begins in the middle of an episode, and ends just after the end of the episode. Unfortunately I'm getting an error (Request URI too long) when I hit "Add attachment or patch". Happy to try again later.