53f2d55740
Previously, we'd pass in a scale factor (based on whether the app was being scaled by the compatibility mode) to Animation.getTransformation(). This scales the pivot point of the animation based on thes cale factor. However, the pivot points were already using information that took the compatibility mode scale into account. For example, using ABSOLUTE and basing pixel values on the width/height of the view would give you values relative to the width/height of the view (pre-scaled). Using RELATIVE_TO_* would use percentages for the pivot point, again taking the scaling of the view into account. So scaling the pivot point added in another scale on top of that already being applied. The net effect was to scale the pivot point in cases where it should not be scale. For example, setting a pivot point to half-way (.5 and RELATVE_TO_SELF) would end up with an animation that would pivot around the bottom/right of the view. The fix is to simply remove the scale factor being passed in; we've already accounted for it in the pivot point, so we shouldn't concatenate it into the transform calculated by the animation. Change-Id: I9daa7581b1b9d0dfb10515e96947160c28c5130e