summaryrefslogtreecommitdiffstats
path: root/packages
diff options
context:
space:
mode:
authorChristopher Tate <ctate@google.com>2015-01-20 14:29:22 -0800
committerChristopher Tate <ctate@google.com>2015-01-20 14:29:22 -0800
commit0721a9463099e94f37b6c48d0aceaa04161bbda0 (patch)
tree10a8db819e6199f1b84fe14f6ca29e39b76cd557 /packages
parent7651dcb92193a5a970a2554e067ec14d6fcad802 (diff)
downloadframeworks_base-0721a9463099e94f37b6c48d0aceaa04161bbda0.zip
frameworks_base-0721a9463099e94f37b6c48d0aceaa04161bbda0.tar.gz
frameworks_base-0721a9463099e94f37b6c48d0aceaa04161bbda0.tar.bz2
Don't try to launch broadcast receivers during boot
It turns out that sysUI visibility / interactivity is racing with boot, and it's possible in some circumstances for the user to start the secure camera swipe gesture before formal boot-completed. Make sure we only send the camera-related broadcast to registered receivers in that case, otherwise we'll implicitly be asking to launch other apps before boot, which is forbidden. Bug 19060618 Change-Id: I7fcf13b5af7b2edfbb4aac06ef04a0fde2c6a0f7
Diffstat (limited to 'packages')
-rw-r--r--packages/SystemUI/src/com/android/systemui/statusbar/phone/SecureCameraLaunchManager.java1
1 files changed, 1 insertions, 0 deletions
diff --git a/packages/SystemUI/src/com/android/systemui/statusbar/phone/SecureCameraLaunchManager.java b/packages/SystemUI/src/com/android/systemui/statusbar/phone/SecureCameraLaunchManager.java
index 3f5cf3f..4a43c47 100644
--- a/packages/SystemUI/src/com/android/systemui/statusbar/phone/SecureCameraLaunchManager.java
+++ b/packages/SystemUI/src/com/android/systemui/statusbar/phone/SecureCameraLaunchManager.java
@@ -175,6 +175,7 @@ public class SecureCameraLaunchManager {
public void run() {
Intent intent = new Intent();
intent.setAction(CLOSE_CAMERA_ACTION_NAME);
+ intent.addFlags(Intent.FLAG_RECEIVER_REGISTERED_ONLY_BEFORE_BOOT);
mContext.sendBroadcast(intent);
}
});