Is there a Linux utility to configure the amount of pressure required to register a click on the haptic touchpad?
I find myself registering false clicks too frequently. It makes the use of gestures a pain as well.
Is there a Linux utility to configure the amount of pressure required to register a click on the haptic touchpad?
I find myself registering false clicks too frequently. It makes the use of gestures a pain as well.
I suggest disabling tap to click first and then there is a sensitivity setting:
The sensitivity of the haptic touchpad has been quite frustrating unfortunately, I can’t count how many times a day I’m just moving the mouse and end up dragging a browser tab out of a window or select a bunch of text.
I tried adjusting the settings via hdi-tools (on Fedora 44) as described but it doesn’t seem to make a huge difference unfortunately, but maybe actually disabling tap to click/drag in gnome will help.
Well it is much better than the Touchpad on any Windows laptop I had, maybe the TrackPoint on ThinkPad is better, except for scrolling. It’s not as good as a MacBook Air/Pro or the external under macOS, not Linux or even Windows.
But I always disable tap-to-click on every touchpad as I often tend to tap when trying to just move the cursor.
Bloody hell, a Python tool that requires root… Great idea! fml I ended up giving my user’s group rw on the devices.
In any case, according to that doc:
To set the sensitivity to Low, run: hid-feature set /dev/hidraw2 -f 80000 1
To set the sensitivity to Medium, run: hid-feature set /dev/hidraw2 -f 80000 2
To set the sensitivity to High, run: hid-feature set /dev/hidraw2 -f 80000 3
and then
To adjust the intensity of the Haptic Touchpad run the command: hid-feature set /dev/hidraw2 -f 90000 70
and finally
The number at the end of the command can be set to any value between 0 and 100.
So, is the scale 1-3 as the first bit says? Or is it 0-100 as the last bit? And what’s the difference between 8000 and 9000 for the first number? According to the help text of hid-feature set, the first number is the feature. So what am I adjusting when using either of those magic numbers? It talks about sensitivity vs intensity. What does this even mean? I feel no difference whatever I set on them.
Honestly, does anyone even proof-reads those docs?
Ok, after experimenting a bit more, I seem to understand what intensity means. It’s about the intensity of the haptic feedback.
If I set it to 0, there is no feedback. If I then set it to 1, there is still no feedback. In fact, it’s only when I set it to 50 or more that the feedback is back. Once it is indeed back, I can set it as low as 1 and it will still have feedback. In any case, there is no difference whatsoever between 1 and 100, so it’s clearly a binary on/off switch. I’m fine with that. The level of feedback doesn’t bother me.
Unfortunately, the sensitivity which is what I do care, only seems to have 3 levels: 1-3 but again with no difference between them. So the choice in this case is not even binary. It is what was given. Period.
I also noticed the same, I could adjust the haptic vibration as a binary and the sensitivity seems to have no noticeable effect - can anyone else confirm the opposite?
I’m coking from a MacBook Air where the touchpad is essentially perfect. I also notice very fine movements are not accurately tracked here on the fw, like trying to move a few pixels here and there it jumps around a bit where on the MacBook it feels one to one with the finger movement
Fine movements seem fine on mine. Comparable with my MacBooks. In fact, tracking movement seems pretty comparable.
Perhaps this is something that can be configured on the desktop environment? I’m on KDE, with pointer speed set to -0.20 and Enable pointer acceleration ticked (this one doesn’t have adjustments).
I’d really like to reduce the click sensitivity, and if possible the tapping sensitivity as well.
The other thing that doesn’t work too well is palm detection. Too frequently I find myself losing focus as I type because my palm touched the trackpad.
I opened a support request. Hopefully this is something that can be addressed in firmware or software.
Novel use for a shiny surface
![]()
Maybe this helps?
There’s this command:
framework_tool --click-force high
framework_tool --click-force medium
Thank you, I wasn´t aware of this tool. I imagine it does the same as tweaking /dev/hidraw? directly. In any case, same results - i.e. nothing noticeable.