-
topjohnwu authored
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.
ada0f936
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| core | ||
| external | ||
| include | ||
| magiskboot | ||
| magiskhide | ||
| magiskpolicy | ||
| resetprop | ||
| su | ||
| utils | ||
| Android.mk | ||
| Application.mk | ||
| b64xz.c |