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

Commit 11c79b02 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

Change-Id: I9f8a8bd156f4a008c8db40faef6625e66363d64f
parents 101c804a 88ec2758
Loading
Loading
Loading
Loading
+1 −7
Original line number Diff line number Diff line
@@ -628,15 +628,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 {