-
Notifications
You must be signed in to change notification settings - Fork 55
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
Shizuku support for Android 14 QPR3+ #45
Comments
I have the same issue as well! I am on same app version, Android 14, and on a Pixel 6 |
Probably 2 different cases, I haven't yet added the Shizuku support for A15 and the redirect to the adb guide is a workaround for #17. |
@karasevm do you suggest for A15 to just auth via adb then? wrt to Shizuku, leave the app authorized or unauthorized? |
@aagha for now yes, A15 is limited to adb only. When it works, Shizuku is used to call the same hidden API used by the adb command to grant the permission, so the authorization shouldn't be required after the first start anyway. I'll add more toasts to communicate this clearly to the user in the next release. |
Hi @karasevm how can I access the logs for the app? |
This will be fixed in the next release. Most devices seemingly didn't get QPR3 that's why there are almost no reports of issues on Android 14. |
I have the same issue with a pixel 8 and Android 15 |
Application Version
1.9.0
Application Version
15
Device
Pixel 7a
How do you provide the permission?
Shizuku
What happened?
I give permission in Shizuku:
But when launching the app it takes me to:
https://karasevm.github.io/PrivateDNSAndroid/
Do I have to give permission via
adb
also?Steps to reproduce
No response
Relevant log output
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: