New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 377165 link

Starred by 15 users

Issue metadata

Status: Verified
Last visit > 30 days ago
Closed: May 2014
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression

Sign in to add a comment

Touchpad tap to click now flaky on HP CHromebook 11

Reported by, May 24 2014

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 5712.61.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.116 Safari/537.36
Platform: 5712.61.0 (Official Build) stable-channel daisy_spring

Steps to reproduce the problem:
1. When using tap to click the touchpad often doesn't register the tap, was fine yesterday before update 

What is the expected behavior?
It to work like it did before.

What went wrong?
The update made the touchpad unresponsive.

Did this work before? Yes Until this update

Chrome version: 35.0.1916.116  Channel: beta
OS Version: 5712.61.0
Flash Version: Shockwave Flash 13.0 r0

Comment 1 by, May 24 2014

Adding link to current Chromebook Central topic "Tap to Click on Latest Stable"

Comment 2 by Deleted ...@, May 25 2014

I am experiencing the same problem.

Comment 3 by, May 26 2014

Same issue here.  After latest os update touchpad behavior has changed.  Tap takes firmer finger tip taps to activate.  And, mouse movement is not as sensitive as before.  Harder to make cross screen placement.
Labels: -Cr-UI -Pri-2 -Type-Bug Cr-Internals-Input-Touch-Pad Pri-1 Type-Bug-Regression
Many reports of laggy touchpad tracking, flaky tap-top-click and lowered sensitivity in 35 stable.
+Caitlin for triage
Status: Untriaged
Seems to be a person-dependent bug.  On the same machine, I cannot repro but someone else can.

Comment 8 by, May 27 2014

I think that's kind of irrelevant, the fact is this has happened since the update. Something has changed fundamentally.

Comment 9 by, May 27 2014

Labels: ReleaseBlock-Stable M-35

Comment 10 by, May 27 2014

Status: Assigned
I'll take a look

Comment 11 by, May 27 2014

Labels: Iteration-107

Comment 12 by, May 27 2014

Labels: -Pri-1 Pri-0
CY, it looks like this is caused by your xorg-conf CL 7075c44f6bd1d2368021921fae6c4507950adebd

Specifically what I see happening is:

- finger merge finger tags a finger GESTURES_FINGER_MERGE
- this prevents the finger from being able to TTC

I wonder if it would be okay to allow these fingers to do TTC on Spring? Iirc, the point of this flag was to prevent wild cursor movement. I suppose, tho, you don't want two-fingers to then cause a tap-click b/c of merging.

Can you look into this today? If it's a small fix to let these tap, that may be the a solution. The alternative is to revert this CL. Either way, can you do one of the options on ToT and request a merge to R35 and R36?

Labels: -Pri-0 -M-35 Pri-1 M-36
The change was reverted in M35. I'll keep this bug open for M36 - not sure if its an issue in M36.
Labels: Merge-Requested
Status: Started
I think it is better to revert the patch on all branches as it is a fundamental issue of the touchpad firmware as we need to find a better way to tell if a finger with higher pressure is a merged finger or simply a fat finger. Let me revert the original change first.

Revert change for M36:
 Issue 378327  has been merged into this issue.
Labels: -Merge-Requested Merge-Approved
Please revert in 36 as well.
Status: Fixed
Mark it as fixed, and rollback to original issue

If this is fixed, please advise when a new OS download (patch) will be available so I can update?  Thanks
Could someone please respond to my previous comment as to when this fix will be made available
The fix will be pushed in a week or so.

cywang: was the change reverted in ToT too? If not, please keep this bug open until that is resolved. thanks!

Comment 21 by Deleted ...@, May 29 2014

Yes, I noticed this too on my HP Chromebook 11.  Touchpad much more problematic now.
Project Member

Comment 22 by, May 29 2014

Project: chromiumos/platform/xorg-conf
Branch : stabilize-5712.61.B
Author : Chung-yih Wang <>
Commit : 455ef4adf6e5aa046cb08e57aa90235c93d47d16

Code-Review  0 : chrome-internal-fetch
Code-Review  +2: Andrew de los Reyes
Commit-Queue 0 : chrome-internal-fetch
Commit-Queue +1: Andrew de los Reyes
Verified     0 : chrome-internal-fetch
Verified     +1: Andrew de los Reyes
Change-Id      : Ifc148943a95c928bc3fcf94e694c414c8baf2ebf
Reviewed-at    :

Revert "50-touchpad-cmt-spring.conf: tweak finger merge thresholds"

This reverts commit 7075c44f6bd1d2368021921fae6c4507950adebd.

BUG= chromium:377165 
TEST=Test team will test

I tracked down most of the people who had trouble before and saw definite improvement for them in today's M35 build.
5712.61.2, 35.0.1916.116

Leaving as unverified for M36 (though the revert has already landed in 5841.23.0).

@cy: I don't see where this was reverted in M37, did you get ToT yet?
Labels: Hotlist-ConOps
Project Member

Comment 25 by, Jun 3 2014

Project: chromiumos/platform/xorg-conf
Branch : master
Author : Chung-yih Wang <>
Commit : b28915b8906a942f9bbe7cd686562383473da945

Code-Review  0 : Andrew de los Reyes, Shyh-In Hwang, chrome-internal-fetch
Code-Review  +2: Chung-yih Wang
Commit-Queue 0 : Andrew de los Reyes, Shyh-In Hwang, chrome-internal-fetch
Commit-Queue +1: Chung-yih Wang
Verified     0 : Andrew de los Reyes, Shyh-In Hwang, chrome-internal-fetch
Verified     +1: Chung-yih Wang
Change-Id      : Icee39f147740177ac310398d95af30fff415b45d
Reviewed-at    :

Revert "50-touchpad-cmt-spring.conf: tweak finger merge thresholds"

This reverts commit 7075c44f6bd1d2368021921fae6c4507950adebd.

BUG= chromium:377165 
TEST=on device, ttc works no matter if we have a fat finger


Comment 26 by, Jun 4 2014

The patch for ToT was merged. Thanks.

I don't see that this was fixed on M-36.  Can someone verify that the revert landed on 36 as well?

Comment 28 Deleted

Yes, the revert landed in M36.
Status: Verified
Labels: -Merge-Approved Merge-Merged

Comment 32 by Deleted ...@, Jan 10 2015

I bought an Acer Chromebook a little over a month ago. After charging and using it for the first time (guess it updated itself), I noticed the trackpad dysfunctioning, going crazy while the was getting it's 2nd charge. Since then the severity of dysfunction varied. Now it seems worse than ever. I found lots of posts about these issues, via Acer & Google forums, etc. Now it's o1/10/12 and I still find no real fix anywhere. What's up with this atrocious lack of TQM (sincere full-time QA) and zero CS (customer service). Needless to say, this mega-fly in the ointment is causing my otherwise positive experience with the paradigm to descend into near rage and severely frustrating disappointment. Any real, sustainable solutions out there?

Sign in to add a comment