AnimationDrawable.setVisible(true, true) was not correctly recording the fact that it had started the animation, so it was possible to call start(0 immediately afterwards and have two animations running on the drawable in parallel, resulting in incorrect frame ordering. Issue #5782773 Change-Id: Ifc328f755a51d10ab76b84006d1999df03d2dca1