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

Issue 860100 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Jul 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

CfM Touch feature of Mimo Touchscreen is not responsive on newer Chrome OS Version.

Project Member Reported by ryutas@chromium.org, Jul 4

Issue description

ChromeOS version: 66.0.3359.203 (from 65.0.3325.184 - 67.0.3396.99)
Cfm device model: Asus Chromebox CN62 (Guado) 
Case#: 16081869

Description:
Touch feature of Mimo Touchscreen is not responsive on newer Chrome OS Version. 

- Issue description: 
Touch feature of Mimo Touchscreen is not responsive on newer Chrome OS Version. Tested On 65 and 66 

- Steps to reproduce 
1.Connect touchscreen to Chrome OS Device or Meet Hardware running in Kiosk Mode. 
2.Try to use touch Feature 

- What's the expected behavior? 
Chrome OS should recognize touch commands. 

- What's the actual result? 
Touch commands are not recognize in Chrome OS nor Kiosk Mode. 

- Does it affect all devices? 
Only one of the devices is affected.

|======Troubleshooting and Workaround======| 
- Troubleshooting steps taken: 
-Wiped the device. 
-Tested on Chrome OS 65-66
.
-When plugging into a device which is on v67.0.3396.99, it fails to work, after multiple presses of the same place on the screen, it works once and then continues to fail again. 
-The customer has sent the device to the manufacturer. It returned with Chrome OS version 59, but upon updating, it failed again. 
-We recovered back to version 59, and the touchscreen seems to work fine in this version. 
-We made sure all the cables are properly connected 
-Connected the screen on another Chrome OS device, but touch failed 

- Existing Workaround: 
Recover to version 59.0.3071.92 

-Log
From 66 (at 14:44 on 06/15/2018 for Log-66.0.3359.203 )
https://drive.google.com/open?id=1IjZNW4VhNQITYTQCU6U-HdmgKN54ifd7

from 59 (not affected)
https://drive.google.com/open?id=1Ojgri9wDvy16I4qwkII6jm7usfH0uhiT

from 67
https://drive.google.com/open?id=1hkWNh7KXwbN4x_WRrWkaPpwx985xpY9-

Hardware configuration
https://drive.google.com/open?id=1vwLzJPpcUJv-Aovkru_aZkTpQ8v2BGMp

Found some errors from logs.
2018-06-26T10:34:53.595979+01:00 WARNING mimo-monitor[1001]: Open deivce fail at port 1 in ReadID, error: -3
2018-06-26T10:34:53.596032+01:00 WARNING mimo-monitor[1001]: Open deivce fail at port 2 in ReadID, error: -3
2018-06-26T10:34:59.876742+01:00 ERR sis-updater[5232]: some error occurs, please check the output. Err = -262
....
2018-06-26T10:35:05.682612+01:00 ERR sis-updater[5289]: Write Header(0x83) fail
2018-06-26T10:35:05.682633+01:00 ERR sis-updater[5289]: retry time out
2018-06-26T10:35:05.682659+01:00 ERR sis-updater[5289]: release RO fail


May related to,
 crbug.com/827452 
crbug.com/834332


 
Owner: kotah@chromium.org
Mergedinto: 808557
Status: Duplicate (was: Untriaged)
Reviewed log, this seems like the same issue as crbug.com/808557. Duping.
This bug seems to be different from the one it has been duped to.

As I've commented in the other bug - the problem here is that the touch component fails while sis-updater (an utility that makes sure that mimo touch component has up to date firmware) attempts to perform an update of device's firmware (as the one installed on this mimo is old).

The reason why it is working for customer with 59 is that 59 didn't yet have that updater (it was added at later CrOS version).

The issue here is likely with this particular mimo unit which resets when an firmware upgrade is attempted.

Sign in to add a comment