From 8fbd79e6897c76c6a6a4f25ecd233fcc2e0da2e3 Mon Sep 17 00:00:00 2001 From: Jooyung Han Date: Wed, 9 Nov 2022 07:55:58 +0000 Subject: [PATCH] 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 | 5 ----- 1 file changed, 5 deletions(-) diff --git a/rootdir/init.rc b/rootdir/init.rc index 975fcc0ae..8d8da5eda 100644 --- a/rootdir/init.rc +++ b/rootdir/init.rc @@ -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