Does anyone know how I can make my animation seamless? What I mean is some of my animations are set up so I use the following;
480 800 10
p 0 1 part0 or
480 800 10
p 1 1 part0
p 1 1 part0 etc..
yet it flashes a white or dark screen at the end of the loop.
Is there a way that I can get it to loop without the flashing white screen?
*Edit I have attached a Call of Duty MW2 in landscape orientation for reference.
should look like this.
480 800 10
p 1 0 part0
p 0 0 part1
the second 0 , before the folder is a time out/pause.
if you want audio, you should change your folder names.
instead of part0, rename it to android, the second folder really shouldnt matter.
so it should look like this..
Code:
480 800 10
p 1 0 android
p 0 0 loop
'480' is the width of the animation
'800' is the height of the animation
'10' is the desired fps of the animation
'p' defines a animation part
'1' how many times this animation part loops
'0' defines a pause (max 10)
'android' is the folder name where the animation images are
'p' defines another animation part
'0' defines that it loops forever (until android starts)
'0' defines a pause
'loop' is the folder for the second animation part.
i did notice a few of my animations had different filenames within each folder.
this caused my animation to have a pause inbetween the first folder and the loop folder.
make sure your images have the same name layout throughout the folders.
android folder:
name_00003.png
name_00004.png
name_00009.png
name_00010.png
loop folder:
name_00013.png
name_00014.png
name_00015.png
name_00020.png
this helped out.
Thanks for responding but I know how to setup desc files. Unfortunately that doesn't help out because my desc file is setup like that. (in my first post it didn't type it out as such) I have attached a copy of a boot if that helps any it's a Call of Duty MW2 in landscape orientation.
This one instead of flashing white flashes dark. I want it to be seamless without any breaks. Any ideas?
here ya go
your desc.txt file was all wrong
Thank you I appreciate it.
I am digging this boot screen. I had it for my Hero and I am trying to resize for my Evo. I I change png size. I also changed the desc.text file to:
480 800 30 (formely 320 480)
p 1 0 fade_in
p 0 0 loop
480 800 being our screen size... when pushed I get nothing but dark screen during the boot time!
http://http://forum.xda-developers.com/showthread.php?t=649468
Change to
480 800 30p
1 1 android
Change your folder name to android
Sent from my PC36100 using XDA App
I had a similar problem earlier today when I was trying to figure this out for myself Google kept bringing me here even though there was no solution.
After screwing with it for over an hour I figured it out. The problem occurs when re-zipping. When you go to zip up your folders make sure your compression method is "Store", by default the drop down for "Normal" will be selected in WinRar, so change that. I re-zipped your file and tested it, works fine on my evo.
I usually use my own boot animation and this desc works for me.
480 800 30
p 1 0 part0
p 0 0 part1
Name your main folder part0 and your loop folder part1.
I use 7zip to "add to archive" and choose the compression method of "store".
Hope it helps.
Edit: Here's the bootanimation.zip you uploaded with my proposed "fixes".
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 ???????
I want to create my own boot animation , i created one with bootanimation factory but it's useless. The Boot animation is attached below , some help to make it perfect?
desc.txt:
1st line: 400 400 30 means that you screen resolution is 400 x 400 pixels. Do you have a blackberry device?
2nd line: p 2 0 part0 means that your png files will be played twice only. Why not use 0 instead of 2?
Finally all your png files (except the first one) have a transparent border? Why?
hello! i think android 13 has a bug with bootanimation, i will explain better.
i found a gif that i liked a lot, and i wanted it as bootanimation, everything went well, except for the fact that android doesn't execute the instructions i write in "desc.txt",
1080 2400 30
c 0 0 part0
c 1 100 part1
I would like that after the bootanimation completes, the screen remains black for 3-5 seconds, that's why I put "c 1 100 part1", in fact, this happens in android 11/12, but it doesn't happen in android 13, it seems that android 13 doesn't take into account the instructions to delay the animation, I tried other bootanimations not made by me, and the problem remains.
i used two different devices
Redmi Note 10 PRO / AlphaDroid 13
Mi A2 Android11/12
I am attaching the bootanimation.