Fix issue #109746350: startWatchingMode fails on P

Remove permission check, reverting to O behavior.

Bug: 109746350
Test: manual
Change-Id: I643321d508abc5fac5df83f4df3605ad8252e378
This commit is contained in:
Dianne Hackborn
2018-06-05 13:21:16 -07:00
parent f5976be9f4
commit 5376edd3b1

View File

@@ -1335,10 +1335,10 @@ public class AppOpsService extends IAppOpsService.Stub {
int watchedUid = -1;
final int callingUid = Binder.getCallingUid();
final int callingPid = Binder.getCallingPid();
if (mContext.checkCallingOrSelfPermission(Manifest.permission.WATCH_APPOPS)
!= PackageManager.PERMISSION_GRANTED) {
watchedUid = callingUid;
}
// TODO: should have a privileged permission to protect this.
// Also, if the caller has requested WATCH_FOREGROUND_CHANGES, should we require
// the USAGE_STATS permission since this can provide information about when an
// app is in the foreground?
Preconditions.checkArgumentInRange(op, AppOpsManager.OP_NONE,
AppOpsManager._NUM_OP - 1, "Invalid op code: " + op);
if (callback == null) {