commit 8fbd79e6897c76c6a6a4f25ecd233fcc2e0da2e3
author Jooyung Han <jooyung@google.com> Wed Nov 09 07:55:58 2022 +0000
committer Gerrit Code Review <noreply-gerritcodereview@google.com> Wed Nov 09 07:55:58 2022 +0000
tree 1a7c4ead4f2b607e0580f9a494175899630ae5dd
parent 1eb3394e9c9ea0d19abf195a60ccbe1c28dd8388

Revert "add apex-ready event after post-fs-data"

This reverts commit 1eb3394e9c9ea0d19abf195a60ccbe1c28dd8388.

Reason for revert: b/244406239, we've migrated to a sysprop(apex.all.ready) instead of an event.

Change-Id: Iae54df241257e3a3dcad4e54fdbf9dd14e9814de

rootdir/init.rc

diff --git a/rootdir/init.rc b/rootdir/init.rc
index 975fcc0..8d8da5e 100644
--- a/rootdir/init.rc
+++ b/rootdir/init.rc
@@ -538,10 +538,6 @@
     # /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-resume
   trigger userspace-reboot-fs-remount
   trigger post-fs-data
-  trigger apex-ready
   trigger zygote-start
   trigger early-boot
   trigger boot