diff options
| author | 2022-12-20 15:52:33 +0100 | |
|---|---|---|
| committer | 2023-02-08 09:18:39 +0000 | |
| commit | e454a698d9f1fcc37c110e3d08b21f31b0be2b7e (patch) | |
| tree | 8f4b159a23f626ea1e5754bf5260c049e84cbbf7 /libs/androidfw/ApkParsing.cpp | |
| parent | 5adb6255396ce266fa25e57a4319d0a0d9035422 (diff) | |
Handle dream restart
When a startDream is called directly after a stopDream for the same
DreamService, the old instance should be stopped and the state
should be cleared. Otherwise, the old dream's
mStopStubbornDreamRunnable messes up the state in the dream manager
and power manager.
In this CL we stop the old dream immediately if a startDream is
called for the same dream component while the old dream is gently
waking. This ensures that the dream state is cleared.
Bug: 260205205
Bug: 260094933
Bug: 265110360
Test: 2x adb shell cmd dreams start-dreaming - verify the device is
dreaming afterwards
Change-Id: Ibd261038430a38f2fa519549372ddbf19d7cb36b
(cherry picked from commit 4bd7a87938db1e9035cb1b72b512f82c40d8d76a)
Merged-In: Ibd261038430a38f2fa519549372ddbf19d7cb36b
Diffstat (limited to 'libs/androidfw/ApkParsing.cpp')
0 files changed, 0 insertions, 0 deletions