diff options
| author | Oli Lan <olilan@google.com> | 2020-02-06 11:40:04 +0000 |
|---|---|---|
| committer | Oli Lan <olilan@google.com> | 2020-04-22 13:35:50 +0100 |
| commit | 54da92ad09cec986c010016b4e4ff012f66314df (patch) | |
| tree | c575bc01474ec5d54cc789b6450300192d0ee790 /apexer/apexer.py | |
| parent | 9fedf7b2f4d74aef585d5e75477fcdf26d3a5b3a (diff) | |
Set apexd.status to "activated" between activation and DE snapshot.
- Cherry-pick of aosp/1228581
As of aosp/1224611, there is a new step in the preparation of APEXes
where init calls back into apexd after DE user data is unencrypted to
allow DE apex data to be snapshotted or restored.
Until this occurs, APEXes should not be used, so apexd.status should
not be set to "ready".
This CL introduces a new status of "activated" that init will wait on
before performing the configuration in the "perform_apex_config" step.
The status of "ready" will not be set only once any needed DE snapshot
or restore has been performed.
Bug: 148672144
Test: build & flash, check boot completes and check in logs that apexd
status was set correctly.
Merged-In: I3d840e414467f3c5934d158114c3cba2029988b9
Change-Id: If698214d92346157db0a4dfd27de02c6cccd7fe5
Diffstat (limited to 'apexer/apexer.py')
0 files changed, 0 insertions, 0 deletions