Lspsoed parasitic manager not able to open it through shortcut for the second time

[ghost]

When I fresh install the module I am only able to open the parasitic manager for the first time, when I close it or after rebooting the Shortcut is there but it doesn't open the parasitic manager. If I disabled the parasitic notification, I need to install the lsposed manager app again to be able to access it. Attached the screenshot of what happens when I click on the shortcut and I am using the latest canary Lsposed build.

[mywalkb]

can you provide logs and more details about your device?

[ghost]

I don't have issues with the installed manager but it recommends me to use the parasitic manager, I get the same message with the original Lspsoed before it wasn't like this. The modules still work for me even after these error and I didn't try with Magisk.

[mywalkb]

before it wasn't like this

Do you know what event triggered this issue?
android update, lsposed update, kernelsu update or others

[ghost]

Actually now it is working, the issue appeared after I went to the Canary verison. To clear memory the phone stops the background running apps so the Shell apparently should be running in the background for the shortcut to work as it was closed the shortcut didn't work when I added it to excluded apps list to not close it now it is working perfectly.

[elswerky]

I just needed to give root access to shell

strange, usually I have root permissions to the shell, but even if I remove them the shortcut continues to work. Parasitic manager works with hooks.

Ro
This issue occur with last few months updates of oneui Samsung devices

And not all devices

Samsung changed something as I expect ,I hope you can figure it And fix it

[elswerky]

before it wasn't like this

Do you know what event triggered this issue? android update, lsposed update, kernelsu update or others

Samsung update in last about 6 months ,, some Samsung devices have this issues,, others not affected
But it is related to an update in oneui 5.1. , I have note 10 lite on ineui 5.1 without issue ,so some devices only

[elswerky]

Foe example I faced this issue on tab S6 lite ,, but when I revert back to old update with same binary I was able to get this issue fixed

So it is related to something changed by Samsung in last few updates. , and again nig all Samsung devices gave this issue with last updates