Zygisk - LSPosed Module suspended because Zygisk isn't enabled

[User10987654321]

Steps to reproduce/复现步骤

install magisk 30.6 on android 16 (I've tried the following with both 30.6 stable and debug)
install Zygisk - LSPosed module v1.10.2
reboot (with zygisk enabled or not enabled; it says zygisk is disabled either way, that's why I have ReZygisk installed, which still has no effect)

Expected behaviour/预期行为

I'm trying to install this so that I can use Hide My Applist, as it appears you need to have LSPosed module in magisk to use the HMA app because in Hide My Applist I get a notification saying "Module not activated - System service not running"

Actual behaviour/实际行为

module suspended

lsposed_verbose.log

lsposed.log

Xposed Module List/Xposed 模块列表

nope

Root implementation/Root 方案

magisk

System Module List/系统模块列表

The only modules I've had installed are ReZygisk and Zygisk-LSPosed

LSPosed version/LSPosed 版本

1.10.2

Android version/Android 版本

16

Version requirement/版本要求

• I am using the latest debug build from GitHub Actions./我正在使用 GitHub Actions 中最新的调试版本。

Logs/日志

lsposed.log

[locuranacional]

daemon/src/main/java/org/lsposed/lspd/service/ConfigFileManager.java

[sdanfa]

Same issue on latest Rezygisk. Please fix.

[JingMatrix]

Your logs seems incomplete, please flash the latest CI debug build and upload logs again, as instructed in #123.

[User10987654321]

Your logs seems incomplete, please flash the latest CI debug build and upload logs again, as instructed in #123.

#239 (comment)

I've already done all of that, if you want specific logs then you'll have to rewrite the instructions instead of telling everyone with this issue they're not uploading the logs correctly.

Maybe resolve this person's issue before coming here, as this is obviously a bug several people are encountering - try reproducing yourself instead of asking for the same log production ten times.

[JingMatrix]

You are right, I can reproduce it (see my next message) with Magisk 30.6 + NeoZygisk.
I was using KernelSU before and wasn't aware of this Magisk incompatibitly happend recently.

By contrast, it works with the Zygisk implementation of Magisk on my device, are you able to reproduce it?
This is unlikely to be an issue of LSPosed.

[JingMatrix]

After reboot, this malfunction disappears, and LSPosed works on Android 16 with Magisk + NeoZygisk.
Currently, I think it is a transient mounting issue due to my change of root implementation.

You are suggested to test the following:

1. Uninstall ReZygisk, enable Zygisk function of Magisk, and test LSPosed
2. Replace ReZgisk with NeoZygisk, disable Zygisk function of Magisk, and test LSPosed

[sdanfa]

After reboot, this malfunction disappears, and LSPosed works on Android 16 with Magisk + NeoZygisk. Currently, I think it is a transient mounting issue due to my change of root implementation.

You are suggested to test the following:

1. Uninstall ReZygisk, enable Zygisk function of Magisk, and test LSPosed

2. Replace ReZgisk with NeoZygisk, disable Zygisk function of Magisk, and test LSPosed

Hi,
Thanks I can still reproduce with new versions of your LSPosed fork and some other forks as well. But old versions of LSPosed work fine with latest CI of ReZygisk. I am using them with APatch. Do you think its possible to fix? I am sure you can reproduce easily on your end. Its ReZygisk from telegram latest with new injection method. Thank you @JingMatrix :)

[sdanfa]

With neozygisk all work fine but neozygisk got random detections for me.

[AllenChangMusic]

I have recently switched from Magisk to KSU Next.

I was having intermittent issues that needed reboot to resolve, as @JingMatrix noted.

I wonder if it's a race condition that causes it in Magisk, and somehow KSU probably manages modules differently, so it doesn't cause the race condition?

[JingMatrix]

@sdanfa What is the detection message, is it the one mentioned in my commit message ? 0e457e3

@AllenChangMusic It is surely a racing problem. The daemon is wating for IPC binder to build up, and abort if waiting too long. However, waiting a bit longer is potentially a detection point, as explain in the above link.

My suggestion is that, no need to worry detection points. They are very easy tricks, and most of them are already disclosed in my NeoZygisk or Demo repo, no secret at all. You should not be afraid, nor be obsessive of it, if it doesn't affect your daily usage.

I am currently rewriting the whole LSPosed project into Vector. With new designs, the detection could be potentially handled easier. Current codebase is a bit mess to add more workarounds for detection bypassing.

[MeowZiii98]

KernelSU_Next_module_action_log_2026-01-17-23-20-31.log
I literally try ton times but I'm not be able to use zygisk lsposed jingmatrix 1.10.2 version in my own build custom rom Root via ksu next can u check this sir I'm not able able to use your lsposed in qpr1 idk whyy

[MeowZiii98]

Kindly check this issue or sorry for bothering you sir I'm not asking for eta but is there any chance for updating lsposed 1.10.2 to further versions in future

[JingMatrix]

@MeowZiii98 If you are using beta version of Android, you should flash the lastest CI build of LSPosed.
Claiming errors without providing logs / reading carefully README is bothering.