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

Issue 730085 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jun 2017
Cc:
pbath...@chromium.org
sdantul...@chromium.org
█ charliemooney@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Touchscreen is not working on Samus

Project Member Reported by abod...@chromium.org, Jun 6 2017 
Google Chrome	59.0.3071.91 (Official Build) beta (64-bit)
Platform	9460.60.0 (Official Build) beta-channel samus
Firmware Version	Google_Samus.6300.174.0

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Au to M59-9460.60.0 and reboot 
(2)Try to touch any buttons 
(3)

Expected Result:
Touch should work.

Actual Result:
Touch is failed.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
debug-logs_20170606-104436.tgz
795 KB Download

Comment 1 by abod...@chromium.org, Jun 6 2017

Labels: -Pri-3 Pri-1

Comment 3 by kathrelk...@chromium.org, Jun 6 2017

Cc: charliemooney@chromium.org
Summary: Touchscreen is not working on Samus (was: Touch is not working on Samus)
The device started working again after rebooting, so we don't have a device in the stuck state anymore.  We'll keep an eye out.

Charlie - is there anything worthwhile in the improved Atmel logs?

Comment 4 by charliemooney@chromium.org, Jun 6 2017

Mergedinto: 715160
Status: Duplicate (was: Untriaged)
I just looked through the logs on this and it does indeed have the new Atmel logging data.  There is clearly a bad baseline which is screwing up all subsequent readings, which is totally consistent with a reboot fixing it.  I'll mark this as a duplicate and add this into the pile of evidence that we're collecting now on how to handle this.

Attaching blurred (to obscure the precise data) heatmaps here that show the gist of what's happening for future reference.

Thanks
deltas.png
90.2 KB View Download
refs.png
91.8 KB View Download
►

Sign in to add a comment