Amino supports the ability to customize the boot animation screen via our online device management platform (Orchestrate) and can be applied on a group basis (so you can create different groups of STB's to implement different boot animations if required)
How to create a compliant Boot Animation
You can customize the visual experience of the boot process by modifying the bootanimation.zip file.
- For details on the boot animation file, refer to bootanimation format.
- For details on boot requirements, see GTVS Requirements.
| Line | Description | Example | |
| Resolution and FPS | Specifies the animation width and height (in pixels) and the frames per second (fps). Resolution values are specific to each animation; changing the numbers might create unpredictable visual effects. | 512 416 60 indicates a resolution of 512 x 416 pixels and 60 fps | |
| Animation instructions | Encoded instructions that define how the animations should play. | Examples | |
| Letter | The letter indicates the mode in which a specific animation section plays.
|
c 1 0 part1 | |
| Number (1) | The first number defines how many times the animation plays.
|
c 1 0 part1 | |
| Number (2) | The second number indicates the number of frames to delay after the animation section ends. This is usually set to 0. | c 1 0 part1 | |
| Directory | This argument specifies the name of the directory that contains the animation resources (the PNG files). | c 1 0 part1 | |
| Number (3) | Applies only to the f type animation.
|
f 0 0 part1 10 | |
To customize the boot animation:
- Download one of the following zip files:
- For devices running Android 12 or higher, use the new bootanimation_12+_2021_03.zip file that has a new fading functionality.
- For devices running Android 11 or lower, use the old bootanimation_11_2021_03.zip file.
- Unzip the downloaded zip file to a directory named bootanimation, then confirm it contains the following:
- Directories (part0, part1, part2, part3, ...), each with one or more PNG files.
- A desc.txt file with encoded instructions for how the animation should play.
- Add new directories in the bootanimation directory as needed to represent sections of the boot animation. You can add up to 240 frames to the animation by splitting the frames into multiple directories.
- Edit the instructions in the desc.txt file as needed.
- Re-zip the bootanimation directory without compressing the files. We recommend using zip as a concatenation method. Example command: zip ../bootanimation.zip * -0 -r
- Add the bootanimation.zip file to /system/media/bootanimation.zip using PRODUCT_COPY_FILES in the device.mk file.
- Test the boot animation from the shell by rebooting the device or running the following command: adb shell su root bootanimation
How to use Orchestrate to push the customized animation
Two Orchestrate ini parameters are used to push a new boot Animation to devices. Similar to boot screens, the animation should be hosted on a web server that is accessible from the STB:
e.g.
boot.animation.url = URL linking to the boot animation zip file.
boot.animation.md5 = this is the md5 checksum of the zip file.
Testing
You can test locally by pushing the files straight onto the STB using the Android Development Bridge (ADB) commands below:
$ adb push <bootanimation.zip> /data/oem/media/bootanimation.zip$ adb shell su root bootanimation
Comments
0 comments
Article is closed for comments.