diff options
| author | wilsonshih <wilsonshih@google.com> | 2020-07-28 17:45:06 +0800 |
|---|---|---|
| committer | wilsonshih <wilsonshih@google.com> | 2020-08-18 23:33:50 +0800 |
| commit | 21d73a78ea285e7e37186cbd0239d0143dacbfb3 (patch) | |
| tree | c3c3db763e94d9a75d286f27c8ba56e1d40531f1 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 519293857a62e0883b82d9333408eedc5eaa8be3 (diff) | |
Fixes start new showWhenLocked activity will stuck on DreamActivity.
1. Update the isTopNonPinnedStack when check visibility for next
activity, otherwise even when DreamActivity is finishing but still on
top, there would still though next activity is not top non-pinned
stack.
2. If we start next activity while isDreaming, we will set
launchTaskBehind for the next activity, which will cause the new
activity stay in unknown apps because client will go through onStart ->
onResume -> onPaused directly, in this case ATMS will receive relayout
before activityResumed. To prevent the app transition hanging there, go
to waiting for relayout directly if we know that activity was set
launchTaskBehind.
Bug: 162190413
Test: atest PinnedStackTests ActivityLifecyclePipTests
Test: atest UnknownAppVisibilityControllerTest
Test: Set crediential and alarm, enable dream, wait to see that alarm
activity should unlock DreamActivity before transition timeout.
Change-Id: I8ef5c5e0424c925fdaccda6baff496302a0ff3ba
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions