TOUCHPAD-EDGE-DETECTOR(1)
β¨ touchpad-edge-detector(1) β¨
okay bestie, welcome to the General Commands Manual page for touchpad-edge-detector and lemme tell you, this little tool is everything π
πΈ NAME πΈ
touchpad-edge-detector β prints the axis ranges for a touchpad device π
π¦ SYNOPSIS π¦
touchpad-edge-detector [--help] WxH /dev/input/eventX
π DESCRIPTION π
so basically, touchpad-edge-detector sits there reading touchpad events straight from the kernel and keeps track of the minimum and maximum coordinates as you move your finger around. it's an interactive tool, meaning you have to do the work, bestie β drag that finger all over the touchpad and genuinely try to trigger an event at every single edge. like, all of them. no skipping. π€
to stop collecting events and get the summary printed, hit Ctrl+C. and ngl, the recommendation is to run this thing several times so you actually get a reliable result. one run is giving "first draft" energy, we want the final version. β¨
π OPTIONS π
WxHβ the width and height of your touchpad, in mm</> (millimeters, queen). so for a touchpad that's100mmwide and75mmhigh, you'd pass100x75. this one is required, no cap. π«Ά/dev/input/eventXβ the event node of the touchpad you want to read events from. wanna find your options? you can get a list of possible event nodes with any one of these commands:libinput record,evemu-record, orevtest. alternatively, the event node for a device is listed in theHandlers=line of/proc/bus/input/devices. also required, periodt. π--helpβ prints a short help description. cute, quick, iconic. π
π NOTES π
when it's done, this tool prints out a summary of all the events it collected plus a suggested udev rule. the tea here is: because of rounding errors, it's rare to get an exact match for your touchpad's actual dimensions. that's just how it is. but if the discrepancy is more than 5mm, you should fix it with that suggested udev rule. don't ignore it. π
and listen β that udev rule should be simplified and then submitted as a pull request to the system repository over at https://github.com/systemd/systemd. if you want further guidance (and honestly, you probably do), go look at the file /usr/lib/udev/hwdb.d/60-evdev.hwdb. it's giving homework but it's worth it. π
π SEE ALSO π
k bye bestie, that's the whole page π this was touchpad-edge-detector(1) from the General Commands Manual β go measure those edges, slay, and remember: several runs or it doesn't count. mwah πβ¨
π¦ where this page comes from
- alpine 3.24: libevdev-doc 1.13.6-r0 Β· MIT
- arch rolling: libevdev 1.14.0-1 Β· MIT
- debian bookworm: libevdev-tools 1.13.0+dfsg-1 Β· MIT
- debian trixie: libevdev-tools 1.13.4+dfsg-1 Β· MIT
- fedora 43: libevdev-utils 1.13.4-2.fc43 Β· MIT
- fedora 43: libevdev-utils 1.13.6-1.fc43 Β· MIT
- fedora 44: libevdev-utils 1.13.6-2.fc44 Β· MIT
- fedora 44: libevdev-utils 1.13.7-1.fc44 Β· MIT
- nixos 26.05: libevdev 1.13.6
- nixpkgs unstable: libevdev 1.13.6
- opensuse-leap 16.0: libevdev-tools 1.13.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libevdev-tools 1.13.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libevdev-tools 1.13.3-160000.2.2 Β· MIT
- opensuse-leap 16.0: libevdev-tools 1.13.3-160000.2.2 Β· MIT
- ubuntu jammy: libevdev-tools 1.12.1+dfsg-1 Β· MIT
- ubuntu noble: libevdev-tools 1.13.1+dfsg-1build1 Β· MIT
- ubuntu questing: libevdev-tools 1.13.4+dfsg-1
- ubuntu resolute: libevdev-tools 1.13.6+dfsg-1 Β· MIT
- ubuntu stonking: libevdev-tools 1.13.6+dfsg-3 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms