Make it safe to use start/stop app ops outside of system proc
We now keep track of all of the active start operations per non-system process, so they can be cleaned up if the process goes away. Change-Id: I9d05f1e0281c47dbe1213de014f0491f1359685c
This commit is contained in:
@ -24,10 +24,11 @@ interface IAppOpsService {
|
||||
// be kept in sync with frameworks/native/include/binder/IAppOpsService.h
|
||||
int checkOperation(int code, int uid, String packageName);
|
||||
int noteOperation(int code, int uid, String packageName);
|
||||
int startOperation(int code, int uid, String packageName);
|
||||
void finishOperation(int code, int uid, String packageName);
|
||||
int startOperation(IBinder token, int code, int uid, String packageName);
|
||||
void finishOperation(IBinder token, int code, int uid, String packageName);
|
||||
void startWatchingMode(int op, String packageName, IAppOpsCallback callback);
|
||||
void stopWatchingMode(IAppOpsCallback callback);
|
||||
IBinder getToken(IBinder clientToken);
|
||||
|
||||
// Remaining methods are only used in Java.
|
||||
List<AppOpsManager.PackageOps> getPackagesForOps(in int[] ops);
|
||||
|
Reference in New Issue
Block a user