Issue metadata
Sign in to add a comment
|
External touch devices stop working when the internal displays lid is closed |
||||||||||||||||||||||
Issue descriptionChromeOS version: 61,62 ChromeOS device model: - Asus 302CA - Acer CB5-312T - HP x360 G11 EE Case#: 13996759 ## Description: Customer experiencing issues with interactive projectors connected to their Chromebooks. Touch functionality does not work when the lid is closed. Issue started with version 61 release. Here is the drive link to the video describing the issue: https://drive.google.com/open?id=1ZJlqHMrcY5MbEG-siiLvKtPudtHc1NoQ Customer also mentioned that they have been able to replicate this by disabling the touch panel on the Chromebook. The interactive projector's board no longer works when it is disabled. Enabling the touch solves that issue. ## Steps to reproduce -Turn on a Chromebook -Connect the interactive -Close the lid and continue working on the whiteboard -After lid is closed the touch capability is no longer present # Additional information: Both of the following devices work both with the lid open and the lid closed with the interactive boards on Version 61.0.3163.123 (Official Build) (64-bit).: Acer C720P - 2625 Acer C740-C4PE ## Current Behavior / Reproduction: Interactive projector's touch board does not work with closed lid ## Expected Behavior: Interactive projector's touch board works with both closed and opened lid Drive link to logs: https://drive.google.com/open?id=1ON_egXNoS6ECI2ztqvG-z2kxjvE7tj99
,
Jan 2 2018
sadrul@ please triage this.
,
Jan 3 2018
I don't know who works on this.
,
Jan 30 2018
Malay, is this related to touch associations you were working on? If not please further triage.
,
Jan 30 2018
This should be fixed moving forward M64.
,
May 28 2018
Jamie Jensen has requested an update for this bug and a consult has been submitted with new logs using ver 66. The issue persists.
,
May 28 2018
#6 This might be related to another issue 827452 which was fixed for M67. Does M67 beta fix this?
,
May 31 2018
The customer replied with version 67 logs. He states he also tried using version 68 in dev channel and both versions are still reproducing the issue.
,
May 31 2018
here is a drive link to the log file mentioned in #8: https://drive.google.com/open?id=1lHVD_yLlUvrroItoQSZ0Nm_vUYGyO6Ue
,
May 31 2018
Was this working pre-M61? Is this a regression? Do we have access to an interactive projector?
,
Jun 1 2018
malaykeshav@ - Yes, it was working pre-61 so most probably a regression. Unfortunately we don't have an interactive projector here to reproduce.
,
Jun 6 2018
Indeed the case was opened because the feature was working pre 61. Are there any updates or any further data you need from the customer's end?
,
Jun 6 2018
Its hard to say what caused the regression without testing with the device. There is another kernel bug that is currently being worked on in Issue 850222 . But looking at the logs, I don't see the error messages that match the diagnosis.
,
Jun 12 2018
Greetings. Do you believe it'd be necessary to request a device from the customer for testing purposes? I'd like to be able to provide a meaningful update to him since he's simply waiting for our updates.
,
Jun 12 2018
#14 Yes. A test device would definitely help getting to the root of the problem. Unless this can be reproduced on other device. However I have not seen another bug that has the same issue.
,
Jun 13 2018
Greetings, the customer states he has tried to reproduce the issue with multiple different devices and multiple interactive whiteboards with the same results. Touch capabilities are lost on the external device when the Chromebook lid is closed. He prefers not to send a testing device, however he's willing to try in case it's necessary.
,
Jun 14 2018
,
Jun 14 2018
,
Jun 14 2018
This effects every device. This is a side effect of Issue 743291 . Specifically, we disable interactions on _ALL_ touch devices if the brightness goes to 0 on the internal display due to a non user initiated action (eg. closing the lid). Ideally we would want to disable the touchscreen that is associated only to the internal display, and not all touch devices. However that requires a significant amount of change to the codebase. As a temporary fix, I am proposing a change to turn off disabling ANY and ALL touchscreens if an external touch device is present. This would also solve the issue where devices like chromeboxes that rely solely on external touch screens for interaction and also as a mode of wake up from suspend can continue to do so. ( Issue 851062 ) (Increasing the priority as this effects every device with an external touch device connected)
,
Jun 14 2018
,
Jun 14 2018
We would also need to update go/cros-wakeup-matrix if the proposed change is to go through. I am not sure what the protocol for that is.
,
Jun 14 2018
The temporary fix in #19 sounds reasonable to me.
,
Jun 15 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2000976a356bb27d591e67eac2cdf7351afc99d7 commit 2000976a356bb27d591e67eac2cdf7351afc99d7 Author: Malay Keshav <malaykeshav@chromium.org> Date: Fri Jun 15 17:32:40 2018 Prevent touchscreen disable on lid close or user inactivity In the event of user inactivity or lid close, this patch will prevent the touchscreens from being disabled if an external touch device is connected to the system. Bug: 797411 Change-Id: I12afd55edfe343ff6508bd2fdd0f4d09c93b5a98 Component: backlights settter, touch device, wake up, power manager Testing: Added ash unittests to check for expected behavior Reviewed-on: https://chromium-review.googlesource.com/1102151 Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> Cr-Commit-Position: refs/heads/master@{#567710} [modify] https://crrev.com/2000976a356bb27d591e67eac2cdf7351afc99d7/ash/system/power/backlights_forced_off_setter.cc [modify] https://crrev.com/2000976a356bb27d591e67eac2cdf7351afc99d7/ash/system/power/backlights_forced_off_setter_unittest.cc
,
Jun 15 2018
,
Jun 15 2018
,
Jun 16 2018
This bug requires manual review: M68 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 18 2018
,
Jun 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2438f5edcf1c00ab1374f29c528d3209ae3eb68b commit 2438f5edcf1c00ab1374f29c528d3209ae3eb68b Author: Malay Keshav <malaykeshav@chromium.org> Date: Mon Jun 18 18:52:43 2018 (merge) Prevent touchscreen disable on lid close or user inactivity In the event of user inactivity or lid close, this patch will prevent the touchscreens from being disabled if an external touch device is connected to the system. Bug: 797411 Change-Id: I12afd55edfe343ff6508bd2fdd0f4d09c93b5a98 Component: backlights settter, touch device, wake up, power manager Testing: Added ash unittests to check for expected behavior Reviewed-on: https://chromium-review.googlesource.com/1102151 Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#567710}(cherry picked from commit 2000976a356bb27d591e67eac2cdf7351afc99d7) Reviewed-on: https://chromium-review.googlesource.com/1104760 Reviewed-by: Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/branch-heads/3440@{#406} Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733} [modify] https://crrev.com/2438f5edcf1c00ab1374f29c528d3209ae3eb68b/ash/system/power/backlights_forced_off_setter.cc [modify] https://crrev.com/2438f5edcf1c00ab1374f29c528d3209ae3eb68b/ash/system/power/backlights_forced_off_setter_unittest.cc |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vkasatkin@google.com
, Dec 22 2017