Cross Reference: /frameworks/base/core/java/com/android/internal/view/SurfaceFlingerVsyncChoreographer.java

History log of /frameworks/base/core/java/com/android/internal/view/SurfaceFlingerVsyncChoreographer.java
Revision		Date	Author	Comments (<<< Hide modified files) (Show modified files >>>)
ed7993b5d147a6741d26fe0b16cc9fa5e34ceaee		28-Mar-2017	Jorim Jaggi <jjaggi@google.com>	Introduce android.anim thread in system_server We create a new thread on which everything is running that directly impacts window animations, i.e. layout, anim tick and starting window creation. This is such that any work on android.display can not lead to jank in the window animation, specifically lock contention on activity manager lock that blocks callbacks from android.display into AM can not lead to window animation jank. Test: Run animation, take systrace, make sure animation is on android.anim Test: AppWindowContainerControllerTestTest: AppWindowContainerControllerTestss Fixes: 36792959 Change-Id: I5d41419a709b7984724e7053a3afdcc1ffe1aaa2 /frameworks/base/core/java/com/android/internal/view/SurfaceFlingerVsyncChoreographer.java
d6d6de6da4c7c32babd65c23804d9fdc6eeed740		31-Mar-2017	Jorim Jaggi <jjaggi@google.com>	Schedule window animations at vsync-sf Test: Run window animation, make sure it's smooth Test: Take systrace, make sure it runs at vsync-tick Test: Move divider, make sure it's still smooth Change-Id: I1600618e074be811134fe4ccb1dfbd5034820c71 Fixes: 36583867 /frameworks/base/core/java/com/android/internal/view/SurfaceFlingerVsyncChoreographer.java