Call systemReady on the lock settings before doing so on the window manager
At systemReady time, the window manager needs to obtain values from the lock settings service (e.g. whether the lock screen is disabled). During the initial boot of a wiped device, the window manager was getting the wrong values because LockSettingsService.systemReady/migrateOldData had not yet been called. Change-Id: I60825d0e4fad53a5b4349dabf9e5e299b863d0d0 (cherry pick of 2458abaf6676d5015af733c1010ecd67a085e9e2 from jb-aah-dev)
This commit is contained in:
@ -701,6 +701,12 @@ class ServerThread extends Thread {
|
||||
}
|
||||
}
|
||||
|
||||
try {
|
||||
lockSettings.systemReady();
|
||||
} catch (Throwable e) {
|
||||
reportWtf("making Lock Settings Service ready", e);
|
||||
}
|
||||
|
||||
try {
|
||||
wm.systemReady();
|
||||
} catch (Throwable e) {
|
||||
@ -726,11 +732,6 @@ class ServerThread extends Thread {
|
||||
} catch (Throwable e) {
|
||||
reportWtf("making Package Manager Service ready", e);
|
||||
}
|
||||
try {
|
||||
lockSettings.systemReady();
|
||||
} catch (Throwable e) {
|
||||
reportWtf("making Lock Settings Service ready", e);
|
||||
}
|
||||
|
||||
// These are needed to propagate to the runnable below.
|
||||
final Context contextF = context;
|
||||
|
Reference in New Issue
Block a user