From f3bd94a776d69730ddb95bbf7104f2fb89d92ae4 Mon Sep 17 00:00:00 2001 From: Jorim Jaggi Date: Tue, 27 Mar 2018 15:38:03 +0200 Subject: Revert "Force client composition if we'd use rotator" This reverts commit 5a96326ee136018ab9bb1cbeec1fd5f9f3a8291a. We'll configure the individual devices to avoid rotator for downscaling instead. Bug: 73640835 Bug: 72106793 Change-Id: Ibbf00b21391dc52e9327c090cf2d745495970618 --- services/surfaceflinger/Layer.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/services/surfaceflinger/Layer.cpp b/services/surfaceflinger/Layer.cpp index 6bd187f820..b56b4e4665 100644 --- a/services/surfaceflinger/Layer.cpp +++ b/services/surfaceflinger/Layer.cpp @@ -628,15 +628,9 @@ void Layer::setGeometry(const sp& displayDevice, uint32_t z transform = Transform(invTransform) * tr * bufferOrientation; } - // STOPSHIP (b/72106793): If we have less than 25% scaling, HWC usually needs to use the rotator - // to handle it. However, there is one guaranteed frame of jank when we switch to using the - // rotator. In the meantime, we force GL composition instead until we have a better fix for the - // HWC issue. - bool extremeScaling = abs(t[0][0]) <= 0.25 || abs(t[1][1]) <= 0.25; - // this gives us only the "orientation" component of the transform const uint32_t orientation = transform.getOrientation(); - if (orientation & Transform::ROT_INVALID || extremeScaling) { + if (orientation & Transform::ROT_INVALID) { // we can only handle simple transformation hwcInfo.forceClientComposition = true; } else { -- cgit v1.2.3-59-g8ed1b