Force system ApplicationInfo update and notify DisplayManager
Propagates any changes to the display config made inside any framework overlay. Notably any display cutout adjustments. Partial revert of ag/I844de9e09eb1464ae112e1b480d21cf662a026e0 with the OMS method moved into AMS. Bug: 130444380 Test: manual test with simulated cutout on blueline device Change-Id: Ifa24954352fa5e92816baa8d669b9abedc4f4ab8
This commit is contained in:
@@ -36,6 +36,7 @@ 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.DisplayManagerInternal;
|
||||
import android.net.NetworkStackClient;
|
||||
import android.os.BaseBundle;
|
||||
import android.os.Binder;
|
||||
@@ -797,6 +798,12 @@ public final class SystemServer {
|
||||
mSystemServiceManager.startService(new SensorPrivacyService(mSystemContext));
|
||||
traceEnd();
|
||||
|
||||
if (SystemProperties.getInt("persist.sys.displayinset.top", 0) > 0) {
|
||||
// DisplayManager needs the overlay immediately.
|
||||
mActivityManagerService.updateSystemUiContext();
|
||||
LocalServices.getService(DisplayManagerInternal.class).onOverlayChanged();
|
||||
}
|
||||
|
||||
// The sensor service needs access to package manager service, app ops
|
||||
// service, and permissions service, therefore we start it after them.
|
||||
// Start sensor service in a separate thread. Completion should be checked
|
||||
|
||||
Reference in New Issue
Block a user