diff options
| author | Robin Lee <rgl@google.com> | 2021-01-20 00:20:47 +0100 |
|---|---|---|
| committer | Robin Lee <rgl@google.com> | 2021-01-29 13:42:45 +0000 |
| commit | f18a9641e6d1e7d7b8014ed207f74a4971c78ffa (patch) | |
| tree | 88a834911fa5689ab9ac4d725aee4adcd9e8ddb3 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 7ee87037f51e651e43c207c67582b36999b3de4a (diff) | |
Don't recompute display mode during a mode switch
When an app requests a display mode change, it's plausible that the next
thing to happen is going to be a configuration change.
During the configuration change, multiple windows that contributed to
the selection of the display mode will no longer be displayed. This can
lead to a device bouncing between two display modes for a while.
We need to wait for windows to redraw and for the screen to unfreeze
again before we next call DisplayManagerService.setDisplayProperties.
Test: atest android.display.cts.DisplayTest
Bug: 158316271
Change-Id: I58e4626e74a911a14cbcd426d1f09ef68303dafa
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions