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

Issue 621569 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 621269



Sign in to add a comment

Touchpad stops working after upgrade to R51 - Swanky

Reported by charliemooney@chromium.org, Jun 20 2016

Issue description

The touchpad on Swanky has a bug in its FW version 4.0 that means it may lose all functionality.  This new FW 4.0 was added to R51 to patch a pullup resistor issue where the physical click-button could stop working after extended use, however, it appears that it also introduced a new bug which can simply prevent the touchpad from functioning entirely.

We need to revert this broken touchpad FW immediately, then upload a new version once Elan (the touchpad vendor) has provided us with a fixed firmware.
 

Comment 1 Deleted

Project Member

Comment 2 by bugdroid1@chromium.org, Jun 21 2016

Cc: bhthompson@chromium.org gkihumba@chromium.org
Labels: Merge-Request-52 Merge-Request-51 M-51 M-52
Hello,

This is an urgent fix to revert a bad touchpad firmware that is completely stopping some Swanky users' touchpads from working.  We really need to merge this back to 51 and 52 to get these users' touchpads functional again as soon as possible.  The touchpad firmware that this CL reverts it to was the one used previously, so it's known to work.  (The newest FW, that caused the issue, was introduced to fix a rare bug with the click button under the touchpad.  It's far less common and severe than the bug it introduced though, so we need to revert it quickly and then we'll add a version with both fixes later)

Thanks,
Charlie
Labels: -Pri-3 Pri-1
Labels: Merge-Approved-52
Project Member

Comment 6 by bugdroid1@chromium.org, Jun 21 2016

Labels: merge-merged-release-R52-8350.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-swanky-private/+/f7d60618ea744c7ddcb3274415b85e0afc4610a2

commit f7d60618ea744c7ddcb3274415b85e0afc4610a2
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Mon Jun 20 17:23:13 2016

Project Member

Comment 7 by bugdroid1@chromium.org, Jun 21 2016

Labels: merge-merged-release-R51-8172.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-swanky-private/+/307f7b1ed713ad2db519a7b1e25d50b232885a07

commit 307f7b1ed713ad2db519a7b1e25d50b232885a07
Author: Charlie Mooney <charliemooney@chromium.org>
Date: Mon Jun 20 17:23:13 2016

Revert has landed in 51, 52, and ToT.

Now we're just waiting for a new FW from Elan
Blocking: 621269

Comment 10 by tin...@google.com, Jun 22 2016

Labels: -Merge-Request-51 Merge-Review-51 Hotlist-Merge-Review
[Automated comment] Request affecting a post-stable build (M51), manual review required.

Comment 11 by tin...@google.com, Jun 22 2016

Labels: -Merge-Request-52 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M52 (branch: 2743)
Status: Fixed (was: Started)
The firmware is reverted to 3.0; marking as Fixed.  Users will get the fix in our next stable update (or in the currently serving dev and beta builds).
Project Member

Comment 13 by sheriffbot@chromium.org, Jun 25 2016

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-Merge-Approved -Merge-Approved-52
Status: Verified (was: Fixed)

Sign in to add a comment