Android 13: READ_LOGS permission changes

[xnumad]

Screenshot of dialog [1]
Choosing "Allow one-time access" for the READ_LOGS permission request apparently gives the Scoop service the permissions as long as it runs, meaning that at the latest after a reboot, it will lose the permission again.

Reference: https://issuetracker.google.com/u/0/issues/232206670#comment19

---

Issues:

1. (bug) Scoop doesn't reliably detect not having the permission:

Scoop status notification falsely reports "Monitoring app crashes" (scoop_running)
and "Permission status" setting states "READ_LOGS permission is granted"
but doesn't detect app crashes

Only after stopping the service via the notification and reopening the app, the Android dialog [1] appears, after which (granting permission) Scoop works.

2. (new functionality) With root permissions, there probably is a way to bypass this dialog.

---

[1] https://twitter.com/MishaalRahman/status/1559930174598270976

Not of priority to me, just want to report it.

[TacoTheDank]

Google's changes are so damn annoying lol. The changes in Android 13 are a lot more involved than in Android 12, but I'll get it done eventually.

[opusforlife2]

The tweet says it's possible through Shizuku, but is that the case for rooted users as well?

[RokeJulianLockhart]

#65 (comment)

In case it's not been aforementioned, the way to remediate after an OS, as a user, is to reapply the adb permission grant command, then force stop and reinitialise the application.