Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8fbd79e6 authored by Jooyung Han's avatar Jooyung Han Committed by Gerrit Code Review
Browse files

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

This reverts commit 1eb3394e.

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

Change-Id: Iae54df241257e3a3dcad4e54fdbf9dd14e9814de
parent 1eb3394e

rootdir/init.rc

+0 −5
Original line number Original line Diff line number Diff line
@@ -538,10 +538,6 @@ on late-init 
    # /data, which in turn can only be loaded when system properties are present.

    # /data, which in turn can only be loaded when system properties are present.

    trigger post-fs-data

    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.

    # Should be before netd, but after apex, properties and logging is available.

    trigger load_bpf_programs

    trigger load_bpf_programs
@@ -1306,7 +1302,6 @@ on userspace-reboot-fs-remount 
on userspace-reboot-resume

on userspace-reboot-resume

  trigger userspace-reboot-fs-remount

  trigger userspace-reboot-fs-remount

  trigger post-fs-data

  trigger post-fs-data

  trigger apex-ready

  trigger zygote-start

  trigger zygote-start

  trigger early-boot

  trigger early-boot

  trigger boot

  trigger boot