Problem Statement
First of thank you for such quick updates and bug fixes.
So the issue is, I noticed the Package Name of Shizuku is hardcoded in the code, but that won't work with Hidden Shizuku as it changes the Package name. So with hidden Shizuku intents stop working even with correct Auth, as package names do not match.
Proposed Solution
As I checked the recent bug fix related to Auth (watchdog support for Shizuku), I noticed it is passed as Read-only variable (val).
So I was thinking, if that can also be made possible for Shizuku's package name, it would make Essentials App super robust.
For example, if "val" can include the default Shizuku's package name, but there's the options in app to change the package name, just like we do with Auth key.
Thanks again 😇💪
Alternatives Considered
No response
Priority
Medium - Would improve my experience
Contribution
Additional Context
No response
Problem Statement
First of thank you for such quick updates and bug fixes.
So the issue is, I noticed the Package Name of Shizuku is hardcoded in the code, but that won't work with Hidden Shizuku as it changes the Package name. So with hidden Shizuku intents stop working even with correct Auth, as package names do not match.
Proposed Solution
As I checked the recent bug fix related to Auth (watchdog support for Shizuku), I noticed it is passed as Read-only variable (val).
So I was thinking, if that can also be made possible for Shizuku's package name, it would make Essentials App super robust.
For example, if "val" can include the default Shizuku's package name, but there's the options in app to change the package name, just like we do with Auth key.
Thanks again 😇💪
Alternatives Considered
No response
Priority
Medium - Would improve my experience
Contribution
Additional Context
No response