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
Download the latest release as a system module.
Install the module via your root manager (Magisk/KernelSU).
Ensure a Zygisk environment (e.g., [NeoZygisk](https://github.com/JingMatrix/NeoZygisk)).
Reboot the device.
BUG: Access management settings via the system notification.
Expected behaviour/预期行为
a manager or some functioning interface appearing on last step
Disabling secure app spawning makes it so the titular error is now the only error encountered.
so the solution is basically just an entire framework patch as suggested here: #340 (comment)? I will try that but it seems more manual and technically very invasive than any solutions to any other problems with this repository or magisk in general which I've encountered so far.
@JingMatrix
Hello,
The parasitic manager (manager supposed to be opened with notification) still doesn't open, as it crashes with DCL failure notification, but the main thing I was trying to achieve (functionality of Hide My Applist) is now working with this build.
The LSPosed apk I'd installed from apkpure during previous attempts had once said lsposed was detected as running(it now says LSPosed is not installed) -- but that was when the notification said LSPosed loaded as opposed to Vector loaded, like it does now(still no manager on tap though). Also the notification used to have a red LSPosed logo(looks like two bicolored bandages - I assume this is now the "Vector" logo) and the logo now is gray with this most recent build having run in magisk.
What I was initially trying to achieve with multiple past issues on this repository; the hiding of my rooted device's rooted status to prevent the "ref:7144:EADE:98V1Q0 Magisk Detected by App" error when booting Pixel Gun 3D on GrapheneOS, has been achieved.
I suppose it would still be good to find an opening of the parasitic manager so maybe keep this open until the solution in #340 has been tried or parasitic manager is successfully run on my system some other way.
tl;dr: HMA is working with the apps I want now but I still can't open any managers from the notification because of "secure app spawning" -> "Shell tried to perform DCL via memory".
The last commands just hangs indefinitely. No new manager app appears after running the first command, which I'd gotten the following error trying to run until I ran adb uninstall org.lsposed.manager, which removed the lsposed manager that was at least giving me an indication of some functionality.
Performing Streamed Install
adb.exe: failed to install ./manager.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE: Downgrade detected: Update version code 3038 is older than current 7181]
Now I have only the broken Vector Loaded notification that continues to crash the shell with an app that never reaches any type of functioning screen.
I gave the Shell root, installed manager as a local app, disabled secure app spawning, and now the shell will not boot correctly. (Pixel is Starting... loading forever, no interaction) This did not happen if any of these steps were done individually but as soon as they were all enabled at once this started happening. Ill send my log folder but I couldnt access them until i rebooted into safe mode, disabled secure app spawning and rebooted again so they might be for the current boot and thus not useful
I apologize, turns out I had punch-hole download progress enabled unknowingly from previous tweaking, and it crashes the shell. Everything actually works now and I was able to get a different module to load. Not sure if modules that affect the shell work tho
This GrapheneOS feature prohibits system applications from performing dynamic code loading. You should install manager located in the module directory.
I've come up with a one-patch module that allows DCL settings to be modified for system apps, allowing you to get the parasitic manager, and all other modules working. Perhaps this patch could get integrated into Vector?
For an integrated patch, the shell should also probably be force-allowed to use DCL like the settings app is. Not strictly necessary but it would mean users don't have to first get the old manager working.
Activity
JingMatrix commentedon Apr 12, 2026
Duplicate of #491 and #340.
User10987654321 commentedon Apr 12, 2026
Disabling secure app spawning makes it so the titular error is now the only error encountered.
so the solution is basically just an entire framework patch as suggested here: #340 (comment)? I will try that but it seems more manual and technically very invasive than any solutions to any other problems with this repository or magisk in general which I've encountered so far.
JingMatrix commentedon Apr 12, 2026
@User10987654321 You may upload the folder
/data/adb/lspd/logas logs for me to help you further.I am not using GrapheneOS, and cannot help you at all without any logs.
User10987654321 commentedon Apr 12, 2026
JingMatrix commentedon Apr 12, 2026
@User10987654321 Invalid file format, upload an
.ziparchive please.User10987654321 commentedon Apr 13, 2026
@JingMatrix
lspd_log.zip
JingMatrix commentedon Apr 13, 2026
@User10987654321 Please use the latest CI build, and trigger the manager crash before uploading your logs.
[-]manager shell crash on tapping "LSPosed Loaded" notification[/-][+]Manager crashes on GrapheneOS[/+]JingMatrix commentedon Apr 13, 2026
My bad, I saw the crash now in your logs:
JingMatrix commentedon Apr 13, 2026
To help the binary debugging, please flash exactly this build: https://github.com/JingMatrix/Vector/actions/runs/24328101053 and upload your logs again.
User10987654321 commentedon Apr 13, 2026
lspd_log1.zip
JingMatrix commentedon Apr 13, 2026
@User10987654321 There is no crash observed in your new logs, did you try open the manager ?
1 remaining item
JingMatrix commentedon Apr 13, 2026
The crucial error is:
JingMatrix commentedon Apr 13, 2026
@User10987654321 From your error log, you have to do #340 to use the parastic manager.
But how about used the installed manager ? See #123 for instruction to install manager manually.
User10987654321 commentedon Apr 13, 2026
@JingMatrix
Hello,
The parasitic manager (manager supposed to be opened with notification) still doesn't open, as it crashes with DCL failure notification, but the main thing I was trying to achieve (functionality of Hide My Applist) is now working with this build.
The LSPosed apk I'd installed from apkpure during previous attempts had once said lsposed was detected as running(it now says LSPosed is not installed) -- but that was when the notification said LSPosed loaded as opposed to Vector loaded, like it does now(still no manager on tap though). Also the notification used to have a red LSPosed logo(looks like two bicolored bandages - I assume this is now the "Vector" logo) and the logo now is gray with this most recent build having run in magisk.
What I was initially trying to achieve with multiple past issues on this repository; the hiding of my rooted device's rooted status to prevent the "ref:7144:EADE:98V1Q0 Magisk Detected by App" error when booting Pixel Gun 3D on GrapheneOS, has been achieved.
I suppose it would still be good to find an opening of the parasitic manager so maybe keep this open until the solution in #340 has been tried or parasitic manager is successfully run on my system some other way.
tl;dr: HMA is working with the apps I want now but I still can't open any managers from the notification because of "secure app spawning" -> "Shell tried to perform DCL via memory".
JingMatrix commentedon Apr 13, 2026
Read #123 to see how to install the manager as an apk, not from apkpure.
User10987654321 commentedon Apr 14, 2026
@JingMatrix
After following steps outlined here, I get the following results:
The last commands just hangs indefinitely. No new manager app appears after running the first command, which I'd gotten the following error trying to run until I ran
adb uninstall org.lsposed.manager, which removed the lsposed manager that was at least giving me an indication of some functionality.Now I have only the broken
Vector Loadednotification that continues to crash the shell with an app that never reaches any type of functioning screen.JingMatrix commentedon Apr 14, 2026
If the manually installed-manager cannot be open, please upload your folder
/data/adb/lspd/logas logs.Only the first the command is needed for installing the manager, which is clearly explained in #123.
Indeed, you don't need a manager at all, you can control vector from its cli interface via
/data/adb/lspd/cli.Enovale commentedon Apr 23, 2026
I gave the Shell root, installed manager as a local app, disabled secure app spawning, and now the shell will not boot correctly. (Pixel is Starting... loading forever, no interaction) This did not happen if any of these steps were done individually but as soon as they were all enabled at once this started happening. Ill send my log folder but I couldnt access them until i rebooted into safe mode, disabled secure app spawning and rebooted again so they might be for the current boot and thus not useful
logs.zip
Enovale commentedon Apr 23, 2026
I apologize, turns out I had punch-hole download progress enabled unknowingly from previous tweaking, and it crashes the shell. Everything actually works now and I was able to get a different module to load. Not sure if modules that affect the shell work tho
chuyb-re commentedon May 2, 2026
This GrapheneOS feature prohibits system applications from performing dynamic code loading. You should install manager located in the module directory.
Enovale commentedon May 2, 2026
Once you've installed the manager (or used the cli) you can use this: https://github.com/Enovale/GrapheneFixer
I've come up with a one-patch module that allows DCL settings to be modified for system apps, allowing you to get the parasitic manager, and all other modules working. Perhaps this patch could get integrated into Vector?
JingMatrix commentedon May 2, 2026
@Enovale Yeap, I think it is a good idea
Enovale commentedon May 2, 2026
For an integrated patch, the shell should also probably be force-allowed to use DCL like the settings app is. Not strictly necessary but it would mean users don't have to first get the old manager working.
JingMatrix commentedon May 2, 2026
@Enovale https://github.com/JingMatrix/Vector/blob/master/zygisk/src/main/kotlin/org/matrix/vector/core/Main.kt#L50 could be your starting point of modification.
Check the docs in each project directory if you need help, or open discussion thread for your development when needed.