Related
To get started, read the posts below by tsachi.
Then give this a glance - Do it yourself guide for theme editing
More Resources:
http://forum.xda-developers.com/showthread.php?t=982300
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=916814
Info on how to edit the items in notification bar:
+ http://forum.xda-developers.com/showpost.php?p=11158662&postcount=3
All credit belongs to the original authors. I am simply gathering all this information to make it easier.
For any help or support, post in this thread and we will try to help you the best we can.
Expanded Information
Introduction
The link in OP gives you instructions on how to replace images, but it lacks information for the inexperienced themer. Here is some background information and some more details on the steps before and after you insert new images in your framework.
System Icons and background images sit in two main files: framework-res.apk and twframework-res.apk. Within these files there is a res directory, and under that you have the folders containing data. Google has guidelines on icon design, although themers usually ignore those in order to get a different from stock look. One thing you would notice is that there are a lot of repeated icons. For example, framework-res.apk has both drawable-hdpi and drawable-hdpi-v4. The first is there for compatibility with older APIs (anroid 1.6 or older) so I am not sure why it is still there, but if you remove it your phone will not like it.
Each application has its own res folder where the launcher icon and other visuals are kept. There are, however, a lot of applications that reference the framework.apk for visuals. An example is the dialer that calls on some background images from both framework-res and twframework-res.
There are 2 types of images that you would encounter. Normal icons and images are non-scalable. They take a certain amount of real estate on the phone, and that’s it. Example of these are the battery levels and notification icons. The other type is the .9 images. These are images that are going to be stretched to fit whatever space is needed. An example of that are the menu backgrounds. The .9 images have a special format. The one pixel border around them defines how they stretch and how content is displayed in them. It is highly recommended to follow the standards in order to get repeatable and consistent look. Android SDK has a tool to help with .9 file design: draw9patch.bat.
Important note: The .9 files show the borders ONLY when de-compiled. If you grab a file from the framework directly you will not see that line. It is therefore required to compile the .9 files after you make them. You can use apk manager or ThemePro-JAVA to recompile the framework apk after modifying the files.
Definitions for which image is used where sit in the xml files under the drawable folder. These are compiled xml files, you can’t edit them with a text editor. For this introduction I will not go into modifying xml files. Each apk also has a resources file that describes what is in there. If you add, remove, or rename files in the apk you will have discrepancy with the resource file and the theme will not work (more likely you will be stuck in an infinite bootup loop)
Before you start:
Warning: frameworks are highly linked with other files. You can’t just take a framework from one ROM and put it in another. Always keep a backup of the original files ready to be installed (see below), otherwise you may need to re-flash the ROM. Frameworks are also sensitive to compression. DO NOT use winzip to handle the files, it can cause problems with the final apk file.
There are several things you would need before you start
A rooted phone
SDK installed on the computer
A zip handling software other than winzip (winRAR and 7-zip are both good options)
Auto-sign (http://forum.xda-developers.com/showthread.php?t=471634) or signing tool (http://forum.xda-developers.com/showthread.php?t=473580)
Create a backup
Grab the framewor
k-res.apk and twframework-res.apk from your phone. They are located in the system/framework folder. You would need them as a starting point for your modification and you need them for a backup
Create a clockwork installation file of the original files (see post below)
Name the installation framework-original.zip, or something else that would be easily recognized in
case of trouble, and then copy it to your internal sd card.
After you are done modifying files
Create an installation file (see post below)
Give the file a name that is easy to recognize and copy it to your internal sd card
Reboot into recovery
Select install zip from card -> choose zip from sdcard
Select the installation of the new framework and confirm the installation
Reboot
If you are stuck in an infinite boot-up cycle
Take the battery out
Using 3-key combination boot into recovery (up-down volume + power. Hold until the AT&T screen cycles back, then release)
Install your original framework backup and reboot
Creating clockwork installation
After you have finished modifying the files, the best way to get them to the phone is through clockwork installation. Make sure that you have the original update.zip file on the sdcard. If you have a rooted phone, you probably have that already, but if not you can install ROM manager from the market and run it to get the update in place.
To create the installation file follow these steps:
Create a folder \framework
Place your modified framework files in that folder
Back in the main folder, create the following folder tree: \META-INF\com\google\android
In the android folder create a text file named update-script
WARNING: Do not name your framework file "update.zip"! You need both the original update.zip and the framework one for the installation.
Note: Although copying of the framework files may be possible, it is highly risky. In my experience installation from clockwork is the easiest
Puzzle Lock Screen Mod
Here is information for people who want to modify the look of the puzzle lock screen. It is only the list of images to replace, not the coding to change functionality.
The files sit in framework-res.apk under res\drawable-hdpi. The files are zzz_unlock_puzzle...
puzzle pieces
zzz_unlock_puzzle_noti_icon_call.png : Missed call piece in the floating state
zzz_unlock_puzzle_noti_icon_call_fit.png : Missed call when it gets to the unlock spot
zzz_unlock_puzzle_noti_icon_unlock.png : General unlock floating
zzz_unlock_puzzle_noti_icon_unlock_fit.png : General unlock at the unlock spot
Same for messages and voicemail.
Background
zzz_unlock_puzzle_bg.png : The image that shows on the lock screen. This should be semi-transparent if you want to show the regular screen background
zzz_unlock_puzzle_bg_pressed.png : Image that shows while dragging the puzzle pieces. Usually a slight modification of the regular background
zzz_unlock_puzzle_bg_land.png : The landscape version
Music player
zzz_unlock_disk... and zzz_unlock_ctr_pr... are the files related to the player.
zzz_unlock_ctr_bg.9.png is the background for the music controls
Text background
Overlaying the unlock image is text. That text can have background that is more opaque than the rest of the unlock screen.
The attached image shows the three regions. These regions also apply to the glass unlock.
Note: These are .9 files and should be done right to ensure correct stretching and text boundries.
Other files
There are some extra background files in the frameworks but I haven't been able to find where they go. There are also some files to control the clock numbers zzz_unlock_clock_...
Working with APK manager
What is APK manager?
APK manager is a tool for decompiling / recompiling apk files. If you want to change anything other than images, it is a must have.
The basics
The basic flow when using APK manager is
Place apk file in place-apk-here-for-modding folder
run the Script.bat file
Type 22 and select the file you want to work with
Type 9 and wait for it to finish decompiling
Modify the items you want modified (they will be in the projects folder)
type 11 to recompile
Sounds easy? It is, and it isn't. There are several places where things can go wrong. Here are a few of the things to watch for:
Bad starting file
This is mostly true for framework files that went through several cycles of modifications. The framework is forgiving to having extra items, or having bad .9 images (see post above about .9 images). Some people may have replaced images without recompiling the framework in a way that breaks internal links. If this happens you will very likely see error messages during the decompile stage. If that happens check the log file and correct things. One of the most common errors is .9 files replaced with regular images. See this post for how to solve this.
Things may not always be "fixable", so the best approach is to get the original framework that is the base for the one you need. Having a clean start can save a lot of headaches later on.
Overwriting your changes
When you recompile, assuming everything worked ok, you are prompted if this is a system file. Most likely you want to say yes. This ensures that the original signature is copied over. You will also be prompted if you want to copy some files over from the original. BE CAREFUL!. There are people who say you reduce the risk of errors if you copy things that didn't change. Personally, if I changed anything that required recompilation (mostly added new images or modified xml files) I always choose not to copy extra files. If you do choose to copy some files over, pay attention to the next step. Do not hit any key until you remove the modified files. You will need to go to the newly created "keep" folder (in the top apk manager directory) and remove any image that you changed and any xml that you modified. Also, if you modified xml files to add new images you need to delete "resources.arsc".
Failed rebuild
APK manager is trying to minimize work by only compiling newly changed items. If you built an apk and realized you have an error, or want to add more changes, I recommend removing the cached build. Go to the projects folder and delete the "build" folder. I've had cases where the new items didn't catch.
Removed items
I highly recommend to leave icons that you do not need. I've had occasions where I removed things that I thought had no more reference, but then ended with endless boot-loops. For example, if you modify the xml to only show 6 out of the 101 battery charge animations, leave the remaining icons in your project.
If you're stuck
Look at the log file. That would usually give you an answer. Also, if you are working on a recent GB ROM you probably need to get the beta 5 version. Version 4.9 will have problems compiling the newer files.
Thanks for the info!!! I have been wanting to play with themes for a while. Now I gots the knowledge.
sent from my Cap using the app.
Thanks for this post...I'll be looking into this for sure.
tsachi said:
After you have finished modifying the files, the best way to get them to the phone is through clockwork installation. Make sure that you have the original update.zip file on the sdcard. If you have a rooted phone, you probably have that already, but if not you can install ROM manager from the market and run it to get the update in place.
To create the installation file follow these steps:
Create a folder \framework
Place your modified framework files in that folder
Back in the main folder, create the following folder tree: \META-INF\com\google\android
In the android folder create a text file named update-script
WARNING: Do not name your framework file "update.zip"! You need both the original update.zip and the framework one for the installation.
Note: Although copying of the framework files may be possible, it is highly risky. In my experience installation from clockwork is the easiest
Click to expand...
Click to collapse
Thanks for this.. Question In #4 above the text file in the android folder. Is that an empty file? no extension? Thanks for your help.
TorqueWrench001 said:
Thanks for this.. Question In #4 above the text file in the android folder. Is that an empty file? no extension? Thanks for your help.
Click to expand...
Click to collapse
The file has no extension but it isn't empty. It contains the installation instructions. Typical instructions would be:
copy_dir PACKAGE:framework SYSTEM:framework
which copies everything in the frameworks folder in the zip file to the system/framework folder on the phone
Sent from a captivate running phoenix using XDA app
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=916814
Good info
Thanks, been wanting to play with themes for a while now!!!!!
This needs a bump for all those requesting themes to be made.
This needs to be a sticky. I detailed guide is just what was needed. I been wanting to play around with themes but always end up doing something stupid so it never works. Now I have some more knowledge and hopefully can avoid that mistake.
Thank you, one of the links has the info I need to fix my text color issue in my notification/menu window!
Sent from a phone using an app.
Why it's not pinned it's beyond me. We have a thread pinned for must have apps that aren't even must have apps, but not this.
That was do to some how me missing this thread for the post few months. It is corrected now. Stuck
Since the thread is getting more life, I just added info on lock screen (fourth post)
Sent from my captivate running the latest firefly
Resorce dump
Well now that this is not going to fall to the depths of page 500, ill unload some rubbish into it.
http://android.modaco.com/content/zte-blade-themes-and-design-customisation/328510/guide-theme-editing-and-related-things/
http://forum.xda-developers.com/showpost.php?p=9066440&postcount=1
http://forum.xda-developers.com/showthread.php?t=593932
http://forum.xda-developers.com/showthread.php?t=695701
http://forum.xda-developers.com/showpost.php?p=8105110&postcount=2
http://developerlife.com/tutorials/?p=309
http://www.droidforums.net/forum/team-inversion-conversion/116419-so-you-want-edit-xmls-more-adb-apk-manager-how-basics.html
http://www.colorschemer.com/online.html
http://www.colorsontheweb.com/colorwizard.asp
Edit: I purposefully did not include descriptions in the links. If you dont know what your doing reading all but the last two links in there entirety will help get you on your way.
whiteguypl said:
Well now that this is not going to fall to the depths of page 500, ill unload some rubbish into it.
http://android.modaco.com/content/zte-blade-themes-and-design-customisation/328510/guide-theme-editing-and-related-things/
http://forum.xda-developers.com/showpost.php?p=9066440&postcount=1
http://forum.xda-developers.com/showthread.php?t=593932
http://forum.xda-developers.com/showthread.php?t=695701
http://forum.xda-developers.com/showpost.php?p=8105110&postcount=2
http://developerlife.com/tutorials/?p=309
http://www.droidforums.net/forum/team-inversion-conversion/116419-so-you-want-edit-xmls-more-adb-apk-manager-how-basics.html
http://www.colorschemer.com/online.html
http://www.colorsontheweb.com/colorwizard.asp
Edit: I purposefully did not include descriptions in the links. If you dont know what your doing reading all but the last two links in there entirety will help get you on your way.
Click to expand...
Click to collapse
Very nice, I will add these to OP with details about each link.
I'm quite happy that this has been pinned finally. Now to get to work. I haven't decided on which ROM I want to do, or even if I wanna port another theme or make my own. SO MANY CHOICES!!
Index
post 1: Introduction
Post 2: Simple image swap
Post 3: Decompiling and recompiling files
Post 4: Image locations in Sense ROMS
Post 8: How to use the kitchen
Post 9: Advanced modification: Add / Remove alarm notification
Post 10: Advanced modification: Add / Remove Location indicator
Introduction
There are several resources available with information about theme creation, however I find that information is usually scattered on many different threads. It is also not always newbie friendly. In this thread I would like to give a quick summary for the newbie to help start making your phone look the way you like it. Before I go into the actual details, I would like to suggest some shortcuts. You don’t always need to do things the hard way. The options that you have are:
Use the Ultimate online Kitchen . For those not familiar, this is an online tool that lets you pick and choose components and then packages them for you into the base files you supply. You can get very far using the kitchen with lots of options for customizing your phone.
Start with the kitchen and add some images. The kitchen is great to get a good baseline without going into code. You don’t have to worry about finding where color definitions sit, or what hex values are good to use. Most of the time, however, we want icons that are not available in the kitchen. The solution a lot of themers are using is to create a good base in the kitchen, then add modifications of their own.
Replace individual images, but keep everything else the same. This is a solution for those who want to manually swap battery files, or create their set of notification items and move it from ROM to ROM. You can use this either on the stock files from your ROM, or on files you generated in the kitchen.
Going into the guts – this is the advanced version. You decompile the files and modify the source code to get what you want. This is the only way to get the non-standard stuff done. Once again, you can start with a stock ROM, or you can run it through the kitchen to do some of the tedious work and then go into the guts.
I will describe the methods for both 3 (post 2) and 4 (post 3). I also have a list of where you can locate icons on the phone in post 3, that I will expand in the future.
Background
System Icons and background images sit in two main files: framework-res.apk (in system/framework) and system-ui.apk (in system/app). Additionally, sense ROMs have com.htc.resources.apk (in system/framework Within these files there is a res directory, and under that you have the folders containing data. Google has guidelines on icon design, although themers usually ignore those in order to get a different from stock look. One thing you would notice is that there are sometimes repeated folders of icons. This is usually baggage from different android versions (2.1, 2.2, 2.3). One thing to remember, it’s usually easy to add images, but you can get into all sorts of trouble if you ake things out.
Each application has its own res folder where the launcher icon and other visuals are kept. There are, however, a lot of applications that reference the framework.apk for visuals. For example the my location in maps, or google talk notification.
There are 2 types of images that you would encounter. Normal icons and images are non-scalable. They take a certain amount of real estate on the phone, and that’s it. Example of these are the battery levels and notification icons. The other type is the .9 images. These are images that are going to be stretched to fit whatever space is needed. An example of that are the menu backgrounds. The .9 images have a special format. The one pixel border around them defines how they stretch and how content is displayed in them. It is highly recommended to follow the standards in order to get repeatable and consistent look. Android SDK has a tool to help with .9 file design: draw9patch.bat.
Important note: The .9 files show the borders ONLY when de-compiled. If you grab a file from the framework directly you will not see that line. It is therefore required to compile the .9 files after you make them. You can use apk manager or ThemePro-JAVA to recompile the framework apk after modifying the files.
Definitions for which image is used where sit in the xml files under the drawable folder. These are compiled xml files, you can’t edit them with a text editor. For this introduction I will not go into modifying xml files, but I’ll describe it in a later post. Each apk also has a resources file that describes what is in there. If you add, remove, or rename files in the apk you will have discrepancy with the resource file and the theme will not work (more likely you will be stuck in an infinite bootup loop). To add, remove, or rename files you have to go through full apk decompile.
Before you start:
Warning: frameworks are highly linked with other files. You can’t just take a framework from one ROM and put it in another. Always keep a backup of the original files ready to be installed (see below), otherwise you may need to re-flash the ROM. Frameworks are also sensitive to compression. DO NOT use winzip to handle the files, it can cause problems with the final apk file.
There are several things you would need before you start
A rooted phone
SDK installed on the computer
A zip handling software other than winzip (winRAR and 7-zip are both good options)
Amend2edify . If you are on a mac you will need auto sign for mac instead
For advanced work - APK manager
These are mostly windows tools, with some support for linux, so if you're on a mac you need to find the equivalent program.
Create a backup
Grab the framewor k-res.apk, com.htc.resources.apk and system-ui.apk from your phone. They are located in the system/framework and system/app folders. You would need them as a starting point for your modification and you need them for a backup
If you plan to modify any other files, grab them and note where you took them from (most likely /system/app for things like dialer, email, etc)
Create a clockwork installation file of the original files (see post below)
Name the installation framework-original.zip, or something else that would be easily recognized in case of trouble, and then copy it to your internal sd card.
Create installation and test it
After you have finished modifying the files, the best way to get them to the phone is through clockwork installation. You can push files to the phone using adb, but in my experience it's not worth it.
Create install file
I am calling the parent folder “main”
Create a folder main\framework
Place your modified files (framework-res.apk and com.htc.resources.apk) in that folder
Create a folder main\app
Place the modified files (system-ui.apk + any other apps you modified) in that folder
Create the following folder tree:main \META-INF\com\google\android
In the android folder create a text file named update-script
Edit the update-script file content “copy_dir PACKAGE:app SYSTEM:app copy_dir
PACKAGE:framework SYSTEM:framework”
From the main folder add the three folders you created to a new zip file
Use amend2edify to convert and sign the zip file you created
WARNING: Do not name your framework file "update.zip"! Do not name your file “PG05IMG.zip”!
Testing
Give the file a name that is easy to recognize and copy it to your internal sd card
Reboot into recovery
Select install zip from card -> choose zip from sdcard
Select the installation of the new framework and confirm the installation
Reboot
If you are stuck in an infinite boot-up cycle reboot back to recovery
You can try to send “adb reboot recovery” to the phone over usb
You can battery pull then use power + volume key to boot into recovery
Install your original framework backup and reboot
hint: if you are like me and have a lot of files, name your test file z_filename.zip That way in recovery you use the up volume and get to it quickly.
Simple image swap
Simple image swap
If all you want to do is swap some images, all you need is a zip handling application (I recommend not using windows built in zip, it does not have the flexibility to properly do everything you need).
Select the apk file you want to modify and open it using a zip program
Inside the opened go to \res\drawable-hdpi\
You can extract all the images from that folder as a starting point
Modify the images you want
Copy the modified images back into the \res\drawable-hdpi\ folder in the apk file
A few things to watch for
Do not try to modify any file that ends in .9.png using this method. You are likely to create weird looking visuals on the phone
If you already know which files you want to copy over (let’s say you have a set of images that you are moving from one ROM to another) you don’t need to extract the images from the apk. Please note, however, that not all base versions use the same file names. Double check the filenames in the new apk before copying over your existing images.
Sense and AOSP roms sometimes use images from different locations (sense may use system-ui.apk for signal and AOSP may use framework-res for signal). If you try changing one place and it doesn’t work, try the other. Over time you will learn what sits where.
Different ROMS and different themes make changes to the xml files, telling the system which images to use. This means that copying files over may not be enough. This is mostly an issue with battery and battery charging, but other status bar animations can be affected. For example, if you start with a stock based rom that only uses 5 levels of battery indication you can copy over 100 images to show accurate progress, but on the phone you will still see only 5 (and probably the wrong 5). Similarly, charge animation can be 5 icons, 30 icons, or 100 icons. It can include the current battery level or not. Copying images from one type of animation to another will result in something that does not make sense on the phone. You have two options to solve this. You can take the full mod way and modify the xml, or you can try to run the framework through the kitchen and select a battery mod that has the behavior you want. After that you can modify the files.
Decompiling and recompiling files
Modifying files by decompile/recompile
What is APK manager?
APK manager is a tool for decompiling / recompiling apk files. If you want to change anything other than images, it is a must have. EDIT: A new thread for APK manager 5 is out, make sure you don't get the old 4.9 version.
The basics
The basic flow when using APK manager is
Place apk file in place-apk-here-for-modding folder
run the Script.bat file
Type 22 and select the file you want to work with
For AOSP based: Type 9 and wait for it to finish decompiling
For Sense based: Type 10. When prompted, drag your com.htc.resources.apk onto the script window, then hit enter
Modify the items you want modified (they will be in the projects folder)
type 11 to recompile
When prompted about system file answer YES
When prompted about copying files over answer NO
Item 6 is where all the magic happens. Go to the projects folder and you will find a sub-folder with the apk name. Inside you have res, where you can replace images and work on xml files.
Bad starting file
This is mostly true for framework files that went through several cycles of modifications. The framework is forgiving to having extra items, or having bad .9 images (see post above about .9 images). Some people may have replaced images without recompiling the framework in a way that breaks the .9 format. The program saves an empty file with the .9.png extensions and a copy of the original without .9 in it. If this happens you will very likely see warning messages during the decompile stage, but you don't see warnings unless you look at the log. This means that you would actually catch it only at recompile. See this post for more details and how to solve this.
Things may not always be "fixable", so the best approach is to get the original framework that is the base for the one you need. Having a clean start can save a lot of headaches later on.
Overwriting your changes
When you recompile, assuming everything worked ok, you are prompted if this is a system file. Most likely you want to say yes. This ensures that the original signature is copied over. You will also be prompted if you want to copy some files over from the original. BE CAREFUL!. There are people who say you reduce the risk of errors if you copy things that didn't change. Personally, if I changed anything that required recompilation (mostly added new images or modified xml files) I always choose not to copy extra files. If you do choose to copy some files over, pay attention to the next step. Do not hit any key until you remove the modified files. You will need to go to the newly created "keep" folder (in the top apk manager directory) and remove any image that you changed and any xml that you modified. Also, if you modified xml files to add new images you need to delete "resources.arsc".
Failed rebuild
APK manager is trying to minimize work by only compiling newly changed items. If you built an apk and realized you have an error, or want to add more changes, I recommend removing the cached build. Go to the projects folder and delete the "build" folder. I've had cases where the new items didn't catch.
Removed items
I highly recommend to leave icons that you do not need. I've had occasions where I removed things that I thought had no more reference, but then ended with endless boot-loops. For example, if you modify the xml to only show 6 out of the 101 battery charge animations, leave the remaining icons in your project.
If you're stuck
Look at the log file. That would usually give you an answer. Also, if you are working on a recent GB ROM you probably need to get the beta 5 version. Version 4.9 will have problems compiling the newer files.
Image loactions in Sense ROMS
Image locations for Sense roms
Framework-res:
1. Progress bar information. Some is in xml files (just color definitions), but there is progressbar_indeterminate*.png that has the progress bar with diagonal lines
2. Spinning processing indicator: spinner_black*.png and spinner_white*.png
3. Most notifications (stat_notify_*.png) including the sync animation (stat_notify_sync*.png)
4. Battery (stat_sys_battery*.png) and battery animation (stat_sys_battery_charge_anim*.png). There are also the stat_sys_battery_unknown.png and stat_sys_battery_charge_animfull.png (this one does not show up on sense)
System-ui:
1. Signal related notifications (Bluetooth, wifi signal, network signals) in stat_sys_data_*.png. Note that connection type is usually named like stat_sys_data_connected_3g.png, but I’ve seen those with different naming conventions
2. Alarm, location, and the “more” stat_notify_alarm.png, stat_notify_more.png, sym_gpsone*.png.
3. GPS: stat_sys_gps_acquiring*.png, although gps on is usually in framework-res (stat_sys_gps_on.png)
Elsewhere:
1. Email and Gmail notifications (in mail.apk and gmail.apk)
2. USB connection (in pcsII.apk)
3. Google voice (in gvoice.apk)
How to use the kitchen
Link: http://uot.dakra.lt/kitchen/
The kitchen's XDA UOT page has all the information on how to get started. I will just give a quick introduction here specific to the TB roms.
When you go to to the web site you have several tabs. go through one at a time and select the modifications you want. The simplest example would be to change the stock battery of the ROM so I'll use that.
1. Select the tab of interest
2. Check the "use this mod" box and the options appear. You can choose the preview option, but don't have to.
3. Once you're done select the File upload tab.
4. In the section Select your rom from kitchen's list, or upload your own files check the "system files" radio button
5. Upload framework-res.apk, SystemUI.apk, and com.htc.resources.apk (for sense ROMs). You will need to extract them from the ROM's installation file if you are on stock view or from the theme install file if you are using a theme. You can also get it from your phone (copy the files to the sdcard using root explorer and then to your computer, or use adb pull if you know how). twframework-res.apk is for Samsung phones only.
IMPORTANT: Some mods require SystemUI.apk and some require framework-res.apk. If you are not sure which one you need upload both. In any case ALWAYS upload com.htc.resources.apk for a sense ROM, without it the kitchen will fail to compile your mod (AOSP based roms don't have the com.htc.resources.apk)
6. Go to the summary page and select "submit work to kitchen"
7. Wait patiently for your files to be ready. It can take a while when the server is busy.
8. Install your modified files and enjoy
Advanced modification: Add / Remove alarm notification
For this modification you will need to decompile SystemUI.apk (see above post).
Go to the SystemUI.apk\smali\com\android\systemui\statusbar\policy folder created by apk manager. Find StatusBarPolicy.smali
search for the text
const-string v1, "alarmSet"
Click to expand...
Click to collapse
There is a line before that that starts with .line and a line after that starts with .line. This is the section you need to change.
Note: The line numbers can vary from ROM to ROM. DO NOT change those two lines. Replace the entire content between them.
Show Alarm Clock:
const-string v1, "alarmSet"
const/4 v2, 0x0
invoke-virtual {p1, v1, v2}, Landroid/content/Intent;->getBooleanExtra(Ljava/lang/String;Z)Z
move-result v0
Click to expand...
Click to collapse
Hide Alarm Clock:
const/4 v0, 0x0
const-string v1, "alarmSet"
const/4 v2, 0x0
Click to expand...
Click to collapse
Recompile the apk and install.
Advanced modification: Add / Remove Location indicator
This will add or remove the general location indicator. It does not affect the GPS indicator.
For this modification you will need to decompile SystemUI.apk (see above post).
Go to the SystemUI.apk\smali\com\android\systemui\statusbar\policy folder created by apk manager. Find HtcCdmaStatusBar.smali
search for the text
.method private updateMtGpsIcon()V
Click to expand...
Click to collapse
The section you are interested in is
.method private updateMtGpsIcon()V
.locals 7
.prologue
const/4 v5, 0x3
const/4 v4, 0x1
const/4 v3, 0x0
Click to expand...
Click to collapse
Show location indicator
const/4 v4, 0x1
Click to expand...
Click to collapse
Hide location indicator
const/4 v4, 0x0
Click to expand...
Click to collapse
I am not sure where I have missed it but when I download the newest APK manager and open the zip there isn't a folder that says place apk here or anything like it in any part of the apk manager. Did I miss something in the instructions about this folder being somewhere else?
TDubKong said:
I am not sure where I have missed it but when I download the newest APK manager and open the zip there isn't a folder that says place apk here or anything like it in any part of the apk manager. Did I miss something in the instructions about this folder being somewhere else?
Click to expand...
Click to collapse
They will be in the directory you installed it to, so something like, c://ApkManager/
Sent from my TBolt using my f***king thumbs...
TDubKong said:
I am not sure where I have missed it but when I download the newest APK manager and open the zip there isn't a folder that says place apk here or anything like it in any part of the apk manager. Did I miss something in the instructions about this folder being somewhere else?
Click to expand...
Click to collapse
If it isn't there as a subfolder when you extracted it, it should be created the first time you run the script
Sent from a gingerbread thunderbolt
tsachi said:
For this modification you will need to decompile SystemUI.apk (see above post).
Go to the SystemUI.apk\smali\com\android\systemui\statusbar\policy folder created by apk manager. Find StatusBarPolicy.smali
search for the text
There is a line before that that starts with .line and a line after that starts with .line. This is the section you need to change.
Note: The line numbers can vary from ROM to ROM. DO NOT change those two lines. Replace the entire content between them.
Show Alarm Clock:
Hide Alarm Clock:
Recompile the apk and install.
Click to expand...
Click to collapse
Would this tutorial work for removing the clock and battery from the status bar?
sent from my mecha using XDA Premium App
warmonster said:
Would this tutorial work for removing the clock and battery from the status bar?
sent from my mecha using XDA Premium App
Click to expand...
Click to collapse
This is the file you need, but the changes are different from what I described here. I'll try to look them up and add them
Sent from a gingerbread thunderbolt
tsachi said:
This is the file you need, but the changes are different from what I described here. I'll try to look them up and add them
Sent from a gingerbread thunderbolt
Click to expand...
Click to collapse
thanks man, I want to learn how to do this but right now this looks very confusing. Also I downloaded apk manger but some vgrabber program installs and I cant find apk manger.
warmonster said:
thanks man, I want to learn how to do this but right now this looks very confusing. Also I downloaded apk manger but some vgrabber program installs and I cant find apk manger.
Click to expand...
Click to collapse
Here are the instructions http://forums.miuiandroid.com/showthread.php?5603-Q-Removing-the-clock-from-the-status-bar, .should work on our ROM too, but I haven't tried it yet.
In terms of apk manager, it is a zip file that you extract, should not install anything else. I think you clicked on a wrong download somewhere. I updated the link to the new apk manager 5 thread, try from there.
Awesome write up!!! Just found this this morning while at work. I've been stubbing my toes all weekend through trial and error to accomplish what you've summed up here. Thank you so much! Subscribed for a more thorough read when I get home.
Sent from my ADR6300 using xda premium
Hey my man, I'm trying to use the kitchen from my phone Inspire 4g..and when I try to upload files to kitchen I don't know where it looks for them at in my phone. It will open my upload folder but I can't find it on my phone anywhere? Dose anyone know what parent folder the upload folder is in...
Sent from my Inspire4G using xda premium
Towboat_man said:
Hey my man, I'm trying to use the kitchen from my phone Inspire 4g..and when I try to upload files to kitchen I don't know where it looks for them at in my phone. It will open my upload folder but I can't find it on my phone anywhere? Dose anyone know what parent folder the upload folder is in...
Sent from my Inspire4G using xda premium
Click to expand...
Click to collapse
First, I think it mentions somewhere on the site or on the kitchen XDA page that they are generally not compatible with phone browsers. Not sure what the compatibility issue is, but you may want to look it up. If you do get it to work from the phone you need a way to browse the system folders. If you can't see the /system/ when you browse for files I would suggest using root exlorer (paid) or file expert (free) to first copy the files over to the sdcard, and then go through the web site and grab them from the card. A lot of the basic explorers, especially those that weren't designed for rooted phones, don't have access to the /system/ so that may be your problem. The files are in /system/framework/ and in /system/apps
Hello A little while ago I managed to learn how to theme totally from scratch. I knew nothing of anything before I started, but now I know how to port themes As I still see myself as a n00b there may be some weird things I've done, but at least I manage to create the themes This might not be the best way to theme, or the easiest, but it works
Overview PNGS
1) Getting the files
2) Getting the images
3) Port
4) Package and Sign
The only programs I've used is 7zip and autosigner download them and install 7zip and extract autosigner to a nice location for example your desktop
Getting the files
The first you need to do (after getting the programs) is to find the file you will mod (edit). This will mostly be the framework-res.apk because this decides most of looks of phone (for example the statusbar). Download the .zip of the rom your going to theme. Open it up (shouldn't require any programs, if does, use 7zip: either drag it onto the 7zip icon or right click and choose open with). Open system -> app and copy the framework-res.apk (or any other apk you would like to theme, for example the settings). Now paste it into an appropriate folder.
Getting the images
Now you need to find the images you want to use in your new theme. Find either an update.zip with a theme or an .apk with a theme chooser theme (if there is both a version for Froyo and GB, use the Froyo version as this will make it easier ) Open it up with 7zip (drag it into the 7zip icon). Now you can do either of two options:
1) You can take the whole drawable-mdpi folder and copy it out. You should probably don’t do this with a Themechooser apk, as they usually don’t have all icons in this folder, as they often lend a few from HDPI.
2) Take only the images you want and copy them to a folder. For example if you want the signal icons, copy the “stat_sys_signal_0” (-4 of course) and copy them out. If you want the statusbar background, copy “statusbar_background”. This way you can mix several themes, take the best of several themes and make your personal theme
When you’re done getting your icons, close the window.
Porting
Now open the Rom’s default framework-res.apk with 7-zip. If you’re going to port a whole theme, delete the /res/drawable-mdpi folder and copy in your own. If you’re going to port just a few icons, open the /res/drawable-mdpi folder and paste your icons. You might want to check if the icons have the same names in the different framework. For example the headset icons can be both “stat_sys_headset” and “stat_notify_headset”. Also if you port from a theme chooser theme, you will have to rename every single .png you port. This is really boring, but necessary. You need to remove the “framework_res” and the “android_systemui” from the beginning of all the names. So “framework_res_activity_title_bar.9.png” needs to be changed to “activity_title_bar.9.png”. Because this is so boring you better keep your renamed icons, so it’s easier to port it to another rom
This is kind of off-topic: my carrier lends network of another carrier. Therefor my phone is allways roaming. This puts a stupid “r” with my signal icons. To avoid this I allways take normal signal icons, copy them, and rename one of the two .pngs from for example “stat_sys_signal_1” to “stat_sys_r_signal_1”. This way I get rid of this stupid “r” and it will always show the normal icons
Packing and signing
Now the porting is done and the next job is to push the new framework to your phone. If you are familiar with adb, you can push it to system/framework on your phone. You don’t need to anything more with the apk before pushing it. Else you can create a flashable .zip for your theme. I’ve attached a .zip with update script (I haven’t created it. Just stole it from one of Elelinux’ add-ons ). Download the zip. Create a folder named system and a folder named framework. First drag the new, modded framework_res.apk to the framework folder, then drag the framework folder into the system folder, before you drag the system folder into the attached zip. If you use Clockworkmod recovery, you can just flash the zip right as it is, but if you use Amon_Ra or want it to be compatible with every recovery because you want to post it, you need to do something.
Unpack autosigner and launch the exe file inside. Drag the .zip into the new window and press sign. It will now appear a new file in the same folder as the file you wanted to sign. Its name is the same, but with “_signed” at the end. You can rename the file as you wish both before and after the signing.
XML Editing:
I decided to add a little section about XML editing as well I really don't know all about this myself, but i can tell how to set it up and some examples to what you can do Even though this may seem really complicated, it's not written in a completely different language, like Java in the smali files, so often it is possible to use logic to get what you want
Tools needed: APK Multi-tool. as well as Java, if you don't have it installed.
Overview:
1) Setting up
2) Examples
3) Finish
Settings up
Download APK Multi-tool and extract/ unzip it to wherever you want ( I have it on my desktop). Now you can place the apk you want to modify (usually the framework_res.apk) in the "Place_apk_for_modding" folder. Then you open the script. If you don't get an error, proceed to b), if you do get an error proceed to a)
a)) If you do get an error where it says something like "java not found" you need to correct the Java path (or install Java if you haven't done that, which you should have) . I had to do this to get it working. First open my computer and click disk C, or D if you have installed Java there. Open programfiles (or whatever it's called in your language) and scroll to the Java folder. Now open the folder there jdk folder or whatever you have there and open the "bin" folder. Look at the top of your window, where it says where on you're computer you are (like Windows: C to the left, and then Programfiles and so on). Right click it and click copy address. Mine is "C:\Program Files\Java\jdk1.7.0_01\bin . Now you can close the window.
Open "My computer" again. On the top bar below the navigationbar, click Sytemoptions (sorry, not really sure what it's called in Englsih, as my computer is Norwegian, please correct me if I'm wrong). On the left click the "advanced" link and in the popup that appears click "environment variables". Scroll down to the "path" variable and edit it. Paste the address you copied and click OK. You should now be able to proceed to b). If you still get an error, please tell me and I'll try to help
b) type 25 and press enter to select current project. Here you will see all the apks in the "Place_apk_for_modding" folder. Select the appropriate number (in this case probably 1) and press enter to continue. Then you hit 9 and enter to decompile it. I cannot really explain it, but it enables you to edit the xmls in the apk. If you try to edit them by using 7Zip, the xmls will be just messed up. When it's done decompiling, you have gotten a new folder in the "projects" folder. In this case it is probably named framework_res.apk. Minimize the script (DON'T CLOSE IT) and you're ready to edit the xmls
Examples on edits:
COMING SOON
Finish:
When you're done editing, open the script again (remember what I said about not closing it? ). Click 11, unless you are editing a non system apk. If you are editing the framework or settings or such, use 11. If you get an error now, you have probably done something wrong, try to see in the log what you have done wrong. Every time I've had an error, I've ended up in bootloop when I've flashed, so it is probably better to just start over. Another tip is to do one thing at the time. For example: you decompile, edit the notification color in pulldown, compile. Take the compiled apk, decompile edit another thing and so on, this makes it easier to not mess up and it also shows what you are doing wrong.
On the "Is this a system apk?" you should probably say y, as I said above. I also usually copy over the files I didn't edit, as this seems safer. Follow the instructions and you should be fine. When you're done and the script is done compiling, you will find a unsigned_**** (for example unsigned_framework-res.apk) in the "place_apk_for_modding" folder. This is your modified apk, and you can try to push it to ur device with an update.zip or adb, if you know how to use that
Well this was the end of my guide for now If there's anything which is unclear or you have other suggestions, feel free to post I've probably forgotten something
Finally after all my attemps to modify the android framework before i have do it correctly. I have changed a couple of things, the lock screen and battery icons so far. The framework I'm modifying is the one on Ele's Gingerbread and i wonder how to get the battery icon percentage 1 by 1 as i saw in some other themes. What i mean is that in the original framework there is only battery icons for 15, 20, 25 and so on, and if i push the 16, 17, 18, 19 they won't work. Is Theme Chooser the one on charge of this? how can i get that? some help please?
(Also tryed to theme a sense rom, but everything was messed up, i guess because of sense or maybe I did something wrong)
So thanks for your guide, really helpfull
Yeah, I've never tried to theme Sense so I don't know. It is probably possible to make icons for every %, but then you'll have to decompile using APK tool, and it is harder. I don't know how. If you want to try, you could try asking a question here
thanks
so funny=))
i'm tried
Great guide helped me a lo thx.
Finally, someone who CAN explain it...
I'm now porting ICS to GB (no cm7), cause I think CM sucks.
mDroidd said:
Finally, someone who CAN explain it...
I'm now porting ICS to GB (no cm7), cause I think CM sucks.
Click to expand...
Click to collapse
Hmm, ICS themes can be made really awesome, if you do some more advanced stuff. For example you want to remap the pulldownbar a bit, and change som text colors. But to do this you need to use a tool like APK multi-tool, and it is a bit more advanced. If you want to, I can create a new section where I show how to this
Thank you.
GUIDE UPDATED! Added a section about XML editing really quick, probably forgotten something and such, so just ask if there is something you don't understand This is for those who are getting used to the PNG editing and want to proceed to something slightly more advanced, for example you 7Tosta
Cheers
BTW: I should've reserved the 2nd post, this is getting messy
Edit: If there's anything specific you want me to add to the EXAMPLES section, tell me
Good Afternoon XDA Family and Friends - Modders and such...
Today, I would like to bring you something of a how to that would possibly get Sticky-d as I think that this app is growing in popularity and customization requests. Due to some demand on our Youtube Partner Channel, we are working on a Video on how to modify and deploy these new themes for this app to your non-rooted phone / device.
Many of you may or may not know about this software: MiLocker - App to allow you to get the MIUI type Themes that are seen on their ROMS on Non-Rooted and Rooted Phones. This app will let you customize your Lockscreen and have that MIUI type theme.
Please note that this tutorial - How To involves basic knowledge of XML and modifications of types of variables that are used in the theme.
I have enclosed 2 Samples that you can use as a basis, I have converted them from Japanese / Chinese language so that you can understand them better.
Some of the basic steps are outlined below.
1. First get the theme downloaded that you wish to modify using the Machine of your choosing: Mac or PC.
a. Upon getting the theme from the provider of the application to the device, you will then need to get it on the PC.
b. Connect your device to your machine as normal, and use “Disk Drive” to access the data storage on the device. (this could be internal or SD depending on device)
c. Once you have accessed the data on the device, look for the folder “MIUI” and under will be the “Theme” folder. In this folder will be all your downloaded themes. (MTZ Format)
2. After you have the MTZ files copied to your machine, (always best to create copies as this ensures you don’t break the mtz file you have already as source)
3. You can then (if you don’t already get 7zip for PC or The Unarchiver for Mac both free utilities) to then open the MTZ file and extract it’s contents to your desktop or destination of choosing.
4. Upon extraction you will usually find a few folders and files in there. Most notably: “Preview Folder”, “Wallpaper Folder” “Fonts folder”, lockscreen file, icons file, description.xml.
5. These are usually the basics for the theming. Most of them are self-explanatory.
a. For modifying or making your own wallpaper or preview, this is quite simple, just modify the wallpaper you find in the folders and create new ones using Paint, Photoshop or GIMP (utility of your choice)
b. Create a new wallpaper of the same dimensions used and name it the same as the original file found in the folder. Just delete the original when done. (Best cases for this I have tested are : 480x954, 480x860 and a few others) at about 72DPI or better.
6. Once you have created the wallpaper and it’s preview that you wish to show in the chooser, place those files in the respective folders.
7. To first start the modification and in this the main reason for the XML is to change the Chinese Characters displayed to English or US. Most people will just change the Wallpaper and repack, and that is ok. This is for those who seek to have English displayed.
8. In the first XML : description.xml - This file allows you to customize fields of Title of the Theme , Author, Version and such. These are the only three I recommend changing. ONLY CHANGE DATA between the <Title> THIS IS TO BE CHANGED</Title>
a. (changing only the data between the start and stop tags which are the <Field></Field> items)
9. Please note that changing the information in-between the start tags and end tags for XML is how the data is read by the application. So those values are how this is displayed.
10. The second XML is called the manifest.xml file, and it’s in the lockscreen file.
11. To modify this file, you need to rename the lockscreen file to lockscreen.zip and then extract the contents and open the folder under and look for the manifest.xml file.
a. Renaming method for Windows: Start > Run > cmd | in the command prompt, CD to the correct location of the lockscreen file and then issue the command with out quotes: “rename lockscreen lockscreen.zip”
b. Renaming method for MAC: Terminal – cd to the location of the lockscreen file issue the following command : “sudo mv lockscreen lockscreen.zip” It will ask for password, input your user password.
12. If the renaming happened correctly you should now see the file as a zip file.
13. You can now extract this file using 7zip or Archive utility or other to extract to a destination of your choice.
14. After you have done this, find the “manifest.xml” file in the folder from extraction.
15. You can edit this file in any great number of free XML utilities out there: PC : Notepad++ and MAC : TextWrangler. Editing this will allow you to find all the characters, which are not English and then copy them, open a browser and go to translate.google.com and translate them and insert the correct words as necessary.
16. When you have completed editing all the Japanese and Chinese out of the document, save it and then back out of the directory that you extracted and then ZIP the lockscreen file back up using Winzip, 7zip or Arhcive Utility in Mac or whatnot.
17. Once you have compressed and ZIP’d the lockscreen folder back up, you will see a new lockscreen.zip file with your modified files in it.
18. Now it’s time for you to Reverse Rename the file and removes the .zip file making it a file plain object. (Hint – Do the reverse of step 11 above, going from lockscreen.zip to lockscreen)
19. Once you have completed this phase, you will need to compress it to a MTZ to put back on the phone. 7Zip has this built in and you can just compress using 7zip and select MTZ as the file format. As for MAC I recommend using this Automator, which will do it for you. (MAC USERS WILL NEED TO TO one extra step)
a. Mac users will need to after creating the MTZ file, make the file Unix Executable – Terminal (open this app) and then go to the MTZ file and issue the following command: “sudo chmod a+x yourfile.mtz” , it will ask for password, do as above. Then the system will make it a UNIZ Executable just like the other MTZ’ files
20. Now transfer the MTZ file you have created back to your device and launch the app and choose your new theme.
MAC TOOLS for MTZ:
PLEASE EMAIL ME for TOOLS (don't have enough posts)
IF you have any questions, please feel free to email us at [email protected]
Or check our Youtube Channel as we will be posting a tutorial on this soon!
Please EMAIL for YouTube Channel (not enough posts)
Thanks.
FluxboxMedia and GeekTekneek
*****UPDATE******
Upon more and more research , our team has discovered that simple repackaging of the theme once modified does not always work as listed above. If you are using the PC and wish to use the 7zip method, the tip we found on DroidForums was to Open the MTZ file in 7zip and leave it open. Then 'Drag' From the file manager of 7zip the contents to your machine which will allow you to modify a copy of the theme. Make your changes , wallpapers and such, and then copy 'drag' them back into the open Archive of MTZ theme you did from above in this update. Once done, close the archive by closing 7zip. If you make any changes to the 'advance' folder under the lockscreen file (note you can just 2x click on the lockscreen file while in the 7zip archive and it will open), you will need to copy the changed files into this folder, and then click the "up one folder icon " it will annouce "There are changes to the original packing files, would you like to update the file and repack?" CHOOSE YES. Then you can close the entire 7zip app and deploy to your device. If you have questions, please feel free to email us. Video YTube tutorials will be online shortly.
Great idea. I really like this application. I also see it becoming a hit.
Yup, this app is awesome! I didn't know about 7zip's ability to compress to mtz, thanks for sharing that. What we really need is a tutorial on converting themes to mdpi
Great tut tho. Excellent and clear.
Tapatalkin it from my IHO CM7.1'd, ICS Themed Optimus V
Thanks for the support so far. We at our studio have done lots over the last 2 years with customizations and installations and testing, and just feel that now is the perfect time on a brand new app.
We are going to be doing a tutorial Video which will show the basics on it.
Some of them however are not happy with configuring the XML in the manifest file. (meaning as soon as you modify any part of it, the repack and then put on device) The theme comes out as just the default.
We are still working on some of the buggy themes.
Thanks
Examples of our work thus far
Examples of the Customization Completed
Converted from Japanese/Chinese to English Format
Attached as Inline image posting is restricted to people more posts than 8
???
Nice, I'm also working a TUT, nice locker/screenlocker to have! Easy to theme!
Pitty it doesn't run the ICS'ed ones
Hello
if i want to modify a theme for my SGA what resolution and DPI should i choose?thnks
kcls said:
Yup, this app is awesome! I didn't know about 7zip's ability to compress to mtz, thanks for sharing that. What we really need is a tutorial on converting themes to mdpi
Great tut tho. Excellent and clear.
Tapatalkin it from my IHO CM7.1'd, ICS Themed Optimus V
Click to expand...
Click to collapse
From HDPI to M/LDPI just resize images, and change dimension values in manifest.xml (be aware of how MIUI roms/apps sees y value), although you don't need to do that, if you're using newest MiLocker version (1.4.2 I guess?). But as for M/LDPI Miui rom port you have to do it.
Sent from my GT-I5800 using Tapatalk 2 Beta-5
Nice Info for people who are Novice about MIUI Themes and Lockscreens.
Thanks for the great tut :good: You deserve more thanks.
Introduction
This is going to be a long post! A few weeks ago I started thinking about making my own themes for my LG G5. I had installed some custom roms previously and used substratum a bit but I have always ended up going back to xpirt's Fulmics rom, which doesn't allow this. I started to think how I could do this and have today got to the first stage of being able to change the colours of my phone to precisely what I want, not only for the settings but in some of the stock apps. I thought I would share this with the community and provide some step by step instructions so you can try it yourself. This should work on LG G6, V10, V20 & V30 if you use an app made for these phones but I have no way of testing this so don't hold me to it. This has taken me about 5 full days to work this out and there is still more that I need to do.
I am not in anyway a developer or coder and have very little knowledge of Java so if anything goes wrong here it is likely that I will not be able to help you. I absolutely am a noob at this and do this only for a hobby, using just my common sense and our friend Google to overcome the problems I have come across. Saying that, I will try to offer assistance if I can.
I managed to make my theme from reverse engineering a free LG theme app that was readily available. If you do this method though please consider getting approval from the app developer first. There is a template on here posted by Raafat here. While this was helpful it was only basic and I could not work out exactly what to do. Reverse engineering an app was much easier. Here is how I did it with step by step instructions:
******DISCLAIMER******
I am in not responsible for what you do to your phone. If you decide to try and theme your phone make a backup first or be prepared to do a full reset if anything goes wrong. You do this at your own risk.
1. Programmes
The programmes/software needed for theming are:
• Notepad++
• Apktool
• Android Studio (I used version 2.3 as I was getting an error on re-signing with 3.0)
2. Installing Frameworks Using Apktool:
• Firstly, delete the files in your local temp directory. To do this open ‘Search’ and type in %temp% and delete all files in this folder. You may not be able to delete some of the files. This does not matter
• Next, extract the framework files from your rom/custom rom. For Fulmics 5.5 this was:
Frameworks-res.apk
lge-res.apk
• At a guess I would say that any rom will have these files named exactly as they are above, but I am not sure if these have been altered by xpirt for his rom so you may not be able to use them across other roms.
• Open a command prompt and navigate to the folder where the framework files are kept. This is easiest in a folder called C:/apktool so create a folder in your C:/ drive and place them there. You can of course name the folder or locate it where you want though.
• Use apktool to install the frameworks using this command in the command prompt in C:\apktool
apktool if framework-res.apk
apktool if lge-res.apk
• Once this is done you should find the following files Installed here: C:\Users\[your username]\AppData\Local\apktool\Framework
1.apk
2.apk
• If, like me, you get an error with apktool that says it cannot write to C:\Users\[your username]\AppData\Local\apktool\Framework and instead has placed them in the temp folder then go into the Local folder using the pathway above and create a folder called 'apktool' and then a subfolder called 'framework'. Try the commands again and it should then work.
• You should also find the following files in the C:\apktool folder (if that is the folder you are using). If they are not here you may have to copy and paste them from the apktool github download.
apktool.jar
apktool.bat
• If you have found these files then you are set to go with decoding the theme/app you have chosen as a basis to amend.
3. Decoding APKs Using Apktool
• Download the apk/app you want to use. I used Backup and Restore app from Play to get the app I wanted to use onto my PC. Once you have this on your PC place the main APK/app in the same folder as the apktool.bat and the apktool.jar (for me this this was C:\apktool)
• Point the command prompt at this place and type the following:
apktool d [app name]
• A folder with the name of the app you just decoded will appear in the directory that you use (in this case C:\apktool)
• In this folder you should find another folder called assets. There may be more sub APKs here in subfolders. This subfolder will likely be assets>overlays
• All the sub APKs in here will have to be decoded otherwise you will have different signing keys and the app, once compiled again, will not work. Decode all the sub APKs in this same folder. You will have to copy the following files to the folder you are decoding the sub APKs in. These are:
apktool.jar
apktool.bat
• Decode every sub apk using the command apktool d [sub_apkname]
• You should now have the same number of folders in the drive as the number of sub APKs, if you decoded them all.
4. Changing the Colours and other Themes from the Decoded APKs Using Notepad++
• Many theme APKs will have internal APKs, such as common, settings, phone, systemui, calendar etc, etc. This is what I have worked out so far:
Common: Changes the switches, brightness bar and the text headings in settings, changes swipe left panels in apps such as gallery, changes background, message icon & phone icon colour in contact/phone app, statusbar background, separating lines in settings (some themes do not have these), background bar of setting title (i.e. wireless network, device etc), settings text colour, secondary text (i.e. the text you see under Wifi and Bluetooth which shows you what you are connected to), the headings in apps such as clock where it shows 'Alarm' 'World Clock' 'Timer' etc
System UI: Changes the quick settings tiles & text and the non-heading text in settings
• To change the colour of these you have to amend the colors.xml located in one of the folders in the assets>overlays and then the folder of the overlay you want to change. I used Notepad++ to do this. Navigate to 'res' folder and then usually something like 'values-xxxhdpi-v4'. There is sometimes more than one color.xml file so you may need to look in more than one folder and amend all the color.xml files. The colours are at the end of the lines of text and will be standard Android colour coding, such as ffffffff (white) or 00000000 (black) or any other colours.
5. Building APKs & Signing with Android Studio
• If you are building the sub APKs from an app (these are the ones inside an APK such as common, systemui, phone etc) I found it best to use a different folder. For this I used C:\apktool builder
• Copy and paste the folder from the decoded APK (e.g. the [appname].LGE.common folder) that is in the asset>overlays folder to the apktool builder folder above
• Once you have made the colour amendments it is time to build the amended themes. To do this you will need Android Studio
• Open the splash screen of Android Studio and instead of the 'Open' command use the 'Import Project' command and navigate to the folder you want to import
• When opening Android Studio you have to configure the frameworks otherwise you will not be able to sign the app. This warning should come up automatically. THIS MUST BE DONE FOR IT TO WORK
• Navigate and find your APK in apktool builder and import it. If you do this more than once you will be prompted to overwrite the settings a few times.
• Go to ‘Build’ along the top and choose ‘Generate Signed APK’. If this is the first time it will ask for the Key Store Path. You will need to choose ‘Create New’. Select a place to store this key (I chose C:\apktool Builder) and input the passwords and the other data in the boxes. You must put a two-digit country code in the last box, for example US, UK etc). For ease I kept most of these very simple. For example, password was 'asdfgh'
• Once this has been completed and if there are no errors (warnings are ok) then it will generate a signed sub APK and save it to the location you are in (in this case C:\apktool builder). Copy and paste that sub APK over the one in the C:\apktool folder where the original sub APK was kept.
• Once you have done this then you need to sign the main app APK. Do the same as above and build in Android Studio. If there are no errors it will save it to your directory (in my case C:\apktool\[app name].
• Copy and paste this APK into your phone, apply the theme and it should work.
Everytime you amend a sub apk you will have to re-sign it through Android studio and then re-sign the main app apk. Once you get the hang of it though it is fairly straight forward.
6. Other Things
Nothing else in the app will change at this point. The name, wallpaper jpegs, screenshots and icons will all be the same. I am working on this at the moment but they don't actually need changing that much. The difficult thing for me is how to change the 9.png icon files and still get them to work. Once I have worked this out I will be able to finish it off.
7. Screenshots
Attached are some screenshots of how my phone now looks. I have made a few different apk's with different colours so I can now change this daily if I want a change (see post 2 for updated screenshots).
8. Thanks/Credits
@xpirt - Made it easy to get the framework files I needed for apktool and for a great custom rom!
@Raafat - for giving me the idea and the initial information
@iBotPeaches - for developing apktool.
.
Building Your Own LG Theme
I've been able to fine tune the themes over the past few weeks and have been able to colour the settings icons on the main settings page as well as putting a background behind it. I've also been able to theme the switches initially getting over a problem of the 'off' switch not showing. Here is some updated screenshots of a green/grey&blue theme.
I've also attached the updated blue & red theme from the initial post. I've not fully completed this yet though as I started to concentrate on the green/grey&blue theme as I preferred that.
Could someone make a stock theme just dark? I found one on play store but is not the best thing (it changes system sounds and other things that i don't like) I'd like a full stock theme but dark. Thanks in advance
Help
Can you help me? I tried changing package names in .json file and added new icons in the theme. I don't understand why it is failing on apply. It was running properly with only color change before doing this.
[email protected] said:
Can you help me? I tried changing package names in .json file and added new icons in the theme. I don't understand why it is failing on apply. It was running properly with only color change before doing this.
Click to expand...
Click to collapse
Here is the apk.
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
strikerman10 said:
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
Click to expand...
Click to collapse
Take your time, and thanks. ?
[email protected] said:
Take your time, and thanks. ?
Click to expand...
Click to collapse
In case you haven't checked the apk I provided earlier, I have found and fixed some package name errors but the result is still same. It get stuck at 90% and then fails. I have changed icons too, is there anything needed to do in public.xml ? New apk is attached below.
strikerman10 said:
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
Click to expand...
Click to collapse
Did you took a look at it?