Created attachment 120066 [details] libinput-list-devices Pointer speed is unusable slow. Is there any setting how to fix the problem? Can I provide some more data? Thanks.
Created attachment 120067 [details] libinput-debug-events
libinput 1.1.1 (fc23)
Created attachment 120089 [details] xinput list-props
Created attachment 120090 [details] evemu-record
great. the touchpad doesn't even look like a touchpad, it just does the mouse emulation. So to libinput (and the rest of userspace) it just looks like a 5-button mouse with 2 scroll wheels. Until we have kernel support for that there isn't much you can do beyond trying to increase the pointer acceleration to maximum speed.
I see, that's not so nice. I will store the device in a drawer then. Thank you for your time and analysis. Let me know if I can help with testing.
closing this bug for now, this needs to be fixed in the kernel first. Please raise a bug there or if you're really keen you can start reverse-engineering the protocol HP uses for these devices.
Even this bug is closed, I would be interested in having a look at the raw events of your touchpad. Could you please attach a hid-recorder (project hid-replay[1]) of few events reported by your device? [1] http://bentiss.github.io/hid-replay-docs/
Created attachment 120316 [details] hid-recorder Attached hid-recorder output. Hope it helps.
Created attachment 120317 [details] hid-record2
Thanks for the logs. From a HID point of view, your touchpad is seen with 2 types of reports, one for the buttons/wheel and one for the mouse events. There is nothing there which allows to think that there is a hidden mode where the touchpad sends true multitouch data. There is nothing I can do for you, sorry. You might have more success by reverse engineering the protocol the windows driver uses, but this goes beyond the scope of this bug. Plus, I am not even sure that such a mode exists.
So that I bought a crap, good to know. Thanks for your feedback.
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.