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

Revert "Populate active apexes cache in a background thread"

Browse Source 
This reverts commit 97fc6d9c29.

Reason for revert: b/132236259

Change-Id: I5270140580ebad16a9dc1db6b2e5f9faa977f54a
Bug: 132236259
This commit is contained in:
Mohammad Samiul Islam
2019-05-08 14:41:53 +00:00
committed by Nikita Ioffe
parent 97fc6d9c29
commit bdccb7501b
3 changed files with 57 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -115,7 +115,6 @@ import com.android.server.om.OverlayManagerService;
import com.android.server.os.BugreportManagerService;
import com.android.server.os.DeviceIdentifiersPolicyService;
import com.android.server.os.SchedulingPolicyService;
import com.android.server.pm.ApexManager;
import com.android.server.pm.BackgroundDexOptService;
import com.android.server.pm.CrossProfileAppsService;
import com.android.server.pm.DynamicCodeLoggingService;
@@ -628,12 +627,6 @@ public final class SystemServer {
watchdog.start();
traceEnd();
// Start ApexManager as early as we can to give it enough time to call apexd and populate
// cache of known apex packages. Note that calling apexd will happen asynchronously.
traceBeginAndSlog("StartApexManager");
mSystemServiceManager.startService(ApexManager.class);
traceEnd();
Slog.i(TAG, "Reading configuration...");
final String TAG_SYSTEM_CONFIG = "ReadingSystemConfig";
traceBeginAndSlog(TAG_SYSTEM_CONFIG);