- 13 Jan, 2022 1 commit
-
-
topjohnwu authored
Close #5134
-
- 12 Jan, 2022 3 commits
- 11 Jan, 2022 7 commits
-
-
LoveSy authored
-
vvb2060 authored
-
残页 authored
Fix topjohnwu#5013 When installing from recovery, previous implementation may select f2fs partitions to store sepolicy rules, but magiskinit won't mount them and unable to load sepolicy rules.
-
LoveSy authored
Fix #5178
-
topjohnwu authored
Apparently some boot images with ramdisk still have recovery_dtbo, so this assumption is no longer safe to do. Expect the user to set this option properly themselves in the app. Fix #4976, close #5070, close #5184
-
RikkaW authored
This will fix the SnackBar position if BottomNav or FAB is visible. Fix #5163 Fix #5135
-
vvb2060 authored
-
- 03 Jan, 2022 2 commits
- 02 Jan, 2022 1 commit
-
-
topjohnwu authored
-
- 29 Dec, 2021 6 commits
-
-
topjohnwu authored
-
LoveSy authored
Fix #4402 Co-authored-by:
topjohnwu <topjohnwu@gmail.com>
-
LoveSy authored
See https://github.com/dgibson/dtc/pull/65
-
残页 authored
Fix topjohnwu#5125 cgroup root path might be mem cgroup instead of acct, especially on low-ram devices. https://android.googlesource.com/platform/system/core/+/bc131c3244a6aa4961092ba08285f9d0435a8882%5E%21/#F0
-
残页 authored
-
LoveSy authored
See https://cs.android.com/android/platform/superproject/+/master:system/core/init/first_stage_mount.cpp;drc=master;l=155 From the source of `FirstStageMount`, dt fstab can fail gracefully and if any error occurs it will fall back to default fstab. Magisk now replaces the default fstab and dt fstab unconditionally, bringing potential errors to the default fstab and causing init fails to load partitions.
-
- 27 Dec, 2021 4 commits
-
-
vvb2060 authored
-
vvb2060 authored
-
topjohnwu authored
-
Arbri çoçka authored
-
- 26 Dec, 2021 1 commit
-
-
topjohnwu authored
Handled by external MagiskBot
-
- 15 Dec, 2021 2 commits
- 14 Dec, 2021 13 commits
-
-
John Wu authored
-
南宫雪珊 authored
-
南宫雪珊 authored
Fix #4960
-
vvb2060 authored
-
LoveSy authored
Fix #5051
-
topjohnwu authored
vbmeta header should not be patched in most cases
-
LoveSy authored
Caused by this commit: https://cs.android.com/android/_/android/platform/system/core/+/e98afa2687eb56184dad8569b929eba04fb93068 Fix #5057
-
LoveSy authored
* Further fix `oplus.fstab` support In some oneplus devices, `oplus.fstab` does exists but `init` never loaded it and those entries in `oplus.fstab` are written directly to `fstab.qcom`. Previous implementation will introduce duplicate entries to `fstab.qcom` and brick the device. This commit filters those entries from `oplus.fstab` that are already in `fstab.qcom` and further filters duplicated entries in `oplus.fstab` (keep only the last entry). Fix #5016 * Fix UB Since we moved entry, we need to explicitly copy its member. For c++23 we can use `auto{}`.
-
南宫雪珊 authored
-
南宫雪珊 authored
-
vvb2060 authored
-
残页 authored
-
vvb2060 authored
-