Issue metadata
Sign in to add a comment
|
Reduce brightness used when displaying boot splash screen |
||||||||||||||||||||
Issue descriptionThe boot splash screen is too bright. See http://go/cros-splash for more discussion. Original description: "Default brightness setting after rebooting machine is way too bright. The brightness setting that I manually set before rebooting should be retained."
,
Nov 17 2017
<triage> ovanieva@ to review
,
Nov 17 2017
tested and it looks like current behavior or CrOS - brightness not retained. Oshima@ do you have background on this? why can't we retain brightness settings between reboots?
,
Nov 21 2017
derat@ to triage
,
Nov 21 2017
There's nothing eve-specific about this. Previously: issue 209400 issue 214064 issue 268046 (same request as this, WontFix) issue 443603 (same request as this, WontFix) Even if powerd were changed to restore the previously-set brightness, the white-background boot splash screen would still be too bright since it's displayed before powerd starts. Changing this is a decision for UX to make, in any case.
,
Dec 1 2017
,
Oct 11
Getting rid of the white-background boot splash in favor of a darker background one (the original ChromeOS boot splash was a black background) would alleviate the frequent user pain here. I've trained myself to always close my eyes or look away when powering on a chromebook ever since we decided to make it white for some unfathomable to me reason. It hurts me otherwise.
,
Jan 11
Setting defect without priority to Pri-2.
,
Jan 12
Christina put together a doc at http://go/cros-splash to explore various options for making the boot splash screen less painful to see at night. The current thinking is that we can try reducing the brightness that boot-splash.conf sets. It's currently at 40% (calculated linearly, IIRC). I believe that UX is onboard with this, but we'll still need to verify that it doesn't make the splash screen look "dingy". powerd would probably also need to be updated to defer adjusting the backlight until Chrome has drawn the login screen; otherwise the brightness will be increased while the splash screen is still up. I'm not sure how much complexity this will add: I think that when I looked at it before, waiting for Chrome to take ownership of the DisplayProvider D-Bus service name wasn't long enough (because it takes longer for Chrome to actually draw the login screen). I'm unlikely to be able to experiment with this until the end of the month.
,
Jan 12
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by arnelz@google.com
, Nov 14 2017