This guide will explain how to theme your Dialer for firmwares 2.2 and higher. This will very likely only work on De-Odexedroms. If you're not sure what deodexed is, it is not Dell Stock, if you have a custom ROM check with the Chef.
I will make this as easy as possible. This is for windows. The only tools you should need is 7zip and a good image editor, like Photoshop, Paint.net or GIMP.
I will attach an DialerTheme.zip with custom Contacts.apk and a stock Phone.apk to use.
Theming Contacts.apk, will customize the things you see before placing a call.
Theming Phone.apk, will customize images during or in-call.
For Dialer background in Contacts before calling, I recommend using an 800x800 .png, make sure its not just renamed .png but actually saved as a .png
This can be a photo, picture or solid color, whatever you desire. Name this "custom_dialer_background.png" without quotes and with the underscores.
I will explain how to copy this to the .apk, most will know how to do this, but I will explain. With 7zip installed, right click on my DialerTheme.zip, choose 7zip, then mouseover to ..open archive. then double click on \system folder, then double click \app folder, then double click contacts.apk, double click \res folder, then double click \drawable-long-finger folder. Now simply drag and drop your custom_dialer_background.png into this folder. It will ask you if you want to replace. Say Ok or yes. Don't worry it doesn't move, just copies and keeps your original. Next do the same and copy to \drawable-long-land-finger and also \drawable-mdpi-finger. Now close the window and it should ask yo to update the archive, say Ok or yes. Done. That's it for contacts and the 1st dialer.
The next one is a bit trickier and may take a bit more time. It involves .9.pngs, which are stretchable images and can be difficult to work with. Lets make it easy for our selves. Again open DialerTheme.zip as an archive with 7zip and navigate to Phone.apk\res\drawable-hdpi. we need to copy the first 5 files from here to your desktop, or a folder to make things neater.
These are:
bg_in_call_gradient_bluetooth.9.png,
bg_in_call_gradient_connected.9.png,
bg_in_call_gradient_ended.9.png,
bg_in_call_gradient_on_hold.9.png, and
bg_in_call_gradient_unidentified.9.png
A quick way to do this is to open any one with your photo editor and make your changes, (eg.paste your picture or image). The ones I am using are 480x754, but I think it should be fine using the same 800x800 from before. If you start adding layers to it though it may not save correctly, I find copy/paste works just fine. Now save and it should retain the .9.png extension. You can either do the remaining 4 or just open the 1st one and choose save as: bg_in_call_gradient_connected.9.png,(or even a copy and rename should work) just make sure it naturally retains the .9.png extension which already contains the boundaries and data we need. When you have all 5 looking as you wish with .9.png extension still intact, we can then move these to our zip in the same location( mulit-move by holding CTRL while selecting all 5). It will ask if you want to overwrite say yes. Also copy these 5 files to phone\res\drawable-long-finger, and say ok to overwrite.
Now we need these same 5 for a landscape view in-call. So you either rotate them, if it doesn't compromise your image. These images are also normal .png's, so they will not stretch. You may need to crop them, or expand your canvas. The ones I am using are 802x477 and look just fine. When you have all 5 name them as before except without .9. (I wouldnt recommend just renaming a .9.png to .png, although it would probably work, I suggest opening a.9 and saving it as .png first then copying and renaming should be fine. Same 5 filenames as before without .9
bg_in_call_gradient_bluetooth.png,
bg_in_call_gradient_connected.png,
bg_in_call_gradient_ended.png,
bg_in_call_gradient_on_hold.png, and
bg_in_call_gradient_unidentified.png
copy these like we did before to phone\res\drawable-long-land-finger.
Close the archive when finished and it should ask you to update, say OK. Thats it. Now place on SD Card and flash in recovery.
This doesn't theme anything else, but you can change all the other images yourself in the same manner. Try making the buttons transparent,etc! Just remember to retain the .9.png or it will not display correctly.
Because we have done it this way, if you try to decompile and rebuild it is likely you will get "missing .9.chunk data, etc." But we shouldnt need to decompile again, all images can be drag and dropped.
This method should not have any problems, bootloops, stuck at logos, because were only swapping out .png's, If anything you may get an immediate force close when trying to open phone or contacts, likely becuase an image is missing/named incorrectly or the size is too far from the original.(which I think android will still try to display...up to a point)
There is also a .zip in next post to return to stock phone and contacts.apk
If you need further assistance, search, then post here and we will try to help.
reserved
Update: custom background will now be on all screens!
If no one else makes a transparent buttons-so you can see your whole wallpaper-theme, I may do it when I have time. This theme also doesn't change any background in your contact list, etc. Those will still be black. I can change those as well and may do so in an update. If so, it will use the same image as custom_dialer_background.
::bump::
The secret sauce...
great post
Howdy
I'm glad you posted this, I have been PM'ing peolpe to try and found out how to do this, not to look a gift horse in the mouth, but might you have something similiar for the keyboard??
THanks again for the post.
Related
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.
My laptop was stolen recently so I won't be able to help anyone out until I can get a new one. Thanks for stopping by though.
This is no longer a tutorial, just a simple user friendly Lock Ring Kit.
Please download the updated kit at the bottom of this post.
I will also take requests here for anyone who doesn't want to mess with it.
Since people are still rocking 2.3.3 ROMs, please specify if your ROM is 2.3.3 or 2.3.4 when making a request. There are subtle differences.
Also you have a few rosies to choose from, let me know which one you want. If you don't request something specific, I'll just make the default rosie. Rosie choices attached at the bottom of this post. If you would like a rosie I don't have here, let me know and I'll see what I can do to add it to the kit. Also, I've played around a little with themes enough to feel comfortable to help out wherever I can. So if you have a request that is not related to my kit, I still may be able to help you out.
All 2.3.3 requests I've done are posted on Post# 3 and Post# 4
2.3.4 version requests are posted on Post# 125 and Post# 126
Thumbnail gallery of all the Lock Rings I've made HERE
Links to my Lock Ring folders on Box.net
2.3.3 Lock Rings
2.3.4 Lock Rings
2.3.4 Lock Rings - Transparent Rosie
2.3.4 Lock Rings - Red Outline Rosie
First of all, this is intented for Deodexed ROMs on the EVO 3D. Other qHD devices may work as well but I cannot guarantee. For devices such as the EVO 4G (WVGA), use one of the tutorials below . While these mods have been working flawless on several ROMs, there is the occasional error. Just to be safe MAKE A NANDROID to go back to if something goes wrong. If you don't read up and just flash something, lock ring mods or any other, and something should screw up, you can't be mad at anyone but yourself if you've got nothing to go back to.
With this method, your ring will only show up on the default skin or the HTC supplied skins, Burgundy and BlueSky. Every custom skin has its own lock ring which overwrites the default. If you have a custom skin installed and would like a custom lock ring, go to my second post for a mini tutorial on editing custom skins.
---------------------------------------------------------------------------------------------------
I originally learned how to make these from this thread: [Tutorial] Sense 3.0 Custom Lock Ring Kit so big thanks to jmaher1023 for that.
Another thread to check out is [TUTORIAL] User-Friendly Custom Lock-Rings for Sense 3.0 (EVO 4G) by gamendorf. *Thanks gamendorf for the help with the batch file.
Also, you should stop by this thread [DEV-TOOLS] [MODE10] Mode10Tools now released ! and give thanks to Flemmard and Diamondback2010, the devs of the m10 tools that make all this possible.
---------------------------------------------------------------------------------------------------
As Posted by Diamondback2010 in the m10 tools thread:
System-Requirements
You need a working .NET 4 Framework installation to run the M10Editor.
m10decoder and m10encoder should run in console-version without anything special.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------
Instructions
1. Unzip the attached Lock_Ring_Kit_2.3.3.zip or Lock_Ring_Kit_2.3.4.zip to your C drive (C:\Lock_Ring_Kit_2.3.3) or (C:\Lock_Ring_Kit_2.3.4)
2. Pick your image and resize it to 271x270. For the image to show up correctly you have to rotate it 180 degrees and mirror it. Your image must be saved as a .png
3. Save your edited image as LockRing.png and move it to the root of your Lock Ring Kit
4. Run the batch file for the Rosie you want (look in "Rosie Screenshots" folder to decide)
5. A flashble zip file will be created at the root of your Lock Ring Kit. Rename it, sign it if you want, move it to your SD Card and flash in recovery
E3D_Lock_Ring_Kit_2.3.3.zip
Dropbox Mirror
E3D_Lock_Ring_Kit_2.3.4.zip
Dropbox Mirror
Recent Changes:
Added in Red Outline to the rosie choices
*Not that anyone actually reads the entire first post, but just for your information, making Lock Rings for GSM and Sense 3.5 is not possible yet. As of right now m10 tools is unable to decompile these m10 files. Until we get a m10 tools update for these we have no way to edit.
The above comment was really nothing more than a speculation. I went ahead and asked the devs of the m10 tools if they could confirm what I thought and this was his answer...
Diamondback2010 said:
Well yea, I have to leave you here without hope
This fusion apk uses the new type 14 images. There is no way atm to decode them
You just have to wait as well as the sense 3.5 crowd
Click to expand...
Click to collapse
Big Thanks to Donators:
-NascarKid
-nuggyunlimited
-Foxworth
This is a quick tutorial for anyone who wants to edit just the lock ring of a custom skin. Honestly it's more to get you playing with M10Editor.exe.
Again, pick your image, resize it to 271x270, rotate 180 degrees, and mirror.
Inside the M10_Tools folder there is M10Editor.exe.
1. Open M10Editor.exe.
2. Click the Load File button and choose the skin.apk you want to edit.
3. Go to the m10 files tab and highlight the only m10 file shown (usually shared.m10)
4. Check the Decode Images check box.
6. Click the Decompile/Show button.
7. Once clicked, you'll be moved to the Editor tab.
8. Expand by clicking the arrow next to shared.m10.
9. Continue to expand until you expand Textures.
10. Scroll through Textures until you see the default (or sometimes modified) lock ring image.
11. Right click the image and choose Show in Explorer.
12. The image will already be highlighted when the explorer opens, copy the name of the highlighted file.
13. Change the name of your image to the one you just copied and drag or copy your image inside to replace it.
14. Close the explorer and go back to the Start tab in M10Editor.exe.
15. Click the Save File button. If you want to change the name of the apk when prompted, go ahead.
16. Sign the apk and install through a file explorer.
Sometimes you have to reboot for the lock ring to show.
Personally when I edit a skin, I also edit my ROMs fusion.apk and Idlescreen_Base.apk in order to remove traces of the default ring. Some ROM creators mod these apks for their ROM. If you know for sure that your ROM does not have a modded fusion.apk and Idlescreen_Base.apk you can simply use my lock ring kit to make your lock ring. If your ROM does have a modded fusion.apk and Idlescreen_Base.apk you should pull those files from the ROM and use M10Editor.exe to edit those files directly. The only m10 files you need to edit are the Default shared.m10 in fusion.apk and Lock_ring_motion.m10 in Idlescreen_Base.apk.
Requests
For 2.3.3 ROMs. If your on 2.3.4 and see something you like, post or PM me to get it converted. Or read the tutorial and attempt it yourself.
For 2.3.3 ROMs. If your on 2.3.4 and see something you like, post or PM me to get it converted. Or read the tutorial and attempt it yourself.
same here...
aannd another
And Ill join if thats ok with you guys!
And one more since Im on a role!
Does decompiling m10 files multiple times decrease the quality of the images in them?
triscuit1983 said:
Here's a quick tutorial of how to make lock rings for those who want to learn.
First of all, this is intented for Deodexed ROMs only. Also, with this method, your ring will only show up on the default skin. If you have a custom skin installed and would like a custom lock ring, go to my second post for a mini tutorial on editing custom skins.
I originally learned how to make these from this thread: [Tutorial] Sense 3.0 Custom Lock Ring Kit so big thanks to jmaher1023 for that.
If you want to, watch the video tutorial to get an idea of what to do.
DO NOT download the Lock Ring Kit attached in that thread, because the files included are not for qHD.
I've included a modified Lock Ring Kit for E3D here: E3D_Lock_Ring_Kit.zip
The E3D Lock Ring Kit and tutorial are about the same as jmaher1023's tutorial, but I changed the process and folder organization a little to hopefully simplify things.
Also, you should stop by this thread [DEV-TOOLS] [MODE10] Mode10Tools now released ! and give thanks to Flemmard and Diamondback2010, the devs of the m10 tools that make all this possible.
If you don't already have one, download an archiver like 7zip or WinRAR. I use 7zip.
To keep things simple, unzip the attached E3D_Lock_Ring_Kit.zip to your C drive (C:\Lock_Ring_Kit)
Inside the Lock_Ring_Kit you will see 3 folders (Copy Contents to Working, M10_Tools, Working), a zip file (Base_Lock_Ring.zip), and a doc file (Names & Commands.doc).
Now pick your image and resize it to 271x270. For the image to show up correctly you have to rotate it 180 degrees and mirror it. Save the edited image to a place of your choosing.
Now your ready to start creating the lock ring.
This is my method, step by step:
1. Open your Lock_Ring_Kit folder and (obviously) copy the contents of the Copy Contents to Working folder to the Working folder.
2. Open your Working folder and copy your edited image to the following folders - BlueSky1,Burgundy1,Default1, and Lock_ring_motion1.
3. Open the Names & Commands.doc and rename your copied images to the PNG Names. After renaming the images, move them into the inner folder and replace the existing image (eg. move the BlueSky png into BlueSky1\shared).
4. Open command prompt and change directory to C:\Lock_Ring_Kit\M10_Tools.
5. Go back to the Names & Commands.doc and copy and paste each of the m10 Commands into comand prompt and hit enter. This will compile new m10 files with your image inside.
6. Now you have to copy the newly compiled m10 files to their correct location within the Base_Lock_Ring.zip. The newly compiled m10 files are
in folders BlueSky(shared.m10), Burgundy(shared.m10), Default(shared.m10), and Lock_ring_motion(Lock_ring_motion.m10).
7. Copy the Base_Lock_Ring.zip to the Desktop or anywhere else you'd like.
7. Use 7zip (or WinRAR) to open Base_Lock_Ring.zip (eg. Right click>7-Zip>Open Archive)
8. Navigate to \system\app\fusion.apk\assests\BlueSky\drawable and drag your newly compiled shared.m10 file inside to replace the existing shared.m10. Do the same for Burgundy and Default. Use the back or folder up button to update the apk. A prompt will come up asking if you want to continue.
9. For Idlescreen_Base.apk, navigate to \assests\scenes\base and drag your newly compiled Lock_ring_motion.m10 inside to replace the existing Lock_ring_motion.m10. Back out to update the apk, and close the archiver.
That should be about it. You can rename the Base_Lock_Ring.zip to whatever you like. I'd say go ahead and sign the zip, but thats up to you. Put the zip on your SD Card, go into recovery and flash.
Click to expand...
Click to collapse
When doing step 3, if using Vista or Windows 7, make sure to omit the .png extension when renaming your edited image from the word document. You will end up with a .png.png and nothing will have changed.
Rydah805 said:
Does decompiling m10 files multiple times decrease the quality of the images in them?
Click to expand...
Click to collapse
Not that I've seen so far. But with the files I've provided in the E3D Lock Ring Kit, your only compiling. I've included the decompiled files for you to add your image and compile. Unless your talking about m10 files in general and not specifically the files I've included?
ducky1131 said:
When doing step 3, if using Vista or Windows 7, make sure to omit the .png extension when renaming your edited image from the word document. You will end up with a .png.png and nothing will have changed.
Click to expand...
Click to collapse
In that case, you can simply delete the .png part in your Names & Commands.doc. I show all file extensions on my computer and I copy and overwrite the whole name, extension and all. If you want to show file extensions to be able to see .png on your image name, go to Folder Options in your explorer, go to the View tab, scroll down and uncheck "Hide extensions for known file types".
Here is a black Chevy logo I made for a friend using your lock ring kit, thought I'd share
Black Chevy Logo Lock Ring
Is there a way to edit the rest of the lock screen? Like the bar at the bottom where the lock ring sits on? I see what looks like the png for it in the images in the default, bluesky, and burgandy folders. I tried editing them and compiled them back to shared.m10 and ten flashing the zip but it didn't work. I was able to edit the background of the clock on the home screen this way and it worked but again I was unable to get the same result for the stuff at the bottom (the bar and soft buttons). Is there another place where these are edited or am I doing something wrong?
mikeaveli007 said:
Is there a way to edit the rest of the lock screen? Like the bar at the bottom where the lock ring sits on? I see what looks like the png for it in the images in the default, bluesky, and burgandy folders. I tried editing them and compiled them back to shared.m10 and ten flashing the zip but it didn't work. I was able to edit the background of the clock on the home screen this way and it worked but again I was unable to get the same result for the stuff at the bottom (the bar and soft buttons). Is there another place where these are edited or am I doing something wrong?
Click to expand...
Click to collapse
I'm thinking that is probably within Rosie.apk but I don't really know. This m10 file stuff is new to me and I'm slowly learning. m10 files are reminiscent of cab files on windows mobile to me. I'm hope someone who has been doing full themes can comment on this.
triscuit1983 said:
I'm thinking that is probably within Rosie.apk but I don't really know. This m10 file stuff is new to me and I'm slowly learning. m10 files are reminiscent of cab files on windows mobile to me. I'm hope someone who has been doing full themes can comment on this.
Click to expand...
Click to collapse
Ahhh thanks, i'm poking around in there and that looks more like what I was looking for. Hmm so I wonder what all those png files in the m10 files in fusion are for.... Thanks for pointing me in the right direction though hopefully thats all I need.
Can one of you guys make an Indianapolis Colts lockring? Everything I make comes out looking like ass.
ducky1131 said:
Can one of you guys make an Indianapolis Colts lockring? Everything I make comes out looking like ass.
Click to expand...
Click to collapse
Will this work?
Colts_Lock_Ring-signed.zip
thanks.....
Thanks a bunch for the tutorial! I made one for the guys...its a singe upper female anatomy part so I wont post it here...but it is pretty fully to drag it out into the screen If anyone is interested pm with your email. Not sure if im permited to host it here somehow so I wont. Working on other ones so I will update when I make some cool ones.
triscuit1983 said:
Not that I've seen so far. But with the files I've provided in the E3D Lock Ring Kit, your only compiling. I've included the decompiled files for you to add your image and compile. Unless your talking about m10 files in general and not specifically the files I've included?
Click to expand...
Click to collapse
Sorry, I'm speaking in general...?
This guide will assume the basics (image editing, apk manager setup, adb, etc..) are understood. Minus 9png's, I will go over that. The point is to have a base here for discussion on how to edit things properly. If anyone has something to add, please do.
OK, lets start with something that caught me off guard when switching to a phone with blur... there are certain apps that have dependencies. You have to set those dependencies up. The easiest way to do this is, from whatever ROM you are running, open the zip up with 7zip. Also open up your APK Manager and go into the "other" folder. From your ROM grab framework-res.apk, blur-res.apk, moto-res.apk, settings.apk and systemUI.apk and copy them into the "other" folder. Once there, open up a command prompt. change directories until you are in the "other" folder. Once there do this for each item. apktool d framework-res.apk and hit enter. Then, apktool if framework-res.apk. Do that for the rest.
9pngs.. Everyones afraid... they are a walk in the park. 1 extra step and its done. Decompile your apk, Edit it to your liking and save it. Open it up with draw9patch and add the guides back in and save it. The right and the bottom just make a big ass black line from one side of the image to the other (most of the time). The left and top side require a little fine tuning. Basic rule is to stick a dot in "the middle". Over on the right, see if it looks right. If it doesn't, adjust it. Once done, save it. Recompile and you are done. If using apk manager 4.9 or newer, make sure you delete the images you edited in the keep folder.
Editing xmls....
You are going to be editing xmls to either change background color or text color. Heres a general rule that will help... open the xml in notepad++ and hit ctrl +f. search for android:background .... you can change whatevers there to a hex color. like, if you wanted a dark red.. #ffbc1010. if changing text colors, do a search for android:textColor. Do the same thing with searching and changing.
Some edits will be found in the values folder... this would either take place in Colors.xml, drawables.xml or styles.xml
As I have found, some xmls just dont have a call to a bacground or text color so.. you just have to make one yourself. I always stick those in right after the androidrientation stuff. For example, you want a red background and nowhere in the xml can you find a spot to change it. No worries.. add this... android:background="#ffbc1010" . Good to go.
Some apks wont decompile with apk manager 5.01. You get an out of bounds error. Use apk manager 4.9 for those.. it will open them.
If you try to install an app and something doesnt work.. 1 minor thing, even though the rest does work.. do not try to install another re-edit until you have gone back to a fully functional version. Otherwise, none of your new edits will take hold even if they are correct. (Learned that one the hard way)
Remember, trial and error siis the Android Way!!!
Lastly, I leave you with this... each app has its own "fun-ness" to it. If you are ever stuck and need help, please feel free to ask. I can't do magic.. like looking at Sense... cause I dont have it.. but if you are running GB stock, Blur or its just an app for any phone.. please ask. I will answer, even if I dont know the answer and we have to work together to figure it out.
This is my contribution to XDA. Let's keep progression moving forward. I want to see more themers and more options!!!!
EDIT:
NEW INOFRMATION
I copied this over from my how to on DF... The links are probably still good (I just updated them) but just make sure you are getting the latest version... I wrote the how-to in January.
Since I see a lot of people trying to figure out how to get into theming and such, might as well share my knowledge...
I would also like to thank Devildog8791 and say that he went thru and added a lot to this via PM (which I then pasted here). He also made it a lot more detailed and easier to follow along for everyone.
Things you will need:
-APK Manager located here. It is the one from post #226. It uses apktool version 1.3.1 instead of the newest one, 1.3.2. The new version has some bugs that have not been worked out yet.
-Android SDK located here. There are two different files for Windows: a zip file and an .exe file. I downloaded the zip file, but you can try the .exe file.
-7zip located here. Make sure you pick the right installation for your setup (32-bit or 64-bit)
-Java JDK located here. Make sure you pick the right installation for your setup (32-bit or 64-bit)
Before I begin, please keep in mind that this is just how I did it. Maybe it's perfect, maybe its wrong, BUT... it worked for me.
NOTE: PLEASE READ THIS
Unless you are going to be pushing apks to your phone or pulling them directly from the phone, you do NOT need to bother with steps 3-6 and 9-11. You also only need to add the Java stuff to your Environment Variables.
OK here is how I set all this up and in the order that I did it.
1) Install the Java JDK. You probably don't need to, but I rebooted after the installation was complete.
2) Install 7zip.
3) Extract the android SDK file and move the extracted folder to the root of the C: drive. I renamed the folder "androidsdk", but you can rename it whatever you want. On my computer, the SDK is at C:/androidsdk (whatever you name this and anything in its filepath, make sure there are NO SPACES).
4) Go into your sdk folder and run "SDK Manager".
5) When the "Android SDK and AVD Manager" screen opens up, select "Available packages". Select the packages you want to install and click on "Install Selected". If the "Choose Packages to Install" screen comes up automatically, then select "Accept All" and click "Install". This will take a few minutes. Go ahead and get a drink and stretch your legs.
6) When your packages get done downloading and installing, close the "Installing Archives" and the "Android SDK and AVD Manager" screens.
7) Extract the APK Manager zip file and move the extracted folder to your user file. Mine is located at C:\Users\Tim\apk_manager_4.9.
8) Now you need to set your environment variables. To do this, click on "Start" and then right click on "Computer". Left Click "Properties" and in the left pane you will see "Advanced system settings". Click on that and it will open up a new window called "System Properties". Click on "Environment Variables" at the bottom of the screen.
9) Now that you are in the Environment Variables screen, you want to look at the top part of the screen first. Under "User variables for <your name here>", click on "New...".
10) In the "Variable name" section, type in ADB.
11) In the "Variable Value" section, type in C:\androidsdk\platform-tools\adb.
12) Now go to the bottom part of the screen and find "Path" on the left side under "Variable".
13) Double-click that "Path" section and it will bring up the edit screen.
14) Go to the end of the "Variable value" section and add the following: ;C:\Program Files\Java\jre6\bin;C:\Program Files\Java\jdk1.6.0_23\bin;C:\androidsdk;C:\androi dsdk\platform-tools;C:\androidsdk\tools. Verify that the bin file locations for java are in the same place as indicated here. They should be the same, but check it to be safe. Also, don't forget to change the name to whatever you named your sdk folder. One last thing is to make sure you have a semi-colon in between each path as indicated.
15) Click "OK" when done and close all the windows.
16) Reboot your computer.
Now that you have your environment variables set, you should be good to go to use APK Manager. One thing that you might have to do is set up your adb drivers for your phone. I have a Droid Incredible and I went to this site to get mine set up. If you have a Motorola Droid 1 (which most on this site do), then it should set up with the proper drivers when you plug it in the computer. My wife has a Droid 1 and that is what happened for me.
So, now you have 7zip, SDK, Java and APK Manager installed, setup and ready to use. Fantasmagorical!
Great, now, what the hell do you do with it...lol
1) You decide on an apk file (let's choose phone.apk) to use. You can grab it from the stock ROM your using, pull it off your phone, whatever...
2) Now that it is on your computer, move it into the APK Manager's "place-apk-here-for-modding" folder.
3) Run the script.bat and select option 22. Then choose the apk (project) you want to work with.
4) Now select option 9 to decompile the apk.
5) Once that's done select option 11 to recompile the apk. If it asks you if it's a system app (y/n) then you are in business. If it says there is an error, it is most likely that the apk has some .9.png images without guides. If this occurs, grab the stock images and stick them in by using 7zip and choose "open archive".
6) OK, so it works fine, now what? Just choose "N" and when it's done, go to the "place-apk-here-for-modding" folder and delete the "unsignedphone.apk" file.
7) Now go back to the script and choose option 9 to decompile again.
8) Once it's decompiled, navigate to the "projects" folder and go into the phone.apk folder.
9) Make all your xml edits.
10) Now, go back to the script and choose option 11. Choose "Y" and then choose "Y" again.
11) Now, go into the "KEEP" folder and delete the resources.arsc file and also delete every single xml you edited. Then go back to the script and "press any button to continue".
12) Once that is done, you are done. Go into the "place-apk-here-for-modding" folder and you will see an unsignedphone.apk file.
13) Put it in an update.zip that you can install to your phone and then rename it to phone.apk.
14) If you are wanting to now stick your own images in, use 7zip and select "open archive" and then drag your images into the proper folders.
15) Close 7zip and select "yes" to the box that pops up.
16) Now you are ready. Move the zip file to your phone, reboot into recovery and install it.
Going to add something blur related here. AK Manager 4.9 will give you errors recompiling phone, contacts and dialer. To fix it, go into the decompiled apk and open apktool.yml with notepad++ or similar. You will see 3 lines.. -1, -3 and -2. Put them in order.. -1, -2 and -3. Good to go.
Very nice thanks for this
Sent from my DROID X2 using Tapatalk
No problem. Get out there and make some good stuff!!
Hey thanks for the guide. I have a lot of programming experience but I am fairly new to android.
With that said, you state that: "This guide will assume the basics (image editing, apk manager setup, adb, etc..) are understood."
Is there a page were this things are explained, I have the image editing down, but have no idea about the apk manager,adb,etc...
I found this and I was wondering if this is the apk manager:
http://forum.xda-developers.com/showthread.php?t=1227179
Thanks, and sorry if this sounds too noobish.
Yes, that is apk manager. I would use 4.9 though because 5.01 will give you a lot of "out of bounds" errors when decompiling. 4.9 wont. And the apps work.
There is also another thread here on XDA .. So you want to make a theme.. or something like that.
I also wrote a How-To on installing java, apk, adb and setting all of your environment variables. That is in the "Team Inversion Conversion" area on droidforums.net.
Edit: Added the how to to the original post.
Question
So i wanted to theme and started reading guides on xda and came to the conclusion that it was a lengthy process requiring knowledge of may different programs, most of which was over my head. Just recently i started digging into roms wanting to change the lockscreen background and incall backgrounds. using 7z i located the lockscreen background file at system\framework\framework-res.apk\res\drawable-hdpi\zz_moto_gradient_bg2.png I then copied the file out and opened it and using paint, changed the image to a different one and then pushed the modified file back into the zip and then flashed the rom. I was very happy to end up with this
.
My question is, not using apk manager or apktool or a command prompt or any of the methods that ive read, am i doing something wrong? Will editing roms in this method run me into problems? Or is it just a noobish approach that actually works?
afm1118... There is absolutely nothing wrong with the way you are doing things. Just make sure you don't mess with any 9pngs. if you edit those with your method, it will break the signature. The image would still work but the guides would be gone. When I first started learning to theme, I didn't understand what a guide was. So, heres my explanation... look at your keyboard... in landscape mode, the buttons are bigger than they are in normal view. guided 9s will make the images stretch perfectly to fit the required dimensions. unguided 9pngs will just take the actual image and make it bigger. Kind of like if you went into an image editor and re scaled a 40x40 pixel image to 100x100 pixels. It would still be there but it would be a little distorted.
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
afm1118 said:
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
Click to expand...
Click to collapse
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
TheMuffStuff said:
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
Click to expand...
Click to collapse
Im not scared of um, i just thought i would figure them out when i wanted to change one. but so far,with nitros rom and with muffstuff xkape and funkencools themes along with uot kitchen ive been very happy. The themes are great, im looking forward to whats next.
afm1118 said:
Yeah i just stay away from the 9pngs because i dont understand them and just know not to touch. You definitely helped me understand them better tho. What i dont understand is the need to use apk manager, or what recompiling/decompiling is. Like just using 7z i modified phone.apk in the same fashion i did the lockscreen, changing the incall background. Im guessing apk manager is necessary for editing xml. I really want to understand all this.
Click to expand...
Click to collapse
TheMuffStuff said:
I dont do .9 pngs and I still create alot of themes, dont be scared to theme cuz u cant do .9.
Click to expand...
Click to collapse
.9s are integral to theming....cheating them and not doing them arent an execuse
Nitsuj. Instead of bringing negativity into the thread, try being useful. This is a help section not a your doing it wrong thread. If you would like to discuss it further pm me.
Sent from my Nexus S using XDA App
Nexus S.. Ha.. Editing the build.prop har further reaches than I thought.
Anyway, yes, editing an xml requires decompiling and recompiling... or does it? Not so fast. You can use a Hex editor to edit those colors but, I have no clue. I never went that route.
I guess the easiest way to think about apks that are compiled or decompiled is like this... lets say you have a game.. Football.exe on your computer. you click it, it opens. Now, to save space, you zip it up and its now in a zip file called Football.zip. You click it, it does NOT open. The OS cant read a zip file as an executable file.
You open a compiled xml, can't read it. you open a decompiled xml.. its all right there in plain English. Why would you want to edit an xml? Many reasons. I am going to give you an example right here...
This is the decompiled progress-horizontal.xml from the framework. It controls the color of the bar when you are dwnlading an ap, adjusting the ringer or media volume, etc..
<?xml version="1.0" encoding="UTF-8"?>
<layer-list
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:id="@id/background">
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ffdfdfdf" android:endColor="#ffdfdfdf" android:angle="270.0" android:centerY="0.75" android:centerColor="#ff000000" />
</shape>
</item>
<item android:id="@id/secondaryProgress">
<clip>
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ff000000" android:endColor="#ffbf0d0d" android:angle="270.0" android:centerY="0.75" android:centerColor="#ffbf0d0d" />
</shape>
</clip>
</item>
<item android:id="@id/progress">
<clip>
<shape>
<corners android:radius="0.0dip" />
<gradient android:startColor="#ffbf0d0d" android:endColor="#ffbf0d0d" android:angle="270.0" android:centerY="0.75" android:centerColor="#ff000000" />
</shape>
</clip>
</item>
</layer-list>
Im not going to go look at a hex chart but I think this is from when I was making an orange theme the other day. You can see there are 9 hex codes for color. You can edit those and make the progress bar have a different background and color. If I remember correctly, the first 3 control the background and the other 6 control the color of the bar. Play around and experiment til you see one you like. you can also add in transparencies and such to get fading and whatnot. like #80dfdfdf instead of #ffdfdfdf.
Some xmls wont be as clear cut.. it mught say something like android:background="@drawable/status_bar_bg"
This still can be changed. You can actually add something to a folder..image, color, etc.. but you also need to make an xml for it too. (I think, never done it).
You can make it point at a different item or, you can just give it a hex color.
ok so with the lockscreen i did, i could have done it two different ways. i could have changed the xml to target a different file or what i did, modify the image file itself. its just like html or any programing, its been a while.
correct man. Deciding which way to go is key. some of those images show up all over the place. In each instance just have to decide if its better to point it something else or just change what its pointing to looks like.
When I first themed ShapeWriter(back when I hadn't even heard of a .9) I got into a whole new mess with .smali, turns out that's where the tracer color was defined. You could never edit smali without decompiling first, although for theming its rare to have to.
Once you start theming you start learning little things here and there. And usually if your theming, it's cause your trying to do what no ones done yet; so most of what your going to learn is from a LOT of trial and error.
I'm not good at writing guides or anything but anyone can feel free to ask in my thread or pm me if you have some specific questions, etc..
Sent from my DROID X2 using XDA App
Also just thought I'd add: things may seem confusing sometimes but so would basic algebra if it hadn't been etched into your brain already.
Sent from my DROID X2 using XDA App
I was wondering is someone could explain to me a little better as to how to make a flashable zip.
I wanted to change the background image of the dialer, but when I have a finished apk I dont know hot to make it flashable.
Thanks
Electroniko said:
I was wondering is someone could explain to me a little better as to how to make a flashable zip.
I wanted to change the background image of the dialer, but when I have a finished apk I dont know hot to make it flashable.
Thanks
Click to expand...
Click to collapse
Well I could get pretty indepth but if you just want one that works you could borrow mine or probably anyone else's and change it for your needs(deleting my files adding yours).
without getting into the actually scripting the basics are:
A script that tells you what files/dir go where(among other things) and the files.
Usually it will just unpack everything in the zip to the "root" of your system partition. So if you were to use my zip i would keep my dir's and just delete the actual files.
basically if you want to put a file in "/system/framework/" on your phone you would put the file in "/system/framework/" in the zip.
also a note if you use mine; it will only copy to the system partition and not sd or sd-ext. even with that it should fit your needs.
Hope that all helps
Sorry for all the questions lately, even though I'll probably have more.
I'm working on the SystemUI.apk from IE20 and my method of compiling consists of using the keep folder method and deleting all the files I changed with apk manager 4.9.
Now I can change the Status_bar.xml and status_bar_tracking.xml without a hitch, however if I delete status_bar_expanded.xml from the keep folder (whether I change anything in it or not) I get force closes when I get it loaded onto my phone.
There's no error in the log so I'm pretty lost...So I was wondering if there's something else I have to do that anyone knows of?
Thanks if you can help!
The only thing that should be deleted are images that you edited (if you didn't edit any images just leave the folder). But if you edited ANY xml ONLY delete the resourses.arc from the keep folder. But don't delete any individual xml's from keep. And yes the size will change because of the compression used in apk mgr.
good day.
chopper the dog said:
The only thing that should be deleted are images that you edited (if you didn't edit any images just leave the folder). But if you edited ANY xml ONLY delete the resourses.arc from the keep folder. But don't delete any individual xml's from keep. And yes the size will change because of the compression used in apk mgr.
good day.
Click to expand...
Click to collapse
Thanks for the response,
However, by not deleting the xmls I edited in the keep folder it seems it just replaces them with the stock files.
Soo...This stopped the force closes, but none of my edits took.
Maybe it's time to to switch to a linux build environment...I'm frustrated to say the least. Google'd every possible problem and nothing...
EDIT: But before I do that could someone possibly try to compile this SystemUI.apk with a color edit in the res/layout/status_bar_expanded file?
Would highly appreciate this ^^^
Hi welcome to my guide on the Basics of making and editing Skins for sense 4
Skins are incredibly easy to make and can be really good fun, they are also a good way for you to give back to the xda community without really breaking a sweat
What are Skins and how can i make them ?
Skins are HTC's equivalent to themes for The HTC sense U.I (Up to sense 5) and can change many things that you see in your phone, there are two main ways to create and edit the skins. The first and easiest way is using a popular program named VTS by the virtuous team which pretty much does all the tricky and confusing stuff for you, Which is good:good: or you can make it yourself and do all the work yourself, which is what my mini guide is all about :laugh: If you want to save yourself some time then download the VTS program and use this Guide http://www.virtuous-ten-studio.com/index.php/other-stuff/94-how-to-create-your-own-sense-skin
Requirements:
A phone or Device that actually runs Sense 4 *Duh
A computer or laptop that's newer then Windows 95
7zip or WinRar (google them if you dont have them already)
A programe called Notepad++
A brain & a bit of patience
Your HTC framework (com.htc.resources.apk)
And a base skin
1. Download the skin you want to use as a base for creating or editing (this will save a lot of time.) examples of base skins are ones we already have such as Matte/serene/aluminum which can be found here http://forum.xda-developers.com/showthread.php?t=2038155
Your'e also going to want to get the htc framework .apk which is now known as "com.htc.resources.apk" from your phone found in the root of your device under system/framework/ ..... Make sure both of these apk files are in a folder on your computer where your going to remember
2. Now your going to want download this http://www.4shared.com/zip/Z8rB_hIS/file.html and extract it then put the FOLDER "APKTOOL" into a new folder called android and move it to the root of your'e C directory (or equivalent) Your'e also going to want to move both "Base skin.apk" and "com.htc.resources.apk" Inside the Apktool folder (just so its easier for you later)
After you've done this you're gonna want to install the framework and decompile the "base skin.apk" Use this guide to help you Decompile http://forum.xda-developers.com/showthread.php?t=1989533
3. Okay so once you've successfully completed the above steps you can now finally edit the images of the theme as you please (the extracted should be in a folder in "C:\android\apktool"
In the folder named Assets you'll find 4 images in this folder you can: change the preview image that you would see in personalize before you select the theme, and the wallpaper that will be automatically set when you choose your skin in personalize
In the folder named res you'll see a load of different folders, but the only folders we care about for now is the folder called "drawable-hdpi" where you can edit .pngs as you like with a program like: Photoshop or Gimp. (Don't edit .9.png's though until your'e experienced)
As an example we can change the lock ring (see the screenshot below) (if you want inspiration for lockrings then check this thread http://forum.xda-developers.com/showthread.php?p=22011398
In the res folder there is another folder called Values Edit Strings.xml with a program called notepad++. You'll see a line of text in the xml that says <string name="skin_name">Matte (or what ever the base skin was called)</string> you can edit "Matte" text to whatever you want the name of your theme to be e.g. " <string name="skin_name">Beats Skin by Joe</string>" then make sure you save.
4. So now you need to recompile the folder into an .apk refer back to this guide (the bit says finishing/recompiling finished project) http://forum.xda-developers.com/showthread.php?t=1989533
5 Now to finish it off you need to sign the .apk and align it, so use this https://code.google.com/p/apk-signer/
6. Now copy the Signed and aligned .apk to your device, and install it. :fingers-crossed:
*I don't take credit for any of the tools used in this guide, all i did was brought it all into one in this thread for you
However if you want to hit the thanks button then don't be shy about it
*I'll sort out the font and size of the text soon, add more screen shots, and make a video on how to do it so its slightly easier to see and understand
....
If you follow the simple steps above you'll get something like the Skin attached
Nice one! Added to Index.