diff options
| author | Winson <chiuwinson@google.com> | 2019-03-04 15:21:04 -0800 |
|---|---|---|
| committer | Winson <chiuwinson@google.com> | 2019-03-04 15:55:37 -0800 |
| commit | 3f5ad738c199ef8a7729fccdc76edbb4b6c98b33 (patch) | |
| tree | ebb5ceb9e7d5d27e56b33184385a7ac3beb342fe /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 5a95250b5b59dbefe931c4a4f19a8252b67cc3b0 (diff) | |
Remove target Q check for transient night mode in UiModeManager
The target SDK check I originally added was broken since it used
the wrong UID vs User ID type.
While diagnosing, a separate concern came up about how to handle
different apps' expectations for how night mode should
work.
Checking target is weird because the system/other apps could
also be enabling car mode, and it's unclear which target level
would take precedence if multiple apps requested car mode be
enabled.
Rather than resolving that, this makes night mode transient in Q,
regardless of target version. The use cases in the wild are
probably small, and because ag/5074744 locked night mode by
default, most apps won't be affected by this behavior.
Bug: 117346726
Test: atest UiModeManagerTest
Test: manual car/night mode test app
Change-Id: If43c2f54b93e04918eeed00d8d50536bfb083630
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions