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

Issue 787465 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
User never visited
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Ability to enable sleep mode or turn off the CfM table top touch display

Project Member Reported by vkasatkin@google.com, Nov 21 2017

Issue description

Summary: 

Ability to manage power of CfM table top touch display device in Hangouts Meet hardware kit (https://enterprise.google.com/chrome/devices/google-hangouts-meet-hardware-kit/).
Either turn off device completely or/and set the device into a sleep mode. 
  

Use case / Motivation:
Manage device power consumption for energy conservation 


Case#: 14221566

 

Comment 1 Deleted

Hi katierh@ , could you please help with triage?
Cc: katierh@chromium.org
Owner: srivatsanr@google.com
It seems a bit awkward to sleep the controller - since the calendar details etc now live on the MIMO. 

Sri - can we sleep the display and keep the touch on - or does SIS support a very low power mode on the touch controller where it can tape to wake up but is otherwise in a LP mode? 
The touch controller does not draw a lot of power - we could turn the display off and keep touch on all the time. 

Am checking with SiS on low power mode support, but I recommend, not putting touch in low power mode at all and instead just turn the display on/off when a touch event is detected.

Not to open a can of worms - but what is the display power vs touch power vs Chromebox not in suspend power... wondering if we're chasing the wrong thing
I dont have the exact display power numbers, but I expect the touch interface to draw up to 100mW while the display should be 3W-4W.
Cc: josefink@google.com

Comment 8 by kotah@chromium.org, Jun 25 2018

Cc: cvintila@chromium.org
 Issue 856285  has been merged into this issue.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Owner: tjvarghese@chromium.org
Reassigning bug to TJ for prioritization and follow up - I am no longer on the HMHW team. 
We would like ability to put kiosk set ups with auto login of public sessions enabled to sleep when not in use after X hours.

Sign in to add a comment