diff options
| author | 2016-01-04 11:36:08 -0600 | |
|---|---|---|
| committer | 2016-01-04 11:36:08 -0600 | |
| commit | a8d54b243bd453ded01c9c82ecc1aa019f5c50cc (patch) | |
| tree | 8151648ca24f4e26db24c2582d0fe00d682145a3 | |
| parent | db73912471df39aa527971f2884f37295616d3a9 (diff) | |
[WindowManagerService] fix starting window issue
Symptom:
1. Acitivity A and B belong to same task.
2. A is started and start B in its code
3. B is opened with blank screen
If starting icon has been display, both startingWindow and
startingView should not be null.
Current logic only uses judgement on startWindow. In above
case, it leads startingView set to null as A and B shares
the same starting window due to same task. Then system will
not get chance to remove startingView as it is null.
It needs add judgement on startingView.
Change-Id: I6cfa1a3ebce93ce435cc2d9ada239b1e808988de
| -rw-r--r-- | services/core/java/com/android/server/wm/WindowManagerService.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/services/core/java/com/android/server/wm/WindowManagerService.java b/services/core/java/com/android/server/wm/WindowManagerService.java index 8a73815abaf5..aa74b424b5a1 100644 --- a/services/core/java/com/android/server/wm/WindowManagerService.java +++ b/services/core/java/com/android/server/wm/WindowManagerService.java @@ -4312,7 +4312,7 @@ public class WindowManagerService extends IWindowManager.Stub AppWindowToken ttoken = findAppWindowToken(transferFrom); if (ttoken != null) { WindowState startingWindow = ttoken.startingWindow; - if (startingWindow != null) { + if (startingWindow != null && ttoken.startingView != null) { // In this case, the starting icon has already been displayed, so start // letting windows get shown immediately without any more transitions. mSkipAppTransitionAnimation = true; |