Pressing power key on convertible Chromebooks should not have UX that is any different then Android tablets. We currently just lock the device on power button press, I suggest that put it in suspend mode instead.
Not sure if this change should be handled on UI or power daemon's side.
Chrome already has the ability to ask powerd to suspend the system.
I don't think that this will work the way you'd like with Chrome OS's current notion of "suspending", though. I imagine we would need to do something much more lightweight, which would likely require some kernel work (which Sameer can probably comment on). I doubt that this could happen for M54.
We'll want to iterate on this to get it right. Ultimately, we'll want a "screen off" mode similar to what phones and tablets do, but I agree with derat@ that building that in time for 54 seems unrealistic.
tbuckley@ let's discuss offline.
I'm happy to be involved in this discussion too if you want to set up a VC. :-)
For example: as a first pass, would it be desirable to just turn the screen off immediately when the button is tapped, while still keeping the existing inactivity delay for suspending the system? If so, I can start thinking about how to let Chrome request that from powerd.
The problem with just turning off the screen and not suspending is that might be surprising from a user-expectations POV. The CPU would stay fully active and draining the battery. I could imagine that being really not what the user wants. Especially since we lack a notification/alert system that would work in such an environment.
Let's tackle in 2 stages:
1: Change Chrome to have a tap on the power button while in touchview do a full suspend.
2: Start a separate longer term effort to figure out the CORRECT behavior here.
I'll file a tracking bug for the second. derat@ I'll make sure you're in on the conversation.
Sounds good. And just to make sure that it's clear: it's likely that with the initial full-suspend-on-tap change, a user might need to wait several seconds before they can wake up the device.
Comment 1 by derat@chromium.org
, Aug 1 2016