aboutsummaryrefslogtreecommitdiffstats
path: root/mtdutils
diff options
context:
space:
mode:
authorDoug Zongker <dougz@android.com>2014-03-07 09:21:25 -0800
committerDoug Zongker <dougz@android.com>2014-03-07 09:45:44 -0800
commiteac881c952fc6be0beeb5f719e3a70e651f3610e (patch)
tree89508421fe11ed892975a0d967c12a9e97619384 /mtdutils
parent182c1df40a3af36eca4ff0106a26a93f5744a56e (diff)
downloadbootable_recovery-eac881c952fc6be0beeb5f719e3a70e651f3610e.zip
bootable_recovery-eac881c952fc6be0beeb5f719e3a70e651f3610e.tar.gz
bootable_recovery-eac881c952fc6be0beeb5f719e3a70e651f3610e.tar.bz2
change how recovery animation is implemented
Instead of one 'base' installing image and a number of overlay images that are drawn on top of it, we represent the installing animation with one PNG that contains all the animation frames, interlaced by row. The PNG is expected to have a text chunk with the keyword 'Frames' and a value that's the number of frames (as an ascii string). This representation provides better compression, removes the need to subclass ScreenRecoveryUI just to change the position of the overlay or number of frames, and doesn't require gr_blit() to support an alpha channel. We also remove the 'indeterminate' progress bar used when wiping data and/or cache. The main animation serves the same purpose (showing that the device is still alive); the spinning progress bar has been redundant for a while. This changes the default recovery animation to include the antenna-wiggling and gear-turning that's used in the Nexus 5 recovery animation. Change-Id: I51930a76035ac09969a25472f4e572b289418729
Diffstat (limited to 'mtdutils')
0 files changed, 0 insertions, 0 deletions