[Samus] Unable to wake Chromebook using input devices connected after suspending |
||||||||
Issue descriptionChrome Version: 54.0.2840.93 (Official Build) (64-bit) Chrome OS Version: 8743.83.0 (Official Build) stable-channel samus Chrome OS Platform: Chromebook Pixel 2 Steps To Reproduce: (1) Insert power, display and external keyboard cables to the sleeping Chromebook. Keep the lid closed. (2) Tap the keyboard. Expected Result: The Chromebook wakes up in docked mode. Actual Result: The Chromebook doesn't wake up. The only way to wake it up is lift the lid until it extends the desktop onto the external monitor, then close it again to put the machine into docked mode. How frequently does this problem reproduce? Always What is the impact to the user, and is there a workaround? If so, what is it? You need to lift the lid to wake the laptop, which just makes docking the machine at my desk more of a chore.
,
Feb 28 2017
I am able to repro this on Samus with version: 58.0.3021.0/9325.0.0 (Official Build) dev-channel
,
Feb 28 2017
I believe this is not a bug, but WAI. The device was suspended with lid closed before plugging the peripherals. The device will resume if the peripherals were connected before and during the suspend state. Otherwise you have to open the lid, and close it again to dock the device.
,
Feb 28 2017
yes it is WAI, but adding Kuscher just FYI in case they want to change it
,
Feb 28 2017
Observation is that many (other) boards do not wake up even if peripherals are plugged before and during the suspend.
,
Mar 1 2017
If the Chromebook is suspended, it isn't "docked". We typically use "docked" to refer to the mode you're in when the system stays awake when its lid is closed while an external display is already connected. I don't think that this is something that can be changed (apart from shipping new hardware that behaves differently), but adding Benson to confirm. If you aren't able to wake other devices using USB input devices that were connected *before* suspending, please file a separate issue for that. I thought that that was supported on all boards, but I could be wrong.
,
Mar 1 2017
Dan, I think maybe this is actually a bug we need to address. In the original bug description, pbeevers@google.com describes that the keyboard is plugged into samus before entering suspend via idle. He says that upon letting the system idle suspend, tapping the keyboard doesn't wake it. That seems to be a problem to me. The topic of devices attached later on is a separate one. This one is actually about waking from suspend (with lid closed) from an already present usb input device.
,
Mar 1 2017
Are we reading different bugs? :-) This sentence suggested to me that it was already suspended: "Insert power, display and external keyboard cables to the sleeping Chromebook."
,
Mar 1 2017
Oh my mistake. Yeah this is working as intended. We don't wake the system on USB attach as a policy. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rjahagir@chromium.org
, Jan 26 2017Components: OS>Kernel>Display
Labels: M-54
Summary: [Samus] Unable to wake Chromebook when docked without lifting lid. (was: Unable to wake Chromebook when docked without lifting lid.)