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

ColorDisplayService should always be started

Browse Source 
Even if no color transforms are available, for requesting whether
color modes or configurations are available.

Bug: 111215474
Test: atest FrameworksServicesTest:ColorDisplayServiceTest

Change-Id: I10a4b3b1214920117312e752ba5ea0033ff70293
This commit is contained in:
Christine Franks
2018-12-10 10:19:02 -08:00
parent fdb30ae286
commit 17a9bc82b4
1 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -36,7 +36,6 @@ import android.content.res.Configuration;
import android.content.res.Resources.Theme;
import android.database.sqlite.SQLiteCompatibilityWalFlags;
import android.database.sqlite.SQLiteGlobal;
import android.hardware.display.ColorDisplayManager;
import android.os.BaseBundle;
import android.os.Binder;
import android.os.Build;
@@ -1443,11 +1442,9 @@ public final class SystemServer {
mSystemServiceManager.startService(TwilightService.class);
traceEnd();
if (ColorDisplayManager.isNightDisplayAvailable(context)) {
traceBeginAndSlog("StartColorDisplay");
mSystemServiceManager.startService(ColorDisplayService.class);
traceEnd();
}
traceBeginAndSlog("StartColorDisplay");
mSystemServiceManager.startService(ColorDisplayService.class);
traceEnd();
traceBeginAndSlog("StartJobScheduler");
mSystemServiceManager.startService(JobSchedulerService.class);