I tried to create a Ghost in the Shell Laughing Man boot animation, but it doesn't seem to be working for me. Think anyone could take a look at it? Here is a link:
http://www.mediafire.com/?2r6i7gb89sc7ac9
I just can't figure out where I'm going wrong. Any ideas?
Credit for the images goes to Sushiman0001 and Nocturnophile.
SolsticeZero said:
I tried to create a Ghost in the Shell Laughing Man boot animation, but it doesn't seem to be working for me. Think anyone could take a look at it? Here is a link:
http://www.mediafire.com/?2r6i7gb89sc7ac9
I just can't figure out where I'm going wrong. Any ideas?
Credit for the images goes to Sushiman0001 and Nocturnophile.
Click to expand...
Click to collapse
Your desc.txt is wrong.
Should be
480 800 30
p 0 1 part0
PS: You might want to optimize the png images.
theidlemonk said:
Your desc.txt is wrong.
Should be
480 800 30
p 0 1 part0
PS: You might want to optimize the png images.
Click to expand...
Click to collapse
Thanks for the tips. I'll try those. Any advice on a good program to optimize PNGs?
EDIT: I tried changing my desc.txt, and still no dice. Any more ideas?
SolsticeZero said:
Thanks for the tips. I'll try those. Any advice on a good program to optimize PNGs?
EDIT: I tried changing my desc.txt, and still no dice. Any more ideas?
Click to expand...
Click to collapse
Try PngOptimizer, fairly simple to use. Also, the desc.txt should be edited with a program like textpad or equivalent so it saves as an unix file.
theidlemonk said:
Try PngOptimizer, fairly simple to use. Also, the desc.txt should be edited with a program like textpad or equivalent so it saves as an unix file.
Click to expand...
Click to collapse
I'm using notepad++. Would that work?
Yes that should work, but make sure you specify that its an unix format file not PC. Also the dimensions of your images are 480 x 854. The evo is 480 x 800.
Attaching edited desc.txt
theidlemonk said:
Yes that should work, but make sure you specify that its an unix format file not PC. Also the dimensions of your images are 480 x 854. The evo is 480 x 800.
Attaching edited desc.txt
Click to expand...
Click to collapse
Awesome, thanks. I'm going to crop the images, optimize them, and then use your desc.txt.
Also instead of fps of 30 like in 480 800 30, try 10 like as 480 800 10
Related
I'd like to change the look of the frame used with the picture frame widget, but I can't find the image anywhere in the ROM (CM 4.1.999). Anyone know where I might find it? Thanks!
Camera.apk/res/drawable/appwidget_bg.9.png
daveid said:
Camera.apk/res/drawable/appwidget_bg.9.png
Click to expand...
Click to collapse
thank you
Awesome. Thank you!
Edit: Hmm ok, so I went in and replaced the default image with one I made, almost exactly the same except it's got sharp corners (I know, I'm picky). Anyway, I went ahead and repacked the apk and pushed it thru adb to /system/app. Now, the default frame is gone, but the one I made isn't showing up. It's like there's no border at all. Thoughts? I used Photoshop,, same dimensions as original with transparent background, saved as PNG.
this image is a ".9.png", are you aware that these have to be edited and compiled correctly to work correctly? You should search the theme forums for "draw9patch", it is a tool that is used to properly recompile these images.
A ".9" is a strechable image that has guide-lines on it that tell the OS where to stretch the image. then you must use eclipse to recompile the images, and THEN they will show up and work correctly.
If you need any help, or a good in-depth explanation of how this works, lemme know...
-BMFC
bmfc187 said:
this image is a ".9.png", are you aware that these have to be edited and compiled correctly to work correctly? You should search the theme forums for "draw9patch", it is a tool that is used to properly recompile these images.
A ".9" is a strechable image that has guide-lines on it that tell the OS where to stretch the image. then you must use eclipse to recompile the images, and THEN they will show up and work correctly.
If you need any help, or a good in-depth explanation of how this works, lemme know...
-BMFC
Click to expand...
Click to collapse
Thank you! Now I've got something "fun" to look forward to after class.
daewond3r said:
Thank you! Now I've got something "fun" to look forward to after class.
Click to expand...
Click to collapse
If you don't plan to do a lot more "theming" than setting everything up to sign 1 .9.png probably isn't worth it for you.
If you upload the file I'll sign it for you.
nebrada said:
If you don't plan to do a lot more "theming" than setting everything up to sign 1 .9.png probably isn't worth it for you.
If you upload the file I'll sign it for you.
Click to expand...
Click to collapse
Thanks nebrada!
daewond3r said:
Thanks nebrada!
Click to expand...
Click to collapse
not a problem. here ya go! lemme know if it still doesn't look right
nebrada said:
not a problem. here ya go! lemme know if it still doesn't look right
Click to expand...
Click to collapse
It's perfect! Thanks man. Would you mind doing a black one for me as well?
Ok,... My Hero gets delivered tomorrow (my 1st Android device), and I want it to be completely my own. I want to make my own bootscreen... but want to know two things,...
1,... If the preset one already on there loops over and over, or if it just plays once?,... If it does loop, can i change it to only play once?
2,... What size the file of the preset one is so can try making mine roughly the same.
Any help would be much appreciated. Thanks.
ddotpatel said:
Ok,... My Hero gets delivered tomorrow (my 1st Android device), and I want it to be completely my own. I want to make my own bootscreen... but want to know two things,...
1,... If the preset one already on there loops over and over, or if it just plays once?,... If it does loop, can i change it to only play once?
2,... What size the file of the preset one is so can try making mine roughly the same.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
The stock bootscreen is made of 2 gif files. the first one runs 1 time, the second one loops until the phone is done starting up.
tristan202 said:
The stock bootscreen is made of 2 gif files. the first one runs 1 time, the second one loops until the phone is done starting up.
Click to expand...
Click to collapse
Aha,... Brilliant. Does anyone have idea of sizes?!... I could just wait until tomorrow but i really want to make a start on this.
Thank you.
ddotpatel said:
Aha,... Brilliant. Does anyone have idea of sizes?!... I could just wait until tomorrow but i really want to make a start on this.
Thank you.
Click to expand...
Click to collapse
Basically anything up to 320x480. And keep them indexed 255 colors. Then if you have images smaller than 320x480 you place them with a config file.
tristan202 said:
Basically anything up to 320x480. And keep them indexed 255 colors. Then if you have images smaller than 320x480 you place them with a config file.
Click to expand...
Click to collapse
Sorry, i meant file size.
Thanks again Tristan.
ddotpatel said:
Sorry, i meant file size.
Thanks again Tristan.
Click to expand...
Click to collapse
File size doesn't matter that much. Of course there is an upper limit, but I have made all the way from 50kb up to 8mb bootscreens.
tristan202 said:
File size doesn't matter that much. Of course there is an upper limit, but I have made all the way from 50kb up to 8mb bootscreens.
Click to expand...
Click to collapse
You are a DIAMOND!!! Thanks alot for your help yesterday. You'v told me exactly what i wanted to hear, I was afraid the upper limit would be something like 1 mb. Brilliant!!!
I'v got the 1st animations i wanted now. Thank you!
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
Running 200 here on cm 7 with no problems
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
SAPPH1RE said:
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
Click to expand...
Click to collapse
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
shyv said:
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
Click to expand...
Click to collapse
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
lpachuong said:
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
Click to expand...
Click to collapse
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
SAPPH1RE said:
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
Click to expand...
Click to collapse
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
shyv said:
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
Click to expand...
Click to collapse
Hmm, weird.. Try flashing other CM7..
SAPPH1RE said:
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
Click to expand...
Click to collapse
Thx man
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
snowmer said:
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
Click to expand...
Click to collapse
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
truc007 said:
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
Click to expand...
Click to collapse
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
snowmer said:
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
Click to expand...
Click to collapse
Really, this is very easy to do on the phone, without any extra applications. Just use a file explorer with root access (like root explorer), navigate to /system/, open your build.prop file, modify the density line (ro.sf.lcd_density=xxx) to whatever you want and reboot. 190 is working nicely for me (nightly 30/CleanDHD).
snowmer said:
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
Click to expand...
Click to collapse
Sorry, forgot this.
Just type "adb remount" to mount the system in Read/Write instead of ReadOnly
If you're under linux you may need sudo (but don't think so as under w7 you don't need admin...)
I dont see any improvement by changing it to 200 its only bad look now, I will change it back to 240.
And what improvements it should give me, by changing to lower density?
Sent from my Desire HD using XDA Premium App
s2 density at 200 not booting
please assist my s2 is not booting after changing to 200 with lcd density changer on a rooted s2. heeeeeeelp
When try to decompile framework-res.apk I get some errors. I'm using apktool v1.5.2 and java runtime environment 7 update 21, I'll attach the prompt.
Thank you
ThisAwesomeGuy said:
When try to decompile framework-res.apk I get some errors. I'm using apktool v1.5.2 and java runtime environment 7 update 21, I'll attach the prompt.
Thank you
Click to expand...
Click to collapse
Ok its showing you must have made changes to something in res/drawable/nodpi and res/drawable/hdpi,so im thinking it was images?If so you need to make sure the images you use to replace the deafaults,need to be the same resolution and 24 bit format.If you look at the error,you can see your images are exceeding the limit.
Diablo67 said:
Ok its showing you must have made changes to something in res/drawable/nodpi and res/drawable/hdpi,so im thinking it was images?If so you need to make sure the images you use to replace the deafaults,need to be the same resolution and 24 bit format.If you look at the error,you can see your images are exceeding the limit.
Click to expand...
Click to collapse
I haven't changed anything yet because of error. Could it be the original framework-res.apk that is causing the issue?
ThisAwesomeGuy said:
I haven't changed anything yet because of error. Could it be the original framework-res.apk that is causing the issue?
Click to expand...
Click to collapse
If you havent made any changes yet,yes it very well could be.
Edit: Would need to pop this open in a hex editor, and find out what has extra padding. I think density is overflowing its variable. Its a short, which limit I know is around 33000 and some of the densities reported by com.htc.resources is around 66000.
Diablo67 said:
If you havent made any changes yet,yes it very well could be.
Edit: Would need to pop this open in a hex editor, and find out what has extra padding. I think density is overflowing its variable. Its a short, which limit I know is around 33000 and some of the densities reported by com.htc.resources is around 66000.
Click to expand...
Click to collapse
Will HxD Hex Editor work? If so how would I use it? sorry
Jumped ship
Are these boot animation files supposed to be like 80 megs for a single file?
Tiribulus said:
Are these boot animation files supposed to be like 80 megs for a single file?
Click to expand...
Click to collapse
Size can vary on length and its in 1080p probably.
Closed at OP's request