From: mariond@facts.com
Marion wrote:
> Unless someone has a better idea, I'm might soon try to use Automate +
> Shizuku since Automate can expose flows as homescreen shortcuts.
After extensive trial and error, even with Shizuku, my unrootable Samsung
device on Android 13 still blocks DIRECT one-tap external access to hidden
system activities, such as attempts to DIRECTLY launch either of these:
...or...
It seems that GrantPermissionsActivity is the 'system dialog' that appears
when any app requests any runtime permission that the user must grant or deny.
Meanwhile, ManagePermissionsActivity is the 'settings UI' that enables us
to manage an app's permissions such as toggling precise location for Maps.
I'm not an expert, but so far, even with Shizuku, my unrootable Samsung
on Android 13 blocks DIRECT external invocation of these activities.
GrantPermissionsActivity = system dialog
ManagePermissionsActivity = settings UI
As far as I can tell, here's the difference between the two types above.
GrantPermissionsActivity = system dialog
A temporary window created by Android itself.
It appears on top of the current app when that app requests a permission.
For example, when Google Maps prompts for "Allow" or "Deny".
It's a short-lived modal window you must respond to before continuing.
ManagePermissionsActivity = settings UI
A screen (aka activity) that shows inside the Android Settings app.
It lets the user review and change permissions at any time.
For example the screen where we toggle Google Maps precise location.
It's a persistent screen the user navigates to that can be revisited.
It seems that both GrantPermissionsActivity (system dialog) and
ManagePermissionsActivity (settings UI) exist inside the permission
controller package where, so far, all my attempts to invoke them
DIRECTLY from outside the system didn't work, even with Shizuku.
I'm not ready to conclude this, but it may be that those activities
can't be launched by a 1-tap shortcut on unrooted Samsung Android 13.
Settings > Apps > Maps > Permissions > Location > Use precise location
The most promising alternative approach seemed to be perhaps non-runtime
control directly to the Google Maps runtime through shell commands like:
adb shell pm revoke com.google.android.apps.maps android.permi
sion.ACCESS_FINE_LOCATION
adb shell pm grant com.google.android.apps.maps android.permi
sion.ACCESS_FINE_LOCATION
But, when run on the local device, those commands seem to require the
shell user to have the same privileges adb has when connected from a PC.
On my unrooted Samsung, my local shell user doesn't have those privileges.
Worse, even Shizuku doesn't seem to be able to grant those privileges.
Shizuku might elevate permissions for a Pixel, but when I try to use it
for pm grant or pm revoke on Maps' fine location permission, Samsung's
security model appears to be blocking those calls (AFAICT).
While my original plan went to hell, apparently due to Samsung's
strict added permission issue, my latest next-level plan may be to
add a Settings intent that opens the Maps app info page.
Settings > Apps > Maps > Permissions
Unfortunately, from there we still need to tap Permissions, then
Location, and only then can we toggle precise location on or off.
Hence, my next step may be to explore whether an intent can open the
Maps app info screen to reduce the tap count from 6 taps to 3 taps.
For that, maybe an intent such as ACTION_APPLICATION_DETAILS_SETTINGS
with the Maps package name can be used. If successful, this would
create a shortcut that lands directly on the Maps app info page in
Settings. That may be the closest shortcut available sans root access.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
