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

1 files changed, 1 insertions, 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<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 {