Ok,
following on from, http://forum.xda-developers.com/showpost.php?p=10414748&postcount=22
I've been looking at this thread, I've got to page 12 of 22 so far. think my eyes are gonna melt soon....
unfortunately my knowledge of editing etc is limited to ZERO
http://forum.xda-developers.com/showthread.php?t=710204
I've attached a bootanimation file which is from a HTC phone and the mini pro system/bin folder . If you open it in a file editor and press search for mp3, there's a few lines etc pointing to folders with mp3's in. I think the file also points to other xml files and db files located on the HTC.
If you look at the original bootanimation file on the mini pro located in the system/bin folder there's nothing on mp3 in it.
I've noticed from the line debug.sf.nobootanimation in the mini pro and HTC varies (which is where I found the differences)
I've attached both bootanimation files in the zip below if anyone wants to take a look. I've renamed them accordingly.
I've also posted here http://forum.xda-developers.com/showpost.php?p=10565772&postcount=217 for some helpful info.
I've had a look at the bootanimation file(s) from the HTC one listed here and the bootanimation file in system/bin on the mini pro which tells the phone to look in the media and local folders respectively.
The difference is on the mini pro version it doesn't point to any xml files/scripts etc whereas the HTC one does.
I've tried putting the HTC bootanimation on the mini pro and the animation works fine.
I've also tried adding lines from the HTC file to the mini pro one. I also tried changing the path names on the HTC file to reflect the location(s) of file(s) on the mini pro. I even tried copying the audio file in to several folders.
I've even tried using the bootscreen folder listed somewhere (again pointing to it using the HTC file)
Are there any files etc I've missed that could get the sound working?
Related
Can anyone port this bootanimation for our tattoo, or explain me how to do that? http://forum.xda-developers.com/showthread.php?t=1005201
its much better than the one in nfinity rom....would be great if anyone could help!
I think that it's included in pot kitchen. You can try it.
http://uot.dakra.lt/kitchen/
If it isn't, maybe you'll find another one(have a lot)
They succeeded
Download the file bootanimation.zip
Extract on the desktop the two folders and the file.
Open desc.txt and change the two numbers, write 240 400
Now you have to use winzip, not winrar, to create another file called bootanimation.zip put in the two folders and files changed by choosing "let me choose the specific .." and "zip: no compression".
Any other method has failed
You can also use the original .zip file but the images are too large for the tattoo display
You can follow the instructions of the link
"If you use a custom ROM copy it in the folder data / local
If you use CyanogenMod7 ROM copy it in the folder system / media "
You can use "root explorer" or "adb"
Instructions for adb are:
adb remount
adb push bootanimation.zip /system/media/bootanimation.zip (/data/local /...)
adb reboot
First make a backup of the rom.
sorry, I used google translate
I made edited bootanimation.zip as you say so.. But when I reboot phone I only see black screen.
sure you use winzip as described?
this issue not to use Winzip correctly.
I have redone the same procedure with the original bootanimation and works fine
if you fail to do here is the link
http://www.megaupload.com/?d=WNWIQW7Z
(rename to bootanimation)
If you use some app to change bootanimaton, then you can try puish the file in / data / local
This is because Android first look in / data / local and then in / system / media
I didn't use 'no compression'.. Now it works :]
Your edited bootanimation works great.. Thanks
I edited this bootanimation for our tattoo http://forum.xda-developers.com/showthread.php?t=648555
You can download it from here http://www.multiupload.com/S9T7H8PM03
Well finally i find a solution for my black custom bootscreen.
I made one personal, and was in despair because i could'nt make it appear!
I renamed each files ,changed the file type, tried to make files be a multiple of pic/sec...
Thanks to liupos i found that the winrar compression was the prob
liupos said:
If you use some app to change bootanimaton, then you can try puish the file in / data / local
This is because Android first look in / data / local and then in / system / media
Click to expand...
Click to collapse
can you suggest me an app to choose between bootanimations?
Thank you.
Does anyone have the call of android boot animation with sound for the galaxy s II? I can't seem to find one thats compatable. I have it rooted and flashed with entropy and have a custom boot installed, but I can't seem to find the COA one that works.
Download the bootanimation.zip located in the Attached Files section at the bottom of this post. It is formatted 800 x 480 which is correct for our phones. Copy to your sdcard and then use a root file manager such as root explorer to copy it into the /system/media directory. You may want to rename the bootanimation.zip that is already there so you don't overwrite it. Root explorer is a paid app. Super Manager by GPC includes a free root file explorer is you need one.
For the boot sound, the author provides an mp3 file. Our phone uses PowerOn.wav in the /system/etc directory. So I converted the mp3 to wav which you can download here. (dropbox - click to listen, right click and Save file as to download) Transfer this wav file to the /system/etc directory and you will hear the sound with the boot animation. The only problem is that there seems to be a limit of about 7 seconds on the boot sound. The whole sound file is there, but the phone only plays the first part of it. On my phone, the sound stops about 1 or 2 seconds before the animation stops.
This boot animation is sick, hope it gets properly ported soon
Hello,
How can I tell what version a *.apk file is before I move it to the phone and open it?
I have many email.apk versions and would like to see, which version it is in Win$ows before I try to open and install it on my Vibrant.
Here is an example from the Vibrant-Droid-Razr 2.1 from Fishman.
Tx,
The_Toggle
Apk files are actually zip files, or something similar. You can see what is inside them using file managers on the phone, or probably unzip on a PC. I took a look at one I had, and found the version number by viewing the AndroidManifest as a text file.
I want to change the sound of the phone when I touch it (for selections). I know the directory is system/media/audio/ui, but I don't know how the selection is done from the files within the directory? Do we replace the file with our own with the same filename? Because I changed from one rom (Omega 16.2) to another (Omega 9.2) and I saved in my pc the folder /system/media/audio/ui from both roms to compare them. Although both roms have (almost) the same files in the directory, the touch sound (which is the one I want to change) is different. So how do I choose which file the system uses for each operation?
For anyone interested, I found that it was the file Effect_Tick.ogg in the above directory
After hours of decompiling and things alike, I finally managed to extract the Oppo Colour OS 2.1.x files from the .dat file. But Once I extracted the folders and other things. I come to the launcher folder which has 3 things in the root of the Oppolauncher folder. A folder names "arm", another folder named "lib", and the launcher apk file itself. I know by past experience (Haven't tested myself.) That the apk needs those two folders. (theres also a folder names "oppolaunchersystem" with an arm folder and "oppolaunchersystem.apk.") In order to port these apk files for use with Lollipop devices (Colour OS 2.1.x I believe is lollipop.) Do I have to implement the lib and arm folders (maybe the launchersystem apk)? And if so, how? Thanks for anyone willing to help me with creating the system dump.
I attached the two folders in a Zip file for anyone who wants to examine it.
Sorry for my bad English if I made any errors.
{EDIT} I tried installing OppoLauncher.apk through ADB and I got back [INSTALL_FAILED_DEXOPT] and with OppoLauncherSystem.apk I got back [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]. So it seems that OppoLauncher will work on the device I tested it on (Droid Ultra on 4.4.4) but It needs some sort of resource within the Colour OS 2.1 .x ROM.