yashsingh1/xdaforums huggingface dataset:
[HD2 General] Wil Badger:
Don't expect it to be anything like the Sense we know and love in 6.5 it will most likely be a hub or tile (what ever they call those stupid squares) with a clock and weather in it. They can not impliment their own UI on Win7.

So don't expect it to be pretty you will still get to look at those stupid squares on your homescreen.
[HD2 General] juggs:
Oh you just summed it up right there, I'm glad I'm not the only one that thinks this social networking **** has gone way too far. You made me giggle.
[Android Themes] philosophics:
For some ludicrous reason, I cannot apply themes nor modify the framework-res myself anymore. Everytime I try, I get a bootloop or a flood of FC's

I removed /audio from RC2 along with a few other things so it shouldn't be a space issue.

Just wondering if anyone wants to take the time to make a flashable.zip or metamorph that would bring the black scroll bar back.

And if all possible, I would like my status bar icons back as well. Who ever is interested, you can get all the .png's here,

Meclairo-Images.zip

I will be very grateful to the first person to get this done!

2 rules,

1. Use the icons in the .zip on this post

2. DON'T RELEASE IT UNTIL YOU HAVE TESTED IT ON YOUR DEVICE AND IT DOESN'T FAIL OR YOU DID SOMETHING BESIDES APPLY OR FLASH!

(no one wants to fix_permissions for a theme...)

I want a screen shot from DDMS.BAT in your post along with the .ZIP or METAMORPH download link

Happy theeming and may the android gods be with you!

Thank you to all who tried anyway!
[EVO 4G Q&A, Help & Troubleshooting] Brutus2TheMax:
Can anybody find this wallpaper that will fit the EVO? No I'm not trying to make my phone look like an apply product I just like the wallpaper.
[Nexus One Q&A, Help & Troubleshooting] verboten:
I am having some very frustrating BT issues.

I only use one bluetooth device, a Kenwood KDC-BT945U car stereo. When using any vanilla android rom, the phone and deck struggle to work. They hardly ever pair and once it does, they never reconnect later and I must go through the process of trying to re-pair again.

Here is what I find odd. Any SenseUI rom that I have tried, the phone and the deck connect without issue.

My question is, would it be possible to take the bluetooth from Modaco's R23 and use it on CM6? Any advice?

Verboten

UPDATE.

I got brave and took the bluetooth.apk from Modaco's R23 ROM and pushed it to my phone running CM6 RC2 and my issues are 95% better. It works great but the phone wants to pair every time I get into the car. I wish it would auto connect but at least it is working.
[Nexus One Q&A, Help & Troubleshooting] AverageCanadian:
That sucks. I have similar issues with stock Froyo. Just coming in to see if rooting and a custom rom would fix the issue.

Everytime I get into my car I have to turn off my bt on my phone and turn it back on for the radio and the phone to pair.

Not sure if its an Android issue(my Milestone did the same exact thing) or my radio(Clarion)

Even more annoying, is half the time as soon as the phone pairs with the radio it starts playing music. Not my preference that is for sure.
[Captivate Android Development] rahlquist:
Wanted to get rid of the stock startup animation and sounds here is how I did it.

/system/etc/PowerOn.wav

/system/media/bootsamsung.qmg

/system/media/bootsamsungloop.qmg

I renamed those 3 files and thats all it took, killed the two boot animations and sounds. So now I get the Initial white AT&T screen a long black period followed by the lock screen.

Now if someone would decipher how to manipulate these QMG files. It looks like others have found a way around them possibly ( http://forum.sdx-developers.com/themes/bootanimation-zip-(testers-needed)/ ), not too sure.
[Captivate Android Development] decepticon:
Anyone have the stock startup and shutdown animations from the Galaxy S? I want to de-brand this as much as I can.
[Captivate Android Development] rahlquist:
More data from inside the /system/bin/bootanimation2nd

debug.sf.nobootanimation 0 BootAnimation boot animation disabled %0 80 /data/local/bootanimation.zip /system/media/bootanimation.zip desc.txt descMap is null %d %d %d p %d %d %s images/android-logo-mask.png images/android-logo-shine.png SurfaceFlinger died, exiting... linkToComposerDeath failed (%s)

So it looks like we have some tinkering to do.
[Captivate Android Development] rahlquist:
ok if you take the bootanimation zip files from the other forum and place them in /system/media and chmod to 644 and chown to root you can launch the bootanimation file in /system/bin remotely with adb and the animation shows on the screen of the phone. So we are on the right path. Rebooting the phone does not cause the animation to play however. Anyone who wants to lend a hand is welcome!
[Captivate Android Development] sfernandez:
LOCATIONS OF SOUNDS AND ANIMATIONS

Startup sound;

/system/etc/PowerOn.wav

Startup animation;

/system/media/bootsamsung.qmg

/system/media/bootsamsungloop.qmg

/system/bin/bootanimation

/system/bin/bootaniamtion2nd

Shutdown sound;

/system/media/audio/ui/shutdown.ogg

Shutdown video (directory of .pngs);

/system/media/shutdown/

THIS IS WHAT I FOUND ON ANOTHER SIGHT

You can just delete all other files and folder so you only have fx if your bootscreen is placed like this: META-INF and system system> customize> resource>bootanimation.zip

That should be your only files and folders. Of course if you your bootscreen is placed in data/local/bootanimation.zip then that should be your only directories and files

THIS IS HOW I DID IT WHEN I HAD AN ARIA( not sure but seems like it should be same?)

1. Copy the NEW bootanimation.zip of your choice in SDK Folder

2. Open up CMD

3. cd C:\AndroidSDK\tools (or were ever you SDK files are)

4. adb remount

The filesystem is mounted read only. You need to mount it read/write.

5. adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system

6. adb push bootanimation.zip /system/media/bootanimation.zip

7. adb push bootanimation.zip /data/local/bootanimation.zip

To return to read only,

8. adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system

9. Reboot and there you go

HOPE this helps
[Captivate Android Development] kenjindomini:
I've renamed some of the files to see if they do anything also executed a few of the BINs.

/system/bin/bootanimation -- Displays "ANDROID" with a shine going across the text. This animation is not seen at any point during boot, renaming the file did nothing.

/system/bin/bootaniamtion2nd -- Displays "ANDROID" in plain android font. This animation is not seen at any point during boot, renaming the file did nothing.

/system/bin/playlogo -- Executing this file (atleast via the adb shell, although it does output "=============> 1" the exits after a few seconds.) did not appear to do anything. Renaming this file did not appear to change anything in the boot process.

/system/bin/playlogos1 -- Executing this file via the adbshell caused the 2 boot videos (not the "AT&T World Phone" BIOS splash image, just the ATT bars with fire balls and the galaxy S animated logo) to play. This cause similar out put to playlogo in the adb shell, except it counted to 5 and never exited. A Ctrl+C in DOS forces the adb shell to quit which causes the bin file to halt execution also.

I'm going to try and open the playlogos1 file and/or try to find a qmg player, we may just have to replace the qmg files to MOD the boot animation.
[Captivate Android Development] rahlquist:
Some relevant source ( http://github.com/Dieken/SurfaceFli...rks/base/cmds/bootanimation/BootAnimation.cpp ). Its starting to look like the qmg files are raw frame buffer information.
[Captivate Android Development] kenjindomini:
I went through the playlogo and playlogos1 bin files again with bvi (linux app for viewing binary files) one of the legible sections before the part that points to the *.qmg file loads a decoder. The qmg files appear to be Qmage files.

See quramsoft.com/solution_e/qmage.asp

sorry cant post links yet.
[Captivate Android Development] rahlquist:
You may have nailed it on the head which is a good find, but unfortunately it looks like we will never be able to edit one of these.
[Captivate Android Development] kenjindomini:
So I take it no one has yet attempted to use a bootanimation.zip like on the Samsung moment http://forum.sdx-developers.com/themes/(how-to)-bootanimation-zip/

I might give this a try later today:

Rename playlogos1 -> playlogos1.orig

find sexy bootanimation.zip on the interwebs and load it into /system/media

I'll report back with my findings, even if they're depressing.
[Captivate Android Development] rahlquist:
Yes I have tried several, and while you can launch them manually they do not trigger on reboot.
[Captivate Android Development] kenjindomini:
Yeah :(

I even tried to chmod the file in both data/local and system/media to mode 777 and still just a black screen.

Looks like we are waiting for a hacked kernel.
[Captivate Android Development] rahlquist:
In the meantime I am looking to see exactly how/where these are being called in the boot process.
[Captivate Android Development] rahlquist:
Ok since things just didnt seem to be working here is what I did. I renamed the playlogo and playlogos1 file and replaced them respectively with renamed copies of

/system/bin/bootanimation

/system/bin/bootaniamtion2nd

then put a bootanimation.zip in both /system/media and /data/local then when I rebooted I get the plain white at&t screen. followed by a short black screen, and then the bootanimation.zip.

So this works it just has a 7 second or so black screen.
[Captivate Android Development] derek4484:
Ok, something weird is happening. I'm trying to rename /system/etc/PowerOn.wav to PowerOn.wav.bak because I have downloaded the Bootsamsung.qmg, Bootsamsungloop.qmg and PowerOn.wav from the I-9000 but every time I rename /system/etc/PowerOn.wav to *.bak using root explorer it says its renamed successfully but then if I do a view refresh, its right back to how it was originally. Same thing if I just go and try to outright delete it, it looks like its deleted until I do a view refresh then its right back there. Like I cant get rid of it at all. Anybody know whats going on??

On another note I copied the Bootsamsung.qmg and bootsamsungloop.qmg from the I-9000 to the folder /system/media and just let it overwrite the orignals. Now the flying att 3G antenna stuff is gone. It goes from the white world phone screen to a black screen then to the Galaxy S animation. But its still playing that super loud whoosh sound because I cant get rid of the original PowerOn.wav file to save my life.

The PowerOn.wav from the I-9000 is 5 seconds long, its the same as the AT&T one except it doesnt have the first two seconds that contains the really loud and annoying "Whoooosh".
[Captivate Android Development] rahlquist:
I had this problem at first. Make sure you are mounted r/w. If that doesnt work move the file out of the folder. I seem to recall that one file was a pita for me too.

If you get it working let us know!
[Captivate Android Development] derek4484:
HaHa, that worked great. Thanks.

I was mounted as r/w in root explorer. I tried renaming and deleting dozens of times with no success, never really thought about move. It let me move it right out of /system/etc. Then I was able to copy in the new PowerOn.wav from my sdcard. Then I could rename the original to PowerOn.wav.bak, then move it back to /system/etc just in case for the future. So now I dont hear that really loud and annoying "whoosh".
[Captivate Android Development] Darkeligos:
Is the /video/shutdown folder with the 60 frames of .pngs the same as the startup animation perhaps played backwards? I'm thinking of making my own custom animation and replacing those files to see how it looks.
[Captivate Android Development] kenjindomini:
If you look in the init.rc there is BOOTCLASSPATH line and it lists framework files, they are compiled java code (*.JAR) one of these files or a modified version of the android kernel would be responsible for executing the playlogos1 bin file. playlogos1 is the only file on the of the 4 in that directory that we have talked about that does anything during boot on the captivate. playlogo seems to be remnant from the older samsung androids (E.G the moment). The 2 bootanimation bin files just display the word android in green android style font 1 with a shine and 1 plain.

I've looked through almost every system file and I can think of, there is no reference to the playlogs1 file that can be viewed in plain text. It would be the very first thing to be called soon as linux begins to load. The ATT world phone splash image I would assume, just like on a pc, hides the BIOS/POST output and the boot animation is hiding all of the linux init output. though it does sadden me that renaming the files the play the boot animation does not cause all the boot text to display.

This is not the case. the playlogos1 bin file, the file responsible for launching the boot animation, loads a QMAGE decoder before loading the 2 *.QMG files. If look back to my previous post on the first page there is a link to the developer of QMAGE and its a compressed library of images that get decompressed on-the-fly.

@the guy with the I9000 boot animations and audio, Dude where did you get those? i9000 forum? link us? Attach here? Please?
[Captivate Android Development] KryptosXLayer2:
Yes, this needs to be mandatory - if you've got something good working that gets rid of the AT&T JUNK sounds and animation, then you gotta attach them on this thread and tell us the steps you took to get it going! Thanks in advance!
[Captivate Android Development] LGSilva:
Just got rid of that awful AT&T bars animation and now I have the beautiful Samsung Galaxy S start-up animation.

Download the original animation from here: http://xdaforums.com/showthread.php?t=720567 (first file)

Then replace /system/media/bootsamsung.qmg with the one you downloaded
[Captivate Android Development] p4ranoid4ndroid:
@lgsilva i did this and now just have at&t animation without galaxy s. Still have sound for galaxy s boot tho
[Captivate Android Development] KryptosXLayer2:
Okay, nevermind about it not working before.... gonna try to get this thing loaded up, or maybe just wait for the new ROM instead!
[Captivate Android Development] NukaCola:
When I was poking around i the initramfs I found this:

# disable boot animation for a faster boot sequence when needed
boot_anim=`getprop ro.kernel.android.bootanim`
case "$boot_anim" in
0) setprop debug.sf.nobootanimation 1
;;
esac

So it seems we can load up the settings data base and set debug.sf.nobootanimation 1 to turn off boot animations completely using the same procedure as the market place restriction fix(?). Looks like that speeds up boot as well since the devs seem to want to do it ;)
[Captivate Android Development] kenjindomini:
W00T Thank you so much this is fantastic. now I just need the original power on audio from an unbranded galaxy S
[Captivate Android Development] brodie7838:
I hate to be that n00b that de-rails the conversation to ask a basic question, but how do you actually do this step (above)?

I've tried copying the file in Astro, and pushing the file in adb, both resulting in 'Permission Denied' type error responses. I can't quite figure out how to get around the permissions...
[Captivate Android Development] LGSilva:
I use root explorer, the select "mount r/w", navigate to the file and rename it to ".bak" and copy the new one
[Captivate Android Development] LGSilva:
1) To disable the start up sound, in the /etc directory, rename the file PowerOn.wav to PowerOn.wav.bak.

From this thread: http://xdaforums.com/showthread.php?t=731806
[Captivate Android Development] irus:
I like your idea. imho I don't care about looks i just want speed :)
[Captivate Android Development] Phaze13:
I replaced the file amd now I got no animations at all, however I still have the att and samsung sounds.

Odd, maybe i'll try the one posted a few post back.
[Captivate Android Development] Fortune090:
Think this animation swap tutorial should be posted somewhere in the "How to Remove (Almost) Every Trace of AT&T" thread. ;)

EDIT: Got it working. Was a VERY simple process and the plain Galaxy S boot is awesome. Anyone have a link to the original PowerOn.WAV for the i9000?

EDIT2: Nevermind. Found it!

Now to get rid of that elusive ATT World Phone logo...
[Captivate Android Development] irus:
has anyone tried this yet???
[Captivate Android Development] LGSilva:
I was trying to replace the first splash screen (the white one "world phone") but so far no lucky. I had to restore my phone after a bad flash from a custom "tar" file... hehehe

phone -!- computer icon it's no good :P

Does anyone know how to remove or replace that splash screen? do we need to dump the boot loader then patch it?
[Captivate Android Development] sfernandez:
I found this maybe this will explain better than I can

http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/
[Captivate Android Development] LGSilva:
Thanks but that will only work on devices with fastboot. Our Samsungs don't have it...:(
[Captivate Android Development] r_3:
I tried this trying to change the intro video by using the link provided with the original galaxy video. I just get a blank screen without the 3g or galaxy s video now.

I did however edit the wav file to just produce the samsung intro sound.

Any thoughts?
[Captivate Android Development] washow:
so would it brick our phones if we just apply stuff like http xdaforums.com/showthread.php?t=696193 ??
[Captivate Android Development] hokiemoto:
I've seen everyone talk about replacing bootsamsung.qmg to change the startup animation, but what is bootsamsungloop.qmg? It's a much smaller file... how is it involved?
[Captivate Android Development] LGSilva:
That's just the S logo glowing after the animation...
[Captivate Android Development] irus:
Has anyone been able to disable the boot up screens altogether. It was mentioned in post 3 and post 24 but i wasn't sure if anyone has gotten it yet
[Captivate Android Development] rahlquist:
rename the files mentioned early on in the thread if they dont load then they dont run.
[Captivate Android Development] justmart:
Any workaround For the BLACK screen with sound!?!? I get this and I want my boot animation back :D Thanks
[Captivate Android Development] darkamikaze:
Does removing these boot logo actually speed up the boot process or will I just be starring at a blank black screen instead? :o and with that has anyone customized boot logo and sound? and if yes :D video please
[Captivate Android Development] USHERROB:
I keep looking for the PowerOn.WAV from the i9000 but i cant find it! Can you post/pm me the .wav please?

EDIT: NVM, for you guys looking, its on the Vibrant section. Link is here: http://xdaforums.com/showthread.php?t=732311
[Captivate Android Development] mmm_tacos:
It is my understanding we cannot do custom boot screens without editing the .qmg files is that correct? I looked at the files and can some what make out the header, but the data is compressed it seems. The .qmg file is just an archive of many qm files. It looks like the "image" section is broken into 3 parts.

This what I see when I look at the QM header.

dword - magic (QM)

word - ? (128 always?)

word - screen dimension X (480 my device)

word - screen dimension Y (800 my device)

word - unknown (always blank?)

dword - offset to last chunk (#3?) (this offset leads to two repeating file size dwords)

word - # of frames

word - current frame number

word - always blank??

word - always 1??

dword - offset to middle data chunk or (1st chunks size)

dword - unknown only seems to have a value on the first entry of the file

Each new frame has its own QM file. So for instance in the bootsamsung.qmg there are 97 QM files in the .qmg.

That was my 10 minute look at the file. If the data is compressed it is something lightweight and would explain the rather big file sizes.

Anyone mess with it?
[Captivate Android Development] tazman171:
I just did the Galaxy S screen just as described and that boot up screen is really sharp. Also have Mudvayne playing during bootup. :cool:
[Captivate Android Development] adfree:
Hello.

It seems we have same problem but different handsets. :)

I have S8500 Wave...

http://www.badanation.de/topic.php?t=222&page=6

*.qmg files ( single Pics, no Animations) are packed into ZIP Archiv *.smt.

These are our Themes. :)

Now I took bootsamsung.qmg._____kkm from yours.

Thanx to Uploader.

"Cut the first Frame" and now I have white Background.

After playing a little bit... I have now yellow Screen. 480 x 800 Pixel.

Changed 8 Bytes...

Also I was able with changing few Bytes to make lines in the bottom of Picture...

Interessting is. My changes leads not to Error or Reset. It seems we could change and try... maybe we find Algo.

Lets work together.

Best Regards
[Captivate Android Development] mmm_tacos:
If the headers are the same for your qmg files you should change these 2 bytes in your file to 01 00 at the very least.

http://i.imgur.com/wZ0t2.png

Based on everything I've seen this 16 bit value represents the total number of frames present in the qmg. I'm assuming it compares the next 16 bit with the 16 bit value I've selected and if the value I've selected is higher than the other it continues on.

I've attached my battery charging qmg (you see it when the phone is off and you plug USB in on the captivate). You can try slicing off the the first QM and then adjusting the total number of frames to 1 (the value placement I've selected in image should say 5 originally). If it works it should most certainly not be all white.
[Captivate Android Development] adfree:
Thank you for posting.

I will try soon.

Most of our qmg files have IHDR on correct Position for PNG...

But I was not able change correct Bytes to make valid PNG... :o

Maybe QMG allow RAW or PNG uncompressed/compressed... :confused:

Attached few examples. Maybe you see more.

Screenshot is from other Pic with Resolution 104 x 107...

Thank you.

Best Regards
[Captivate Android Development] mmm_tacos:
Well, it looks like the short at 0x4 is how we determine the version. Your file is quite different than ours. The only thing that suggests PNG is the IHDR in the file, but the image is most certainly not zlib compressed as far as I can see.

Do you have any different ones that are not battery icons?
[Captivate Android Development] adfree:
I have attached from incoming devices... lower Res 240 x 400...

S5250

S5330

Extracted from Firmware...

To find Resolution of QMGs easier look into:

SamsungThemeTouchwiz3.xml

Best Regards and thank you.
[Captivate Android Development] mexiken:
Can someone please re up the samsung i9000 boot animation???? The link in the other thread is down
[Captivate Android Development] adfree:
@ mmm_tacos

This is what I can see if I use your battery_charging_100.qmg without Modification.

Sorry for late answer, but as you can see, sooo many replies... :( :(

Anyway. Thank you for uploading. :cool:

Best Regards
[Captivate Android Development] mmm_tacos:
That was exactly what it is supposed to look like. :)

I'm still looking at your files. I haven't had any luck or much time so far though.
[Captivate Android Development] BodaciousDrake:
Has anyone tried this?

This question has been asked before, but no one has said anything yet....

EDIT: I can't find any setting in settings.db that looks like it would accomplish this. Maybe in another db?
[Captivate Android Development] xayatox:
i found the jpg with the ATT World Phone... but I haven't been able to remove it.

check it out and let me know what you think!

/data/data1/logo_ATNT.jpg
[Captivate Android Development] adfree:
Our problem solved, as Samsung released Theme Designer...

with QMG compression. :cool:

http://innovator.samsungmobile.com/down/cnts/toolSDK.detail.view.do?platformId=13&cntsId=7860

Seems NO Animation support... but better as nothing. :)

Best Regards