diff options
| author | Jorim Jaggi <jjaggi@google.com> | 2017-08-02 14:37:49 +0200 |
|---|---|---|
| committer | Jorim Jaggi <jjaggi@google.com> | 2017-08-02 14:37:49 +0200 |
| commit | ea039a8074522168742e735aa47a5c839ac57b60 (patch) | |
| tree | 5adfcc04e7b0d070a1fe24e188edede80b4ee056 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 27eb322ed2d04bab3850e05e9a0a5fb08f65026f (diff) | |
Start all visible running activities when attaching app
This fixes an issue where a translucent activity was on top of a
normal activity in the same process. Now, when reopening the
translucent activity after the process has been killed we only
used to start the very top activity, leaving the normal activity
in destroyed state. However, we make the activity visible already
so in window manager we are waiting for it but a window is never
added to it.
This fixes the issue by starting all activities that are visible
and running once the app is attached.
Test: go/wm-smoke
Test: Have app with translucent activity on top of normal
activity, kill app via shell, navigate back to app via recents.
Observe no excessive delay.
Change-Id: I444b7064b8e2e878fac5fa9ac8b36e0e2fe248bc
Fixes: 33269100
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions