diff options
| author | 2021-01-15 21:09:40 +0000 | |
|---|---|---|
| committer | 2021-01-15 21:09:40 +0000 | |
| commit | 60c5e2ed7fac3da25efa96e7a951631fd60cf008 (patch) | |
| tree | 4304657b8b543f73f762034950b1588a4a0fa572 | |
| parent | 17a32e8072da33bfb5c137a3660e59b7287f8a3c (diff) | |
Separate FINE and COARSE location ops
Today FINE op maps to COARSE op. When we revoke FINE permission, it
also revokes COARSE permission due to the mapping. This CL separates
FINE and COARSE ops to fix the issue.
Test: manual test to revoke FINE permission and it doesn't revoke COARSE
op.
Change-Id: I73961eb9949710733c6ec2d8f80a41405a49436b
| -rw-r--r-- | core/java/android/app/AppOpsManager.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/core/java/android/app/AppOpsManager.java b/core/java/android/app/AppOpsManager.java index a23dd35fa55f..161b7313b893 100644 --- a/core/java/android/app/AppOpsManager.java +++ b/core/java/android/app/AppOpsManager.java @@ -1645,7 +1645,7 @@ public class AppOpsManager { */ private static int[] sOpToSwitch = new int[] { OP_COARSE_LOCATION, // COARSE_LOCATION - OP_COARSE_LOCATION, // FINE_LOCATION + OP_FINE_LOCATION, // FINE_LOCATION OP_COARSE_LOCATION, // GPS OP_VIBRATE, // VIBRATE OP_READ_CONTACTS, // READ_CONTACTS |