Bug 96875 - Decreased touchpad area - Lenovo V360
Summary: Decreased touchpad area - Lenovo V360
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-09 23:15 UTC by Diego Palacio
Modified: 2016-07-15 04:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
udev rule (136 bytes, text/plain)
2016-07-09 23:15 UTC, Diego Palacio
Details
Content of /sys/class/dmi/id/modalias (134 bytes, text/plain)
2016-07-09 23:16 UTC, Diego Palacio
Details
Virtual description of my input device (113.71 KB, text/plain)
2016-07-09 23:17 UTC, Diego Palacio
Details
udevadm info output (692 bytes, text/plain)
2016-07-09 23:18 UTC, Diego Palacio
Details
Current libinput settings for the device (1.26 KB, text/plain)
2016-07-09 23:19 UTC, Diego Palacio
Details
touchpad-edge-detector tool (656 bytes, text/plain)
2016-07-11 00:43 UTC, Diego Palacio
Details
new udev rule (137 bytes, text/plain)
2016-07-13 00:45 UTC, Diego Palacio
Details

Description Diego Palacio 2016-07-09 23:15:08 UTC
Created attachment 124971 [details]
udev rule

Recently, I followed the advice to change synaptics over to libinput. The former allowed only to use the vertical scrolling, whereas the latter activate both the vertical and the horizontal scrolling. Nevertheless, the scrolling edges are now too wide and, according to the man page, libinput does not allow to disable the horizontal scrolling.

I followed this instructions: https://wayland.freedesktop.org/libinput/doc/latest/absolute_coordinate_ranges.html. And I found a significant discrepancy.

For the time being, it seems that the axis override worked; then, I want to attach the necessary information.

I have a Lenovo V360 laptop and its touchpad dimensions are: 80 mm x 41 mm. I use Archlinux.

The libinput version: 1.3.3-1; and: xf86-input-libinput-0.19.0-1.
Comment 1 Diego Palacio 2016-07-09 23:16:11 UTC
Created attachment 124972 [details]
Content of /sys/class/dmi/id/modalias
Comment 2 Diego Palacio 2016-07-09 23:17:29 UTC
Created attachment 124973 [details]
Virtual description of my input device
Comment 3 Diego Palacio 2016-07-09 23:18:10 UTC
Created attachment 124974 [details]
udevadm info output
Comment 4 Diego Palacio 2016-07-09 23:19:06 UTC
Created attachment 124975 [details]
Current libinput settings for the device
Comment 5 Peter Hutterer 2016-07-11 00:34:24 UTC
run the touchpad-edge-detector tool too please, so we know what the actual coordinates are the touchpad sends. thanks.
Comment 6 Diego Palacio 2016-07-11 00:43:50 UTC
Created attachment 124997 [details]
touchpad-edge-detector tool

No problem, here it is...
Comment 7 Peter Hutterer 2016-07-11 02:44:57 UTC
hmm, you already have something that overrides the touchpad range. where is this coming from? I don't see anything upstream for this
Comment 8 Diego Palacio 2016-07-11 03:29:15 UTC
(In reply to Peter Hutterer from comment #7)
> hmm, you already have something that overrides the touchpad range. where is
> this coming from? I don't see anything upstream for this

I'm not quite sure what do you mean. The only thing that I can say is that I followed the instructions and (maybe subjectively) I think that it worked, because I feel the difference and the values are now different; but I don't have actual proofs.

Maybe, if you give me some instructions, I can find something. 

Sorry for not being of any help...I'm only an intermediate user.
Comment 9 Peter Hutterer 2016-07-11 04:53:16 UTC
wait, so you mean you already put the hwdb file in place? if so that explains where the overrides come from, if not go search for a .hwdb file that sets 

EVDEV_ABS_00=1260:5853:54
EVDEV_ABS_01=821:5330:90
Comment 10 Diego Palacio 2016-07-11 05:03:51 UTC
(In reply to Peter Hutterer from comment #9)
> wait, so you mean you already put the hwdb file in place? if so that
> explains where the overrides come from, if not go search for a .hwdb file
> that sets 
> 
> EVDEV_ABS_00=1260:5853:54
> EVDEV_ABS_01=821:5330:90

Yes, I already put it in place. For that reason, I wanted to report that it worked. The file that I used is attached (udev_rule).
Comment 11 Peter Hutterer 2016-07-12 05:21:39 UTC
ah, now I get it. though the touchpad edge detector sends different axis ranges than the ones in the udev rule. please run it again, make sure you really do reach all edges on the touchpad, then post the output numbers here. I'll get this into system asap after. bonus points for doing the resolution calculation for me based on the final set of numbers :)
Comment 12 Diego Palacio 2016-07-13 00:45:24 UTC
Created attachment 125044 [details]
new udev rule

(In reply to Peter Hutterer from comment #11)
> ah, now I get it. though the touchpad edge detector sends different axis
> ranges than the ones in the udev rule. please run it again, make sure you
> really do reach all edges on the touchpad, then post the output numbers
> here. I'll get this into system asap after. bonus points for doing the
> resolution calculation for me based on the final set of numbers :)

I made it again and I attached the new udev rule (udev_rule_2). Although, the touchpad-egde-detector tool does not showed the exact numbers (but they are pretty close): 

Move one finger around the touchpad to detect the actual edges
Kernel says:	x [1170..5931], y [886..5330]
Touchpad sends:	x [1243..5927], y [902..5330] \^C

Touchpad size as listed by the kernel: 82x40mm
Calculate resolution as:
	x axis: 4761/<width in mm>
	y axis: 4444/<height in mm>

Suggested udev rule:
# <Laptop model description goes here>
evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvr2DCN18WW:bd06/18/2010:svnLENOVO:pn0911BCS:pvrLenovoV360:rvnLENOVO:rnMoutCook:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:*
 EVDEV_ABS_00=1243:5927:<x resolution>
 EVDEV_ABS_01=902:5330:<y resolution>

...I suppose that it does not matter,
Comment 13 Peter Hutterer 2016-07-13 01:06:49 UTC
thanks, submitted as: https://github.com/systemd/systemd/pull/3712

also I just filed bug 96910 because despite the axis corrections I think we should just get rid of the horizontal area in your case.
Comment 14 Peter Hutterer 2016-07-15 04:34:27 UTC
Merged into systemd, see https://github.com/systemd/systemd/pull/3712


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.