Snappy: Mitigate involuntary input of touchpad
Snappy design has mechanic issue around the touchpad:
Namely hold the device and shake it intensively, it would
generate false input events, which potentially causes an
involuntary UI event from user's perspective.
In order to tackle this odd, we were suggested to follow
the CL:352860.
This patch diables "Zero Finger Clicks" for snappy to
mitigate ghost events; even click is reported physically,
the higher level gesture-interpreter will suppress it
so there will be no fingers action on the UI layer.
BUG=b:36018765
TEST='cros_workon-snappy start chromeos-base/gestures-conf'
'emerge-snappy chromeos-base/gestures-conf'
'cros deploy IP-of-DUT chromeos-base/gestures-conf'
reboot to apply new cmt configuration onto device,
intensively shake device while using online painting
application such as 'https://sketch.io/sketchpad/'
to examine its efficacy of supressing false event;
Alternately, move mouse pointer over a clickable
UI element while shaking device to examine.
It is able to monitor low-level 'evtest' report in
parallel to examime these involuntary clicks are
successfully been suppressed.
Change-Id: Id19269ad96dab3afe8015487b9f514d4b170bf06
Signed-off-by: Harry Pan <harry.pan@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/456122
Commit-Ready: Harry Pan <harry.pan@intel.corp-partner.google.com>
Tested-by: Johnny Jiang <johnny.jiang@quanta.corp-partner.google.com>
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
diff --git a/50-touchpad-cmt-snappy.conf b/50-touchpad-cmt-snappy.conf
new file mode 100644
index 0000000..d2e884c
--- /dev/null
+++ b/50-touchpad-cmt-snappy.conf
@@ -0,0 +1,7 @@
+Section "InputClass"
+ Identifier "touchpad snappy elan"
+ MatchIsTouchpad "on"
+ MatchDevicePath "/dev/input/event*"
+ MatchProduct "Elan"
+ Option "Zero Finger Click Enable" "0"
+EndSection
