New issue
Advanced search Search tips

Issue 809649 link

Starred by 1 user
Status: Duplicate
Merged: issue 793188
Owner: ----
Closed: Feb 2018
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

Intermittent disabled touchpad events after suspend

Reported by christia...@fraction.io, Feb 6 2018 
Google Chrome	63.0.3239.140 (Official Build) (64-bit)
Revision	0
Platform	10032.86.0 (Official Build) stable-channel samus
Firmware Version	Google_Samus.6300.174.0
ARC	4524559

What steps will reproduce the problem?
(1) Close lid to suspend.
(2) Lift lid to resume.
(3) Move finger across touchpad.

What is the expected result?
Touchpad should continue working normally and move the cursor.

What happens instead?
Touchpad only registers hard clicks, but doesn't respond to taps, swipes, or any other movement. The only way to fix the touchpad is to restart the computer. This only happens intermittently, so I took the opportunity to dump the logs now that it's happened again. This issue has persisted across powerwashes, full system recovery, and mentioned by other 2015 Chromebook Pixel (Samus) owners.

I've used `evtest` in crosh to show that only the hard click event is registered, as well as dumping my logs below. Please let me know if there's any other useful information I can add. Thanks for your help on this issue!
debug-logs_20180206-113955
2.2 MB View Download
evtest.log
3.2 KB View Download

Comment 1 by christia...@fraction.io, Feb 6 2018 

I'm not sure whether this is available to you in the debug log above, but while troubleshooting I found this change, which was *very* useful: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/493612

I was able to open chrome://system and take a look at the Atmel values (attached), which show the touchscreen (atmel_ts) having reasonable values while the touchpad (atmel_tp) values are all zeroed out. I'm not sure what causes the change, but I thought it might be useful for debugging.

P.S. I've enabled chrome://flags/#ash-debug-shortcuts to toggle the touchpad on and off, but unfortunately this doesn't seem to re-calibrate the values in chrome://system.
atmel.log
41.9 KB View Download

Comment 2 by dtapu...@chromium.org, Feb 6 2018

Components: Internals>Input>Touch>Pad

Comment 3 Deleted

Comment 4 by christia...@fraction.io, Feb 6 2018 

I've found some related issues describing similar problems:

- https://bugs.chromium.org/p/chromium/issues/detail?id=543616
- https://bugs.chromium.org/p/chromium/issues/detail?id=593395
- https://bugs.chromium.org/p/chromium/issues/detail?id=598751
- https://bugs.chromium.org/p/chromium/issues/detail?id=698775
- https://bugs.chromium.org/p/chromium/issues/detail?id=719251
- https://bugs.chromium.org/p/chromium/issues/detail?id=774546
- https://bugs.chromium.org/p/chromium/issues/detail?id=793188

I wasn't able to find any debug logs, evtest results, or atmel_tp settings, so I'm hoping that my data is useful (especially as the Log Analyzer told me to open a new issue), but I'm happy to have this issue closed as a dupe if that's the right call.

Comment 5 by susanjun...@techmahindra.com, Feb 7 2018

Labels: Needs-Triage-M63

Comment 6 by vamshi.kommuri@chromium.org, Feb 16 2018

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET OS-Chrome
Mergedinto: 793188
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue!

As this issue seems to be similar to that of  Issue 793188  , Hence merging into it. Please feel free to undupe if they aren't similar.
►

Sign in to add a comment