Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 195bf188 authored by Jorim Jaggi's avatar Jorim Jaggi Committed by android-build-merger
Browse files

Merge "Revert "Force client composition if we'd use rotator"" into pi-dev am: 88ec2758

am: 11c79b02

Change-Id: Iba3c5486facc9889f0736587886418835e4e4204
parents 9069c30b 11c79b02
Loading
Loading
Loading
Loading
+1 −7
Original line number Diff line number Diff line
@@ -624,15 +624,9 @@ void Layer::setGeometry(const sp<const DisplayDevice>& 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 {