Jason Simmons 5017f23284 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)

2012-08-08 13:15:00 -07:00

..

common_time

common_time: Turn the logging up to 11

2012-07-20 15:49:33 -07:00

input

Move and rename user activity event type constants.

2012-07-27 18:14:56 -07:00

java

Call systemReady on the lock settings before doing so on the window manager

2012-08-08 13:15:00 -07:00

jni

Merge "screen-off animation won't be handled by SF anymore" into jb-mr1-dev

2012-08-02 21:49:25 -07:00

tests/servicestests

…