[Vibrant Android Development] zaduma:
Ok, so here is a bit of a preamble to stop flaming and unnecessary posts in this thread. This thread is not about changing bootdown animation for that go here.

Also do not do this if you don't understand what this all means, i am not responsible for your device, or anything else.

To the post:

I flashed back to stock last night to help everyone who wants to be able to use custom bootanimations (those like most other android phones can.) By placing a bootanimation.zip into /system/media and it should play when you boot. However as most of you know their is a proprietary format (QMG) getting called. Since I do not want to pay Quram and I also want custom bootanimations it leaves me with one choice, make it call the bootanimation.zip IN STEAD of the bootsamsung(loop).qmg. This is where what I am trying is different then other attempts I have read. Most other attempts try to break the QMG, why not just go around it and call what you want anyway.

The goodies:

I can get a custom bootanimation (specifically this one here) to play on my phone. Should work for any custom bootanimation.zip as long as it is built properly. Try to find one for our resolution or it will be tiny, but whatever I'm sure you can fix that right. You are in development forum anyways. ;) There is a weird delay between the black and white VIBRANT screen and the animation playing but since it is progress and on the stock rom (rooted of course) I am going to post what I did, and others can come in and help. ALRIGHT!

What to do:

Open up your command prompt and cd to the directory with your adb i.e. cd C:\adb\. Also place the bootanimation.zip (C:\adb\bootanimation.zip)

Then run this below in your command prompt window.

1. adb push bootanimation.zip /sdcard/bootanimation.zip
2. adb shell
3. su (NOTE: Allow root access on actual phone)
4. mount -o remount,rw /dev/block/st19 /system (NOTE: This just allows read/write access on /system)
5. busybox cp /sdcard/bootanimation.zip /system/media/bootanimation.zip
6. cd /system/bin/
7. mv playlogo playlogoBKP
8. mv playlogos1 playlogos1BKP
9. busybox cp bootanimation playlogo
10. busybox cp bootanimation2nd playlogos1

Now go ahead and reboot and enjoy your own custom bootanimation.zip

Also when done playing around you might want to revert everything back, cause I do not know if there are other repercusions of doing this. Although none I have noticed.

Video Evidence. (Because I am not a recognized member of this forum)

[YOUTUBE]wmu6RePTVmo[/YOUTUBE]

Replacing the bootanimation sounds and bootdown is not something covered by this thread as it is super easy, just go here.

Q. Well it seems like you figured everything out already Zaduma, what do we need with a thinktank thread about this?

A. There is a delay that lasts between 3-5 seconds between VIBRANT Screen and actual animation playing. Let's get rid of this.

Updates (not reflected above.) -- I will try to keep this updated with important information so you can just jump in.

We might be able to remove the lag if we can edit the init.rc, it calls playlogos1 only, which pretty much means that playlogo, bootanimation, and bootanimation2nd are useless files, of course unless you rename them playlogos1. The problem with this is that playlogos1 is called like this.

service playlogos1 /system/bin/playlogos1
user root
oneshot

But bootanimation should be called like this (as we know from AOSP builds and from bootanimation2nd, which i think is probably samsungs first attempt to put proprietary QMG in opening)

service bootanim /system/bin/bootanimation(2nd)
user graphics
group graphics
disabled
oneshot

I am not 100% sure of why being called from user graphics (most likely a root access user, or the disabled line would have anything to do with anything, but they are there.)

Also something I have seemed to find conclusive, if you run /system/bin/bootanimation it plays the animation almost instantly, but if you run /system/bin/bootanimation2nd it plays after a bit of a delay. So after renaming bootanimation to playlogos1 I noticed no change at actual boot time. I really feel like being able to update init.rc might hold some key, this is just a hunch I'm kinda figuring out what I can as I go.