| Summary: | Palm detection doesn't work on Chuwi Lapbook 14.1 touchpad | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | xrcrod |
| Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | peter.hutterer |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
xinput list and xinput list-props
evemu-describe output |
||
looks like this devices isn't detected as touchpad device. Please attach an evemu-describe output here for the two device nodes exposed by the device, thanks. Created attachment 131031 [details]
evemu-describe output
I actually had to wipe that Manjaro install because the emmc is buggy. I'm currently waiting for a ssd but in the meantime, is it OK if I continue with Ubuntu 17.04 off a live USB? The kernel version is the same, the xinput list output is the same and the issue is the same.
right, the problem here is that the device isn't recognised by the kernel as touchpad device. The first event node event4 is a keyboard, the second node event5 is a relative mouse with a few multimedia keys on top. The mouse provides vert and horiz scroll wheels, but if the device physically is a touchpad then it is still in mouse emulation mode. That's the common thing for touchpads, they need some special sequence to switch them into absolute mode - without that we cannot provide the various touchpad functions, palm detection is one of those. This device needs kernel support first. I did some research and it appears that some touchpads might not physically support absolute mode (and I'm not sure if this one does). I understand there are some fancy palm detection algorithms (https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html), but if I'm OK with just disable-while-typing, is enabling support for disable-while-typing something that should be done in libinput or in the kernel too? I'm sure they physically support it, because that's how sensors work. Whether the firmware exposes it or whether the drivers can be reverse-engineered is another matter though. See if there are windows drivers that support it, that'll at least tell you the answer to the second question. dwt is handled by libinput, but all that support is hooked up into the touchpad code which is quite different to the mouse code. so it's a bit of work to move it across and make it more generic. I'm flat out with other things, so you'd have to take that project on if you want it done. I git cloned the libinput source code and took a look at the source code and it doesn't seem too intimidating. Unfortunately, I'm currently busy with my ISP (because they seem to keep disconnecting my internet line) but I'll hopefully be able to submit a patch in 2 weeks or so. Was there any progress on this? I also have a Chuwi with the same touchpad, and it's quite annoying that the cursor keeps jumping around while typing. Love to have palm rejection or at least turning it off while typing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 130885 [details] xinput list and xinput list-props I am using libinput with X on Manjaro Linux and the palm detection doesn't seem to work. I do not see an option to disable the touchpad when typing either. The touchpad itself works fine. I can manually fix this using synclient/syndaemon but if I'm not mistaken, if I want this to work out of the box for other GNU/Linux users with the same hardware, I have to file a bug report so that it can be added to the database? Correct me if I am wrong please.