You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I moved to lsposed_mod precisely because of the cli so I can disable individual lsposed modules without needing to disable lsposed itself in case of systemui crash caused by a module
Although the way it is implemented in that fork is that it needs to boot into system first to access cli so you need to be quick to do whatever changes you need as soon as adb is enabled and before the systemui crash loop forces another reboot
Yes, that's what I want to avoid as doing that would uninstall all modified apps that I have installed (by disabling signature verification)
And iirc disabling lsposed would also disable all modules so I will have to reboot twice to enable them again (three if you count the reboot required to disable lsposed as I don't run twrp). Plus I've had instances where the order in which lsposed modules are enabled affect how they work so I have to keep a note of that as well which is another hassle
Tldr disabling lsposed is an option but it would require me to remember and setup a lot of stuff again to get back to the same working state and I'm lazy
Edit: to be clear I've only needed to use the cli this way twice to rescue my system so it is not a common occurrence. But having a fallback option is pretty nice to have
Modified apps are installed on top of originals by disabling signature verification using lsposed. Disabling lsposed would also disable that
I'm might be misremembering the disabling modules part, but I think the modules got disabled for me once/twice. It might be because of booting into safe mode or rescue party trigger. It happened long ago so not sure about the details
My main point was that cli would allow disabling buggy modules without turning off other lsposed modules which I want turned on 24/7
If an modified app is installed by tricking the normal signature verification, then it will keep installed even if you disable CorePatch (I guess you are using this module).
If modules get disabled, that could be caused by safe mode, which is not your described situation.
It is not common that users have buggy modules that frequently breaks their system UI.
Jangan.meminta hal yang konyol .bagi kami para moder pemula .LSposed bangkit kembali saja sudah cukup menjadi angin segar di karenakan fox versi lama sudah usang .masalah cli anada terlalu memaksa .sementara future tersebut dimiliki pada versi LSposed mod . Gunakan saja versi tersebut dan meminta kepada developer nya untuk merawat proyek nya .cukup versi ini saja kami sungguh sungguh berterimakasih kepada @JingMatrix
Activity
JingMatrix commentedon Oct 27, 2024
Well, not really feeling that it is very useful. We can wait for other users' opinions, of course.
MmyGgithubAaccount commentedon Nov 8, 2024
I moved to lsposed_mod precisely because of the cli so I can disable individual lsposed modules without needing to disable lsposed itself in case of systemui crash caused by a module
Although the way it is implemented in that fork is that it needs to boot into system first to access cli so you need to be quick to do whatever changes you need as soon as adb is enabled and before the systemui crash loop forces another reboot
JingMatrix commentedon Nov 8, 2024
@MmyGgithubAaccount In your described situtation, you could simply disable the
Zygisk - LSPosedmodule directly.MmyGgithubAaccount commentedon Nov 8, 2024
Yes, that's what I want to avoid as doing that would uninstall all modified apps that I have installed (by disabling signature verification)
And iirc disabling lsposed would also disable all modules so I will have to reboot twice to enable them again (three if you count the reboot required to disable lsposed as I don't run twrp). Plus I've had instances where the order in which lsposed modules are enabled affect how they work so I have to keep a note of that as well which is another hassle
Tldr disabling lsposed is an option but it would require me to remember and setup a lot of stuff again to get back to the same working state and I'm lazy
Edit: to be clear I've only needed to use the cli this way twice to rescue my system so it is not a common occurrence. But having a fallback option is pretty nice to have
JingMatrix commentedon Nov 8, 2024
Why disable LSPosed will imply the following?
All of them are saved in database, and simply disabling a module won't change them at all.
MmyGgithubAaccount commentedon Nov 8, 2024
My main point was that cli would allow disabling buggy modules without turning off other lsposed modules which I want turned on 24/7
JingMatrix commentedon Nov 8, 2024
If an modified app is installed by tricking the normal signature verification, then it will keep installed even if you disable
CorePatch(I guess you are using this module).If modules get disabled, that could be caused by safe mode, which is not your described situation.
It is not common that users have buggy modules that frequently breaks their system UI.
AnatolyJacobs commentedon Dec 10, 2024
@elvizlai
I use the CLI by @mywalkb to manage LSPosed from my PC via ADB. Just created a fork from this repo by @JingMatrix (CLI added): https://github.com/AnatolyJacobs/LSPosed_CLI
Khalmods commentedon Mar 8, 2025
Jangan.meminta hal yang konyol .bagi kami para moder pemula .LSposed bangkit kembali saja sudah cukup menjadi angin segar di karenakan fox versi lama sudah usang .masalah cli anada terlalu memaksa .sementara future tersebut dimiliki pada versi LSposed mod . Gunakan saja versi tersebut dan meminta kepada developer nya untuk merawat proyek nya .cukup versi ini saja kami sungguh sungguh berterimakasih kepada @JingMatrix
Generation88 commentedon May 5, 2025
CLI should be there. It's always better to add good features