From ae846f4a15eead9a6e82d5d8668999e724fae36e Mon Sep 17 00:00:00 2001 From: Wale Ogunwale Date: Mon, 22 Feb 2016 14:00:56 -0800 Subject: [PATCH] Fixed bug with non-focusable stack activity not displaying on start. Activity manager normally singals window manager that it is okay to start the app transition process for an activity we are launching during the resume process. However, the activity will not be resumed if the activity is been launched in a non-focusable stack (e.g. pinned stack). So, the app transtion will not start and it will not be visible until the app transition time's out in window manager. Activity manager now tells window manager to execute app transitions if we are launching an activity in non-focusable stack. Bug: 27224884 Change-Id: I35245fceb2637b927e7885b2c02daa1d55deaabb --- services/core/java/com/android/server/am/ActivityStarter.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/services/core/java/com/android/server/am/ActivityStarter.java b/services/core/java/com/android/server/am/ActivityStarter.java index 1166ae18387ab..6614e638b9837 100644 --- a/services/core/java/com/android/server/am/ActivityStarter.java +++ b/services/core/java/com/android/server/am/ActivityStarter.java @@ -1037,6 +1037,9 @@ class ActivityStarter { // make sure it becomes visible as it starts (this will also trigger entry // animation). An example of this are PIP activities. mTargetStack.ensureActivitiesVisibleLocked(null, 0, !PRESERVE_WINDOWS); + // Go ahead and tell window manager to execute app transition for this activity + // since the app transition will not be triggered through the resume channel. + mWindowManager.executeAppTransition(); } } else { mTargetStack.addRecentActivityLocked(mStartActivity);