Environment
- OS: Android 16
- Access Type: Shizuku Mode
Bug Description
On Android 16, AppControl-X is unable to recognize the Shizuku service. The Shizuku manager shows that the application has been authorized, but upon launching AppControl-X, it defaults to the standard/unprivileged mode. There are no fatal exceptions, freezes, or crashes; the app simply fails to detect the Shizuku provider interface silently.
Steps to Reproduce
- Ensure Shizuku is active and running.
- Allow Shizuku access for AppControl-X in the Shizuku app.
- Launch AppControl-X.
- Observe that the app does not switch to Shizuku-powered mode.
Expected Behavior
The application should detect the active Shizuku binder token and initialize the package management features accordingly.
Notes
Due to recent under-the-hood API changes in Android 16 regarding inter-process communication, older Shizuku binding/init methods fail silently. Updating the Shizuku/Aidl dependency or checking the provider authority queries in the manifest might be required to fix this behavior.
Environment
Bug Description
On Android 16, AppControl-X is unable to recognize the Shizuku service. The Shizuku manager shows that the application has been authorized, but upon launching AppControl-X, it defaults to the standard/unprivileged mode. There are no fatal exceptions, freezes, or crashes; the app simply fails to detect the Shizuku provider interface silently.
Steps to Reproduce
Expected Behavior
The application should detect the active Shizuku binder token and initialize the package management features accordingly.
Notes
Due to recent under-the-hood API changes in Android 16 regarding inter-process communication, older Shizuku binding/init methods fail silently. Updating the Shizuku/Aidl dependency or checking the provider authority queries in the manifest might be required to fix this behavior.