diff options
| author | 2023-01-26 14:41:57 +0000 | |
|---|---|---|
| committer | 2023-01-27 17:13:28 +0000 | |
| commit | 3e24dc3906dcacd9f6bf423bafd781a3d7e6a997 (patch) | |
| tree | 5b8f54422e2a1c15623db0ab468dba2bda95f02c /libs/androidfw/AttributeResolution.cpp | |
| parent | 7e9ff1ef7b1b5455755d1c0d2a1c31593d452ff2 (diff) | |
Release doze wake lock when doze dream is stopped
Before this CL, if the doze dream instance is replaced by another
dream instance, the doze lock was never released. There is a check
in the DreamManagerService#onDreamStopped path, that normally releases
the doze lock in a normal wake up. But when the doze dream instance
has been replaced by another dream instance, the doze dream token
doesn't match the current dream token, and so the doze wake lock is
never released. This causes the display to flicker right before
entering AOD (dozing).
This CL handles the case when a doze dream is replaced by a normal
dream and releases the doze lock whenever a doze dream instance is
stopped.
Bug: 260094933
Test: manual - check that the flickering disappeared
Change-Id: I3fdf10566ba57fadfa83a5d78038db68bf4a1150
(cherry picked from commit eeaba58c8ad976b3ae71c1afc8717169afdf8441)
Diffstat (limited to 'libs/androidfw/AttributeResolution.cpp')
0 files changed, 0 insertions, 0 deletions