Hey, I'm trying to make a advanced Sense UI taskbar for metamorph... one of the images is bigger in resolution (not file size), than the original image... well lets say it bricked the launcher from running when applied.
Is there a file in the launcher.apk that gives size restrictions?
Thanks! I can't wait to get this done so you all can use it!
is this impossible, or no one knows? i need to know...
Related
To the chefs who are having lockscreen bug issue.
I was browing the images of my manila folder and noticed that the one of the default images was a full size screen graphic. When I looked at the same file with my custom wallpaper made with HDWall the same image was half the size of the original image.
So I ask...have you used HDWall to make your manila bacground?
I have been testing a ROM with default background and the bug has not come up so I am leaning towards maybe it is the way how HDWall converts the image file to manila.
At0mAng said:
To the chefs who are having lockscreen bug issue.
I was browing the images of my manila folder and noticed that the one of the default images was a full size screen graphic. When I looked at the same file with my custom wallpaper made with HDWall the same image was half the size of the original image.
So I ask...have you used HDWall to make your manila bacground?
I have been testing a ROM with default background and the bug has not come up so I am leaning towards maybe it is the way how HDWall converts the image file to manila.
Click to expand...
Click to collapse
i made the background in manila editor, not HDWall, and i still got the problem, so maybe its something else to, cause i got less "broken" lockscreen.
and yes it would be nice to get it fixed, and i did'nt have this problem with the same MS build and manila 2.1.
smaberg said:
i made the background in manila editor, not HDWall, and i still got the problem, so maybe its something else to, cause i got less "broken" lockscreen.
and yes it would be nice to get it fixed, and i did'nt have this problem with the same MS build and manila 2.1.
Click to expand...
Click to collapse
Post your manila background files and let me take a look. Are you just having with 2.5?
At0mAng said:
Post your manila background files and let me take a look. Are you just having with 2.5?
Click to expand...
Click to collapse
well im sorry im just reflashed to 2.1 now, and will soon flash other build, so im not in position to share them atm.
playing to much to get some version fast, stable, touch x like
but no problem with manila 2.1 and hdwall either. so i think the problem lies in with block in nk the modules go, and how many modules, cause the more modules the worse lockscreen and the slower manila, and more "memoryleak in the new manila 2.5.
i got much moore lockups with the new 2.5 and by not converting modules to files in OEM and some sysfiles i also got more lockups!
keeping the modules under 500 and running a xip newer than 2302x with any sys version does go flashing fast, and without memoryleak if you run maila 2.1. so its quite a dilemma
Manila 2.5 and 2.1 handle the the background diffrently and I believe this is what is causing it. In my 2.1 and no TF3D ROM I do not have the issue but in 2.5 I do.
hey,
i don't know if that helps you somehow, but the bug does only appear for me if my phone is in suspend-mode for some time (at least 1-2 hours). if it goes into suspend mode for let's say 30-45mins the bug doesn't appear.
I think this issue has been fixed by now
you might want to look here:
http://forum.xda-developers.com/showthread.php?p=4182640#post4182640
Simple, make the images you want for the BG & name them LS_BG_P.png & LS_BG_L.png or what ever you want. Now set these in \Windows of your ROM. Next, open LS_Global_(Resolution).cpr. Change the Source="(whatever)" to the file path of your image. Done, now the Lockscreen will use this image. Normally it is set to ConfettiPlus::WallpaperBitmap, which is the stwater from the in-use Theme/.TSK.
drkfngthdragnlrd said:
Simple, make the images you want for the BG & name them LS_BG_P.png & LS_BG_L.png or what ever you want. Now set these in \Windows of your ROM. Next, open LS_Global_(Resolution).cpr. Change the Source="(whatever)" to the file path of your image. Done, now the Lockscreen will use this image. Normally it is set to ConfettiPlus::WallpaperBitmap, which is the stwater from the in-use Theme/.TSK.
Click to expand...
Click to collapse
can you elaborate on to why this fixes the lockscreen half size screen issue?
not being a graphic artist/person myself I am just curious
At0mAng said:
To the chefs who are having lockscreen bug issue.
I was browing the images of my manila folder and noticed that the one of the default images was a full size screen graphic. When I looked at the same file with my custom wallpaper made with HDWall the same image was half the size of the original image.
So I ask...have you used HDWall to make your manila bacground?
I have been testing a ROM with default background and the bug has not come up so I am leaning towards maybe it is the way how HDWall converts the image file to manila.
Click to expand...
Click to collapse
If you use Leo packages from sys you will not have this problem
I dont have photoshop, but i need to have a see through or opaque picture to use as my lockscreen background. can anyone help me, or even make a quick one? with a grey background if its opaque.
BUMP! come on people someone must have photoshop, this would only take 5 minutes.
doesn't the one from the other thread work?....
http://www.mediafire.com/imageview.php?quickkey=idhtmtuqyrm
..... Then have a play with DroidExplorer?... apparently it can do the ADB stuff for you......
EDIT..... Droid Explorer - 0.8.6.0 [06/19/2010] - Conan O'Brian Edition
Why someone with photoshop. It's just as doable with Gimp, a totally free image editor.
i dont have an image editor, slash i didnt know that. And its not the actual lock screen or anything i need.
i downloaded lockbot and you can use your own image as the background, so if i got a transparent one then i would have a transparent lockscreen..
http://forum.xda-developers.com/showthread.php?t=707599
i modified the file from Cronos 1.7.1 so i'm not sure it will work for villainrom...
if you do want to try it ... do a nandroid or bart backup before you PUSH the file onto /system/framework folder
i think i tried that one before, but i'm not sure, i'll give it a shot.
it says verification failed?
If your looking to set an image as a lockscreen background its not as easy as having a transparent image. Android does not treat it as if it is transparent.
Hoping someone can work out a fix soon though.
oh i see. well thats helpful thanks. Also when trying to flash all these zips that people are putting together for me, when i try to flash them i get an error "verification failed"!!
archie winnington-ingram said:
I dont have photoshop, but i need to have a see through or opaque picture to use as my lockscreen background. can anyone help me, or even make a quick one? with a grey background if its opaque.
Click to expand...
Click to collapse
use GIMP instead.
Lennyuk said:
If your looking to set an image as a lockscreen background its not as easy as having a transparent image. Android does not treat it as if it is transparent.
Hoping someone can work out a fix soon though.
Click to expand...
Click to collapse
There was a Vanilla ROM with transparent locksscreen. I think it even was SuperHero and I remember it coz people did not like transparent lockscreens. It made screen look messy. Also some other vanilla ROMs have semi transparent lockscreens - it shows only wallppaper, not all icons and widgets - which I found very cool, especially if you like live wallpapers. I want to make it work on sense ROMs, don't know how so
for future reference:
fotoflexer.com
free online image editing.
Have you got a rooted phone?
hello everyone,
i am trying to port the HTC_IME to a 240x320 res phone, (their is a current one floating around on here but it looks funky) so i have the .png files all resized and thats working fine the keyboard predicts and everything just fine but in each of the keys the letters are just slightly too big, what file controls the size of that
if not could anybody tell me which file controls the size of the keys to make them bigger?
also if its an xml file what would be the best way to go about making the changes?
Why not just rip off the wildfire one?
Sent from my HDfied HTC Desire
K900 said:
Why not just rip off the wildfire one?
Sent from my HDfied HTC Desire
Click to expand...
Click to collapse
so the one for the cm build is the same as the one we already have and it looks really odd, as far as pulling it directly i dont think you can i thought it needs the roise framework to run
Okay,
I was fiddling around with boot animations on my sensation an made a sweet one that i like from a couple of youtube vids all credit goes to them ie korea android ad and i think a fellow in a design class made the other one (look below i have attached) but when i tried to do the same for my xoom i got stuck in the boot animation where it kept recylcing the boot and never actually booted into the rom... to say the least i had to do a nandroid to get back just from a boot animation which kinda sucks... anyway ill lay out the specifics
1. I used jpgs, same as with my sensation they seem to work just as well as .pngs but keep the zip much much smaller and dont look choppy
2. I use the original boot animation from the tiamat 2.2.2 version as my base zip file which i edited with my pictures
3. I used the actually spec'd dimensions of the xoom of 1280 x 800 for the pictures, however i noticed that the boot from tiamat used 704 x 440 maybe that could be it (i will be trying that now and report back)
4. as my boot time took a while i thought i may try to use 900 images (a bit dumb i know, in my sensation i use 400 and it gets through them nicely, each pic is a pretty quick segment tho) (i will edit the same amount as my sensation and try again)
can anyone shed some light onto why mine may not have worked other than the amount of pics..
here is a youtube link for what i actually made
boot
i tried to just change the resolution to 704 x 440... and i deleted half the images... and tried again... again it kept replaying and never actually booted into the rom so again i am nandroiding lol
You will need to edit your desc.txt file
1408 880 24
p 0 0 part 0
put all your pictures in folder named part0.
Then zip folder using 7zip and make sure you choose store as compression method.
Hope this helps.
i have done that but used done3 as my folder name.. as i said i used the tiamat moray boot animation as my base zip =]
the name of the folder inside the zip shouldn't make a difference especially as i got it to play but it keeps playing and playing a small bit and not the whole file nor booting into the rom...
on all my bootanimations, it helps if you make each image 960 x 600.
then on your desc.txt file, make the screen size 1280 x 800 (the correct size for the xoom).
sometimes if there is an extra pixel hanging off it could cause you to blackscreen or bootloop.
also, sometimes you'll get a bad jpg file, that could also cause the black screen or bootloop.
best suggestion would be to get the desc.txt file from a known working bootanimation and just adjust the frame rate. be sure to hit enter for a new line after you have put in the info for the last part folder.
oh, and a little trick i found. use the bootanimation installer to push the bootanimation, then restart the xoom and be sure to close the bootanimation installer.
leave your xoom connected to your pc. if you do get into a bootloop, wait a few minutes for it to loop then just reopen the bootanimation installer and push a known working bootanimation. after a few seconds the new bootanimation (or default one) should show and should boot normally. this is my procedure.
Sardo Numspa said:
on all my bootanimations, it helps if you make each image 960 x 600.
then on your desc.txt file, make the screen size 1280 x 800 (the correct size for the xoom).
sometimes if there is an extra pixel hanging off it could cause you to blackscreen or bootloop.
also, sometimes you'll get a bad jpg file, that could also cause the black screen or bootloop.
best suggestion would be to get the desc.txt file from a known working bootanimation and just adjust the frame rate. be sure to hit enter for a new line after you have put in the info for the last part folder.
oh, and a little trick i found. use the bootanimation installer to push the bootanimation, then restart the xoom and be sure to close the bootanimation installer.
leave your xoom connected to your pc. if you do get into a bootloop, wait a few minutes for it to loop then just reopen the bootanimation installer and push a known working bootanimation. after a few seconds the new bootanimation (or default one) should show and should boot normally. this is my procedure.
Click to expand...
Click to collapse
Sweet ill try that.. I tried 3 dimension sizes the true size, and 2 dimensions i got from boot animations with the roms.. I reduced the number of jpgs..
One last thing what setting do u choose for your jpg in photoshop? Or do u jyst use pngs.. I can use setting of 6 medium sized compression for me sensation even tho it works for my phone that may be affecting the xoom
Sent from my mind control device
doesnt really matter the file size. we've made bootanimations with upwards of 7 parts and 200+ mb.
i would say try it first with pngs and if it works then convert to jpgs. i use a file sizing program to make sure of the picture ratio, it gets rid of any of those hanging pixels.
Sardo Numspa said:
doesnt really matter the file size. we've made bootanimations with upwards of 7 parts and 200+ mb.
i would say try it first with pngs and if it works then convert to jpgs. i use a file sizing program to make sure of the picture ratio, it gets rid of any of those hanging pixels.
Click to expand...
Click to collapse
Well considering i set canvas size with photoshop that constricts pixel dimensions quiet well but ill take ya advice and try that and i might split it up too
Sent from my mind control device
also remember that there is a file number limit per part (folder).
looks good
Success it would seem.. Jpgs are fine.. I think i have found the upper limit of pictures no matter the amount of folders.. The 130 per folder helped.. Will update when i get home from work
Sent from my mind control device
Hey, is there a method to replace the standard white-ish backround of an app (e.g. Settings) with a custom wallpaper?
If I decompile .apk - can I replace a .png? (simply as that?)
I'm obsessed with X10's 1.6 look (that sexy-blue theme) and wondered if I could transform some of my apps (Conversations, Settings, Contacts) to look like that.
I hope someone will reply, thanks! :silly:
P.S. If there's an easy way to create a theme - it would be even nicer!
weekender90 said:
Hey, is there a method to replace the standard white-ish backround of an app (e.g. Settings) with a custom wallpaper?
If I decompile .apk - can I replace a .png? (simply as that?)
I'm obsessed with X10's 1.6 look (that sexy-blue theme) and wondered if I could transform some of my apps (Conversations, Settings, Contacts) to look like that.
I hope someone will reply, thanks! :silly:
P.S. If there's an easy way to create a theme - it would be even nicer!
Click to expand...
Click to collapse
I don't know how to create a theme, but on the LT29i, you can replace the "semc_bg_light.png" and "semc_bg.png" files in "/res/drawable-xhdpi" from the "framework-res.apk"; and, I think you might just be able to do this with 7zip, no need to decompile (don't take my word for it because I always decompile anyway).
Antiga Prime said:
I don't know how to create a theme, but on the LT29i, you can replace the "semc_bg_light.png" and "semc_bg.png" files in "/res/drawable-xhdpi" from the "framework-res.apk"; and, I think you might just be able to do this with 7zip, no need to decompile (don't take my word for it because I always decompile anyway).
Click to expand...
Click to collapse
Good, thanks a lot! Will try this weekend.