Related
Hello!
I'm trying to make my own Rom right now. With dsixda's Kitchen it isn't very hard to do so I thought I'd just give it a try. I'm taking a rooted official Update (Version: 2.10.405.2) as my base. Adding busybox runparts, the /data/app functionality, a2sd+, the custom bootanimation functionality etc. isn't a problem. Removing some apps like Maps, Facebook, Teeter (and so on) and adding some like Rom Manager, Neocore or Quadrant isn't a problem, too. But if I want to implement a theme like the Carbon Espresso Mod or a theme I made with the UOT Kitchen I'm getting bootloops at booting the phone. Here's what I do: I unzip the folder (for example a theme made with the UOT Kitchen) and I copy over the framework-res.apk from the unzipped folder to my Working Folder of the Kitchen (to system/framework) and I overwrite the original framework-res.apk.
And NO: I didn't choose a battery mod or a bootanimation in the UOT Kitchen....
Hope you guys can help me
I might be wrong but doesn't the new file have to be signed? I know there is a signing option in the kitchen.
Sent from my PC36100 using Tapatalk
It's a system .apk so it doesn't have to be signed.
I can't shed any light on the subject, but here's a bump.
Are you replacing the whole "framework-res.apk" file? If so then you will need to resign your entire ROM. Why? When you change a system file ("framework-res.apk", "com.htc.framework.apk", "twframework-res", "rosie.apk", etc.) it no longer has a matching "signature" for all the files it serves images to. Plug your phone into your computer and open up "ddms" in your android_sdk > tools folder to watch what happens when the phone boots up.
A workaround (The way I do it, it's more fun IMHO) is to open up your .apk files in 7zip (or if you're on a mac BetterZip) and add the images from the themed .apk to your stock .apk. This way makes it so your original .apk has the same signature as your other system files yet has the new images from the other files that you wanted. I've had a lot of luck with this method. I don't know if it will still work if you change any .xml files as I have not messed with those yet.
I've subscribed to this thread so if you have any questions post back here or you can PM me if you want. I'm on XDA all day, every day so I'll try to help as much as I can.
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
DomiKamp said:
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
Click to expand...
Click to collapse
The kitchen signs the .zip that you flash when you build it. It does not sign any .apks for you on its own. However, there is an option to sign .apks within the kitchen.
In my opinion, taking all of the images and figuring out how it all works is fun. I feel like I've already learned quite a bit from just digging around and moving files around.
As for the .xml files, you can decompile the .apk and edit them and then recompile the .apk. I'm actually looking into this today. It sounds like some work but hopefully I'll get it figured out.
Sounds like fun indeed So, I'll just have to try it. Where can I find the "Settings" for the Notification Bar? Thanks
The variois status*.xml files in the res/layout folder of the framework-res.apk and the status*.smali files in the services.jar.
What? If I want to implement a Theme made with the UOT Kitchen (without battery) I should just copy over those files to my existing res-framework.apk OR copy over the whole res-framework.apk (the new one) and sign it?
EDIT: Just tried it with a theme from the UOT Kitchen and it worked perfectly. I've just signed the res-framework.apk and the htc.com.resources.apk (or whatever) in the Kitchen, flashed it on my Phone and it just worked like a Charm. But I have got a 50% Transparent Notification Bar and all the system icons (Battery and time/date) are still black and not transparent! Has anyone got a idea where to change this? (.xml or whatever)...And does anyone know where I can find the HTC Wallpapers? I want to change them a little bit
HeyItsLou said:
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
HeyItsLou, I looked up your ROM thread but couldn't locate the video tutorial.... do you mind providing the url? Specifically, I am trying to add to the list of wallpapers in a ROM. (I have setup apktool but not sure where/which folder to add my wallpapers in Framework-res.apk Launcher.apk before recompiling/signing). Thanks.
You COULD use the Theme Porter by daneshm90. It will only port the PNG s for it so things like clock colour n stuff will be lost, but it will get you alot closer...
http://forum.xda-developers.com/showthread.php?t=737526
Sent from my HTC Hero using XDA App
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
DomiKamp said:
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
Click to expand...
Click to collapse
Isnt that what I said in the 2nd post -.- lol jk. Glad you got it working!
Yes! And that's why I tried it. And it worked! Thanks Husker and, of course, everybody else!
Glad you got it working. Welcome to the development side of android!
Sent from my PC36100 using XDA App
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
bestialbub said:
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Click to expand...
Click to collapse
I was curious about this too. I always edit the framework-res of any ROM I flash using a custom set of images I have and have never signed the apk afterwards and it has always worked. Maybe cause I'm only replacing images? I usually do this with framework-res and twframework-res and they both can sometimes grow by 1MB or more. Just my experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
DomiKamp said:
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
Click to expand...
Click to collapse
I think that in order to do the "welcome to" thing you'll have to edit the update-script file. I'm not 100% on it though. Look at a cm Rom and see what all is in there.
Sent from my HTC Evo 4G using XDA App
(I'm new at this, any help would be appreciated)
I'm using Daneshm90's (very awesome) APK Manager to mess around with my framework-res.apk file. I've sucessfully reskinned some pngs and changed some xml files and stuff like that.
Why does the following cause a bootloop?
1) Decompile Framework-res.apk
2) Make a copy of res\drawable\btn_default_small.xml and rename it btn_default_small2.xml
3) Change the background of something to android:background="[a]drawable/btn_default_small2"
4) Compile\flash to phone etc, watch it bootloop
(please note: [a] is really the email 'at' symbol, the forums get mad at me for using it)
I can edit existing files just fine, but whenever I try to add and use a new file everything grinds to a halt, even if its just a copy of a working 'stock' file. What am I missing? Is there a list of files somewhere I need to add my new xml file to? Should I be building from source instead of using apk manager?
I've seen it asked quite a few times now, so I thought I would share how I've been creating my own themes for the Nook. This is a quick and dirty guide as I've almost got it down to a science for quick, keyboard shortcut, theming.
Things you'll need
Photoshop or The Gimp for editing files
Android SDK so you can push and pull files to/from the Nook.
draw9patch app in the Android SDK /tools folder for creating 9.png files
APK Manager (http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1)
Notepad++ or some other text editor for editing XML files. After using Notepad++ on this, I'd highly recommend it though
An attention span
Some restraint
This is a rather good guide that helped me get started. My only complaint is that it is almost to complicated and includes more information than what is needed for a basic theme.
http://forum.xda-developers.com/showthread.php?t=916814
Getting Started:
Download the Android SDK and get it installed.
Download APK Manager
ADB pull /system/framework/framework-res.apk
Make a copy of the framework-res.apk files as a back-up in case you need to revert
Copy the framework-res.apk file to the /place-apk-here-for-modding folder under the APK Manager folder
Launch the APK Manager Script.bat file
Type in 22 to select the default project
Type in the number next to framework-res.apk in the list to select it as your project
Select 1 to extract the files
Select 9 to decompile (this is what makes the XML files readable)
Go to the /projects/framework-res/res folder under the APK Manager folder to view all the files from the theme
Images are located in the /drawable-mdpi folder. XML files are located throughout, but the files specific to layout are under the /layout folder. To change global settings, such as color codes and strings, edit the XML files under the /values folder.
Creating custom PNG files: If you are using Photoshop, use the Save For Web feature when saving. Save the image as PNG-24. Select None under the Matte option. Select None under Metadata.
A word on 9.png files: 9.png files are files that can be stretched by the OS. There is a 1 pixel border all the way around the image. In that 1 pixel border, you'll notice solid black lines here and there. The black pixels indicate which portions of the image are to be stretched. You can add this border and the black pixels in Gimp or Photoshop, or you can open the file the draw9patch app under the Android SDK /tools folder. The draw9patch app will actually display how the image will look when stretched as you add the black pixels around the border, so it can come in handy and it's what I prefer to use. You can open and edit .9.png files in draw9patch and edit the border even after you save the file.
Once you have all your files edited, recompile the APK package with APK Manager
Option 11
y
y
It will tell you to delete the files under the /keep folder that you have edited. Delete any images and XML files, from the /keep folder, you edited under the /projects folder. If you edited XML files, delete the /keep/res/resources.arsc file as well
Press any key to continue and let the script finish
In a separate command line window, mount your Nook's /system folder (adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system)
back in APK Manager, select 8
/system/framework/framework-res.apk
Reboot your Nook
Boot Loop: If you messed something up and are stuck in a boot loop, most of the time you can still mount your Nook, push the original framework-res.apk to it and reboot. Or, you can use an unedited version of the CWM flashable zip file from the link below.
NOTE: it is not smart to push your framework-res.apk file to the Nook. I've learned the hard way that you can only do this about 10 times before you run out of memory and can no longer boot your Nook until you reflash Froyo again.
I'd recommend only a few flashes on a bare bones copy of Froyo until you feel comfortable with working on the framework theme. After that, I'm attaching a base, flashable zip for you to use in CWM so you can flash the theme instead of pushing. This will prevent you from getting stuck in a boot loop (unless you do something wrong yourself).
To add your framework-res.apk file to the zip, just open the zip and replace the /system/framework/framework-res.apk file (I'd recommend 7zip).
A Few Goodies
I'm including all of the PSD files I use to edit and create themes. If you want to create your own, custom theme, these will get you started. The only downside to these PSD files is that they are at the MDPI scale. If you want to create an HDPI theme, you'll need to increase the sizes.
Link to PSD files for creating your own theme, plus the flashable CWM zip file:
http://jjis.me/android-theme-templates
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
PMDColeslaw said:
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
Click to expand...
Click to collapse
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
wretchedlocket said:
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
Click to expand...
Click to collapse
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment updater-script.zip
PMDColeslaw said:
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment 546902
Click to expand...
Click to collapse
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
PMDColeslaw said:
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. I had too many things to do with the family yesterday.
If you haven't got this working yet, I'd suggest trying to start with removing just the /system/app/Vendind.apk file via the updater-script. If it works, then go back in and add each additional line until you run into problems again. At that point, you'll know what your problem is.
Since everything else (framework-res.apk, services.jar, etc.) gets replaced successfully, leave those lines alone. I'd just start with the basics of replacing the Vending.apk first and then work your way back up from there.
After reading from articles , now more or less I got some idea on how to create a theme for a custom rom , but still there's something I don't know .
1) First , I extract files from a rom using 7zip . Then , I extract out the content of framework-res.apk and make some modifies / changes to those .png files . So , after completed those modifies , I just open archieve on the original framework-res.apk , drag and drop the one I modified to replace the original one ? After that , how do I pack it in .zip file that can be updated in open recovery ? .xml file shouldn't be modified right ?
2) What if I do this , I get a theme.zip made for the rom , and then I extract the contents of the theme.zip using 7zip , then again I modify the .png files and after completed , I packed it again by open archieve on the original theme.zip , drag and drop the one I modified to replace the original one ? Does this works ?
3) What if I modify other system apps such as calender.apk ? Using the same method , extract , modify , drag and drop , replace , then again how do I pack it in .zip file that can be updated in open recovery ? Is there any "bond" between those system apps and framework-res.apk ? Can I just modify anyone of both ? Or I have to modify both system apps and framework-res.apk to get it works ?
Thanks
nikctsh said:
After reading from articles , now more or less I got some idea on how to create a theme for a custom rom , but still there's something I don't know .
1) First , I extract files from a rom using 7zip . Then , I extract out the content of framework-res.apk and make some modifies / changes to those .png files . So , after completed those modifies , I just open archieve on the original framework-res.apk , drag and drop the one I modified to replace the original one ? After that , how do I pack it in .zip file that can be updated in open recovery ? .xml file shouldn't be modified right ?
2) What if I do this , I get a theme.zip made for the rom , and then I extract the contents of the theme.zip using 7zip , then again I modify the .png files and after completed , I packed it again by open archieve on the original theme.zip , drag and drop the one I modified to replace the original one ? Does this works ?
3) What if I modify other system apps such as calender.apk ? Using the same method , extract , modify , drag and drop , replace , then again how do I pack it in .zip file that can be updated in open recovery ? Is there any "bond" between those system apps and framework-res.apk ? Can I just modify anyone of both ? Or I have to modify both system apps and framework-res.apk to get it works ?
Thanks
Click to expand...
Click to collapse
Here's what I know so far. I'm still trying to learn as much as I can:
1) If you are making a theme by trying to replace pngs in an existing framework-res.apk file, you can do this: open the apk file within your zip program, and edit the apk there (so you'll have two zip windows open. Once the apk is updated, close the most recent zip window. The first zip window should recognize that you've updated the apk file, and ask you to update the first zip window.
I've been playing around with this: http://forum.xda-developers.com/showthread.php?t=1432152
What it allows you to do is modify the files in Windows Explorer (or whatever file explorer you're using), and then let the script do the rest of the work for you. The actions it can do are: decompile apk, recompile apk, sign apk, created update.zip.
The xml files need to be edited if you want to achieve certain effects. For example, in the Gingerbread theme there are some edits that have to be made to a few xml files in order to achieve white text on black backgrounds on the popup menus. The nice thing about the framework flasher link from above is that it 'compiles' the files (meaning it will check if the .9.pngs are correct, and if your xml files point to correct assets), so you can go about doing xml edits and stuff without fear of bootlooping.
2) Yes, this should work.
3) If the updater script is a generic script (that is, it moves everything from the /system folder to /system, and /data to /data), then you can create directories in the update.zip that refer to whatever apk you want to replace, with the same structure as in Android. The cool thing about Metamorph, from what I gather, is that you can create folder structures with just the assets you want to replace, rather than the entire apk. This means that if you want to replace just a few images in Phone.apk, for example, you create a directory in the Metamorph script under /system/app/Phone/res/drawable-hdpi and add the images you want to replace in there. I think that's the way I want to create my themes from now on, I just need to figure out how to do it correctly
I tried the framework flasher , after located the framework-res.apk and run RunMe , it shows echo is off , the log process shows 'java' is not recognized as an internal or external command,
operable program or batch file.
Do you have Java installed?
Mioze7Ae said:
Do you have Java installed?
Click to expand...
Click to collapse
No , I have no Java installed . Tried to install before but couldn't get the right version .
Java
I've yet to find one all inclusive theming reference. Just a lot of searching & reading & trial & error. This might be a good place to get started.
Edit: You'll also want to get the Android SDK
3rdstring said:
Java
I've yet to find one all inclusive theming reference. Just a lot of searching & reading & trial & error. This might be a good place to get started.
Edit: You'll also want to get the Android SDK
Click to expand...
Click to collapse
BTW , since I'm still too new to theming , I'm thinking of making my first step by changing the colour of a completed theme . This is what I'm currently doing : I extracted the files content of your DarkFroyo.zip and then extracted it's framework-res.apk . ( IT'S YOUR THEME , CAN YOU GIVE ME THE PERMISSION TO DO THIS ? ) I'm changing the original orange colour of all those icon to light pink using photoshop , then replace the original one . The files type are .png . Also , I changed the battery status icon and status bar background . However , I haven't touch those .xml files , I just leave it there . So after I complete , do I just flash it right away in my phone or I need to doing something like "sign" ? As for now , I don't have any idea about "sign" .
nikctsh said:
BTW , since I'm still too new to theming , I'm thinking of making my first step by changing the colour of a completed theme . This is what I'm currently doing : I extracted the files content of your DarkFroyo.zip and then extracted it's framework-res.apk . ( IT'S YOUR THEME , CAN YOU GIVE ME THE PERMISSION TO DO THIS ? ) I'm changing the original orange colour of all those icon to light pink using photoshop , then replace the original one . The files type are .png . Also , I changed the battery status icon and status bar background . However , I haven't touch those .xml files , I just leave it there . So after I complete , do I just flash it right away in my phone or I need to doing something like "sign" ? As for now , I don't have any idea about "sign" .
Click to expand...
Click to collapse
Changing the color in Photoshop is fine for normal ".png"s but ".9.png"s are special, they have a 1 pixel border with guides that define how they are stretched to fill a space (& are only visible is a decompiled state). Just editing a .9.png in Photoshop might break the .9 patch. Since you are trying to modify my theme it might also be wise to grab the "undo.zip" so if (when) something you try bootloops the phone you can flash the undo to get back to stock. I know had numerous bootloops when I was first starting out (still do occasionally).
3rdstring said:
Changing the color in Photoshop is fine for normal ".png"s but ".9.png"s are special, they have a 1 pixel border with guides that define how they are stretched to fill a space (& are only visible is a decompiled state). Just editing a .9.png in Photoshop might break the .9 patch. Since you are trying to modify my theme it might also be wise to grab the "undo.zip" so if (when) something you try bootloops the phone you can flash the undo to get back to stock. I know had numerous bootloops when I was first starting out (still do occasionally).
Click to expand...
Click to collapse
Hey 3rdstring. I noticed you release a new version of your theme for the ODEXED version of CM6. For APKs that have ODEX files (such as Phone), are you deodexing them using apktool, then reodexing them? A brief pointer would be nice!
molohov said:
Hey 3rdstring. I noticed you release a new version of your theme for the ODEXED version of CM6. For APKs that have ODEX files (such as Phone), are you deodexing them using apktool, then reodexing them? A brief pointer would be nice!
Click to expand...
Click to collapse
No the only thing I'm changing in any of the odexed apks are images. I use a Metamorph file with ZipThemer to build the update.zip (& undo) after I've decompiled / recomfiled framework-res for the white menu text & 10% battery increments.
3rdstring said:
No the only thing I'm changing in any of the odexed apks are images. I use a Metamorph file with ZipThemer to build the update.zip (& undo) after I've decompiled / recomfiled framework-res for the white menu text & 10% battery increments.
Click to expand...
Click to collapse
The reason I ask is b/c I tried pushing a modified Phone.apk to CM6, but it didn't pick up any of the changes I added (images only). It made me think that the assets were already prebuilt in the odex file, so changing the apk wouldn't do anything unless the odex file was changed too.
I also tried applying a metamorph script on top of the odex ROM, but it caused a lot of fcs. I think it's b/c of the ODEXing too.
EDIT: My bad. Phone.apk is the calling screen, Contacts.apk is the dialer + contacts. DOH!!!
My edits are pushed correctly
Hello all
I have a rooted dinc4glte and I want to do 3 thigns
a) change the battery to one that has digits so I can drop a widget from my home screen
b) change my boot animation
and 3 change the default check marks to something with a bigger check. I have trouble seeing them.
so once I figure out whch files to upload to uot I can take the zip file from uot and find and mod the check boxes myself but which files odo i upload.
or soemoen can tell me which files i need.
also will i need to deodex the whole rom? i didn't need to on my stratosphere.
I had a Samsung with gb before and it was clear which 3 files but with sense htc its less clear
dcooterfrog said:
Hello all
I have a rooted dinc4glte and I want to do 3 thigns
a) change the battery to one that has digits so I can drop a widget from my home screen
b) change my boot animation
and 3 change the default check marks to something with a bigger check. I have trouble seeing them.
so once I figure out whch files to upload to uot I can take the zip file from uot and find and mod the check boxes myself but which files odo i upload.
or soemoen can tell me which files i need.
also will i need to deodex the whole rom? i didn't need to on my stratosphere.
I had a Samsung with gb before and it was clear which 3 files but with sense htc its less clear
Click to expand...
Click to collapse
On the bottom of the file upload page, under NOTE 1, UOT says which files to upload for ICS Sense. You'll upload the Systemui.apk, the framework-res.apk. and the com.htc.resources.apk. Also, UOT says that it has support for odex roms, but traditionally you would use a de-odexed rom. There is a rooted de-oedexed .605 stock rom in the android development section.