diff options
| author | Michael Wright <michaelwr@google.com> | 2018-01-25 23:25:20 +0000 |
|---|---|---|
| committer | android-build-team Robot <android-build-team-robot@google.com> | 2018-01-27 00:04:09 +0000 |
| commit | 8aab42761b3ed7c42d268949d6a9999c4edd2571 (patch) | |
| tree | a87c7895b0a5c2ece13045aafe9206ceec5688d3 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | ccaeb127f8699784bbc9237439b9fe4623c2c654 (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
(cherry picked from commit 44dc8b1da8ec60095524c391fd9b8f1c907e76ea)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions