From 3c020a9cd78cf989d8b5ae39049aea61b2eb0017 Mon Sep 17 00:00:00 2001 From: JingMatrix Date: Mon, 2 Dec 2024 12:06:09 +0100 Subject: [PATCH] Partially revert the previous commit Current commit will restore the modifications 1,4 in the previous commit 156c6ae855d6fc7a2a13e19239ad6c3721e84cdc. Thanks for people in the community, @privacyguy123, @aviraxp and @HuskyDG, just to name a few, to notice my sever mistakes. Those mistakes are mainly caused by my inconsistent usage of testing environments. I wrongly compared the detecting results with different `Zygisk` implementations and was too assertive and careless to make those changes. Here is the explanation for reverting the previous commit: 1. `system.prop` is not extracted for Android 1O+ devices in `customize.sh`; 2. mounting /data/resource-cache is still needed in some systems (ColorOS, to be confirmed), and it isn't a detection point. To verify that modifications 2,3 are effective, I tested them with `Zygisk Next` 1.2.4 (445-031a64c-release) and `Holmes` V1.5.1 Narcissus on `Magisk` a34c04f9 280002. --- magisk-loader/magisk_module/daemon | 2 ++ magisk-loader/magisk_module/system.prop | 1 + 2 files changed, 3 insertions(+) create mode 100644 magisk-loader/magisk_module/system.prop diff --git a/magisk-loader/magisk_module/daemon b/magisk-loader/magisk_module/daemon index 2f68cff1..fb08a510 100644 --- a/magisk-loader/magisk_module/daemon +++ b/magisk-loader/magisk_module/daemon @@ -23,6 +23,8 @@ if [ $debug = "true" ]; then fi fi +mount tmpfs -t tmpfs /data/resource-cache + if [ ! -S "/dev/socket/zygote" ]; then timeout 0.5 inotifyd - /dev/socket:near | while read -r line; do $debug && log -p v -t "LSPosed" "inotify: $line" diff --git a/magisk-loader/magisk_module/system.prop b/magisk-loader/magisk_module/system.prop new file mode 100644 index 00000000..64184152 --- /dev/null +++ b/magisk-loader/magisk_module/system.prop @@ -0,0 +1 @@ +dalvik.vm.dex2oat-flags=--inline-max-code-units=0