[HP Stream 11 Notebook - 11-d010nr] Max Double-Tap Time too short

[Amordea Whiteoak]

Hi,

There is an issue with this clickpad's simulated clicks. Specifically, the window for double-tapping (tapping the touchpad twice to simulate a double-click) is remarkably brief. Let me be clear, double-tapping on the touchpad does work, however if you do not get the second tap within a very short window after the first tap, it seems to fail to register as a double-click, counting it as two unrelated single clicks--this is an uncomfortably short window of opportunity.

This problem exists upstream as well, tested as of this writing on the latest mainline kernel (version 3.18rc7).

Things I have tried:
Believing it to be a possible configuration issue, I attempted to increase the double-tap window by running the command:
synclient MaxDoubleTapTime=500
to allow a half-second delay instead of the default 180ms. However even after disabling and re-enabling the touchpad (xinput disable/enable <id>), there was no change in the brevity of this window.

WORKAROUND: Tapping three times will register as a double-tap with a much more forgiving windolw of opportunity, but this is not ideal as it sometimes will also count the third click as its own separate click, which could cause unforseen problems in places where only a double-click specifically is desired.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: amordea 1728 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
Date: Mon Dec 8 20:26:02 2014
HibernationDevice: RESUME=UUID=6777feff-0199-4057-9990-625a28c71914
InstallationDate: Installed on 2014-12-03 (5 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP Stream Notebook PC 11
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=978b7845-5b80-4552-91ed-1f031c360c6e ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8023
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.06:bd11/14/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Stream Notebook PC 11
dmi.product.version: Type1 - ProductConfigId
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Amordea Whiteoak (amordea)]

Sorry, I believe I may have been unclear, but I have tested this on the current 3.16.0-25 kernel as well with the same issue, so it is both mainline and upstream.

However I would like to add that as part of bug #1398533 I reported this issue to the kernel.org linux-input mailing list. They did not believe it was a kernel issue and wanted me to report it here as a separate bug first.

If you would still like for me to take this upstream, I will, but I just want to make sure that is truly the appropriate place for this bug, first.

Thank you.