One of the many customisable elements of your Android tablet is the boot animation.
In the neverending quest to personalise your device, one popular customisation is the boot animation. There are many readymade animations squirreled away on XDA-Developers, so there’s bound to be one that just screams you; however, the real pros create their own.
This method should work for most devices (tablets or phones), but not Samsungs, as they use a different format. Check compatibility before you begin.
The boot animation is actually just an uncompressed .ZIP file filled with a series of folders containing sequentially numbered .PNGs and a desc.txt file describing how to ‘play’ them. So to create your own boot animation, the first thing you need is to understand how bootanimation.zip works.
Each folder in the .ZIP contains a ‘scene’ in the animation. Having different scenes allows you have, say, a first scene play once, and then a second scene loop until the boot finishes. You can have as many scenes as you like.
The way these scenes play and loop is defined by the desc.txt file, which is formatted like this:[width] [height] [frame-rate]
p [loop] [pause] [folder]
p [loop] [pause [folder]
The first line is pretty self-explanatory: 'width' and 'height' equal the resolution of the device/.PNGs. The 'frame-rate' defines how many images play each second, but you shouldn’t really set it above 30. The 'loop' setting defines how many times the scene will play before switching to the next and 'pause' defines (in frames) how long the scene will pause on the last frame before looping or switching to the next scene. For example:1280 800 15
p 1 40 part0
p 1 0 part1
p 0 0 part2
Here, the 1,280 x 800 .PNGs play at 15fps. The first scene plays once and pauses for 40 frames (FYI 40/15 = 2.66 seconds), before moving onto the next scene, which plays once before immediately moving onto the final scene, which in turn loops until the boot has finished.
The next thing you need is a series of .PNGs in the same resolution as your tablet display and no greater than 32-bit colour depth. Each .PNG should be sequentially numbered (padded up to 5 numbers), starting at 00001.png, and maintaining the order across scenes; for example, if your first scene finishes at 00065.png, the next scene should start at 00066.png.
Once you’ve created the PNGs using your preferred image editor, place them in their respective folders and, using a Unix/Linux-compatible editor like Notepad++, create the desc.txt file as per the layout in the screenshot directly above. Adjusting the timing of the scenes can be fiddly, but such is the life of the Android customiser. Once that’s sorted, open up 7-Zip and create the bootanimation.zip with an archive format of ‘ZIP’ and a compression level of ‘Store’.
Most devices have their animation stored in /system/media/, but will ignore this animation if it finds one in the user-accessible /data/local/ directory, meaning you don’t need root access. HTC stores its in the /system/customize/resource/ directory, which you’ll need root and S-OFF to write to.
I copy the bootanimation.zip to my device via Windows and then move it to the appropriate directory using an on-device file manager – after backing up the original bootanmiation.zip, of course. You could also use 'adb' if you prefer command lines.