commit e4dc1328d657b8e83426204386ac255bef83fb41
author Cam Bickel <cambickel@google.com> Wed Apr 24 14:53:56 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed Apr 24 14:53:56 2024
tree 28aee05b0486d5b6a57849525ec7602168675c4f
parent 4621c9e0d06cea3cf878e54be3d04182541d6a39

brightness: If ambient light sensor is disabled, save the cause in pref

This CL creates a new local-state pref called
kAmbientLightSensorDisabledReason that stores the reason that the
ambient light sensor was disabled. When the brightness control in
Settings feature is enabled for all users, we anticipate a possibility
where many users may unintentionally permanently disable the ambient
light sensor by changing the brightness, without realizing what they're
doing. This pref allows us to "roll-back" (if necessary) the disablement
of auto-brightness for a specific subset of users (e.g. users who
disabled the ambient light sensor because they changed the brightness
via the keyboard/quick-settings), but keep the disablement of
auto-brightness for other users (e.g. users who manually disabled
auto-brightness via the Settings app).

Test: ash_unittests --gtest_filter=*BrightnessControllerChromeosTest*
Bug: b/328287584
Change-Id: Ie088e321c64bb17473b2d9f836149bd354b31d13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5444196
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Camden Bickel <cambickel@google.com>
Reviewed-by: Wenyu Zhang <zhangwenyu@google.com>
Reviewed-by: David Padlipsky <dpad@google.com>
Cr-Commit-Position: refs/heads/main@{#1291873}