[SOLVED] Why is my custom boot animation not working?

[Basher51]

Bootanimation not displaying

@stephtheduke :

Thanks a lot for sharing the zip compression issue.I was facing exactly the same problem.I will share what I did for other members as well.
Step1) I had 2 folders (part0 anf part1) containing my bootanimation images and a text file named 'desc'.
Step2) Select all the above 3 -> right click on mouse->Select 'Add to archive..'
Step3) In the popup box,select 'Archive format' as 'zip' and 'Compression method as 'Store' ; give the name of zip file to be created as 'Bootanimation.zip in the 'Archive name ' field and then press the 'Ok' button.
Step4) Step3 will create a zip file called 'Bootanimation.zip'.
Step5)Now, copy the created zip file to /system/media/ ; reboot device to view your boot animation.

Good luck !

Hi everyone,
You guys are likly to be my last resort !

I succesfully managed to push my downanimation which works as expected ..

But the bootanimation doesn't
I've tried adding the last line, encoding to ANSI or UTF-8 without BOM (and trying crazy things) but all this was vain

I spent so much time on it, it just drove me crazy and I have now absolutly no idea of what wrong with this
I hope you guys will be able to help :crying:

===

The day after ...
I figured out that when you add or replace files into the archive through windows explorer or 7-zip, the archive do not still uncompressed wich leads android to not be able to open the bootanimation zip file.
To sum this up, make sure you create bootanimation.zip from scratch with no compression and once created do not add or replace files directly inside it.


PS: Thank you for pointing out "adb shell bootanimation" command which saved my time a bit.

 

[Luckydewani]

You made my day!!!

In the "desc.txt" place all the info in it that's required. In my case it was all one line. If you have multiple lines go to the end of the last line and press "enter".
That's what solved my problem.

If that doesn't happen, it won't boot.

thank you sooo much..

 

[CVAngelo]

Hi everyone,
You guys are likly to be my last resort !

I succesfully managed to push my downanimation which works as expected ..

But the bootanimation doesn't
I've tried adding the last line, encoding to ANSI or UTF-8 without BOM (and trying crazy things) but all this was vain

I spent so much time on it, it just drove me crazy and I have now absolutly no idea of what wrong with this
I hope you guys will be able to help :crying:

===

The day after ...
I figured out that when you add or replace files into the archive through windows explorer or 7-zip, the archive do not still uncompressed wich leads android to not be able to open the bootanimation zip file.
To sum this up, make sure you create bootanimation.zip from scratch with no compression and once created do not add or replace files directly inside it.


PS: Thank you for pointing out "adb shell bootanimation" command which saved my time a bit.

I broke the cardinal rule: "make sure you create bootanimation.zip from scratch with no compression and once created do not add or replace files directly inside it" Geez Lueez! I must have spent a good two hours trying to figure out why my phone just froze after I not only compressed but replaced files inside the zip!

I ended up soft-bricking (I mean really soft). I had to use ADB shell to delete the new animations and push my backed-up stock animations into the phone. Thank God I made copies of them.

Thanks for posting this man. You saved my bacon!

 

[lynchyy89]

Randomly came across this thread whilst browsing for solutions, I made a bootanimation, it runs perfectly on the boot factory thing on my PC, I've added the extra line in my desk.txt and used notepad++.. Created zip using store method, put into /system/media named bootanimation.zip with rw-r--r-- however when I preview it using ROM toolbox it will only play what's in the part0 folder but not the part1 folder, any ideas? Sorry to post on such an old thread but I've spent hours trying different methods and searching Google but no luck

 

[CVAngelo]

Randomly came across this thread whilst browsing for solutions, I made a bootanimation, it runs perfectly on the boot factory thing on my PC, I've added the extra line in my desk.txt and used notepad++.. Created zip using store method, put into /system/media named bootanimation.zip with rw-r--r-- however when I preview it using ROM toolbox it will only play what's in the part0 folder but not the part1 folder, any ideas? Sorry to post on such an old thread but I've spent hours trying different methods and searching Google but no luck

What's in your desc.txt file? Can you post your desc.txt file? Sure sounds like you set the LOOP value of part0 to 0, or that you set the PAUSE value so high that there's not enough time to finish part0 before the system is loaded. Such settings would ensure that the animation never moves to the second folder.

And did you actually try it in your phone to see if it does work? What does your phone do? Does it play only part0? Or does your phone hang (meaning you possibly replaced or edited a file inside your uncompressed zip so it's no longer uncompressed).

You may find the following link helpful. Please review the section that describes the desc.txt file:

P.S. REMEMBER TO SAVE A BACKUP OF THE STOCK BOOT ANIMATION FILES in case you should need to replace them!

 

[lynchyy89]

What's in your desc.txt file? Can you post your desc.txt file? Sure sounds like you set the LOOP value of part0 to 0, or that you set the PAUSE value so high that there's not enough time to finish part0 before the system is loaded. Such settings would ensure that the animation never moves to the second folder.

And did you actually try it in your phone to see if it does work? What does your phone do? Does it play only part0? Or does your phone hang (meaning you possibly replaced or edited a file inside your uncompressed zip so it's no longer uncompressed).

You may find the following link helpful. Please review the section that describes the desc.txt file:

P.S. REMEMBER TO SAVE A BACKUP OF THE STOCK BOOT ANIMATION FILES in case you should need to replace them!

Once its been compressed I don't touch any of the files, the desc.txt file is as follows:

1)1080 1920 4
2)p 1 0 part0
3)p 0 0 part1
4)

Everything is backed up but I didn't trust rebooting the device to find out that it got stuck, hence testing it in ROM toolbox first, I can post the whole boot animation if you like?

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

Once its been compressed I don't touch any of the files, the desc.txt file is as follows:

1)1080 1920 4
2)p 1 0 part0
3)p 0 0 part1
4)

Everything is backed up but I didn't trust rebooting the device to find out that it got stuck, hence testing it in ROM toolbox first, I can post the whole boot animation if you like?

Sent from my D6603 using XDA Free mobile app

Yes, the desc.txt looks totally correct!

But when you said "once it's been compressed" you did not literally mean that you compressed the files correct? You mean you stored the files UNCOMPRESSED using the zip utility. I am presuming you said you "compressed" the files merely because they are in a ZIP format.

I'd be interested in checking out your zip files. Maybe it's just the ROM Toolbox that's messed up and your animation is perfectly fine!

You're obviously quite experienced. That's why I was suggesting that you should not feel too inconvenienced by testing the animations on your device. If your phone does hang on boot, it is a really, really soft brick. Just make sure your USB debugging is on (mine is permanently on LOL). All you then have to do is use ADB to open a shell, get into the system/media directory where you placed the animations, delete/rename them, and them copy in the stock animations which you know do work. Usually what I do is that I leave the stock boot/shut animation zips in there and I just rename them with a .bak at the end of the original file names. That way if anything goes wrong, I simply delete the custom animation zips and remove the stock zips back to their original names. Then just reboot without any hassles.

 

[lynchyy89]

Yes, the desc.txt looks totally correct!

But when you said "once it's been compressed" you did not literally mean that you compressed the files correct? You mean you stored the files UNCOMPRESSED using the zip utility. I am presuming you said you "compressed" the files merely because they are in a ZIP format.

I'd be interested in checking out your zip files. Maybe it's just the ROM Toolbox that's messed up and your animation is perfectly fine!

You're obviously quite experienced. That's why I was suggesting that you should not feel too inconvenienced by testing the animations on your device. If your phone does hang on boot, it is a really, really soft brick. Just make sure your USB debugging is on (mine is permanently on LOL). All you then have to do is use ADB to open a shell, get into the system/media directory where you placed the animations, delete/rename them, and them copy in the stock animations which you know do work. Usually what I do is that I leave the stock boot/shut animation zips in there and I just rename them with a .bak at the end of the original file names. That way if anything goes wrong, I simply delete the custom animation zips and remove the stock zips back to their original names. Then just reboot without any hassles.

I've soft bricked with a previous bootanimation that I made and I managed to reboot the phone into recover then removed the file, I probably didn't word it right, I selected part0, part1 and desc.txt then went to add to archive and set the mode to store.. If that makes any more sense? This is the zip file..
https://docs.google.com/file/d/0BzNj7crTP8XvQTk3Y3pXME1FS1E/edit?usp=docslist_api


EDIT: I THINK I may have sorted it.. I booted up using it and the device boots quicker than the animation.. Gonna speed it up and see what effects that has

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

I've soft bricked with a previous bootanimation that I made and I managed to reboot the phone into recover then removed the file, I probably didn't word it right, I selected part0, part1 and desc.txt then went to add to archive and set the mode to store.. If that makes any more sense? This is the zip file..
https://docs.google.com/file/d/0BzNj7crTP8XvQTk3Y3pXME1FS1E/edit?usp=docslist_api


EDIT: I THINK I may have sorted it.. I booted up using it and the device boots quicker than the animation.. Gonna speed it up and see what effects that has

Sent from my D6603 using XDA Free mobile app

That's too funny....such are the frustrations of a fast phone! LOL Glad you sorted it out.

Still doesn't explain what was up with ROM Toolbox, but that's a story for a different day..

EDIT: I reviewed your zip file and I have two casual observations: 1) Perhaps the reason your part0 animation runs more slowly that your phone boots is that each of your JPEG files is relatively large at 70-120Kb each. And your part0 folder has 85 images! Just by way of comparison, most of the animation images I see are around 5Kb and there arent as many total images to run through (so I just repeat the animation multiple times). Given that there isn't much by way of graphics in your part0 folder, perhaps you should use a much smaller pixel density for these. 2) I may be mistaken but are those thumbs.db files inside the part0 and part1 folders of your ZIP? They aren't there when I extracted the folders and the desc.txt, but they are definitely inside the folders in the ZIP. Seems strange. How did they get there? The one in the part0 that's inside the zip is over 1MB. It's definitely not needed inside the zipped folders and I'm not sure what effect during the boot animation. Perhaps you should remove them even if they aren't hurting anything.

 

[lynchyy89]

That's too funny....such are the frustrations of a fast phone! LOL Glad you sorted it out.

Still doesn't explain what was up with ROM Toolbox, but that's a story for a different day..

It used to take 1 minute 05 to boot before, now boots in about 30 seconds, but I changed the fps and still not solved the problem, it starts the sequence but cuts it off near the end of the first folder, so its getting worse now trying with .PNG files instead, will update after I've tried

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

It used to take 1 minute 05 to boot before, now boots in about 30 seconds, but I changed the fps and still not solved the problem, it starts the sequence but cuts it off near the end of the first folder, so its getting worse now trying with .PNG files instead, will update after I've tried

Sent from my D6603 using XDA Free mobile app

You must have responded while I was editing my previous response. See my earlier observations regarding the size of the JPGs (you probably don't need to switch to PNGs) and about the thumbs.db files that are someone appearing inside your zip. Check your original part0 and part 1 folders before you zip them up with the desc.txt.

 

[lynchyy89]

You must have responded while I was editing my previous response. See my earlier observations regarding the size of the JPGs (you probably don't need to switch to PNGs) and about the thumbs.db files that are someone appearing inside your zip. Check your original part0 and part 1 folders before you zip them up with the desc.txt.

Yeah I probably did, I haven't a clue how the thumbs.db got there they just appeared after being zipped and I had a huge file size problem with a previous one, had in total 200 images due to not being able to loop it and the zip was near 100mb.. Never been good at getting small file sizes, not sure I could reduce the amount of images in part0 as trying to get it to seem like a realistic windows style start up, part1 is just an optional extra due to liking that animation from someone else so I used it in mine (I did ask their permission first) I will attempt to get smaller file sizes in the morning to see if it makes a difference and also do a bit of research on these unknown files that seem to keep appearing

Sent from my D6603 using XDA Free mobile app

 

[lynchyy89]

You must have responded while I was editing my previous response. See my earlier observations regarding the size of the JPGs (you probably don't need to switch to PNGs) and about the thumbs.db files that are someone appearing inside your zip. Check your original part0 and part 1 folders before you zip them up with the desc.txt.

Removed thumbs.db, it no longer appears once zipped, total zip size under 3mb, each file is approx 20kb and quality has been reduced but still no luck it gets to a certain part of the sequence and then goes black, I'm completely baffled now

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

Removed thumbs.db, it no longer appears once zipped, total zip size under 3mb, each file is approx 20kb and quality has been reduced but still no luck it gets to a certain part of the sequence and then goes black, I'm completely baffled now

Sent from my D6603 using XDA Free mobile app

Hey Lynch. Now that is downright weird. But I love a good mystery. Solving them only leads to a deeper understanding of these bad-boys. LOL. By the way, when you say your phone "goes black" do you mean the animation just seems to halt, or does the phone boot before the animation is done, or is the phone hanging at that point? Please clarify.

Also, go ahead and load the new zip file on Drive and repost the link here. What I plan to do is unpack your zip, change all the images to the dimension of my test phone (it's a little Alcatel M'Pop that's been tormeneted with every possible thing I could throw at it), and then rezip it and run it on my phone. Let's see if the same weird thing happens and why.

 

[lynchyy89]

Hey Lynch. Now that is downright weird. But I love a good mystery. Solving them only leads to a deeper understanding of these bad-boys. LOL. By the way, when you say your phone "goes black" do you mean the animation just seems to halt, or does the phone boot before the animation is done, or is the phone hanging at that point? Please clarify.

Also, go ahead and load the new zip file on Drive and repost the link here. What I plan to do is unpack your zip, change all the images to the dimension of my test phone (it's a little Alcatel M'Pop that's been tormeneted with every possible thing I could throw at it), and then rezip it and run it on my phone. Let's see if the same weird thing happens and why.

The animation just comes to a hault, its around the same point every time with all attempts, the phone just carries on booting with a black screen so it doesn't cause any problems just doesn't want to run the whole animation.. Take your pick I done 1 with 2 folders and 1 that just uses 1 folder

2 folders > https://docs.google.com/file/d/0BzNj7crTP8XvTWhWXzlYZjY2Y2M/edit?usp=docslist_api

Single folder > https://docs.google.com/file/d/0BzNj7crTP8XvcF9NNV84M05ITlU/edit?usp=docslist_api


EDIT:

so, I decided to remove a few images, doesn't run great anymore but more of the animation runs (still stops just further in) so it's got to be something to do with the amount of images which is confusing because I've seen some with well over 200 images run smoothly with no problems..


Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

The animation just comes to a hault, its around the same point every time with all attempts, the phone just carries on booting with a black screen so it doesn't cause any problems just doesn't want to run the whole animation.. Take your pick I done 1 with 2 folders and 1 that just uses 1 folder

2 folders > https://docs.google.com/file/d/0BzNj7crTP8XvTWhWXzlYZjY2Y2M/edit?usp=docslist_api

Single folder > https://docs.google.com/file/d/0BzNj7crTP8XvcF9NNV84M05ITlU/edit?usp=docslist_api

Sent from my D6603 using XDA Free mobile app

Wow...what a mystery! Something is definitely funky. Here's what happened. So I unpacked and converted all your images to the size of my test phone which is 320 x 480. I created the zip file with the retro animation in part0 and the XPERIA animation in part1. I have other animations that are in multiple folders and they all work perfectly. In this case, my phone did not play part1. But I did not get a black screen. It just got stuck on the last image in the part0 folder. My reaction can be described in 3 letters - WTF?

THEN MY PHONE THREW AN ERROR MESSAGE WHICH I'VE NEVER SEEN BEFORE. So this may be a clue. The message said: "Update time failed, please try again later." The phone eventually booted to the home screen as normal.

So I got to thinking. Perhaps your frame-rate was way too slow. So I changed it to 30 frames per second. Same result! Stuck on last image in the part0 folder. But then there was another clue. It got to that 85th image like a rocket and before the boot music could finish. Well what ever is happening in the background to throw this error also stopped THE BOOT MUSIC dead in it's tracks. That is really freaking amazing, So my conclusion is that somehow, something is making the boot animation process "believe" it is done. But it ain't.

Then I figured that perhaps the problem was that the images in part1 were not following the numbering sequence of the images in part0 as the numbering sequence started over again at 0. So I renumbered all the images in part1 starting with 85. But again, same damn result! It simply refused to play the second folder.

So then I had to prove that it was not something funky with the last image of the part0 or the first image in part1. So I moved all the images to a single folder and VIOLÁ, it played the whole thing. Thus proving that there is no problem with the images themselves. But of course, this is not the solution because you want the XPERIA images to repeat and not just play once. So how to make the second folder play?

I tried another tweak. I thought, since the frame rate is 30 per second which means part0 is gonna be done in under 3 seconds flat, what if I change the number of times to repeat from 1 to say 3 or 4? Same result! It plays just once and refuses to play the second folder.

So stupid me, I'm thinking, maybe there is a limit to how many images can be in a single folder if there is a follow on folder. I only guessed at this because the STOCK boot image for Alcatel phones of this type has even more images than your animation and they are in 6 folders! One of those folders had 58 images, but none had 85. So my last step was to split your images into 3 folders -essentially, took your part0 and split it into two (part0 and part1), and the final was part2 with the XPEDIA animation which was to repeat. You won't believe this, but it refused to go past the first folder! So same result!!!

So back to the ERROR message. I began to look into it further. Obviously, after it gets past the very first folder, it is trying to update something. But what? And why does it fail. So I started looking at the OWNERSHIP of the bootanimation. I'm using Root Browser. I can set the permissions of the file equal to those of every other bootnaimation zip that is inside my /system/media folder. I set the owner of the file to 0:Root. But for some reason, I cannot change the owner of the group to 0:Root like the stock file and my other bootanimation files. The group owner stays at 1015:sdcard_rw. That's the only "invisible" difference between this boot animation zip and all the others I am using. I'm also not sure if this ownership thing has anything to do with the problem.

Now, what I cannot figure out is what on earth is it about this file that would be any different than all my other files??? I'm now also totally stumped by something that should be so simple. I've done this so many times before. It must be something so simple we are just missing it. I'll keep trying (I have one final idea to test...will lt you know how it goes).

 

[lynchyy89]

Wow...what a mystery! Something is definitely funky. Here's what happened. So I unpacked and converted all your images to the size of my test phone which is 320 x 480. I created the zip file with the retro animation in part0 and the XPERIA animation in part1. I have other animations that are in multiple folders and they all work perfectly. In this case, my phone did not play part1. But I did not get a black screen. It just got stuck on the last image in the part0 folder. My reaction can be described in 3 letters - WTF?

THEN MY PHONE THREW AN ERROR MESSAGE WHICH I'VE NEVER SEEN BEFORE. So this may be a clue. The message said: "Update time failed, please try again later." The phone eventually booted to the home screen as normal.

So I got to thinking. Perhaps your frame-rate was way too slow. So I changed it to 30 frames per second. Same result! Stuck on last image in the part0 folder. But then there was another clue. It got to that 85th image like a rocket and before the boot music could finish. Well what ever is happening in the background to throw this error also stopped THE BOOT MUSIC dead in it's tracks. That is really freaking amazing, So my conclusion is that somehow, something is making the boot animation process "believe" it is done. But it ain't.

Then I figured that perhaps the problem was that the images in part1 were not following the numbering sequence of the images in part0 as the numbering sequence started over again at 0. So I renumbered all the images in part1 starting with 85. But again, same damn result! It simply refused to play the second folder.

So then I had to prove that it was not something funky with the last image of the part0 or the first image in part1. So I moved all the images to a single folder and VIOLÁ, it played the whole thing. Thus proving that there is no problem with the images themselves. But of course, this is not the solution because you want the XPERIA images to repeat and not just play once. So how to make the second folder play?

I tried another tweak. I thought, since the frame rate is 30 per second which means part0 is gonna be done in under 3 seconds flat, what if I change the number of times to repeat from 1 to say 3 or 4? Same result! It plays just once and refuses to play the second folder.

So stupid me, I'm thinking, maybe there is a limit to how many images can be in a single folder if there is a follow on folder. I only guessed at this because the STOCK boot image for Alcatel phones of this type has even more images than your animation and they are in 6 folders! One of those folders had 58 images, but none had 85. So my last step was to split your images into 3 folders -essentially, took your part0 and split it into two (part0 and part1), and the final was part2 with the XPEDIA animation which was to repeat. You won't believe this, but it refused to go past the first folder! So same result!!!

So back to the ERROR message. I began to look into it further. Obviously, after it gets past the very first folder, it is trying to update something. But what? And why does it fail. So I started looking at the OWNERSHIP of the bootanimation. I'm using Root Browser. I can set the permissions of the file equal to those of every other bootnaimation zip that is inside my /system/media folder. I set the owner of the file to 0:Root. But for some reason, I cannot change the owner of the group to 0:Root like the stock file and my other bootanimation files. The group owner stays at 1015:sdcard_rw. That's the only "invisible" difference between this boot animation zip and all the others I am using. I'm also not sure if this ownership thing has anything to do with the problem.

Now, what I cannot figure out is what on earth is it about this file that would be any different than all my other files??? I'm now also totally stumped by something that should be so simple. I've done this so many times before. It must be something so simple we are just missing it. I'll keep trying (I have one final idea to test...will lt you know how it goes).

See now for me it wouldn't even make it to the last image of part0 it got about 10 from the end and cut out, even if I put all images into 1 single folder it will still hit the same part and stop, I did however reduce the amount of files from 180 odd down to 140 (total merged) and it would complete the part0 images and 10 of the xperia images but no luck with 2 sperate folders.. I've only ever encountered issues with running 1080 and 720 (had trouble running a 1080 but the 720 worked fine ) so this is something completely new to me.

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

See now for me it wouldn't even make it to the last image of part0 it got about 10 from the end and cut out, even if I put all images into 1 single folder it will still hit the same part and stop, I did however reduce the amount of files from 180 odd down to 140 (total merged) and it would complete the part0 images and 10 of the xperia images but no luck with 2 sperate folders.. I've only ever encountered issues with running 1080 and 720 (had trouble running a 1080 but the 720 worked fine ) so this is something completely new to me.

Sent from my D6603 using XDA Free mobile app

I wonder if anyone else in the forum has any ideas? This is truly baffling. Yet, I think I've made progress. I think the issue has something to do with the naming of the image files and how they are interpreted by the animation system. You see, I went and placed the characters "A_" at the start of the image names, so instead of being just a number like say 00050.jpg, it is A_00050.jpg. Guess what happened? The animation refused to play ANY of the folders. It would not even play the first folder and then stop. It simply did not make it to any of the images in any of the folders! That is truly a revelation.

So my next step is to use exactly the same naming convention that was in the stock animation and see if that will make a difference. will let you know what happens.

EDIT: EUREKA!!! That was the problem. WHAT YOU NAME THE IMAGE FILES MATTERS! So the solution is to use the same naming convention that was used for the stock animation. WOW, WHO KNEW? In my case, the boot files were named boot_xxxxx.jpg where the xxxxx were the sequential numbers of the images. Note that you can skip numbers too, but they will play in numerical order! I have researched all the boot animations I have used with this phone. And they have all worked. But they all used either boot_xxxxx.jpg or alcatel_onetouch_xxxxx.jpg. WHAT A NASTY ISSUE THIS IS. AND THERE'S NO DOCUMENTATION ANYWHERE TO WARN USERS ABOUT THIS.

---------- Post added at 11:20 PM ---------- Previous post was at 10:29 PM ----------

See now for me it wouldn't even make it to the last image of part0 it got about 10 from the end and cut out, even if I put all images into 1 single folder it will still hit the same part and stop, I did however reduce the amount of files from 180 odd down to 140 (total merged) and it would complete the part0 images and 10 of the xperia images but no luck with 2 sperate folders.. I've only ever encountered issues with running 1080 and 720 (had trouble running a 1080 but the 720 worked fine ) so this is something completely new to me.

Sent from my D6603 using XDA Free mobile app

Lynch, did you see my edit? I'm not sure if your app notifies you of edits to posts. Anyway, I figured out what was wrong and I've gotten your animation to work perfectly! Try the solution and see if it also works for you too. Let me know.

 

[lynchyy89]

I wonder if anyone else in the forum has any ideas? This is truly baffling. Yet, I think I've made progress. I think the issue has something to do with the naming of the image files and how they are interpreted by the animation system. You see, I went and placed the characters "A_" at the start of the image names, so instead of being just a number like say 00050.jpg, it is A_00050.jpg. Guess what happened? The animation refused to play ANY of the folders. It would not even play the first folder and then stop. It simply did not make it to any of the images in any of the folders! That is truly a revelation.

So my next step is to use exactly the same naming convention that was in the stock animation and see if that will make a difference. will let you know what happens.

EDIT: EUREKA!!! That was the problem. WHAT YOU NAME THE IMAGE FILES MATTERS! So the solution is to use the same naming convention that was used for the stock animation. WOW, WHO KNEW? In my case, the boot files were named boot_xxxxx.jpg where the xxxxx were the sequential numbers of the images. Note that you can skip numbers too, but they will play in numerical order! I have researched all the boot animations I have used with this phone. And they have all worked. But they all used either boot_xxxxx.jpg or alcatel_onetouch_xxxxx.jpg. WHAT A NASTY ISSUE THIS IS. AND THERE'S NO DOCUMENTATION ANYWHERE TO WARN USERS ABOUT THIS.

---------- Post added at 11:20 PM ---------- Previous post was at 10:29 PM ----------



Lynch, did you see my edit? I'm not sure if your app notifies you of edits to posts. Anyway, I figured out what was wrong and I've gotten your animation to work perfectly! Try the solution and see if it also works for you too. Let me know.

No I don't get the notification for edits, I will have to give it a try, although regarding naming I'm using the original xperia animation which was created by some one else and it works fine, it's also just named 00000 ect but I will look at trying your method on my one to see if it makes a difference

Thank you for all your help! Not many people would attempt to solve such a confusing problem

EDIT:

Just looked at my stock animation and although there are many folders the images are named exactly the same as the ones in my animation so I don't see naming being the issue for my phone

Sent from my D6603 using XDA Free mobile app

 

[CVAngelo]

It's interesting that I had exactly the same problem you did when I used your animation zip. And the image names were the issue.

By the way, you remember you'd made an off hand remark about changing the image formats to PNG? It's quite possible that this could be a solution (Lol...funny that you'd have come up with it yourself) given the numerical names of the images.

Only reason I point this out is that I've seen a couple other animations with numerical names and they all were PNG format (well not all but the vasy majority of those zips).

Bottom line as you said...it couldn't hurt to try though it would clearly be a pain to execute. Yet, we learn from the experience.

Sent from my ALCATEL ONE TOUCH 7040D using XDA Free mobile app