topjohnwu ada0f93686 Apply all sepolicy patches pre-init ... Boot services tend to fail in the middle when the kernel loads a sepolicy live. It seems that moving full patch (allow magisk * * *) to late_start is still not enough to fix service startup failures. So screw it, apply all patched in magiskinit, which makes sure that all rules are only loaded in a single step. The only down side is that some OEM with a HUGE set of secontexts (e.g. Samsung) might suffer a slightly longer boot time, which IS the reason why the rules are split to 2 parts in the first place.		2018-08-09 03:20:28 +08:00
..
core	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
external	Update BusyBox	2018-06-25 16:11:31 +08:00
include	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
magiskboot	Let Magisk compile against SDK 16	2018-07-13 22:14:32 +08:00
magiskhide	Kill all processes using the same UID of the target	2018-08-08 05:47:58 +08:00
magiskpolicy	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
resetprop	Sync source with AOSP	2018-07-14 04:34:48 +08:00
su	Make root shell always use dev_pts	2018-08-02 20:29:18 +08:00
utils	Kill all processes using the same UID of the target	2018-08-08 05:47:58 +08:00
Android.mk	Rename log_monitor -> log_daemon	2018-07-06 07:57:18 +08:00
Application.mk	Let Magisk compile against SDK 16	2018-07-13 22:14:32 +08:00
b64xz.c	Rename module core to native	2018-01-27 09:11:28 +08:00