summaryrefslogtreecommitdiffstats
path: root/tools/layoutlib
diff options
context:
space:
mode:
authorJorim Jaggi <jjaggi@google.com>2014-03-31 16:35:15 +0200
committerJorim Jaggi <jjaggi@google.com>2014-04-02 22:11:19 +0200
commitcff0acb6b1eea23c3f44a078a0a5e81c11faea35 (patch)
tree900f324f271f8cfceccdc64575333b9aca15cbf1 /tools/layoutlib
parent8533b95b4c217c588bddfbc1e57051377d963cc0 (diff)
downloadframeworks_base-cff0acb6b1eea23c3f44a078a0a5e81c11faea35.zip
frameworks_base-cff0acb6b1eea23c3f44a078a0a5e81c11faea35.tar.gz
frameworks_base-cff0acb6b1eea23c3f44a078a0a5e81c11faea35.tar.bz2
Wait for Keyguard to be drawn after boot.
The old logic with waiting for the Keyguard to be drawn assumed that it is in an own window, and just checked for the visibility. This is no longer possible as the Keyguard is in the status bar, and the status bar might have been drawn without the Keyguard. So we have to wait explicitely until Keyguard told PhoneWindowManager that it has now been drawn and we can turn on the screen. In addition, the starting logic of SystemUI is moved into SystemUIApplication such the we can make sure that the status bar already exists when the callbacks from PhoneWindowManager reach KeyguardService. This simplifies the logic a lot. Bug: 13635952 Change-Id: Ifd6ba795647edcf3501641e39052e4d04bc826fb
Diffstat (limited to 'tools/layoutlib')
-rw-r--r--tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java4
1 files changed, 4 insertions, 0 deletions
diff --git a/tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java b/tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java
index 743a26c..e8c8d5d 100644
--- a/tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java
+++ b/tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java
@@ -462,4 +462,8 @@ public class IWindowManagerImpl implements IWindowManager {
// TODO Auto-generated method stub
return false;
}
+
+ @Override
+ public void enableScreenIfNeeded() throws RemoteException {
+ }
}