Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer setting resets after reboot (shizuku)? #601

Open
spart0n654 opened this issue Dec 8, 2023 · 3 comments
Open

Installer setting resets after reboot (shizuku)? #601

spart0n654 opened this issue Dec 8, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@spart0n654
Copy link

spart0n654 commented Dec 8, 2023

Idk if this is an issue or a feature request

So using shizuku installer works just fine but after every reboot, even after starting shizuku first without opening droidify then open droidify the installer is reset to session.

Is there a way to have droidify try to verify shizuku is running when droidify is launched, if it was set to shizuku previously, before just resetting the settings?

@spart0n654 spart0n654 added the enhancement New feature or request label Dec 8, 2023
@Iamlooker
Copy link
Member

This was to ensure that the installer is not set to shizuku if it is not running. I will try to find a workaround in future builds

@spart0n654
Copy link
Author

spart0n654 commented Dec 9, 2023

This was to ensure that the installer is not set to shizuku if it is not running. I will try to find a workaround in future builds

Well that makes me feel better that it's not a bug, that it's working as intended. Currently I'm not rooted using automate to start shizuku on boot if that helps with anything. Also love droidify, keep up the great work.

@BRBsoup
Copy link

BRBsoup commented Feb 22, 2024

Shizuku installer setting has to be manually set each time phone restarts and re-enabling Shizuku ~ I understand the reason, but any way to get the app to remember if installer was set to Shizuku, and switched back because Shizuku was not found to be running, to then revert back to the Shizuku installer setting again once Shizuku is actually enabled again. Perhaps staying on Shizuku and then fall-back to Session if Shizuku not found on every install or something... Or just any way to get around this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants