User Tools

Site Tools


doc:appunti:android:logo_bootanimation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
doc:appunti:android:logo_bootanimation [2019/10/07 11:08] – [Unpack and repack the log.bin] niccolodoc:appunti:android:logo_bootanimation [2019/10/07 16:32] – [Contents of bootanimation.zip] niccolo
Line 31: Line 31:
 ==== Unpack and repack the log.bin ==== ==== Unpack and repack the log.bin ====
  
-Download the Python script **[[mtk-android-logo]]**.+Unfortunately the [[https://github.com/rom1nux/mtkimg|mtkimg]] did not work with my logo.bin. The [[https://github.com/rom1nux/mtkimg/issues/6|issue]] is about unsopported signature and RGB format. So I write a Python script, download it here: **{{mtk-android-logo.txt|mtk-android-logo}}**.
  
 <code> <code>
Line 53: Line 53:
 </code> </code>
  
-so we can desume that the picture is 4 bytes/pixel, i.e. a 32bit RGB. By trial and error we found that it is an BGRA (Blue, Green, Red and Alpha), we can convert it into PNG with ffmpeg:+so we can desume that the picture is 4 bytes/pixel, i.e. a 32bit RGB. By **trial and error** we found that it is an BGRA (Blue, Green, Red and Alpha), we can convert it into PNG with **ffmpeg**, specifying the **bgra** pixel format:
  
 <code> <code>
Line 73: Line 73:
   ffmpeg -pix_fmts   ffmpeg -pix_fmts
 </code> </code>
-===== Web References =====+===== bootanimation.zip =====
  
 +The logo contained into the **logo.bin** partition is displayed in the early stage of the boot process. Once the system partition is available, an animation is played for some seconds. That animation is contained into a zip file. In our case it turned out that the file is stored in **/system/media/bootanimation.zip**. To replace it, being into the **/system/** directory, **root privileges** are required.
 +
 +There should be an executable responsible to actually run the animation, it should be **/system/bin/bootanimation**. It may search the bootanimation.zip in several directories, where the first one found, will be used. Searched directories can be:
 +
 +  * **/custom/media/bootanimation.zip**
 +  * **/oem/media/bootanimation.zip**
 +  * **/data/local/bootanimation.zip**
 +  * **/system/media/bootanimation.zip**
 +
 +If bootanimation.zip file is **not found**, the **framework-res.apk** package is searched into directories **/system/customer/framework/** or **/system/framework/**, that file contains two images that are used as a fall-back animation:
 +
 +  * assets/images/android-logo-mask.png
 +  * assets/images/android-logo-shine.png
 +
 +==== Contents of bootanimation.zip ====
 +
 +Generally the animation is composed of **two parts**: the first is played just **once**, the second part is played in **loop** until the system is ready. This is controlled by the contents of the **desc.txt** file contained into the zip, here it is an example:
 +
 +<file>
 +720 1280 15
 +p 1 0 part0
 +p 0 0 part1
 +</file>
 +
 +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 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 **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**.
 +
 +<file>
 +720 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).
 +
 +So the directories structure should be something like this:
 +
 +<code>
 +.
 +├── desc.txt
 +├── part0
 +│   ├── img_000.png
 +│   ├── ...
 +│   └── img_196.png
 +└── part1
 +    ├── img_197.png
 +    ├── ...
 +    └── img_207.png
 +</code>
 +
 +To pack eveything into a zip file you can use the command:
 +
 +<code>
 +zip -r -Z store bootanimation.zip desc.txt part0 part1
 +</code>
 +
 +Beware of the **%%-Z store%%** option: the zip archive must be created using the **store compression method**, not the //deflate// one.
 +===== Web References =====
  
 +  * **[[https://github.com/rom1nux/mtkimg|mtkimg]]** Unpack/Repack boot.img, recovery.img and logo.bin for Mediatek
   * **[[https://forum.xda-developers.com/showthread.php?t=1560836|BOOT ANIMATION explained]]**   * **[[https://forum.xda-developers.com/showthread.php?t=1560836|BOOT ANIMATION explained]]**
 +  * **[[http://muzso.hu/2012/07/15/understanding-boot-animations-in-android|Understanding boot animations in Android]]**
doc/appunti/android/logo_bootanimation.txt · Last modified: 2019/10/07 16:33 by niccolo