diff options
| author | 2022-09-20 23:29:16 -0700 | |
|---|---|---|
| committer | 2022-10-25 22:52:24 -0700 | |
| commit | f5358585a26b2089875282f7ef9cf2d22e2ae59f (patch) | |
| tree | 53b0ec5482d798e6eb3c619b056588bde8d84846 /libs/androidfw/AssetsProvider.cpp | |
| parent | fe8b17d49d118e3a466b01c8d20919c7a8a58b5b (diff) | |
Workaround for doze/AOD problem with global wakefulness
When the global wakefulness is dozing and a non-default group
VirtualDisplay wakes up, the global wakefulness becomes awake and the
default display's individual wakefulness remains dozing. But some of
our code in Notifier and PhoneWindowManager that listen to the global
wakefulness kick off a chain of events that results in
KeyguardViewMediator thinking dozing has stopped, and the display gets
stuck in what feels like a sort of half on / half off state where it
shows keyguard at the low brightness and refresh rate we're supposed
to use for AOD, but it isn't responsive to touch inputs.
The workaround in this CL is to restart dreaming in this case to get
the AOD unstuck.
Bug: 187231320
Test: atest PowerManagerServiceTest
Change-Id: I8e348ffe52c7f2d5cbdd11b058254cb087b1021d
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions