Philip Howard

``` sudo usbhid-dump --model=093a:2510 007:012:000:DESCRIPTOR 1634121261.154741 05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 03 15 00 25 01 75 01 95 03...

The second descriptor is your (very complicated and fancy :laughing:) mouse: ``` 0x05, 0x01, // Usage Page (Generic Desktop Ctrls) 0x09, 0x02, // Usage (Mouse) 0xA1, 0x01, // Collection (Application)...

For comparison, here's my Alienware AW610M mouse (wireless dongle): ``` sudo usbhid-dump -d 0461:4ec0 001:023:002:DESCRIPTOR 1634155310.886475 06 00 FF 09 01 A1 01 09 02 15 00 26 FF 00...

A bit of sleuthing reveals the raw report size from my mouse is 12 bytes, and looks something like: ``` # LMB Pressed 149.1145 72 49 67 61 00 00...

Okay I've fleshed out that tool into something that'll try and annotate some of the stuff it detects: https://github.com/Gadgetoid/pi400kb/blob/feature/tools/tools/rawcap.py eg: ``` 7.2861 8b 50 67 61 00 00 00 00...

> And mouse move events show as keypresses in laptop terminal. Thought I’d fixed this- IE the events were just mislabelled. There might still be a bug. The keyboard is...

This is no-doubt some USB descriptor and report ID weirdness then. What's OS are you running on your laptop?

That'll do it! Whoops! Actually writing a systemd unit was on my TODO list for this now it works better as a daemon with a toggle on/off. I feel it...

Yeah if you don't completely replace the USB descriptors with the ones from your mouse then there will be a disconnect between the events fetched from the mouse and how...

Really basic hook added in https://github.com/Gadgetoid/pi400kb/pull/9