From 2632b5d0d2c307f28bd3416ca6414d6cc1e2ffdc Mon Sep 17 00:00:00 2001
From: Chet Haase <chet@google.com>
Date: Thu, 8 Aug 2013 09:56:57 -0700
Subject: [PATCH] Reduce amount of invalidation when old-style animations are
 running

Previously, old animations (view.animation.*) would cause invalidations on
both the area of the child view and then the entire parent area. There's no
reason for the second invalidation; only the child area need be redrawn.

Issue #10229470 Old animation code in View.draw() may be invalidating too much

Change-Id: I4d0d16321e20b2f34dc579eacf5d3841aed33d6d
---
 core/java/android/view/View.java | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/core/java/android/view/View.java b/core/java/android/view/View.java
index 3dff1b030041e..7a8289276ea47 100644
--- a/core/java/android/view/View.java
+++ b/core/java/android/view/View.java
@@ -14013,10 +14013,6 @@ public class View implements Drawable.Callback, KeyEvent.Callback,
         }
 
         if (more && hardwareAccelerated) {
-            // invalidation is the trigger to recreate display lists, so if we're using
-            // display lists to render, force an invalidate to allow the animation to
-            // continue drawing another frame
-            parent.invalidate(true);
             if (a.hasAlpha() && (mPrivateFlags & PFLAG_ALPHA_SET) == PFLAG_ALPHA_SET) {
                 // alpha animations should cause the child to recreate its display list
                 invalidate(true);