[MOD] Android Wear Boot Animation For Other Devices [ROOT] [Android 4.1+]

What would you like next?

  • Versions for older versions of Android (pre 4.1)

    Votes: 3 16.7%

  • Versions with lossy compression for slower devices

    Votes: 1 5.6%

  • Versions with Android logo displayed for longer

    Votes: 14 77.8%
  • Total voters
    18
Search This thread
By:
Advanced…
P

pcwalker

Member
Nov 13, 2014
17
0
lagging

hello, i appreciate your work on this bootanimation but it lags on my phone.

Device: Alcatel OT Idol 6030x; Stock ROM; Rooted; JB 4.1.1
Resolution used: 960x540

I've read from your previous post to use a lower resolution. I just want to verify if it also applies to my problem. Thanks!
 
L

Lovatastic

Senior Member
Nov 23, 2014
111
23
Manchester
Google Pixel 3
Doesn't work on Moto G 4G

Downloaded the 1280x720 boot animation and it fails on Moto G 4G. When the boot screen shows it's just blank and then loads the lock screen. Tried installing it manually and using ROM Toolbox.
I love this animation and I can't have it :(

[Edit:] Turns out that it seems to be this animation that doesn't work as I downloaded one from ROM Toolbox and it booted fine showing the animation. Maybe as Motorola uses a video to play the boot animation may be causing the problem.
 

Attachments

  • Screenshot_2014-11-24-03-52-03.png
    Screenshot_2014-11-24-03-52-03.png
    199.2 KB · Views: 472
Last edited:
wollac11

wollac11

Senior Member
Aug 25, 2010
264
213
Cambridge
www.littlegreendude.com
Lovatastic said:
Downloaded the 1280x720 boot animation and it fails on Moto G 4G. When the boot screen shows it's just blank and then loads the lock screen. Tried installing it manually and using ROM Toolbox.
I love this animation and I can't have it :(

[Edit:] Turns out that it seems to be this animation that doesn't work as I downloaded one from ROM Toolbox and it booted fine showing the animation. Maybe as Motorola uses a video to play the boot animation may be causing the problem.
Click to expand...
Click to collapse

You were bang on with your edited point. Motorola uses a modified bootanimation binary to play MP4's instead of the default animation format. That is actually quite a cool feature and that binary has actually been posted on XDA for people to use on other devices. I could try and make an MP4 version for the you and other Moto G and Moto X users if I get time or otherwise you would need to replace your bootanimation binary (in /system/bin) with one from stock Android of the same Android version and then this format of bootanimation will work.
 
wollac11

wollac11

Senior Member
Aug 25, 2010
264
213
Cambridge
www.littlegreendude.com
pcwalker said:
hello, i appreciate your work on this bootanimation but it lags on my phone.

Device: Alcatel OT Idol 6030x; Stock ROM; Rooted; JB 4.1.1
Resolution used: 960x540

I've read from your previous post to use a lower resolution. I just want to verify if it also applies to my problem. Thanks!
Click to expand...
Click to collapse

Lag on the animation just means your device is struggling to play this animation and there is no a whole lot I can do to fix it. The lower resolution you use the less power is needed, which is why trying lower resolution versions can help. Are you saying that the lower resolution fixed the lag on your device or that it still was not smooth?

The animations have already been optimised very thoroughly frame by frame to allow them to be as smooth as possible so if your device still lags with a lower resolution then the device is just not very powerful and there is not a whole lot I can do, I'm sorry.
 
wollac11

wollac11

Senior Member
Aug 25, 2010
264
213
Cambridge
www.littlegreendude.com
Persnoody said:
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.
Click to expand...
Click to collapse

Hmm that is very odd. I personally know other people using this animation on Nexus 5's running stock 4.4.4 with no issues and really all bootanimations should be largely the same and have no effect on the boot process so I have no idea what is happening on your device. I can't even think how most Xposed modules should be able to effect this unless you had something which specifically related to bootanimations or something like that. Xposed modules don't usually effect the boot process either really.

My final idea is that perhaps your filemanager is doing something funky. I have just made a flashable zip for the 1080p version to install the bootanimation from recovery. Give it a shot and let me know if that works for you. Note that it will replace the animation in /system/media so have an appropriate backup of your current one in case you wish to revert. Also if you have any bootanimation in /data/local currently it will override whatever is in /system/media so you might need to remove the bootanimation from there if there is one.
 

Attachments

  • v2-1920x1080-bootanimation-flashable.zip
    1.6 MB · Views: 49
L

Lovatastic

Senior Member
Nov 23, 2014
111
23
Manchester
Google Pixel 3
Yeah I thought so, I extracted the images and added them all to Movie Maker (simple I know) to make them into a little movie and zipped it using winrar, but yet it still booted with a black screen

If you could make a working video from the images that would be fantastic, it seems Motorola run close to stock android very different compared to Google's versom of stock android, very strange.

Sent from my XT1039 using XDA Free mobile app
 
M

MrFrinkles

Senior Member
Jun 20, 2014
98
16
can you please add a qmg file?

please add a qmg zip file that i can flash in samsung galaxy s duos because this rom only supports qmg bootanimations...
:):):)
 
M

misterandroid

New member
Dec 5, 2014
1
0
KUKU VPN+ Opinion

KUKU VPN+ [provides you better stability and premimum connection with its unique feature on web-compression which allows you to save up to 70% on your data plan without compromissing on security. What is your opinion?
 
G

grtgbln

Member
May 30, 2014
24
2
Denver
Huawei Nexus 6P
Essential Phone
Verizon HTC One M8 (5.0.1)

Has anyone tested this on a Verizon (not sure if it matters) HTC One M8? Running custom 5.0.1 ROM based on the GPe update that came out last weekend. I have a Moto 360, and love the boot animation. Anyone know if it works, or has the capacity to work, in which case I'll test it and get back to you with the results? Just don't want to screw up my phone.
 
wollac11

wollac11

Senior Member
Aug 25, 2010
264
213
Cambridge
www.littlegreendude.com
grtgbln said:
Has anyone tested this on a Verizon (not sure if it matters) HTC One M8? Running custom 5.0.1 ROM based on the GPe update that came out last weekend. I have a Moto 360, and love the boot animation. Anyone know if it works, or has the capacity to work, in which case I'll test it and get back to you with the results? Just don't want to screw up my phone.
Click to expand...
Click to collapse

That should work just fine. Boot animations don't really have the ability to mess up your device anyway since they are purely aesthetic. If it can't load it for some reason it will do one of 3 things during boot:
1. Load the stock boot animation from /system/media (assuming you placed this one in /data/local)
2. Display the core Android boot animation (the old Android logo with the shine effect)
3. Display a black screen

In any one of these scenarios the boot process going on in the background will be unaffected. Also it is very simple to reverse since you can just delete the booanimation.zip from /data/local or if you put it in /system/media then you can replace it with the backup of the stock bootanimation.zip.
 
G

grtgbln

Member
May 30, 2014
24
2
Denver
Huawei Nexus 6P
Essential Phone
wollac11 said:
That should work just fine. Boot animations don't really have the ability to mess up your device anyway since they are purely aesthetic. If it can't load it for some reason it will do one of 3 things during boot:
1. Load the stock boot animation from /system/media (assuming you placed this one in /data/local)
2. Display the core Android boot animation (the old Android logo with the shine effect)
3. Display a black screen

In any one of these scenarios the boot process going on in the background will be unaffected. Also it is very simple to reverse since you can just delete the booanimation.zip from /data/local or if you put it in /system/media then you can replace it with the backup of the stock bootanimation.zip.
Click to expand...
Click to collapse

Long v2 1920x1080 (my screen resolution)

Used ROM Toolbox - Boot Animations to install it, first time took a long time booting, first circle part was fast and smooth, rest was pretty smooth, didn't seem to lag, did hang up twice (think the loop started again), took I'd say about three minutes, but did eventually boot up. Popped up with notification about System process not responding, screen flashed a few times. Lost connection/went roaming, warning again. Then no issues.
Rebooted
Second time was perhaps a little faster, but still at least two minutes, hung up once (again, think loop started again), same system process not responding immediately when phone turns on. Warning twice. (Not sure if buggy wifi result of processes restarting. After about two minutes, everything seemed working (wifi went from great to no connection, but I know the 5.0.1 ROM I'm running still has the Lollipop wifi bug)).
Rebooted
Again, about three, maybe even four minutes booting, wasn't actively watching so not sure if hung up, system process not responding at beginning, screen flashed (think the UI had flash to reset). No further issues.

Anyway, the boot animation is causing immediate process failure as the phone turns on, but really nothing after that.

However, that might be your answer as to why people are getting stuck in boot loops. The animation is affecting the initial system processes.

I might keep it, I might now. It looks good, but takes a while, and the system processes warning, though it doesn't seem to affect the overall usage of my phone, would get annoying, and shouldn't be happening in the first place.

---------

UPDATE:
Used ROM Toolbox to re-install original animation, took about half the time (read: normal boot up time), no system process error, though screen did flash after about thirty seconds, data switched to roaming, then switched back.
Rebooted.
Same quicker time, no process issue, slightly long to connect to Verizon network, screen did flash (only apps, not the whole screen, but I think that's the ROM). Anyway, original boot animation not messing up.

So your animation is doing something to mess with the system processes.
 
Last edited:
wollac11

wollac11

Senior Member
Aug 25, 2010
264
213
Cambridge
www.littlegreendude.com
grtgbln said:
Long v2 1920x1080 (my screen resolution)

Used ROM Toolbox - Boot Animations to install it, first time took a long time booting, first circle part was fast and smooth, rest was pretty smooth, didn't seem to lag, did hang up twice (think the loop started again), took I'd say about three minutes, but did eventually boot up. Popped up with notification about System process not responding, screen flashed a few times. Lost connection/went roaming, warning again. Then no issues.
Rebooted
Second time was perhaps a little faster, but still at least two minutes, hung up once (again, think loop started again), same system process not responding immediately when phone turns on. Warning twice. (Not sure if buggy wifi result of processes restarting. After about two minutes, everything seemed working (wifi went from great to no connection, but I know the 5.0.1 ROM I'm running still has the Lollipop wifi bug)).
Rebooted
Again, about three, maybe even four minutes booting, wasn't actively watching so not sure if hung up, system process not responding at beginning, screen flashed (think the UI had flash to reset). No further issues.

Anyway, the boot animation is causing immediate process failure as the phone turns on, but really nothing after that.

However, that might be your answer as to why people are getting stuck in boot loops. The animation is affecting the initial system processes.

I might keep it, I might now. It looks good, but takes a while, and the system processes warning, though it doesn't seem to affect the overall usage of my phone, would get annoying, and shouldn't be happening in the first place.

---------

UPDATE:
Used ROM Toolbox to re-install original animation, took about half the time (read: normal boot up time), no system process error, though screen did flash after about thirty seconds, data switched to roaming, then switched back.
Rebooted.
Same quicker time, no process issue, slightly long to connect to Verizon network, screen did flash (only apps, not the whole screen, but I think that's the ROM). Anyway, original boot animation not messing up.

So your animation is doing something to mess with the system processes.
Click to expand...
Click to collapse

I'm sorry you are having these difficulties but I can 100% assure you the boot animation is not and cannot effect system processes. A boot animation is a series of images . That's it. It contains no code whatsoever so if you are seeing issues such as those you describe then ROM Toolbox is doing something weird that it shouldn't and/or you have a some buggy software throwing up issues.
 
P

pimikiel

Senior Member
Feb 15, 2014
54
5
freezed frame

For me and my PadFone, bootanimation freezes at last frame on second stage (where it supposed to loop animation) and when boot is finished, then starts 3rd stage of animation.
Weird
 
ssergioo23

ssergioo23

New member
Dec 29, 2014
3
1
bootanimation doesn't finish at all! Only works the "part0" of the .zip file! HELP

Before I begin, I would like to thank you for your great post.
My problem is that the bootanimation runs at the begining but then, it stops working at a given time in my phone(Elephone p2000). That given time is the image I attach in this comment.
Casually, the image where the bootanimation stops working is the last one of the folder "part0" of the bootanimation.zip file.
I would like to see the whole process.
So if you know how to fix this problem I would appreciate you effusively. Thanks.

PD: I have tried a lot of possibilities without success like puting all the images in the "part0" folder.
 

Attachments

  • 20140416_boot_260_00130.png
    20140416_boot_260_00130.png
    2.4 KB · Views: 649
Last edited:
You must log in or register to reply here.

Similar threads

moneytoo
[APP][MOD] Spotify Lite - scaled for standalone use on Wear OS
Replies
302
Views
195K
mdianov87
mdianov87
rcky844
  • Poll
[MOD] Convert your Chinese Wear OS to Global Wear OS
Replies
142
Views
111K
Newspaper2333
Newspaper2333
jimmod
[APP] Heart Rate OS for Android Wear with Google Fit sync
Replies
171
Views
71K
uncegila
uncegila
E
[App][Support]WearFaces - Create your own custom watchfaces for Android Wear!
Replies
122
Views
61K
V
vTeritron
moneytoo
[APP] Button Launcher (button shortcuts/combinations) for Android Wear
Replies
97
Views
55K
I
igorsantos07

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 61
    wollac11
    wollac11
    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! :D

    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!

    _20140609_191209_zps62408dfc.jpg

    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! :D

    (and please consider checking out my new Android blog: www.littlegreendude.com - thanks!)
    View
    7
    wollac11
    wollac11
    Very 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. :D

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

    preview_zpse96cfa1c.gif
    View
    6
    wollac11
    wollac11
    New 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! :D
    View
    4
    wollac11
    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
    View
    3
    IgnorCZ
    IgnorCZ
    kurt.gomez said:
    will the nexus 4 be the 720p one or the 1280x768 one...

    and the nexus 7 (2013) will be the 1920x1200 right?

    thanks in advance
    Click to expand...
    Click to collapse

    Hi ... N4 - 768p and N7 - 1200p ;)
    View

New posts