MPP stylus causes "missing/bad" frames

[tmarkov]

I'm using an MPP stylus, and I'm getting "disconnects" (i.e. as if the stylus was lifted and then put down again) all the time (as in, multiple times per second).

Here's some output from wev logging input events:

[13:      wl_pointer] motion: time: 41675531; x, y: 152.277344, 404.492188
[13:      wl_pointer] motion: time: 41675531; x, y: 152.277344, 404.492188
[13:      wl_pointer] motion: time: 0; x, y: 152.277344, 404.492188
[13:      wl_pointer] motion: time: 0; x, y: 152.277344, 404.492188
[13:      wl_pointer] motion: time: 41675540; x, y: 153.277344, 400.160156
[13:      wl_pointer] motion: time: 41675548; x, y: 154.402344, 395.937500
[13:      wl_pointer] motion: time: 41675555; x, y: 158.398438, 387.714844
[13:      wl_pointer] motion: time: 41675561; x, y: 168.273438, 371.828125
[13:      wl_pointer] motion: time: 41675561; x, y: 168.273438, 371.828125
[13:      wl_pointer] motion: time: 0; x, y: 168.273438, 371.828125
[13:      wl_pointer] motion: time: 41675571; x, y: 171.898438, 368.609375
[13:      wl_pointer] motion: time: 41675578; x, y: 175.648438, 365.496094
[13:      wl_pointer] motion: time: 41675585; x, y: 183.648438, 360.609375
[13:      wl_pointer] motion: time: 41675593; x, y: 191.648438, 355.722656
[13:      wl_pointer] motion: time: 41675600; x, y: 200.144531, 354.054688
[13:      wl_pointer] motion: time: 41675608; x, y: 208.769531, 352.500000
[13:      wl_pointer] motion: time: 41675615; x, y: 216.519531, 353.609375
[13:      wl_pointer] motion: time: 41675621; x, y: 231.390625, 357.054688
[13:      wl_pointer] motion: time: 41675621; x, y: 231.390625, 357.054688
[13:      wl_pointer] motion: time: 0; x, y: 231.390625, 357.054688
[13:      wl_pointer] motion: time: 0; x, y: 231.390625, 357.054688
[13:      wl_pointer] motion: time: 41675630; x, y: 233.265625, 359.054688
[13:      wl_pointer] motion: time: 41675636; x, y: 238.890625, 365.054688
[13:      wl_pointer] motion: time: 41675636; x, y: 238.890625, 365.054688
[13:      wl_pointer] motion: time: 0; x, y: 238.890625, 365.054688

I'm guessing the 0 timestamps are causing the issue, but I'm struggling to figure out why they're appearing. I notice that they always appear after a "duplicated: event (and duplicate the coordinates again). My guess is that some frames are improperly parsed, causing errors and values carrying over? But that's just a guess.