New issue
Advanced search Search tips

Issue 594418 link

Starred by 2 users
Status: WontFix
Owner:
adlr@chromium.org
Closed: Mar 2016
Cc:
adlr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Peppy touchpad seemed to think there were two fingers down

Project Member Reported by derat@chromium.org, Mar 13 2016 
Google Chrome	48.0.2564.116 (Official Build) (64-bit)
Platform	7647.84.0 (Official Build) stable-channel peppy

The touchpad on this device started acting really strange; it'd jump all over the place as I moved my finger. When I moved left or right, it tried to go back or forward in a browser window, so I suspect it thought there was a second finger down. I couldn't see any water or debris on the touchpad, and I hadn't suspended or just powered it on or anything like that. It behaved normally after shutting down and booting again, so I assume it wasn't a hardware problem.

I sent a feedback report while the problem was ongoing: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReport=6909610547

Comment 1 by adlr@chromium.org, Mar 16 2016

Owner: adlr@chromium.org
Status: WontFix (was: Untriaged)
Yup, looks like the touchpad has a finger stuck down. Looks like it recalibrated on reboot. In the future, probably a sleep/wake would have fixed this.

I'm going to close as I think we don't plan to fix this in firmware. We could investigate not counting fingers that are effectively stationary for a long time, but that would still lead to some bad behavior. For example, when your real finger moved over the fake finger, the real finger took precedence. Then the fake finger came back after the real finger moved away. Software can't truly fix this :(

Comment 2 by derat@chromium.org, Mar 16 2016 

That's a bummer. So was it a physical issue, or just some unknown bug happening at a low level that we don't have access to? (Or do we not even know?)

Comment 3 by adlr@chromium.org, Mar 16 2016 

It's definitely an issue w/ hardware or firmware. I can see the fake finger wiggling around a bit, so it's not like some memory was stuck uninitialized (where you'd expect the fake finger to be 100% constant). Probably the pad was somehow miscalibrated.
►

Sign in to add a comment