ChromeOS: Samus/Pixel 2 can't start when plugged in from discharged battery |
||||||
Issue descriptionWhen the pixel 2 battery becomes fully discharged if you plug it in it still won't start for at least 10-30 mins of charging. What steps will reproduce the problem? (1) Fully discharge the battery (2) Plug in power (3) Attempt to turn on What is the expected output? Uses power from the cable to turn on like every other laptop. What do you see instead? Either nothing or a brief flash of backlight and little whine of something mechanical starting up for half a second then back to dead. Has to charge for extended period of time before being able to boot.
,
Apr 27 2016
,
Apr 27 2016
> When the pixel 2 battery becomes fully discharged if you plug it in it still won't start for at least 10-30 mins of charging. You mean on the original 60W charger (aka Zinger) provided with the laptop or with another legacy type-C cable or charger ? > What is the expected output? > Uses power from the cable to turn on like every other laptop. That's effectively the expected behavior if you plug the provided charger.
,
Apr 27 2016
This is using the supplied charging brick.
,
Apr 27 2016
Can you file a feedback (alt+shift+i) just after the laptop finally started ? Just to be sure: that's all MP hardware, not old proto brick or laptop laying around ?
,
Apr 27 2016
OK next time it happens I'll try to send feedback. MP hardware? I'm not sure where it came from I just requested it for testing (it has an asset tag and no indication it's a prototype) - Is there something I can check? It's happened to others on my team too (though we all got the machines at the same time).
,
Apr 28 2016
> MP hardware? > I'm not sure where it came from I just requested it for testing (it has an asset tag and no indication it's a prototype) > - Is there something I can check? For the laptop side, in chrome://system, the 'platform_info' section will give you the hardware revision in the 'version' field. For the power supply side, it's more complicated to guess. If it is really old, the firmware update code on the laptop side will 'complain' at kernel startup, we might see it in the feedback report.
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Sep 21 2017
Is this still a bug? It's very stale and I'm going to archive it. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by derat@chromium.org
, Apr 27 2016