Can you please try to make 600 x 400 image dimension for my device.... thanks in advance
Sure, here you go! (see attached)
[MOD] Android Wear Boot Animation For Other Devices [ROOT] [Android 4.1+]
- Thread starter wollac11
- Start date
Sure, here you go! (see attached)
You can already find one for that resolution in attachments of the OP named "v2-1280x800-bootanimation.zip".
The boot animation frames are actually square and take the resolution of the shortest side so that they fit. This means that it does not matter which default orientation your device has and so 800x1280 is the same as 1280x800.
Sent from my Nexus 4 using Tapatalk
T-Mobile LG G3
Hi I was just wondering if anyone else is experiencing this problem. My G3 on starts at the the end of the animation so its just a bunch of orbs moving around. I don't get to see the first part of this amazing boot animation. Great work by the way. I tested this out on my Mako and it work perfectly. I just wanted to know is this a known issue? How can I fix it? Thank you very much for any input.
Hi I was just wondering if anyone else is experiencing this problem. My G3 on starts at the the end of the animation so its just a bunch of orbs moving around. I don't get to see the first part of this amazing boot animation. Great work by the way. I tested this out on my Mako and it work perfectly. I just wanted to know is this a known issue? How can I fix it? Thank you very much for any input.
Hi, this means that the ROM on your G3 (presumably LG stock ROM) doesn't seem to fully support the newer format of boot animations which were introduced in Jelly Bean in for some reason. The first part of the animation is dependent on the new part type and won't load otherwise. I am sorry but at this time there is not much I can do.
Right, I know a lot of you are waiting for me to post this after seeing my videos, social media posts and preview gifs!
Many of you will likely have seen the awesome new Android Wear boot animation as leaked in the LG G Watch system dump. Well now I have successfully made versions for other devices as well!
Initially I made one for the MotoACTV smartwatch (http://forum.xda-developers.com/showthread.php?p=53150797) because it also has a small display and the frames in the system dump are obviously very low resolution for the small screen of the LG G Watch and so are not suitable for phones and tablets. The MotoACTV has an even smaller display and downsizing is not an issue for quality.
However, I have managed to get around this problem. I traced and vectorised each frame to produce a set of scalable SVGs from which I was able to create the high-res png frames needed to make boot animations to suit different devices. There is no limit to the resolution now obviously because I have vector copies of each frame so support for any device is possible. I have also thoroughly optimised the final frames to bring down their file size as much as possible (losslessly) which ensures they run really smoothly (this makes a big difference on high res devices!).
For the MotoACTV I had to change the loop format too because Android pre 4.1 doesn't support the new "c loops" which are required to get the same behaviour as on the LG G Watch (MotoACTV is Gingerbread). On these new ones I had to use a different desc.txt structure to Android Wear for compatibility purposes but have used the c loops and so this actually loops exactly as it would on Android Wear.
It is possible to make animations for devices with earlier than 4.1 too but I will have to change the way it loops slightly. There are also a few devices (like the MotoACTV) which prefer jpgs rather than pngs. I can quickly produce jpg versions if required too. I am willing to take requests for devices people would like an animation for and will try and do them in order of demand but I make no promises on how long the turn around will be.
Below if a video of it running on my Nexus 4 (note: animations are quite a bit smoother than this now and the small amounts of weird jitter were caused by YouTube's video editor) you can also see a preview in post #4:
https://www.youtube.com/watch?v=3jior6pwamg
Update (9/6/14): New v2 versions are up! These are even smaller in file size (read: better performance) and contain some fixes plus two new resolutions!. See post #45 for more details on the update. We now have Android 4.1+ bootanimations which support most common device resolutions: 800x480, 960x640 1280x720, 1280x768, 1280x800, 1920x1080, 1920x1200, 2560x1440 and 2560x1600.
Note: as @vedantgp thankfully reminded me you cannot use these standard type Android boot animations on Touchwiz ROMs because Samsung uses their own proprietary format. There are mods to remedy this though, although I have not tested them. See here: http://www.xda-developers.com/android/add-custom-boot-animation-to-any-samsung-rom/
Instructions
Firstly this will almost always need root. Secondly, these are not flashable zips and you cannot flash these in recovery! This is what you do:
Picking The Correct Animation For Your Device
If you know your device resolution and you see it there then great - grab it move onto adding it to your device. If you don't know the resolution a quick Google of should let you know. You should bare in mind that the actual frames are square so the boot animations are supported based on their smallest dimension (lowest pixel count). This means that whether you have a landscape device (10" tablet) or portrait (most 7" and below) it does not make a difference, the one for your resolution will be fine.
If you find there is no zip matching your device resolution then fear not - you are not out of luck! If you have a different resolution than any listed you can pick the one with largest width (the smallest dimension) that is less than yours (or the same if it exists) and it will work just fine. The only difference is that it will not fill the complete width of your screen. For example: if you somehow had a 1340x950 device then you'd use 1280x800 one as 800px is the closest available smaller resolution of the shortest dimension (width) to your device. You would then just have a 150px gap (75 each side) between the furthest reach of the animation and the edge of your display which would not look too bad as the background is black and most of the screen width is still used. Hope that makes sense. You cannot use one with a resolution greater than your device or it will be cut off.
Manual Method
Download the attachment with the boot animation suited to your device. Rename the zip to bootanimation.zip and push to either /data/local or /system/media making sure the file permissions are set to 644. This process can be done with a file manager or using ADB. If opting for a file manager I do not suggest you use ES File Explorer has it lacks the required permissions options. CM File manager, Root Explorer or Solid Explorer (my favourite) all will work well. If pushing to /data/local the animation will not be wiped when updating your ROM but will be lost with a data wipe / factory reset. For system/media the apposite is true. /system/media is the default location for the boot animation so if using that I suggest you backup your existing one first. My recommendation though is that you use /data/local.
Below is an example of what the permissions should look like for those having difficulty. This is an example from Solid Explorer but others should be similar!
New: for those who find written instructions hard to follow Alexander Ruiz has made a great video of these manual instructions on YouTube: https://www.youtube.com/watch?v=tJ-XyZLGCBc
Simple Method
As helpfully pointed out by @bradhoschar you can actually preview and install boot animations with ROM Toolbox! You can grab the free version here and the pro version here. This might be easier for some users!
Future Plans
I intend to create a flashable zip with Aroma installer at some point in the future so you can flash easily to many different devices with options for different Android versions, device resolution and preferred installation. I will need to make it for a few different device specifications first before this becomes worthwhile.
Disclaimer
As per usual, while this almost certainly not going to cause any damage to your device, if it makes it your phone explode, causes hair loss, summons the dead or tears the universe apart, I am not responsible!
Enjoy!
(and please consider checking out my new Android blog: www.littlegreendude.com - thanks!)
Hi....
In simple words Great Job Done !:good:
Simple thread,Excellent work and works smooth on my GT-N7100 Note 2 like a feather fly in the air !
Hope to see more great work from you soon and a simple query....I used long 1280*720 file , But what is the difference between V2 1280*720 and the one I already used Long 1280*720 ?
Cheers Mate...
Hi....
In simple words Great Job Done !:good:
Simple thread,Excellent work and works smooth on my GT-N7100 Note 2 like a feather fly in the air !
Hope to see more great work from you soon and a simple query....I used long 1280*720 file , But what is the difference between V2 1280*720 and the one I already used Long 1280*720 ?
Cheers Mate...
Firstly, thank you very much, I am glad you like the animation.
The V2 versions of both the long and regular variety have reduced filesize, increased smoothness and most importantly a fix to the colours (there was a glitch in the original versions where some of the dots would change colour for a couple of frames here and there in the middle of the animation).
The difference between long and the regular versions is just that the Android logo at the end is displayed for slightly extended period in the long version.
Hope that clears everything up.
Problems.
For some reason changing to this boot animation causes my phone to get into a boot loop. Before you ask, Yes my Nexus 5 is rooted, I used Root Browser to place file and set permissions (tried both locations), the animation loads fine with no errors, just goes into boot loop. I fixed it in recovery, no harm done, I just wish I could use this very awesome animation since I also own the LG G Watch. My goal is to make my G Watch and Nexus 5 a matched pair.
For some reason changing to this boot animation causes my phone to get into a boot loop. Before you ask, Yes my Nexus 5 is rooted, I used Root Browser to place file and set permissions (tried both locations), the animation loads fine with no errors, just goes into boot loop. I fixed it in recovery, no harm done, I just wish I could use this very awesome animation since I also own the LG G Watch. My goal is to make my G Watch and Nexus 5 a matched pair.
On Galaxy Nexus this animation stutters every five seconds and the device boots much slower than on the stock one.
Are the original SVG files posted? Would like a copy - thanks.
Has anyone made an android animation (Java framework) for this?
Has anyone made an android animation (Java framework) for this?
Sorry I have taken a while to get back to you. I assume you have fixed it by now but if not let me know. Anyhow, that is a strange issue as a boot animation should never actually effect a device's ability to boot. If permissions are incorrect or the device cannot read / understand the animation it should still boot but the boot animation will just not be displayed. If you are having an actual bootloop it is not being caused directly by the bootanimation but a bug in the ROM you are using or some action that was taken when trying to add the boot animation. If you used an app or tool to install it then perhaps that app has done something it shouldn't.
I do think I ever got around to uploading the SVGs but didn't have much demand for them. I can certainly dig them out in a bit and upload them for those that want them though
As for making an Android animation in Java, I do not believe anyone has done this although for this particular animation I am not sure why you would?
The animation should in fact not be a whole lot longer (only a second or so) because the majority of the animation is just a loop while the device waits for boot to complete. Only the very last section is displayed once the system has reported as ready. Most of the differences will be down to perception rather than an actual difference although if it is stuttering then I guess that delay could be extended as it would take longer to complete.
If the animation stutters then the device is struggling to load and draw each frame fast enough. The solution for this is to use a lower resolution boot animation. For the Galaxy Nexus if it is struggling with the 720p version try the 960x540 version. This should still look just fine it just will fill a smaller proportion of the screen. You should find that this is smoother as the lower resolution is less taxing. If it still is not smooth you could try an even lower resolution such as 800x480. Hope that helps.
Sorry it has taken long long for me to reply. Boot animations should not be able to effect the boot process of the device. If no other changes are made when you add it to the device should still boot. If something was wrong with your device reading the animation then it should simply not display but boot would continue regardless.
I therefore think it is one of two things. Either you are using a ROM which has a bug which prevents the system loading when using custom bootanimations (unlikely but I did see one for the Nexus One which did once) or perhaps you simply are not waiting long enough? Depending on the boot animation you has before, the repetitive nature of the main section of this bootanimation (the spinning circles) maybe just making it seem like more time is passing than some which are less repetitive. Did you try waiting for a good length of time just to make sure it was actually boot-looping?
Fixed
It was wierd. I used boot animations by jrummy. I have never had problems with it before until installing this boot animation. All I could do was get into CWM recovery and restore from a backup. I am now using the boot animation from pac rom and it is working fine.
I had considered both theories. 1. I am using the stock ROM from Google for the Nexus 5 for 4.4.4, it is just rooted, any modification I do to it is through Xposed modules, it may be the case that one of the modules might be causing the error. 2. I let it sit while charging (wall plug, not into computer) for a good 30 minutes, the boot animation looped the whole time. Luckily in recovery mode I was able to just remove the boot animation and replace it with the original. At this point I have pretty much given up on it, I am not going to remove features that I use just for a pretty boot screen, it would have been a nice touch though. Thank you for the reply, I just wished your ideas were something I hadn't already tried.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
61Right, I know a lot of you are waiting for me to post this after seeing my videos, social media posts and preview gifs!
Many of you will likely have seen the awesome new Android Wear boot animation as leaked in the LG G Watch system dump. Well now I have successfully made versions for other devices as well!
Initially I made one for the MotoACTV smartwatch (http://forum.xda-developers.com/showthread.php?p=53150797) because it also has a small display and the frames in the system dump are obviously very low resolution for the small screen of the LG G Watch and so are not suitable for phones and tablets. The MotoACTV has an even smaller display and downsizing is not an issue for quality.
However, I have managed to get around this problem. I traced and vectorised each frame to produce a set of scalable SVGs from which I was able to create the high-res png frames needed to make boot animations to suit different devices. There is no limit to the resolution now obviously because I have vector copies of each frame so support for any device is possible. I have also thoroughly optimised the final frames to bring down their file size as much as possible (losslessly) which ensures they run really smoothly (this makes a big difference on high res devices!).
For the MotoACTV I had to change the loop format too because Android pre 4.1 doesn't support the new "c loops" which are required to get the same behaviour as on the LG G Watch (MotoACTV is Gingerbread). On these new ones I had to use a different desc.txt structure to Android Wear for compatibility purposes but have used the c loops and so this actually loops exactly as it would on Android Wear.
It is possible to make animations for devices with earlier than 4.1 too but I will have to change the way it loops slightly. There are also a few devices (like the MotoACTV) which prefer jpgs rather than pngs. I can quickly produce jpg versions if required too. I am willing to take requests for devices people would like an animation for and will try and do them in order of demand but I make no promises on how long the turn around will be.
Below if a video of it running on my Nexus 4 (note: animations are quite a bit smoother than this now and the small amounts of weird jitter were caused by YouTube's video editor) you can also see a preview in post #4:
https://www.youtube.com/watch?v=3jior6pwamg
Update (9/6/14): New v2 versions are up! These are even smaller in file size (read: better performance) and contain some fixes plus two new resolutions!. See post #45 for more details on the update. We now have Android 4.1+ bootanimations which support most common device resolutions: 800x480, 960x640 1280x720, 1280x768, 1280x800, 1920x1080, 1920x1200, 2560x1440 and 2560x1600.
Note: as @vedantgp thankfully reminded me you cannot use these standard type Android boot animations on Touchwiz ROMs because Samsung uses their own proprietary format. There are mods to remedy this though, although I have not tested them. See here: http://www.xda-developers.com/android/add-custom-boot-animation-to-any-samsung-rom/
Instructions
Firstly this will almost always need root. Secondly, these are not flashable zips and you cannot flash these in recovery! This is what you do:
Picking The Correct Animation For Your Device
If you know your device resolution and you see it there then great - grab it move onto adding it to your device. If you don't know the resolution a quick Google of should let you know. You should bare in mind that the actual frames are square so the boot animations are supported based on their smallest dimension (lowest pixel count). This means that whether you have a landscape device (10" tablet) or portrait (most 7" and below) it does not make a difference, the one for your resolution will be fine.
If you find there is no zip matching your device resolution then fear not - you are not out of luck! If you have a different resolution than any listed you can pick the one with largest width (the smallest dimension) that is less than yours (or the same if it exists) and it will work just fine. The only difference is that it will not fill the complete width of your screen. For example: if you somehow had a 1340x950 device then you'd use 1280x800 one as 800px is the closest available smaller resolution of the shortest dimension (width) to your device. You would then just have a 150px gap (75 each side) between the furthest reach of the animation and the edge of your display which would not look too bad as the background is black and most of the screen width is still used. Hope that makes sense. You cannot use one with a resolution greater than your device or it will be cut off.
Manual Method
Download the attachment with the boot animation suited to your device. Rename the zip to bootanimation.zip and push to either /data/local or /system/media making sure the file permissions are set to 644. This process can be done with a file manager or using ADB. If opting for a file manager I do not suggest you use ES File Explorer has it lacks the required permissions options. CM File manager, Root Explorer or Solid Explorer (my favourite) all will work well. If pushing to /data/local the animation will not be wiped when updating your ROM but will be lost with a data wipe / factory reset. For system/media the apposite is true. /system/media is the default location for the boot animation so if using that I suggest you backup your existing one first. My recommendation though is that you use /data/local.
Below is an example of what the permissions should look like for those having difficulty. This is an example from Solid Explorer but others should be similar!
New: for those who find written instructions hard to follow Alexander Ruiz has made a great video of these manual instructions on YouTube: https://www.youtube.com/watch?v=tJ-XyZLGCBc
Simple Method
As helpfully pointed out by @bradhoschar you can actually preview and install boot animations with ROM Toolbox! You can grab the free version here and the pro version here. This might be easier for some users!
Future Plans
I intend to create a flashable zip with Aroma installer at some point in the future so you can flash easily to many different devices with options for different Android versions, device resolution and preferred installation. I will need to make it for a few different device specifications first before this becomes worthwhile.
Disclaimer
As per usual, while this almost certainly not going to cause any damage to your device, if it makes it your phone explode, causes hair loss, summons the dead or tears the universe apart, I am not responsible!
Enjoy!
(and please consider checking out my new Android blog: www.littlegreendude.com - thanks!)7Very soon I shall be renaming all the zips by resolution instead of some by device (it is clearer and neater as several devices are suited to each zip) and adding support the following resolutions: 1080p (1920x1080), 1280x800, 800x480 and 2560x1600 in addition to the current 1920x1200, 1280*768 and 720p (1280x768). I feel this should cover most devices for now. All of these will be for Android 4.1+. I shall later add some zips for lower Android versions for older devices and once I have done that I shall then also combine them into a single AROMA Installer for ease.
Also here is a preview gif so you can see clearly what it looks like (updated preview - no longer huge, fixed colour issues and increased gif speed/framerate):
6New V2 Animations Are Up!
Hi all, I have just added the new version 2 boot animations! These not only contain the previously mentioned colour fix (where certain dots were the wrong colour in a few frames) but are also even smaller in file size (and therefore smoother / faster!) Oh and as a bonus I have added a couple of new resolutions to the mix: qHD (960x440) for devices such as the Moto E, S4 Mini and S4 Zoom (plus loads of Chinese devices) and also QHD (2560x1440) for devices such as the Oppo Find 7, OnePlus One and LG G3!
For these new versions I remade all the SVGs for all the frames again, making sure the tracing process was even more accurate and the colour pallet was opened wider to avoid incorrect colours. The initial downside of this was that the first boot-animation I made from the new SVGs was larger in file size that the previous ones due to the extra colour and detail in the frames. So I decided I would try and push the limits further in terms of reducing the file size of the frames through optimisation without any difference in image quality.
Well guess what!? I now have added a whole new optimisation stage to my boot animation creation process which let's me reduce the PNG colour pallet back down on a frame by frame basis so that only the used colours on a given frame are included. This dynamic colour pallet size along with some other additional tweaks in this stage has taken down the size my loads yet again! Not just counteracting the increase in size from the extra detail provided by the new SVGs they were made from but also going way beyond so they are actually much smaller than before!
As an example, the 2560x1600 animation is now smaller than the old 1080p one and less than 50% what it was before. Of course, the difference between one of my latest optimised copies and a standard boot animation with none of this optimisation work on the frames would be even bigger as even before I was optimising quite a lot! Had I just packaged the pngs as exported from the SVGs without any of of the optimisation then the 2560x1600 bootanimation.zip would be 10.1MB - that's more than 320% of the current size (or 225% larger if you prefer!). This difference is massive and it would be no where near as smooth as they are as a result! This is true for all the resolutions not just this one (although the exact savings vary a little).
If you compare the new versions to the official G Watch one you'll see that the original was 1.1MB for 280x280. I have achieved smaller files sizes than that for the latest versions of both 800x480 and 960x540 boot animations with the identical number of frames and in spite of having a much greater resolution. It is obviously more time and effort to produce these optimised frames but I think you can see from the file size difference it really is worth it. I have found for even the slightest reduction in file size you can gain a lot in smoothness.
For now I left the old versions up too in case there is any issues with the new ones (I really don't think there would be though) but also so you can see the size differences for each. Eventually I will pull the old downloads to make things cleaner. I could probably also do with a tidy of the OP as well! One final thing to note is these are still 4.1+.
Anyway that's enough rambling from me. Enjoy!4Extended 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!3
