LSPosed/magisk-loader/magisk_module
JingMatrix 0e457e3247 Start LSPosed daemon in `service.sh`
This reverts partially commit c622d0f1f9.

In my test device (Pixel 6, Android 16 qpr2, KernelSU), calling twice LSPosed daemon results a detection based on `mount_id` values. In `com.reveny.nativecheck` 7.6.1, it is named as `Detected Magic Mount`.
Of course, this naming is incorrect and misleading. We refer to https://github.com/JingMatrix/NeoZygisk/pull/39 for details of this detection point.
2025-12-04 23:59:55 +01:00
..
META-INF/com/google/android Separate core into bridge and loader (#1766) 2022-03-17 19:12:01 +08:00
action.sh Add action.sh to open LSPosed manager (#74) 2024-10-31 15:02:28 +01:00
customize.sh Start LSPosed daemon in `service.sh` 2025-12-04 23:59:55 +01:00
daemon Partially revert the previous commit 2024-12-02 12:38:58 +01:00
module.prop Release LSPosed v1.10.2 2025-07-12 11:30:46 +02:00
sepolicy.rule Allow dex2oat to access files received from sockets (#165) 2025-01-22 12:01:55 +01:00
service.sh Start LSPosed daemon in `service.sh` 2025-12-04 23:59:55 +01:00
system.prop Partially revert the previous commit 2024-12-02 12:38:58 +01:00
uninstall.sh Separate core into bridge and loader (#1766) 2022-03-17 19:12:01 +08:00
util_functions.sh Update to Zygisk API v4 2024-09-23 11:10:03 +02:00
verify.sh Separate core into bridge and loader (#1766) 2022-03-17 19:12:01 +08:00