You might of have caps lock on by accident, just keep a look out for that (some people can get bent out of shape about it... not me though, because I am looking for some sort of specs/guide for boot animations). So far I've only seen boot animations ported from other phones, which while cool, there is something special about making exactly what you want.
There is a lack of info out there (I believe), because this really isn't something meant for end-users (compared to creating backgrounds or ringtones). Feel free to PM me if you have info on creating custom boot animations (we need to celebrate the rooting of our beloved Incredible =p).
There is loads on info on this stuff. You just have to search. Below is an example desc.txt file. This describes how to construct your desc.txt file and what everything does.
#example desc.txt
Code:
480 800 15
p 1 0 android
p 1 5 end
p 0 0 loop
The first line is Width, Height and Frame Rate respectively. The width and height do not need to be the size of your screen in case your frmaes are an odd size. The remaining lines describe your folders that contain the animations and what to do with them. Each remaining line begins with the letter 'p' as a separator. The first digit after the 'p' defines how many times to play through the animation. A zero (0) in that position will cause that animation to loop indefinitely until the boot process is complete. The second digit defines how many frames to pause before moving on to the next line or animation. The time elapsed is defined by your frame rate and the number of frames paused. For example, if your frame rate is 15 and you choose to pause for 30 frames, the time elapsed will be two (2) seconds. The last element in the line is the folder name to pull the animation from.
The pictures in your folders are the individual frames for your animation. They can be either .JPG or .PNG file types. If your finished product ends up being too large, you can usually reduce the size by converting the frames to .JPG format. The only other requirement is the file names must follow a sequential number sequence incrementing from start to finish.
If you wish to add sound to your animation, it should sync to your storyboard. The sound will start playing immediately after the boot animation starts and will play to either it ends or the phone finishes booting. The audio will not loop unless it is looped in the audio file itself. The audio file name must be named android_audio.mp3 for it to be recognized. The only other requirement is that one of your folders MUST be named 'android'.
It is important to note that when creating a boot animation, the finished product must be placed in a zip file named bootanimation.zip (with the exception of the audio file). However, when doing this always select the 'store' method for compression so the data is NOT compressed. If you mess up, you will know by the blank, black screen you see while booting.
Both the bootanimation.zip and android_audio.mp3 need to be pushed or copied to /data/local/ for the system animation to be overridden.
