Differences

This shows you the differences between two versions of the page.

--- doc:appunti:android:logo_bootanimation [2019/10/07 16:12] – [bootanimation.zip] niccolo
+++ doc:appunti:android:logo_bootanimation [2019/10/07 16:33] (current) – [Contents of bootanimation.zip] niccolo
@@ Line 95: / Line 95: @@
 <file>
 1280 15
-p 1 5 part0
+p 1 0 part0
 p 0 0 part1
 </file>
@@ Line 101: / Line 101: @@
 The first line tell us that the animation is **720x1280 pixels**, at **15 frames per second**.
-The second line tell us that there is a part **p** to be executed **1** time, followed by a pause of **5** (FIXME Not working? Unit of measure?). The actual frames are contained into the **part0** subdirectory.
+The second line tell us that there is a part of **type p** to be executed **1** time. The following number (**0** in the example above) someone says that it is a pause to wait after the animation, in my case it is instead ununsed at all. The actual frames are contained into the **part0** subdirectory.
-The last line defines another part **p** to be executed in an endless (**0**) loop until the system is ready, with a zero **0** pause. The frames are into the **part1** subdirectory.
+The last line defines another part **type p** to be executed in an endless (**0**) loop until the system is ready, with a zero **0** pause. The frames are into the **part1** subdirectory.
+A **type p** means that the animation can be interrupted when the boot process is completed. If you want instead a part to be played as the final part of the animation (e.g. if you want a fade-out effect), you have to use a **tpye c**, which means //play at least once//.
+<file>
+1280 15
+p 1 0 part0
+c 0 0 part1
+c 0 0 part2
+</file>
+In the above example, once the boot process is completed, the **part1** is interrupted, and the **part2** is executed. Animation part **type c** was introduced with **Android Jelly Bean** (i.e. Android 4.1 to 4.3.1).
 Frames are actually **PNG images**, of the proper size (720x1280 in our case).