yashsingh1/xdaforums huggingface dataset:
[Wear OS Software and Hacking General] wollac11:
I've never actually made a CyanogenMod theme since they updated the theme manager to include boot animations etc. I'll look into it but make no promises on time scale!
[Wear OS Software and Hacking General] rjmohit:
take all your time!! :good:
[Wear OS Software and Hacking General] johnnyfr03:
Scared noob

First of all thanks for the updates. Just had a bit of a scare. Downloaded and installed the new 1080 version for my N5. Started working well but it got stuck on the boot animation more than usual. Any ideas? I know boot time is according to phone but it has never taken this long. Scared the jeepers out of this poor noob. Thanks in advance!!
[Wear OS Software and Hacking General] scoobyjenkins:
The v2 looks awesome in 1080, will there be a v2 1920x1200?

Tapatalked that shiznit.
[Wear OS Software and Hacking General] IgnorCZ:
Thanks for update :) .. it's noticeable smoother :) nice!
[Wear OS Software and Hacking General] logonaniket:
Am I the only one who is feeling that this animation is a bit longer (in terms of time) than usual?
[Wear OS Software and Hacking General] wollac11:
Whoops! :o Sorry about that. I'm not sure how I missed that one off when I was uploading. That's actually the one I use on two of my own devices. Just added it now! :D
[Wear OS Software and Hacking General] wollac11:
No problem! And yes, smoothness is one of my big priorities because that makes it look and feel so much nicer!
[Wear OS Software and Hacking General] wollac11:
Can't really think why that would happen as a result of the boot animation change - particularly given this one is more lightweight than the old version. Should be nothing to worry about though. Is it happening every time or just the once?
[Wear OS Software and Hacking General] johnnyfr03:
Once so far. Have not tried again!
[Wear OS Software and Hacking General] wollac11:
Try rebooting. I suspect it was just a one off due to a delay in some app or process your phone was dealing with at the time but let me know if problems persist.
[Wear OS Software and Hacking General] wollac11:
It shouldn't be too much different because the length is dependent on device boot time. However if you have a fast booting device or one which has only a few apps you could find the animation will show for about 2 seconds extra while it displays the last part. Nothing huge. This is due to the new boot animation structure which consists of three parts rather than two. The last part is not displayed until the device is pretty much ready as it is the middle section which loops not the last part as it is in most stock boot animations currently.

In that extra time the device will progress slightly further with startup so it will likely be more responsive when the boot animation ends (a lot of devices have not quite finished when the boot animation ends anyway). The actual time the device spending doing its boot-up tasks will be unaffected by a boot animation so it will just be a visual thing (you may see the animation for a slightly larger percentage of the boot).

You could change the boot animation to be more like the others by taking out either the middle loop and have the end bit looping or just loose the end bit altogether and this would save you those few seconds but it would no longer look and feel as nice and I wanted it to look the same as on Android Wear. I think that the change in behaviour might actually be a way of Google preventing that feeling of lag you get on some devices when the boot animation finishes and you try and use the device straight away before it is really ready. As well as the nice design style you get too obviously.

Hope that makes sense. :)
[Wear OS Software and Hacking General] scoobyjenkins:
Awesome, thanks! I use the 1080 one on my phone and the 1200 on my tablet, love it!

Tapatalked that shiznit.
[Wear OS Software and Hacking General] JovieBrett:
You've done an amazing job! Thanks a bunch dude!
[Wear OS Software and Hacking General] wollac11:
Thanks! Good to see you like it! :D
[Wear OS Software and Hacking General] KnightySU:
Hm, every time i use ur bootanimation, after rebooting i get the process com.android.systemui has stopped and the pin lock is gone. There is no lockscreen at all.

Gesendet von meinem Nexus 5 mit Tapatalk
[Wear OS Software and Hacking General] wollac11:
That's very weird. A boot animation does not contain code (just image frames and a text file defining the frame rate and loop structure) so by its nature a particular boot animation cannot actually cause this. This a bug in the ROM you are using (stock or otherwise) and should never happen. The cause is probably incorrect file permissions or another change unrelated to the content of the boot animation itself e.g. an app. Not that this should normally cause such behaviour.

Did you set the permissions to 644? If you did you can also try loading it from a different location to see if that helps either /system/media or /data/local (whichever you didn't use before). If problems persist and regardless of location and you are sure the permissions are correct try wiping your cache and dalvik cache.
[Wear OS Software and Hacking General] wollac11:
Poll added: Where should I go next?

Hi all! I have just added a poll with options for the most requested versions of this animation I should make. Place your votes to decide the order of priority.

Note that I will likely do each of these at some point it is just as case of the order I do them in!
[Wear OS Software and Hacking General] svnhvn:
Beautifully crafted sir. Thanks!!
[Wear OS Software and Hacking General] KnightySU:
I used data/local, permissions were set to 644. I'm on stock ROM rooted with xposed framework and GB.

Will try other location and wipe later and report.

Gesendet von meinem Nexus 5 mit Tapatalk
[Wear OS Software and Hacking General] wollac11:
Thanks! Glad you like it!
[Wear OS Software and Hacking General] KnightySU:
seems like this was the solution. the problem occured in the same way in /system/media. Now everything seems to work.
[Wear OS Software and Hacking General] wollac11:
Glad it is working now. Hope you like it!
[Wear OS Software and Hacking General] wollac11:
Quick update

Cheers once again for the kind comments guys. I have spent quite a bit of my time producing these as well as responding to people on here, Hangouts and Google Plus so I am glad it has been worth it. It is always nice seeing appreciation of your work and people gaining enjoyment out of it!

Anyway, I have already started work on the extended length versions as from the poll votes so far that appears to be the most popular new version request and so will likely be the first new set to come. These have just an extra second worth at the end for people who want to see more of the Android logo at the finish. Keep voting for your choice though!

Once I have done all three of those new versions mentioned in the poll I shall probably stop working on new versions of this boot animation as we are reaching the limits to things to explore. I will still try new packaging methods though such as the CM theme manager and as a flashable AROMA installer as I know many people have shown interest in these.

After I am done with all that I will move onto new projects but I may also publish the Linux BASH scripts and SVG files which I made in order to produce all these different animations, don't know if people are interested in that?

But yeah, I am happy with how these have turned out however there is only so much you can do with a boot animation and I think I have now done most of them with this one! Perhaps I can do something interesting with some of the other parts of Android Wear. We'll just have to wait and see...
[Wear OS Software and Hacking General] KnightySU:
One reboot later the lockscreen was gone again and there was no reboot option in the power menu. Something is wrong here in combination with gravity box i think.
[Wear OS Software and Hacking General] JovieBrett:
The Part2 images are not showing when my device boots up :/ it just shows the four colors flying around then the 'android' animation does not shows up :( Any workaround? my device is MDPI and used a bootanimation factory tool to resize the images of 480x480.
[Wear OS Software and Hacking General] wollac11:
That's strange. What device and which version of Android are you using? (needs to be 4.1+) Also what screen resolution does your device have? Note the pixel density doesn't matter just the resolution.

But for now try not using boot animation factory - instead try the closest resolution smaller than yours without modification / resizing. If you have a 7" MDPI device for example you'd have 1024x600 screen so then the closest would be qHD (960*540).

Obviously this won't quite fill your screen but if we have it working then I'll make you a version actually for your resolution from the SVGs without any bitmap scaling and run through my PNG optimisation stages so the quality and performance will be a lot better!

Doing this test just means that I know you are using a correctly made boot animation as I provide them and I can troubleshoot from there. It allows me to rule out any possible issue caused by modification.

If you have a resolution lower than 800*480 but have Android 4.1 or greater than just tell me and I'll make you one for your resolution straight away because using resolutions greater than yours as less passable than the other way around and you obviously won't be able to test as I have suggested.
[Wear OS Software and Hacking General] wollac11:
Hmm yes you've obviously got some app or Xposed module causing some issues. You'll have to experiment with different things to find out what the cause is. Hope you manage to find it!
[Wear OS Software and Hacking General] JovieBrett:
I actually used the 480x480 MDPI resolution of the bootanimation you provided for my MDPI 320x480 device then I resized it by using the boot animation factory tool (the pngs are not resized, desc.txt is the one changed by the tool). The bootanimation works great but the only thing is not working is the part2 is missing. Ive rechecked the loop on the desc.txt but nothing seems to be worried about (just the same number of loops the way on the bootanimation your provided). Thanks about that man!

EDIT

I'm using Xperia Mini which is MDPI 320x480, running CM11 4.4.3 :)
[Wear OS Software and Hacking General] wollac11:
New resolutions!

Just to let you all know I have now added versions for 480x320 and 1024x600! Enjoy! :D
[Wear OS Software and Hacking General] wollac11:
Okay, that is bizarre. Well anyway I have made a version with frames which are actually the correct size for your device as you will see has been added to the attachments in the OP. This is preferable to a change to the resolution in the desc.txt as it yields much better performance so I recommend you use that one.

Assuming you are still having issues, is it cutting off after the end of a complete loop of the second part (part1) or part way through? It sounds like it is failing to obey the boot animation loop structure but I am interested in if is deciding to cut off the instant it deems it is done or just ignoring the third part.
[Wear OS Software and Hacking General] JovieBrett:
Ok, will try that.

Whenever I see the bootanimation on my device, it is not cutting off, I think it's just ignoring the Part2 which is the 'Android' logo that is should to appear at.

Thanks alot dude!
[Wear OS Software and Hacking General] Gorillazz:
too short

Thanks for posting an awesome boot animation :) well, i'm facing a strange issue. The boot animations on my phone runs and ends before even showing up the android thing which is part 2 of the file. Just so you know, I'm on Mahdi rom 4.4.3 Dunno what to do. Please help.
[Wear OS Software and Hacking General] wollac11:
It is interesting, you are the second person to have this issue. It would seem a few devices are not obeying the loop structure. So far both reports (including yours) were from people on 4.4.3 custom ROMs which makes me think that there is some bug the the latest version of the source they were complied from (perhaps Cyanogemod as they both use Cyanogenmod source). I have checked the boot animations and their structure is fine so there really isn't any way I can fix this.

If I produce a version for pre 4.1 with a different structure it will loop in a different way and although won't be quite as nice it will likely avoid this issue so when I release those versions you could try using that. However, hopefully an update to your ROM will fix this as this boot animation follows a valid Android boot animation standard.
[Wear OS Software and Hacking General] Gorillazz:
Well, soon after trying your version, I tried another version and it did work but was for nexus 5 and was pixelated. here is the link, if that helps:

http://nexus5.wonderhowto.com/how-t...mation-your-nexus-5-see-for-yourself-0155411/
[Wear OS Software and Hacking General] scoobyjenkins:
I'm running CarbonRom (4.4.3) on my hlte but it's not all from cm sources and Omnirom 4.4.3 on my Pollux_Windy, both work fine with 1080 and 1200 resolution respectively.

Tapatalked that shiznit.
[Wear OS Software and Hacking General] JovieBrett:
Hi! I still don't see any updated 480x320 sizes? :/
[Wear OS Software and Hacking General] wollac11:
God that's horrible. They've taken the frames as they were from the G watch (280x280) and taken the desc.txt format from the stock animation and then stuck the third part (part2) into the first part (part0) and then looped the middle part. You end up with a totally out of order boot animation which does not behave like it should at all and is stretched up horrifically.

But yes, that uses the older format (pre 4.1) like I was saying and so it will show regardless of the bug your ROM appears to have. If I release a pre 4.1 version it will also have to do something different with the order or the way it loops because you cannot have a loop in the middle with the older format, only at the end. This will also show all the frames even on your current ROM.

There is no fault in the way this boot animation works. I suggest you contact your ROM developer and report a bug with it not correctly respecting the rules of boot animations using the "c part" in their animations. You can find out more about the differences here: http://muzso.hu/2012/07/15/understanding-boot-animations-in-android.

Edit: Just out of interest, what device are you using?
[Wear OS Software and Hacking General] wollac11:
Right at the bottom of the attachments. "v2-480x320-bootanimation.zip" ;)
[Wear OS Software and Hacking General] Gorillazz:
Oh, I'm sorry, I'm using a nexus 4 and yes you were spot on about the pre 4.1 thing! Thanks for taking time and helping me rather us :)
[Wear OS Software and Hacking General] scottspa74:
@OP, you must be one of the mist gracious,and kinds devs I've seen in Xda in all my years here . Great job. I used all my thanks on your last posts. Found you on g+
[Wear OS Software and Hacking General] wollac11:
Thanks! Means a lot. I'm glad you like it! :)
[Wear OS Software and Hacking General] wollac11:
Having looked into this further I don't think I will be making a version for CM theme manager any time too soon as unless I am missing something there doesn't seem to be a good way of supporting lots of different device resolutions for boot animations. Sorry about that!
[Wear OS Software and Hacking General] rjmohit:
No problem, thanks for trying.
[Wear OS Software and Hacking General] JovieBrett:
Just a report about the 320x480 v2 of bootanimation, it works perfectly now and smoother than before! Thanks alot man!
[Wear OS Software and Hacking General] wollac11:
Brilliant! Happy it's working for you now.
[Wear OS Software and Hacking General] wollac11:
No root? No problem!

Any of you who aren't rooted but would like to try this animation or other cool things that require root but normally find the proccess behind rooting a bit daunting may want to check out geohots new root app "Towelroot" which will root basically any Android device with one click.

You simply install the app, press a button and your device reboots rooted! It is that easy! No unlocking bootloaders etc. Once it is done you download an app like SuperSU, let it update the SU binary and enjoy using root!

You can find out more over at its XDA thread here: http://xdaforums.com/showthread.php?t=2783157

Hope this is helpful to some of you! :D
[Wear OS Software and Hacking General] Onecton:
First of all thank you OP! :D

Second ->

I don't know if anyone of you had run into the same funky problem. I pushed the bootanimation into system/media with the correct permissions.

On bootup i just get a greyish rectangle the switched to white ... aut 1080x1080 probably....

really strange :p

Im running 4.4.3 PurityRom on a Nexus 5

just wanted to know if anyone has the same probs ... maybe as some suggested maybe its a problem with 4.4.3?
[Wear OS Software and Hacking General] wollac11:
No problem, glad you like it! I can't say I've seen that issue on any of the devices I've seen this running on most of which ran 4.4.3 including the Nexus 5. Perhaps something ROM specific?

I don't want to sound like I'm passing off the possibility of errors on my part, I make mistakes just like anyone else - the colour issues on V1 were an example of a flaw I created. However, there is actually very little to "go wrong" with a boot animation. They either work or they don't and if they don't look right on one device or something weird happens then generally that's device or configuration specific. They don't contain any code (which could have bugs) like in an app or a ROM.

Hope that helps!
[Wear OS Software and Hacking General] IgnorCZ:
Hi :)

.. I am on Purity 4.4.3 with N4 and I pushed this bootanimation into system/media .... I have not such problem .. I know that I have different phone but I have almost same rom .. somebody with N5 must prove if it is working without problem for them .. I want to say that it is not rom problem ... I think :)
[Wear OS Software and Hacking General] Onecton:
Sounds the same for me. I mean the bootanimation is just an epic mass of picture files. I don't know what is wrong with my handset and why it does that. I just wanted you to know. I don't expect that you digg deeper into it :)

Maybe I find ways to workaround that bug. :D

Thanks mate, so I guess its the classic human / device interface problem. Aka I'm to stupid for that :D maybe I find the bug tonight.

Since you ruled out the issue with the ROM you saved me a huge truckload of time reflashing stuff :) thanks mate :):thumbup:
[Wear OS Software and Hacking General] wollac11:
Extended versions now up!

Versions with an extra second added to the end where the Android logo shows have been added as per request and the results of the poll. These start with "long-". All resolutions other than 1440p and 1024x600 have these longer versions added. Those were omitted as they are the two least popular of the normal versions and I had to fit under the 20 maximum attachment limit. I can add those two at some point if required by uploading them all to a separate file host but hopefully this will do for now. I have also now removed the v1 versions.

Enjoy! :D
[Wear OS Software and Hacking General] JovieBrett:
Hi [MENTION=2881708]wollac11[/MENTION] can you make one for 240x240? (LDPI size)? hehe
[Wear OS Software and Hacking General] wollac11:
Sure, here you go! (see attached) What device are you going to run this on out of interest?
[Wear OS Software and Hacking General] JovieBrett:
Sweeeet! thank you so much dude!

I'll push this on my friend's Galaxy Y :) (removing her fugly samsung bootanim lol) hope the framerate will be good at running on that device :D
[Wear OS Software and Hacking General] wollac11:
No problem! Should be pretty smooth given how low res it is! That's actually less than the LG G Watch! :laugh:
[Wear OS Software and Hacking General] Makuuu1:
Working great on Xperia J.
[Wear OS Software and Hacking General] wollac11:
Fantastic! Glad to hear it! :)
[Wear OS Software and Hacking General] teydagrey:
is 800x480 and 480x800 the same? no right?
[Wear OS Software and Hacking General] wollac11:
Yes they are the same resolution. Just one is portrait and one is landscape. You will often see them quoted both ways interchangeably since mobile devices are rotatable.

However, a boot animation takes your device's default orientation (usually large tablets and portrait for smaller tables and phones). This means that it can be important when it comes to boot animations.

The actual area of this particular boot animation is square so it takes the resolution of smallest side in order to fit and it therefore doesn't matter and will work with either orientation.

For example the frame resolution for 480x800 is actually 480x480 and the top and bottom are left black by your device (or left and right if it is an landscape device). I have just named them according to device resolution rather than frame resolution because it is easier for people to identify the correct one.
[Wear OS Software and Hacking General] teydagrey:
Thanks ^^ , its now working great. :)
[Wear OS Software and Hacking General] wollac11:
Awesome!
[Wear OS Software and Hacking General] s.tanbin:
sir is it work on Samsungs galaxy ace running cm9.???

my resolution 320×480
[Wear OS Software and Hacking General] JohnnyGT:
Thanks mate I like it funky boot now with Temasek's v100 CM11 4.4.3 on Galaxy S3 :p
[Wear OS Software and Hacking General] wollac11:
Yes it should work just fine. Just use the one which matches that resolution ("v2-480x320-bootanimation.zip") from the attachments in the OP.
[Wear OS Software and Hacking General] wollac11:
Great! Glad it you like it!
[Wear OS Software and Hacking General] s.tanbin:
sry to say sir it didn't work :(

i think i required jpg rather then png...

but magnificent work..
[Wear OS Software and Hacking General] wollac11:
Pretty much all Android derives well work with either format. Did you rename the file to just "bootanimation.zip" and remember to set the file permissions to 644?

Edit: just realised you said CM9 which is ICS and won't work correctly anyway (needs 4.1+), sorry about that! Is there a CM10 or higher ROM you could use?
[Wear OS Software and Hacking General] wollac11:
Based on the poll I have already made the extended versions (as you have seen) however the other two options received very few votes. I shall therefore work on packaging methods such as flashable zips first. Once that is done I shall return to making versions for older versions of Android.

For now I am leaving versions with lossy compression as there doesn't seem to be much demand for this. Generally the current versions are pretty smooth and as the weakest devices usually have lower resolution displays, even pretty old hardware seems to have good performance. This may be reviewed in the future if there is enough interest but for the for the time being I am discarding the idea of making versions which sacrifice quality for improved framerates.
[Wear OS Software and Hacking General] JovieBrett:
Just ot :) what tool are you using to resize all the pngs of the bootanimation? :)
[Wear OS Software and Hacking General] wollac11:
I'm not resizing the PNGs as that would damage image quality.

I'm scaling the SVGs I made and exporting to PNG for each frame. I have a Linux/Unix BASH script I wrote which does the whole process from the SVGs to full bootanimation.zip for any resolution to speed up the process.

This script takes each SVG file and creates a PNG for each in the desired resolution, it then runs each through pngquant and then uploads each of the new PNGs to Yahoo's Smush.it where they the even more optimised and then downloads the new PNG frames back. It then runs all these frames through optipng for a final optimisation process, writes the desc.txt and then it packs it all up in an uncompressed zip with the correct file name and folder structure.

The program used by the script to create the scaled PNGs from the SVGs is actually Inkscape (using its command line interface).

It's a pretty neat procedure I am proud of. The only thing that isn't done as part of the script was the tracing to make the SVGs from the original PNG frames which I had to do beforehand.