• General
  • Disabling animations cause regression with display changes

  • Edited

When animations are disabled, any display changes such as Night light, Extra dim, Colour correction, etc remain in that state until a different display change is enabled.

For example, I use Colour correction during certain times of the day. When disabling it, it won't turn off until another display option is enabled. And when disabling that option, it won't turn off until yet another display option is enabled.

The only workaround I have been able to discover is to first enable animations, then disable those display settings, and then animations can be disabled again. Which definitely isn't very convenient compared to the quick tiles.

Just thought I'd throw it out there in case anyone else is experiencing this behaviour. Not sure if this has been reported before but I recall something similar used to occur except it affected all devices regardless of animation settings.

Thoughts?

Best to avoid disabling animations. Its not well tested in AOSP and causes various bugs. Is the cause of a security issue we fixed in the last release and is potential it could cause others.

Changing speed of animations in Developer options has similar implications.