Introduce a Lifecycle for system services
Cherry-picked from klp-modular-dev Provide an abstract class for system services to extend from, similar to the android.app.Service. This will allow services to receive events in a uniform way, and will allow services to be created and started in the correct order regardless of whether or not a particular service exists. Similar to android.app.Service, services are meant to implement Binder interfaces as inner classes. This prevents services from having incestuous access to each other and makes them use the public API. Change-Id: Iaacfee8d5f080a28d7cc606761f4624673ed390f
This commit is contained in:
@@ -16,7 +16,7 @@
|
||||
|
||||
package com.android.server.power;
|
||||
|
||||
import com.android.server.LightsService;
|
||||
import com.android.server.lights.Light;
|
||||
|
||||
import android.os.AsyncTask;
|
||||
import android.os.Handler;
|
||||
@@ -56,7 +56,7 @@ final class DisplayPowerState {
|
||||
private final Choreographer mChoreographer;
|
||||
private final ElectronBeam mElectronBeam;
|
||||
private final DisplayBlanker mDisplayBlanker;
|
||||
private final LightsService.Light mBacklight;
|
||||
private final Light mBacklight;
|
||||
private final PhotonicModulator mPhotonicModulator;
|
||||
|
||||
private boolean mScreenOn;
|
||||
@@ -72,7 +72,7 @@ final class DisplayPowerState {
|
||||
private Runnable mCleanListener;
|
||||
|
||||
public DisplayPowerState(ElectronBeam electronBean,
|
||||
DisplayBlanker displayBlanker, LightsService.Light backlight) {
|
||||
DisplayBlanker displayBlanker, Light backlight) {
|
||||
mHandler = new Handler(true /*async*/);
|
||||
mChoreographer = Choreographer.getInstance();
|
||||
mElectronBeam = electronBean;
|
||||
|
||||
Reference in New Issue
Block a user