diff options
| author | Michael Wright <michaelwr@google.com> | 2018-01-25 23:25:20 +0000 |
|---|---|---|
| committer | Michael Wright <michaelwr@google.com> | 2018-01-26 23:05:24 +0000 |
| commit | 44dc8b1da8ec60095524c391fd9b8f1c907e76ea (patch) | |
| tree | adf928e9f0467e3bde2ee5c50451a0e7bd2225e4 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | d55e3e7574863ec85dedc6d9a248ec23a3b22e49 (diff) | |
Clear pending brightness setting when it's redundant.
If we don't clear the pending brightness setting when it's equivalent to
the existing brightness setting then we end up racing the next time
auto-brightness changes. Most of the time the settings change
notification will win and we'll ignore the stale pending brightness, but
sometimes we immediately update the power state again and then we'll see
the stale value which looks different from our current value and so
assume it's a change coming from the user. Whoops.
Bug: 72508527
Test: manual
Change-Id: Id743f3654be6d48a14fca5882c1b8e16fed147da
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions