• topjohnwu's avatar
    Apply all sepolicy patches pre-init · ada0f936
    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
app Loading commit data...
chromeos Loading commit data...
docs Loading commit data...
gradle/wrapper Loading commit data...
native Loading commit data...
scripts Loading commit data...
snet Loading commit data...
utils Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
.gitmodules Loading commit data...
LICENSE Loading commit data...
README.MD Loading commit data...
build.gradle Loading commit data...
build.py Loading commit data...
config.prop.sample Loading commit data...
gradle.properties Loading commit data...
gradlew Loading commit data...
gradlew.bat Loading commit data...
settings.gradle Loading commit data...