diff options
| author | Jorim Jaggi <jjaggi@google.com> | 2015-07-01 16:02:15 -0700 |
|---|---|---|
| committer | Jorim Jaggi <jjaggi@google.com> | 2015-07-07 19:27:29 +0000 |
| commit | 588932a53e63c0a7ee281dea22559c129b40eb99 (patch) | |
| tree | 74d3f363d3955483f50a1a02f1bec675e29c9ffd /telecomm/java/android/telecom/VideoProfile.java | |
| parent | 7e675645a9f02ae2273291d31673164177b7be0b (diff) | |
| download | frameworks_base-588932a53e63c0a7ee281dea22559c129b40eb99.zip frameworks_base-588932a53e63c0a7ee281dea22559c129b40eb99.tar.gz frameworks_base-588932a53e63c0a7ee281dea22559c129b40eb99.tar.bz2 | |
Always wait for the main app window before starting a transition
When waiting for all the windows that belong to an activity, we
skipped the main window, in case it didn't had a surface yet. This
was a problem because with SurfaceViews: They set it's visibility
extremely early in the app visibility change cycle. Then, they use
another thread to draw content. Thus, they have drawn their first
frame pretty fast, where the main thread might still be in the
activity lifecycle phases. Then, we don't even have a surface for the
main window yet, but we start the app transition already because we
think the only interesting window for this app token is the
SurfaceView, which has already drawn.
Bug: 22207948
Change-Id: I708add3aab00575ae1707b25622b9b4614472892
Diffstat (limited to 'telecomm/java/android/telecom/VideoProfile.java')
0 files changed, 0 insertions, 0 deletions