Database Info

Boot animations

IF ANY ONE HAS SOME OR HAS AN IDEA OF ONE PLEASE POST. WHAT I'M LOOKING FOR IS A BLACK BACKGROUND WITH RED HTC LETTERS THEN TO THE INCREDIBLE EYE CAMERA THING... BUT I HAVE NO IDEA ON HOW TO MAKE BOOTS
-------------------------------------
Sent via the XDA Tapatalk App

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).

DeeBG said:
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).
Click to expand...
Click to collapse
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.

If you have pushed a boot animation previously do you need to remove it? If so what are the commands for adb. Thanks for the instructions they were very clear for us noobs..
Sent from my ADR6300 using the XDA mobile application powered by Tapatalk

No you can just overwrite with the new one.
Sent from my HTC Incredible using Tapatalk

I used these two threads to get my new animation. The second one over at AndroidForums has a ton to choose from. Just gotta look through the pages.
http://forum.xda-developers.com/showthread.php?t=682860&highlight=boot+animation
http://androidforums.com/htc-incredible/70040-incredible-boot-animation.html
This is the one I currently use:
http://www.youtube.com/watch?v=9SnsXKFvGQs

very thanks

Updated Voodoo5 Kernels for USCC Mesmerize

I'm going to put a link to this here, because it's relevant to the Mesmerize, but resides in the Fascinate forum. IMO, the Voodoo 5 kernel is awesome and should warrant some attention in the Mesmerize forums.
http://forum.xda-developers.com/showthread.php?t=871915

Nice! Finally got our spot on the forum.....this should help a ton! We should compile a list of all threads that belong here, i know it has been confusing to keep everything straight up till now.

Custom boot animation to go with kernels
I posted this in response to some questions in the other forum so I thought I would paste it here also.
OK, back at the house so here's a quickie on custom boot animation that you can add while using these kernels. I'll post a link so you can check one out.
First, you will will notice it's just a zip file named bootanimation.zip. It is a zip file that is NOT compressed. So when you zip your files up, remember to select store for compression level. This tripped me up for an hour when I first tried this out.
Inside is two folders labled part0 and part1, and a text file named desc.txt. Part0 is the first part of the boot animation that is run one time. Part1 is the part of the animation that can loop over and over depending on how long it needs to and how long it is told to. These two parts need to flow together to look good, so be mindful of this. Also, you don't want to make your boot animations too long. They take up space that can be very valuable on phones that have little to begin with. Ours don't have a problem, but some do.
Inside the folders is a series of PNG files. They are named and numbered. Keep it simple. These are boot_000003.png on up to the end. Make sure you have the zeros in front to keep the spaces, otherwise they could get played out of order. Keep you png files the same specs as your phone. Ours is 480 x 800 pixels. Make sure you work in pixels not inches or cm.
The desc.txt file can be a little confusing at first also. It's just numbers and letters. This particular one looks like this:
480 800 30
p 4 0 part0
p 0 0 part1
That just tells the phone it's looking at pictures that are 480x800 pixels and it's going to go thru them at 30 frames per second (15 is commonly used also). I'm not sure what most of the rest is for other than part0 and part1, obviously, but the second 0 is for looping. 0 tells it that part1 can loop infinitely if need be. So it will continue to play as many times as it needs, until the phone finishes booting.
This particular boot animation was a quickie that I downloaded from UOT Kitchen by going through the process of not selecting anything except the boot animation, finishing the build as a cyanogen based ROM, and the downloading the package. Once it was done, I just modified the png's and the txt file and it was ready. Stored it in a zip file and I put it on my sdcard. From there you can just move it to /system/media. I just use root explorer to do this, but others may want to push the files. Do it however you are comfortable. Once there, all you do is reboot and as long as your kernel is compatible, these are, then it will play the bootanimation.
This is the nexus one's colorful x. Nothing fancy, just a quick one to show you how it's done.
http://dl.dropbox.com/u/14910866/bootanimation.zip

[Q] Issues with boot animations (need a themer's advice)

Hey guys, I have been creating some custom boot animations, and particularly the one located in my signature (revolver 4 boot animation) has some quirkiness to it..
It seems to want to stop playing on a certain image (around 57 of 69 images, something like that). I have checked;
My desc.txt file (all is in order and even swapped out some known-working files as a test, only modifying the resolution/fps line)
The image names and sizes (no numbers skipped/duplicated, no anomalies, all images around the same size of 47KB, all filenames are 5 characters, all PNG format)
I even copied the part0 folder and renamed it part1 and added a part1 line to the desc.txt file to allow it to change to try and get it to loop, it will loop the first 'part0' folder (even playing the images that are usually cut off) but as soon as it reaches part1, it hits the 57th (or whichever file it is) and goes blank..
I am using VIM to edit text and 7zip to pack the files, though that would seem to be OK since if either one was a problem the animation wouldn't play to begin with..the file is in my signature if anyone wants to play around with it and help me out. I can't seem to figure out what the main problem is- so the compromise is either have part1 folder, and/or loop the part0 a few times (haven't even tried but suspect it will go blank on first repeated loop), or have part1 added, add a part 2, etc. to allow it to loop (or just add another 'p1 0 part0' in the desc.txt). And btw, I have tried;
Code:
800 700 20
p0 0 part0
It won't play but once, even though the first 0 is by all accounts supposed to make it loop indefinitely..so, I'm at a loss.
Any help would be greatly appreciated.

I am having a pretty big problem with bootanimations as well but mine will not even run once. Super frustrating. Even when i take a working boot animation and swap out the photos with the same resolution it does not work.

There is something funny about bootanimations- I think you have to use the store function, so that it isn't compressed. Also, maybe the old fashion zip would be compatible- 7zip might not be? Isn't that a windows thing?

gee one said:
There is something funny about bootanimations- I think you have to use the store function, so that it isn't compressed. Also, maybe the old fashion zip would be compatible- 7zip might not be? Isn't that a windows thing?
Click to expand...
Click to collapse
Using WinRar and Store... Probably something to do with the depth of the pictures or the encoding on them

The red flags are flying- It has the same first letters as windows and it's not open source.
Try taking a working bootanimation and re-arranging/re-numbering the images. If it works, then it's your images. If it doesn't, go open source.

gee one said:
The red flags are flying- It has the same first letters as windows and it's not open source.
Try taking a working bootanimation and re-arranging/re-numbering the images. If it works, then it's your images. If it doesn't, go open source.
Click to expand...
Click to collapse
i got it i forgot to flatten my images in photoshop. i feel a little stupid

This is the first issue I've had with it..t may be that I converted the mages from an animated GIF into several frames and then n photoshop saved them as PNGs, but I have other animations that I have created that run fine;
You do need a unix-friendly notepad, like notepad++ or VIM, and yes I pack the files so that they are simply stored; like I said, they play, they just don't finish the animation cycle..and I have heard that there is a limit to how many files can be in a folder, but that it was well-above 70..I have 69..so should not be an issue. Anyone tried my boot animation? It still plays and looks cool, but doesn't loop like it should.

Hey luna this might help its the desc file i used to finally get mine working
Code:
1280 800 20
p1 0 part0
p0 0 part1

mrevankyle said:
Hey luna this might help its the desc file i used to finally get mine working
Code:
1280 800 20
p1 0 part0
p0 0 part1
Click to expand...
Click to collapse
The code means;
1280 800 20
This is resolution (w x h) and the fps (how many images cycle per second)
p1 0 part0
p1= play once (p5 would be play 5x, p0 is play indefinitely), 0 = 0ms delay between initiation and first image and part0 is the folder for the images..
My problem is this; my image files are 800 x 700 and play at 29fps, so first line is obvious- 800 700 29
second line is p0 0 part0, where the image is supposed to run indefinitely. It does not though. It runs once if I use 'p1 0 part0', but does not play all the way through. Yet if the desc file were not right at all, it wouldn't play it would be blank. So I have the desc file compiled, properly otherwise the image in part0 would not even play..the problem is the images do not fully cycle..I appreciate your help but it seems I know more about these files than you do (no offense mate)..I need to figure out why the settings do not run indefinitely until boot, and does not even finish the animation completely..but plays and then goes blank halfway through it...
But when I put a duplicate folder, part1, with the same animation images, and add 'p0 0 part1' to the desc file, the FIRST animation WILL play all the way through, then the second one crashes it..
Android is funny about some things, folder hierarchy, capitalization and folder name structure, file size and compression ratio, etc..I can't seem to figure out why one of my animation images seems to crash the animation altogether..halfway through.

you probobly do know more than me about it as this is the first boot animation i have worked on. Bud i did know what everything in the code meant. And i have looked at quite a few boot animaions in the last few days. It seems to me that the standard workaround is that if you put only the first frame in part 0 with "p1 0 part0" then everything else in part1 with "p0 0 part1" it may fix it.

mrevankyle said:
you probobly do know more than me about it as this is the first boot animation i have worked on. Bud i did know what everything in the code meant. And i have looked at quite a few boot animaions in the last few days. It seems to me that the standard workaround is that if you put only the first frame in part 0 with "p1 0 part0" then everything else in part1 with "p0 0 part1" it may fix it.
Click to expand...
Click to collapse
Good idea...I am going to give it a shot, one thing I have not tried yet is splitting the part0 folder up into multiple folders, I have some doubts that will work but at this point it is worth trying I'll let you know if it solves the issue.
EDIT:
Nope...couldn't even get that one to play at all..and now for some reason my desc.txt file isn't working, I even created one from scratch in VIM and it would not work..blanks screen now. WTF..this should not be this tricky..

png software
could anyone tell me what software I can use to convert a gif animation into a series of png files. I have tried a few freeware converters but not had any luck, or even better a program that can convert any video file into a series of png's so I can skip the gif altogether?

Quick question about creating a boot animation

Hey everyone
I just got Cinema 4d and thought id create a boot animation for the TF101 as my first project. My question is how many frames, and what resolution would be the best. Im rendering at the moment 500-600 frames at 1280x800 each and i assume that will end up far to big also what's some good software to convert avi's to .png or .jpeg? (I think cinema 4d does it just havnt got that far)
Cheers

I've been searching for some boot animations, and downloaded a few, and I saw that most have the resolution set to:
Code:
1282x802
although some have it to:
Code:
1280x720
so I don't think the resolution you selected was the ideal xD. About the fps, they ranged between 10 to 40. So your fps I think is too much, but, I'm not really sure of the fps of a boot animation. Sorry .
In terms of the software you want, I've found this:
Click here
Hope that helped. Bye.

I have done quite a bit in terms of boot animations and i can say 30fps looks the best anything above that might have skipped frames or trouble loading quickly any lower and it will look jittery. As for res the going 2px above isnt necessarily anymore it was just a honeycomb issue afaik. And a big boot animation will maybe have 200~ frames

mrevankyle said:
I have done quite a bit in terms of boot animations and i can say 30fps looks the best anything above that might have skipped frames or trouble loading quickly any lower and it will look jittery. As for res the going 2px above isnt necessarily anymore it was just a honeycomb issue afaik. And a big boot animation will maybe have 200~ frames
Click to expand...
Click to collapse
Im currently rendering it at 640x400 id like it to be 300 frames because its not really a loopable animation but the file size ends up at like 60mb lol (at 500 frames). I packaged that with the desc file into a bootanimation.zip just to see it working (even if it was slow) but it always ended up playing the default android boot animation would this be because of the size? (Ive never changed the boot animation before)

JoinTheRealms said:
Im currently rendering it at 640x400 id like it to be 300 frames because its not really a loopable animation but the file size ends up at like 60mb lol (at 500 frames). I packaged that with the desc file into a bootanimation.zip just to see it working (even if it was slow) but it always ended up playing the default android boot animation would this be because of the size? (Ive never changed the boot animation before)
Click to expand...
Click to collapse
Where are you putting it? and whats the compression on your zip?

mrevankyle said:
Where are you putting it? and whats the compression on your zip?
Click to expand...
Click to collapse
Im on team eos jelly bean I put it in both data/local and system/media because i wasn't sure which one to use, the compression is set to store, im following the instructions from here: (http://forum.xda-developers.com/showthread.php?t=1122535) also im a bit unsure on the naming format I tring to find a batch file renamer to rename the files to android xxx is this right?

JoinTheRealms said:
Im on team eos jelly bean I put it in both data/local and system/media because i wasn't sure which one to use, the compression is set to store, im following the instructions from here: (http://forum.xda-developers.com/showthread.php?t=1122535) also im a bit unsure on the naming format I tring to find a batch file renamer to rename the files to android xxx is this right?
Click to expand...
Click to collapse
The naming convention does not matter at all it just does them in order eg a-z 1-99 ect
So it just does not play at all then? Not even a black screen just the old boot animation?

mrevankyle said:
The naming convention does not matter at all it just does them in order eg a-z 1-99 ect
So it just does not play at all then? Not even a black screen just the old boot animation?
Click to expand...
Click to collapse
Yeah it wiped the eos boot animation that was in system/media and now plays the animation with the gray "android" which some reflections on it
my new bootanimation.zip is 25.9 mb at 222 frames the images are all .pngs named android 001 to android 222
cheers

Sorry to waste your time dude, I got it to work just needed to add file permissions:silly:
Cheers

JoinTheRealms said:
Sorry to waste your time dude, I got it to work just needed to add file permissions:silly:
Cheers
Click to expand...
Click to collapse
That wasn't an issue with ICS so its weird that it would be in JB. but its good to know for future reference.
Looking forward to seeing what you have come up with

mrevankyle said:
That wasn't an issue with ICS so its weird that it would be in JB. but its good to know for future reference.
Looking forward to seeing what you have come up with
Click to expand...
Click to collapse
Ah that is strange, Im uploading it now (I made it for RaymanFX's rom) but its still 69 mb, how can i get it smaller it had been rendered at 640x400 at 42 dpi at 500 frames (It still plays fine though)

here's a link to it if anyone's interested (https://dl.dropbox.com/u/39805348/Boot Animation/bootanimation.zip) (still 69mb) it would be good to get some opinions on how to make it better
cheers

[GUIDE] All Related to Boot Animations !!!

A Guide To Support My Other Thread On How To Create Boot animations So It Is Easier For People To Understand And Grasp The Concept.
so they will ask less questions XD
CONTENTS
The Basics
Inside the bootanimation.zip file
Featured Boot Animations
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Basics :
The Android boot animation is contained within a an uncompressed zip file called bootanimation.zip that can be found in the media folder of the system partition i.e. /system/media on the internal memory of the device. This single file contains all the information required to play the boot animation, and is loaded automatically when the device boots. Thus, customizing or changing the boot animation is simply the process of editing or replacing this file.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Inside The Bootanimation.Zip File
This section is for those interested in finding out how the Android boot animation works. If you just want to install one without bothering yourself about what’s in the file, feel free to move on to the next section, as this one will get a little technical. Though it should be easy and simple enough for anyone to grasp.
While the Android boot animation might appear to be in a video format during playback, it is in fact a little different. If you extract the contents of the bootanimation.zip file to your computer, you will see:
A desc.txt file
A part0 folder (Contains PNG images named in incremental numbers)
More part1, part2 etc. folders (May or may not be present)
As you can see, bootanimation.zip merely contains one text file and one or more folders with PNG images. The animation is played simply by displaying the images in a sequence, and the text file defines how they are to be played. In essence, first the PNG files in the part0 folder are displayed one after the other and afterwards, those in the part1 file – if it exists – are displayed, again one after the other, and so on. All of this is defined in the desc.txt file.
Let’s see how it works in a little detail by taking a closer look at the contents of the file.
The folders
These contain PNG images named in numbers, starting from something like 0000.jpg or 00001.jpg and proceeding with increments of 1. There has to be at least one folder, and there is no known upper limit to the number of folders.
The desc.txt file
This file defines how the images in the folder(s) are displayed during the boot animation, in the following format:
Width Height Frame-rate
p Loop Pause Folder1
p Loop Pause Folder2
An example of a desc.txt file is:
320 480 30
p 1 0 part0
p 0 0 part1
As you can see, in the first line, 320 and 480 define the width and height of the boot animation in pixels for this example. This must be the same as the screen resolution of your device for the boot animation to properly play in full screen. 30 is the frame rate in fps (frames per second) i.e. number of images to display per second.
The second and third lines have a same format, start with p, which stands for a part of the animation and end in part0 or part1, which denotes the folder in which the images for that part are present.
The number after ‘p’ defines how many times this part will loop (repeat playback) before switching to the next part (if present). Specifying 0 would make the part loop indefinitely till the phone has fully booted.
The next number is for the pause, and is expressed in the number of frames, which can be translated into time by dividing it by the frame rate. A pause of 15 for example, would mean pausing for the time it takes 15 frames to play and since the frame rate is 30 frames per second, 15 frames would take half a second.
Translating all of this in case of the above example, the boot animation will play at a resolution of 320 by 480 pixels, at a frame rate of 30 fps, starting with the contents of part0 folder and after playing them in one loop, switching to contents of part1 folder and playing them continuously till the device fully boots.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE :
A note on resolution: Most high-end Android devices with large screens have a resolution of 480 x 800 pixels, and are referred to as HDPI. Some mid-range devices have a resolution of 320 x 480 pixels and are called MDPI. Lastly, the screen resolution of some low-end devices is 340 x 320 pixels and these are called LDPI, though these are either the really old Android phones or the cheapest Chinese models.
As a rule, a boot animation made for a lower resolution device will run fine on a high resolution one but it will be centered on the screen, with the extra screen space around it not being used. Using a high resolution boot animation on a low resolution device will result in the boot animation not fully displaying on the screen, with its outer parts being cut off due to being outside the screen’s bounds.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Featured Boot Animations
Link for some boot animations for ace plus : http://forum.xda-developers.com/showthread.php?t=2197483

reserved
reserved

May u make guide how to make boot splash? Like gaple rom and mb-14 kernel does?
Sent from my GT-S7500 using my finger

mohdradzi84 said:
May u make guide how to make boot splash? Like gaple rom and mb-14 kernel does?
Sent from my GT-S7500 using my finger
Click to expand...
Click to collapse
Thnxxx for d suggestion dude !

IM4U
Sent from my GT-S7500 using my finger.

OX Mobile Spy
Very useful tutorial, it is worth I came to learn

Harshraj said:
A Guide To Support My Other Thread On How To Create Boot animations So It Is Easier For People To Understand And Grasp The Concept.
so they will ask less questions XD
CONTENTS
The Basics
Inside the bootanimation.zip file
Featured Boot Animations
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Basics :
The Android boot animation is contained within a an uncompressed zip file called bootanimation.zip that can be found in the media folder of the system partition i.e. /system/media on the internal memory of the device. This single file contains all the information required to play the boot animation, and is loaded automatically when the device boots. Thus, customizing or changing the boot animation is simply the process of editing or replacing this file.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Inside The Bootanimation.Zip File
This section is for those interested in finding out how the Android boot animation works. If you just want to install one without bothering yourself about what’s in the file, feel free to move on to the next section, as this one will get a little technical. Though it should be easy and simple enough for anyone to grasp.
While the Android boot animation might appear to be in a video format during playback, it is in fact a little different. If you extract the contents of the bootanimation.zip file to your computer, you will see:
A desc.txt file
A part0 folder (Contains PNG images named in incremental numbers)
More part1, part2 etc. folders (May or may not be present)
As you can see, bootanimation.zip merely contains one text file and one or more folders with PNG images. The animation is played simply by displaying the images in a sequence, and the text file defines how they are to be played. In essence, first the PNG files in the part0 folder are displayed one after the other and afterwards, those in the part1 file – if it exists – are displayed, again one after the other, and so on. All of this is defined in the desc.txt file.
Let’s see how it works in a little detail by taking a closer look at the contents of the file.
The folders
These contain PNG images named in numbers, starting from something like 0000.jpg or 00001.jpg and proceeding with increments of 1. There has to be at least one folder, and there is no known upper limit to the number of folders.
The desc.txt file
This file defines how the images in the folder(s) are displayed during the boot animation, in the following format:
Width Height Frame-rate
p Loop Pause Folder1
p Loop Pause Folder2
An example of a desc.txt file is:
320 480 30
p 1 0 part0
p 0 0 part1
As you can see, in the first line, 320 and 480 define the width and height of the boot animation in pixels for this example. This must be the same as the screen resolution of your device for the boot animation to properly play in full screen. 30 is the frame rate in fps (frames per second) i.e. number of images to display per second.
The second and third lines have a same format, start with p, which stands for a part of the animation and end in part0 or part1, which denotes the folder in which the images for that part are present.
The number after ‘p’ defines how many times this part will loop (repeat playback) before switching to the next part (if present). Specifying 0 would make the part loop indefinitely till the phone has fully booted.
The next number is for the pause, and is expressed in the number of frames, which can be translated into time by dividing it by the frame rate. A pause of 15 for example, would mean pausing for the time it takes 15 frames to play and since the frame rate is 30 frames per second, 15 frames would take half a second.
Translating all of this in case of the above example, the boot animation will play at a resolution of 320 by 480 pixels, at a frame rate of 30 fps, starting with the contents of part0 folder and after playing them in one loop, switching to contents of part1 folder and playing them continuously till the device fully boots.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE :
A note on resolution: Most high-end Android devices with large screens have a resolution of 480 x 800 pixels, and are referred to as HDPI. Some mid-range devices have a resolution of 320 x 480 pixels and are called MDPI. Lastly, the screen resolution of some low-end devices is 340 x 320 pixels and these are called LDPI, though these are either the really old Android phones or the cheapest Chinese models.
As a rule, a boot animation made for a lower resolution device will run fine on a high resolution one but it will be centered on the screen, with the extra screen space around it not being used. Using a high resolution boot animation on a low resolution device will result in the boot animation not fully displaying on the screen, with its outer parts being cut off due to being outside the screen’s bounds.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Featured Boot Animations
Link for some boot animations for ace plus : http://forum.xda-developers.com/showthread.php?t=2197483
Click to expand...
Click to collapse
what about these codes :
320 480 36
p 1 0 part0
s 1 /system/media/poweron.ogg
p 0 0 part1
s none
could you explain those ???????