[Please read this guide first]: How to troubleshoot LSPosed?

[JingMatrix]

Is your feature request related to a problem?/你的请求是否与某个问题相关？

Many users frequently encounter similar issues, which can actually be solved by their own, but there isn't an official guide to do so.

Describe the solution you'd like/描述你想要的解决方案

Under current feature request, users are allowed to request common troubleshoot routines and the maintainers should provide pratical instructions and references.

[JingMatrix]

Before we start the troubleshooting

1. Please flash the debug version of the latest CI build in GitHub Actions, which could have fixed the problem for you. Moreover, debug logs are necessary for maintainers to provide their helps. However, make sure that you pick up builds from the master branch instead of some working-in-progress pull-requests.
2. For non-Magisk users, please flash the latest Zygisk module (debug version if possible), such as NeoZygisk, ReZygisk or ZygiskNext.

Status notification for LSPosed manger is not shown

Update your root manager and use the Action button to open LSPosed manger

LSPosed manger cannot be opened

1. Grant root permission to the system Shell(com.android.shell) application.
2. Install LSPosed manger as a user application using the following command:

adb shell su -c cp /data/adb/modules/zygisk_lsposed/manager.apk /data/local/tmp && adb pull /data/local/tmp/manager.apk && adb install ./manager.apk

3. Open manager as a normal application from your launcher.

How to provide useful logs before asking helps?

1. Please go through the previous instructions to open LSPosed manager successfully, and upload the generated logs in your issue.
2. LSPosed manager will automatically save logs of the previous user session. Taking good advantage of the feature can help maintainers to find out a specific bug introduced in some single commit.
3. In case that the LSPosed manager still cannot be opened, we need to the following logs (file lsposed.log) from adb logcat:

adb logcat -s Magisk lspd nativeloader AndroidRuntime LSPosed LSPosed-Bridge LSPlant LSPosedContext LSPlt LSPosedService Dobby '*:F' zygiskd64 zygisk-core64 zygisk-ptrace64 zygiskd32 zygisk-core32 zygisk-ptrace32 > lsposed.log

4. The above adb logcat command is meant to capture the booting logs of LSPosed. Hence, one should connect the phone with computer, authorize the adb connection, run adb reboot, and finally run the previous adb logcat command once the phone screen turns on.

[LeeBinder]

Hi @JingMatrix You write

LSPosed manager will automatically save logs of the previous user session.

but you don't disclose where to :( Can you please share the file system path?

Also: is there any advantage over providing the log from LSPosed Manager in Android vs. running

adb logcat -s Magisk lspd nativeloader AndroidRuntime LSPosed LSPosed-Bridge LSPlant LSPosedContext LSPlt LSPosedService Dobby '*:F' zygiskd64 zygisk-core64 zygisk-ptrace64 zygiskd32 zygisk-core32 zygisk-ptrace32 > lsposed.log

?

[JingMatrix]

You can find logs in the folders /data/adb/lspd/log.old and /data/adb/lspd/log.

The log archive generated by LSPosed Manager contains more informations, such as all tombstone files.
You can uncompress it to discover more.