Hi there,
I am running this Rom and made my own bootanimation with photoshop.
It's 480x480, 72 dpi (I also tried different dpi values) and I tried it with color management (sRGB) and tried it without color management as well.
I put the bootanimation.zip into /system/media with ES Explorer. Until here everything works fine.
But when I reboot, instead of my animation, all I see is the logo.rle (which I customzed as well and works fine) for longer than usual and then a black screen until the boot is finished.
I attached my animation. Hopefully someone has a clue why it doesn't work.
Thank you in advance
Alright. I found the problem myself. -.-
Solution:
The images have to *.jpg's without color management.
dimmu2k said:
Alright. I found the problem myself. -.-
Solution:
The images have to *.jpg's without color management.
Click to expand...
Click to collapse
Are you serious? i've been messing around with this and getting really frustrated...
Especially since the first part plays it's .png's, but then the screen goes black when the second part should start...
I'll try this later today, on an SGS2 with CM10/PA.
EDIT:
Nope, didn't solve it for me.
After a few tries with different file names for the images, only the first part would play, and all of a sudden all i had was a black screen...
Reinstall ROM...
Related
I've been playing with the ThemePorter app and loving it. But while I have the new rom open and swapping the .pngs from the old theme to the new rom I thought I could change the fonts too. I picked a font I liked (.tft format), deleted the old fonts and installed the new ones with all the same names as the old ones (Clockopia, DroidSans, etc etc) but once I zip the rom back together and sign it, it won't load. ADB logcat gives me issues like media_flinger died, and the other media stuff in that library has died warnings too. This makes the boot screen hang and the rom won't load despite complete install. Obviously there are other ways to change the font, so that's not a big deal. I'm just trying to understand how this stuff is connected. I did double check and this can be the only problem. I just unzipped the rom, replaced the original font folder, signed, and rebooted just fine. Any ideas?
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App
futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~
Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"
Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.
I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.
Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?
im using mdj 2.3 clean and S6 kernel.
ive done 2 things and android dont go past black screen and HTC logo.
first i put the new build.prop to fix the green camera, while in windows mobile, inside SD/ANDROID/ROOT/SYSTEM/build.prop
i didnt boot android yet, i created a folder inside SD/ANDROID/ROOT/SYSTEM
called FRAMEWORK and i put framework.jar for RTL inside:
SD/ANDROID/ROOT/SYSTEM/FRAMEWORK/framework.jar
now i tryed to boot android and no success.
what i did is remove all changes but still android wont boot.
what might be the problem/solution?
im trying to save my build here cus i did alot of changes and i have no backup.
i think its the build.prop that wasnt compatible, what can i do to fix it?
eeeeeee said:
im using mdj 2.3 clean and S6 kernel.
ive done 2 things and android dont go past black screen and HTC logo.
first i put the new build.prop to fix the green camera, while in windows mobile, inside SD/ANDROID/ROOT/SYSTEM/build.prop
i didnt boot android yet, i created a folder inside SD/ANDROID/ROOT/SYSTEM
called FRAMEWORK and i put framework.jar for RTL inside:
SD/ANDROID/ROOT/SYSTEM/FRAMEWORK/framework.jar
now i tryed to boot android and no success.
what i did is remove all changes but still android wont boot.
what might be the problem/solution?
im trying to save my build here cus i did alot of changes and i have no backup.
i think its the build.prop that wasnt compatible, what can i do to fix it?
Click to expand...
Click to collapse
I had something similar happened to me as well...no changes yet it won't boot all the way anymore. Stuck on green HTC screen. I suspect file corruptions so I redownload the clean build, move my data.img to it, fix! You can give that a go. Good luck.
azzzz said:
I had something similar happened to me as well...no changes yet it won't boot all the way anymore. Stuck on green HTC screen. I suspect file corruptions so I redownload the clean build, move my data.img to it, fix! You can give that a go. Good luck.
Click to expand...
Click to collapse
im doing it right now
EDIT: im trying replacing the rootfs only maybe this will solve it.
EDIT: replacing rootfs with original solved the problem
Anyone running Taboonay 2.0 and got cell standby off...? How
delete phone.apk and telephony.apk from system/app always works for me. I hear editing the build prop works for some and not for others, same with tabtools app.
shaun298 said:
Anyone running Taboonay 2.0 and got cell standby off...? How
Click to expand...
Click to collapse
Thanks I will give it a try. One warning to other 2.0 user, I added the wifi= thing to the build.prop file and rebooted. Took for ever to come up, lost the splash screen and running 10 times slower and when I touch the app botton at top right to go to applications, the screen goes blank and finaly goes back to desktop. I restored the backup build.prop and rebooted and had the same thing.
The file had correct permission.
Tried other things, but in the end just reflashed.
Thanks for the tip
Update.
deleteing phone.apk locked it up and had to hold power botton in.
deleteing the telphony did not crash anything.
Just renamed both files did not work seems everything in that folder gets run.
The cell.standby icon is still their but its not using the bat.
Maybe erase bat statts..?
Now got to go and see what broke. Im so burnt on roms I could puke, luck Im between jobs and have massive hours to play. Thanks for the help.
using Thor's latest kernel and editing build.prop did the trick for me, with no need to touch phone or telephony.
So today I was trying to look up on how to replace the system icons and such, so I extracted some file I cannot rememeber the name of it and replaced the images from in it with the ones I wanted, then I applyed the stuff with an app and it said I should reboot for it to work, however when it was displaying processing it crashed, and rebooted on its own. It will keep looping in the boot animation, and I'm not sure if I'm gonna have to go back to stock. And fyi I am using manualnooter.
I dont understand how it isnt working and all I edited was pictures, plus a few xmls.
Here are the name of the xmls edited if you need (all of them have nav_ in front of the name)
home.xml, jump.xml, library.xml, quickbutton.xml, search.xml, shop.xml, shop_in_store.xml, web.xml
and if your wondering what pictures were replaced from what I can tell only the status bar stuff was replaced. (i.e. c_back.png)
Also, I was trying to use the SystemUi.apk to change it, but i could not find it. so I found something else that had the icons. (trying to find the name of the file right now)
Edit: I replaced files inside of system\framework-res\drawable-mdpi\
(sort of) Resolved: I had booted a couple different recoveries, until it would get stuck on the 'N', then I did the 8 fail boot and it loaded back up to stock. Guess I'll just reflash manualnooter.