Revert "add apex-ready event after post-fs-data"
This reverts commit 1eb3394e9c.
Reason for revert: b/244406239, we've migrated to a sysprop(apex.all.ready) instead of an event.
Change-Id: Iae54df241257e3a3dcad4e54fdbf9dd14e9814de
This commit is contained in:
parent
1eb3394e9c
commit
8fbd79e689
1 changed files with 0 additions and 5 deletions
|
|
@ -538,10 +538,6 @@ on late-init
|
|||
# /data, which in turn can only be loaded when system properties are present.
|
||||
trigger post-fs-data
|
||||
|
||||
# APEXes are ready to use. apex-ready is a public trigger similar to apexd.status=ready which
|
||||
# is a system-private property.
|
||||
trigger apex-ready
|
||||
|
||||
# Should be before netd, but after apex, properties and logging is available.
|
||||
trigger load_bpf_programs
|
||||
|
||||
|
|
@ -1306,7 +1302,6 @@ on userspace-reboot-fs-remount
|
|||
on userspace-reboot-resume
|
||||
trigger userspace-reboot-fs-remount
|
||||
trigger post-fs-data
|
||||
trigger apex-ready
|
||||
trigger zygote-start
|
||||
trigger early-boot
|
||||
trigger boot
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue