Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Check if window is using blastSync when deciding to use change tx

Browse Source 
Even when blast sync is enabled, we still need to check if the window is
part of a sync transaction when deciding if it should use the change
transaction. If the window is not part of a sync transaction, we should
still apply the bounds change transaction directly. In the cases where
the window is part of a sync transaction, there will be no need for the
bounds change transaction since the buffer will be part of the sync
transaction

Test: PIP works with blast sync enabled
Change-Id: Ie249d787213238a65995823cec344acba881522c
This commit is contained in:
chaviw
2020-10-26 18:28:02 -07:00
parent 764a15f7c7
commit efdb7a287c
1 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
services/core/java/com/android/server/wm/WindowStateAnimator.java
View File

@@ -631,25 +631,25 @@ class WindowStateAnimator {
}
private boolean shouldConsumeMainWindowSizeTransaction() {
// If we use BLASTSync we always consume the transaction when finishing
// the sync.
if (mService.useBLASTSync()) {
return false;
}
// We only consume the transaction when the client is calling relayout
// because this is the only time we know the frameNumber will be valid
// due to the client renderer being paused. Put otherwise, only when
// mInRelayout is true can we guarantee the next frame will contain
// the most recent configuration.
if (!mWin.mInRelayout) return false;
// Since we can only do this for one window, we focus on the main application window
if (mAttrType != TYPE_BASE_APPLICATION) return false;
final Task task = mWin.getTask();
if (task == null) return false;
if (task.getMainWindowSizeChangeTransaction() == null) return false;
// Likewise we only focus on the task root, since we can only use one window
if (!mWin.mActivityRecord.isRootOfTask()) return false;
return true;
// If we use BLASTSync we always consume the transaction when finishing
// the sync.
if (mService.useBLASTSync() && mWin.useBLASTSync()) {
return false;
}
// We only consume the transaction when the client is calling relayout
// because this is the only time we know the frameNumber will be valid
// due to the client renderer being paused. Put otherwise, only when
// mInRelayout is true can we guarantee the next frame will contain
// the most recent configuration.
if (!mWin.mInRelayout) return false;
// Since we can only do this for one window, we focus on the main application window
if (mAttrType != TYPE_BASE_APPLICATION) return false;
final Task task = mWin.getTask();
if (task == null) return false;
if (task.getMainWindowSizeChangeTransaction() == null) return false;
// Likewise we only focus on the task root, since we can only use one window
if (!mWin.mActivityRecord.isRootOfTask()) return false;
return true;
}
void setSurfaceBoundariesLocked(SurfaceControl.Transaction t, final boolean recoveringMemory) {