Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Start AccessCheckingService in SystemServer.

Browse Source 
The service constructor and onStart() only does trivial work and its
start time is also tracked by TimingsTraceAndSlog. The new app op and
permission implementation will only be active when they are later
selected inside the existing permission and app op system services and
that selection will happen behind a feature flag disabled by default.

Bug: 182523293
Test: presubmit
Change-Id: I2d678ef2d5747440afebc92868f92c4a02565856
This commit is contained in:
Hai Zhang
2022-12-10 23:21:10 -08:00
parent a8c89fe807
commit c8a46e1455
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
services/java/com/android/server/SystemServer.java
View File

@@ -154,6 +154,7 @@ import com.android.server.os.DeviceIdentifiersPolicyService;
import com.android.server.os.NativeTombstoneManagerService;
import com.android.server.os.SchedulingPolicyService;
import com.android.server.people.PeopleService;
import com.android.server.permission.access.AccessCheckingService;
import com.android.server.pm.ApexManager;
import com.android.server.pm.ApexSystemServiceInfo;
import com.android.server.pm.BackgroundInstallControlService;
@@ -1110,6 +1111,11 @@ public final class SystemServer implements Dumpable {
startMemtrackProxyService();
t.traceEnd();
// Start AccessCheckingService which provides new implementation for permission and app op.
t.traceBegin("StartAccessCheckingService");
mSystemServiceManager.startService(AccessCheckingService.class);
t.traceEnd();
// Activity manager runs the show.
t.traceBegin("StartActivityManager");
// TODO: Might need to move after migration to WM.