this is more of a technical question for performance reasons.
.jpg's in my experience can be optimized to be a much smaller file size than a .png.
Granted the quality of the image might suffer a little, but the question here is why would anyone choose .png as their boot animation format since there is no benefit in using the transparency information. Or is there?
Secondly... does the android system somehow process a png animation faster/ smoother than a jpg animation? logic would say no, since the jpg file size is smaller , hence the system can load each frame much faster...yes / no?
One of the biggest issues i have in putting in the effort of making a kick ass boot animation is the loading times due to the large file sequence that it might require...effectively making boot up times logically longer since on top of loading up your system, it also has to load up your boot animation. I find that to be kind of foolish, and defeating the purpose of a boot animation if you know what I mean. Jpg with its optimization options make them a little more ideal for long animations but i want to see what you have to say about all this.
tsakali said:
this is more of a technical question for performance reasons.
.jpg's in my experience can be optimized to be a much smaller file size than a .png.
Granted the quality of the image might suffer a little, but the question here is why would anyone choose .png as their boot animation format since there is no benefit in using the transparency information. Or is there?
Secondly... does the android system somehow process a png animation faster/ smoother than a jpg animation? logic would say no, since the jpg file size is smaller , hence the system can load each frame much faster...yes / no?
One of the biggest issues i have in putting in the effort of making a kick ass boot animation is the loading times due to the large file sequence that it might require...effectively making boot up times logically longer since on top of loading up your system, it also has to load up your boot animation. I find that to be kind of foolish, and defeating the purpose of a boot animation if you know what I mean. Jpg with its optimization options make them a little more ideal for long animations but i want to see what you have to say about all this.
Click to expand...
Click to collapse
There are quite a few posts out there in this section explaining why pngs over jpg. Look them up, will explain why png format was choose for android. My two cents on this...if the bootanimation is so big that it makes you think about alternate formats...then it probably needs revisited. You wont believe how much you can optimze your file with a combination of lesser images and a different fps in the desc.txt.
k will look them up, but i didn't find anything on this actual subject matter.
I am already aware of the points you mentioned and I am already utilizing them to the best of my knowledge, this is just another point of optimization i want to look into.
theidlemonk said:
There are quite a few posts out there in this section explaining why pngs over jpg. Look them up, will explain why png format was choose for android. My two cents on this...if the bootanimation is so big that it makes you think about alternate formats...then it probably needs revisited. You wont believe how much you can optimze your file with a combination of lesser images and a different fps in the desc.txt.
Click to expand...
Click to collapse
Quite a few? I can't find any. If you would be so kind to share a link
Related
Sup yall. I was digging around in the system and found the boot.gif for htc5.0.1h. My qquestion is this. The g1 does not render all frames of .gif files only the first frame, the g1 does however play the boot.gif with no problem. Is there a way to get the g1 to play .gif files. I ask this because we can possibly use .gif for animated icons. Animated backgrounds/wallpapers. Not to mention having .git files working in the browser.
Is the G1's Processor and GPU seriously capable of running background task and/or run a few animated icons+background?
This sounds like a good idea, but think about the performance hit that would take place here...
Have you played with the phone at max cpu speed?
It is simply amazing.
The G1 is lightspeed.
I always thought the browser was ****ty and slow because 3G really isn't that great, but dayum. After running at fully cpu speed, the browser just takes off. Seems to load pages faster than my Pc. xD
The G1 could easily handle gifs.
APrinceAmongMen said:
Have you played with the phone at max cpu speed?
It is simply amazing.
The G1 is lightspeed.
I always thought the browser was ****ty and slow because 3G really isn't that great, but dayum. After running at fully cpu speed, the browser just takes off. Seems to load pages faster than my Pc. xD
The G1 could easily handle gifs.
Click to expand...
Click to collapse
and how do we make the cpu fullspeed? that overclocking app ?
It's not an overclock.
It's just a clocking app.
Lol.
But yes, that's how.
i dont think its a problem with it running .gifs
i just dont know why .gifs work during the boot up but wont work within android shell. im lost and have no clue where to start
Probably because the gif on boot is not an animated gif. If you open up the update.zip & look for the actual images that make this gif look animated, theres 3 images in the folder & they all work together. They didn't actually use an animated gif. Its just a gif file
I check the boot.gif and it is the animated htc gif file that plays during boot up. the other files such as sound and the xml file are there but if you just click on the boot.gif it play the animated gif file. Man i wish we could get this to persist after android boots up.
there must be a general class that handles image display. theoretically you can extend that class and make it display animated gif without much perfomance loss since the phone supports partial screen update now. However, these classes are usually implemeted in the way that they only draw the image when they're told to, so it's very hard to animate in real time.
I check the boot.gif and it is the animated htc gif file that plays during boot up. the other files such as sound and the xml file are there but if you just click on the boot.gif it play the animated gif file. Man i wish we could get this to persist after android boots up.
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
EDIT!!! F*&% photoshop defaults to background again when I save! This is ****ting me to tears.
EDIT: Just had a read of this articleabout photoshop background layer being saved by default after reading this guy's thread here
Short answer is that Layer 1 is an arbitrary assigned value to any layer above the background. Layer 0 is what your image needs to be so simply renaming the default value of 1 to 0 works AFAIK. I will be testing this in a couple of minutes.
Will leave the rest as a reference for everyone else. They may learn from my stupidity. I did use the search button though it just took searching and searching till I found that guys thread above that had something specific that applied to my situation.
Hi,
I have am a confident at Android, I have build ROMs and I have a great deal of knowledge and for some reason the most simplest thing stumps me and that is getting bootanimations to work. I understand how they work and I know its not the frame rate or anything like that it has to be something to do with my export settings? Can someone here point me in the right direction?
I will give you a scenario here and why I have mentioned the above. I can get an existing boot animation that is 100% functioning and working and then I might edit the images, say for instance I am changing the colours. I don't change their size or physical dimensions in any way shape or form (they will even play in the preview emulator perfectly), I flash them to the device and nothing? Blank screen on boot up. It completed the boot and opens the OS, but for teh duration of the boot sequence when there is usually a boot animation working it shows completely blank?
Surely it has to do with my export settings? I'm competent with use of GIMP and Photoshop, I have GIMP 2.8 the latest and PS CS6.
Can someone with some knowhow here PLEASE help me with supply "secret settings" for their export of images?
I read somewhere that the images need to be reindexed? I don't know how to do this? I have edited other PNGs that are non-bootanimation PNGS and I knew I had to uncheck indexing and check the box for R,G,B and that allowed me to edit the image.....but if I check the box for an boot animation image (set to R, G, B) back to indexed; when I close the image and re-open it again its back as a R, G, B image? WTF?
I have heard somewhere they need to be 24bit? I have NFI what that means or where to change it? My version of photoshop only has listings for 8bit, 16bit and 32bit?
Yes my kernel allows for bootanimations. Yes a boot animation was working on my phone!
I can change nothing except the colour of the images; package them in the same location in the zip; Test on the previewer for Windows; load it to the phone -> nothing!
EDIT: YES Permissions are set correctly. I can even change back to the boot animation that I changed the colour and it works perfectly
I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.
Jarmezrocks said:
I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.
Click to expand...
Click to collapse
you should upload here that bootanimation.zip file
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
Had no idea the actual image quality could be tweaked. Was browsing the LG Optimus G forums and saw this:
http://forum.xda-developers.com/showthread.php?t=2073013
Wow the improvement is noticeable. And with the camera being slightly disappointing on the Razr HD, any chance it could be similarly modded??
One thing that I noticed that helps is the default is 6MP 'widescreen'. Putting it on 8MP 'regualar' is still widescreen enough and seems to be less grainy.
Still trying to figure out what 'HDR' mode is.
HDR is high dynamic range. It gives the objects in the picture a glow or 'halo' effect, but works best in a well lit environment. Let me check how the XML is setup in the RAZR.
Okay I pulled the XML and the settings can definitely be improved, although whether or not it actually helps with the quality yet remains to be seen. Picture below is taken with the factory XML at 8 megapixels. I am modifying it right now and will push it to the phone, and hopefully if it doesn't result in a boot loop, take new picture with the modified XML.
http://tinypic.com/r/k3x0js/6
Okay my phone is still alive after replacing the XML file. Took picture with the same camera settings, see below. Initial findings show it doesn't seem to make a difference, so we're likely limited to the camera sensor itself. I'll leave the modified XML on my phone since it's not doing any harm. Note that the file size of the pictures are larger than the original set, which suggests that there less image compression being done and the photos are retaining as much details and definition as software allows.
http://tinypic.com/r/zu1t0g/6
Thanks for the effort, and I have the stock 4.2 camera, so does the mod stay the same?
BinarySauce said:
Thanks for the effort, and I have the stock 4.2 camera, so does the mod stay the same?
Click to expand...
Click to collapse
Yes, pull your media_profiles.xml from /etc/, modify it and push it back. I do not advise simply copying and pasting the XML from the Optimus G thread as an improper configuration file can cause your phone to boot loop.
*sigh* I had high hopes for this thread as I have my eyes on the RAZR HD as a possible new phone, but the sub par camera is holding me back.
also make sure when modifying the XML file u use a program that won't change the character encoding (ie word or notepad). Use apps like notepad+ or notepad2
TRF-Inferno said:
Yes, pull your media_profiles.xml from /etc/, modify it and push it back. I do not advise simply copying and pasting the XML from the Optimus G thread as an improper configuration file can cause your phone to boot loop.
Click to expand...
Click to collapse
Did you use the same values from the Optimus G thread? And I think you're too close, back up to the point where some text looks blurry on the original camera and try again
BinarySauce said:
Did you use the same values from the Optimus G thread? And I think you're too close, back up to the point where some text looks blurry on the original camera and try again
Click to expand...
Click to collapse
Yes, used the same value. 100 is the maximum allowed value for encoding, and it's pointless to allocate past 40 MB for image processing as a 8 megapixel RAW file doesn't even get that big.
I have taken other pictures as well (Outdoors, scenery, etc.), and I really can't see a noticeable difference besides the image file being larger (~2.1 MB opposed to 1.5 MB). The camera sensor is the limitation here.