Hi guys and sorry if I'm allowed to make a small guide (I'm learning) to create and replace icons touchwizgtg base to include those that beat us more about working with photoshop ...
I hope this little guide is helpful to all of you who want a little modding the graphics of your terminal
Well I leave you to better understand this video, good vision
http://www.youtube.com/watch?v=i643CZzojEY&feature=player_embedded
Sorry for the video is in italian linguage
P.s. sorry for some typos that I made for the rush (type icons should be 87x87 and 85 as set in the video)
Requirements
TouchWiz installable package with recovery from LINK
STEP 1
Open photoshop and create a new file size you want (eg 300x300) with transparent background
STEP 2
Once created the icons we want, save it in png format, ritagliamola so as to leave no spaces around and in ridimensioniamola 87x87 pixels and save
STEP 3
With 7Zip, navigate inside the Touchwiz.apk, and extract the folder to the Desktop hdpi-drawable (just to get the name of the file we need) copy the name of the png you want to replace (in this case "homescreen_menu_marketbg_0") and rinonimate your icon with that name
STEP 4
Also in the surf with 7Zip Touchwiz.apk, until you enter the following location touchwiz.apk \ res \ drawable-hdpi.
Once this is done you just need to drag your new icon into that folder and answer yes to the question that the program will do.
STEP 5
Now you just need to replace the "old" TouchWiz with this modified by you, or rootexplorer or flash recovery
Special thanks:
Sconcau84 forum
Batista70forum
Italians do it better
thx raffaele, great tutorial!
moved to the section theme
Hello everyone, I am indeed new to these forums and the android development scene as a whole. I would have posted this in the development forum but since I have less than 10 posts....
Anyway, I've got an HTC Desire Z on the Bell network. Completely standard phone, no majors modifications done to it. What I would like to know is if it is possible to rip the skins that HTC includes with its Sense UI onto a computer to partake in graphical modifications, then put them back onto the phone under a different name/title (from Slate, for example, to Slate 2.0).
I would love a customized skin, but I'm a little reluctant in attempting a complete modification (Cyanogen Mod for example).
Welcome, can't help with your question. But wanted to let you know that this is the correct section for your question. Post this type of stuff in the development thread and you would of got flamed.
Sent from my HTC Vision using XDA Premium App
Rule: Now remember: if you want post result of your work (modified skin) you MUST have permission to use .png's from person who originally created them or also from me (if you are using png's from one of my skins in this thread). If you are only modifying skins for personal use, you can use what you want without asking anybody.
Note1: I'm using Windows 7 32 Bit PC, so tutorial is written for this platform. In "[]" are my comments. If you seeing "" you're not writing it, only sentence between them.
Note2: If you want relese skin, post it, and I will create link to your post in my second post, over tutorial.
Note3: If anybody would have any problems or will find any bug in my tutorial - post it.
So, you have awesome idea for a skin for Desire HD, but you don't know how to build it? Here is your answer:
Download & install 7zip.
Download & install Java Development Kit (JDK) & Java Runtime Environment (JRE): http://www.oracle.com/technetwork/ja...ads/index.html
Download & install Android Software Development Kit (SDK): http://developer.android.com/sdk/index.html
Download Auto-sign.zip by Dave Da illest 1: http://www.mediafire.com/download.php?uwzjjydnm2r
Download Apktool by Brut.alll: http://code.google.com/p/android-apktool/downloads/list
I. Installation of Auto-sign:
1. Unpack Auto-sign.zip to any folder and you're done.
II. Installation of Apktool:
1. Unpack: "apktool-install-windows-2.2_r01-3.tar.bz2" and "apktool1.3.2.tar.bz2" to "C:/Windows" directory.
2. Pull from your Desire HD: framework-res.apk and com.htc.resources.apk. They are in "root/system/framework" directory. Save them on your PC.
3. Place com.htc.resources.apk in "C:/Users/'your name'/" directory.
4. Open terminal/command line [Start->Run->type "cmd"->press <enter>] and type "apktool", press <enter>. Then you should see usage help.
5. Write: "apktool if com.htc.resources.apk DesireHD" [There should be created directory "C:/Users/"your name"/apktool/framework" and 2 apk files in it].
III. We will start with modifying standard, HTC made Slate skin. First, we must pull Slate.apk from "root/system/app" folder. In this directry there are also skis: Metal.apk, Wood.apk, Blackboard.apk.
1. Extract pulled Slate.apk with 7zip. [Right mouse button click on skin .apk, from menu choose: 7zip->Extract to "Slate\"]. Now you can edit/replace all .png's stored in "Slate/res/drawable-hdpi; drawable-port-hdpi; drawable-land-hdpi".
2. Place pulled original Slate.apk in "C:/" directory.
3. In command line write: "apktool d -f -t DesireHD C:/Slate.apk".
4. There should be created directory "C:/Users/"your name"/Slate".
5. Editing name of skin, colors, and other miscellaneous things [in decompiled .xml files]:
a. Name of skin: with notepad we are editing AndroidManifest.xml in "C:/Users/"your name"/Slate" folder.
-line: <manifest android:hasCode="false" android:versionCode="8" android:versionName="2.2" package="com.htc.skin.Slate"
change to: <manifest android:hasCode="false" android:versionCode="8" android:versionName="2.2" package="com.htc.skin."your name of skin without spacebar""
with notepad we are editing strings.xml in "C:/Users/"your name"/Slate/res/values" folder.
-line: <string name="skin_name">Slate</string>
change to: <string name="skin_name">"your name of skin"</string>
b. Colors: with notepad we are editing colors.xml in "C:/Users/"your name"/Slate/res/values" folder. [Colors of specified areas of Sense UI are in HTML code. You can check and edit them with help of some sites].
c. Flipping of clock and screen indicator courve line: with notepad we are editing integers.xml in "C:/Users/"your name"/Slate/res/values" folder.
-line: <integer name="clockwidget_flip">1</integer> means that clock will flip. If "1" changed to "0", clock will not flip.
-line: <integer name="rosie_scrollbar_curve">0</integer> means that screen indicator will move in curve line. If "0" changed to "1", indicator will move in strait line [there is no mistake here!].
6. Now if you edited .xml's in the way you want, you must compile .apk of skin. In command line write: "apktool b -f C:/Users/"your name"/Slate "your name of skin without spacebar".apk" [for example: apktool b -f C:/Users/****/Slate Dick_Slate.apk].
7. In "C:/Users/"your name"/" directory will appear compiled skin .apk.
8. Open it with 7zip. [Right mouse button click on skin .apk, from menu choose: 7zip->Open archive]. You will see in this directory 2 folders: assets & res, and 2 files: AndroidManifest.xml [which is edited already] & resources.arsc.
a. In "assets/image" directory there are stored preview.png [which you see when you choosing skin in Skin Picker, on your phone] and wallpaper.jpg.
b. In "res" directory there are folders: drawable [which contains .xml's], drawable-hdpi, drawable-land-hdpi & drawable-port-hdpi [containing .png's which you will replace]. Now you can drag'n'drop previously prepared
[in point III.1.] .png's [or whole folders], so your new files replace those in opened .apk. Close 7zip window.
9. Now take edited "your name of skin without spacebar".apk to Auto-sign root directory [see point I.]. Change it's name to update.zip. Drag'n'drop update.zip at Sign.bat file and in command window press <enter> when signing will be finished. There should appear new file called update_signed.zip. Now you can change it's name to "name of you skin".apk and youre done. This file is installable on your Desire HD.
Click to expand...
Click to collapse
Please. Use google search first. I just searched "Modify HTC Skins Android Sense" and that was the 3rd or 4th hit.
Here's the link for the entire thread.
I must not have searched for the right thing then. Thanks for your help in finding this for me!
Anytime mate, Good luck with the skinning.
PS: if you skin something nice, post it! xD
Small tutorial on how to edit custom accents in WP7 by registry editing!!
THIS IS FOR THOSE WHO COULDNT GET A CUSTOM ACCENT VIA HOMEBREW APPS!!
(ESPECIALLY LUMIA USERS...THEY GET ERRORS WHILE SAVING CUSTOM ACCENTS VIA HOMEBREW APPS!)
before editing....get advanced config tool from Devstore7 or wherever and go to themes and select add new...youll b given a colour palette....select the colour and it will show u Hexadecimal code at the top (starts with #F)...copy that and go to Calculator('calc' from run) and change the view to programmer...select Hex and enter the code without '#'....now with the code pasted select the Dec and it will give a 10 digit code (starts with 428, 427 or whatever)....this code is the main thing....NOTE it!!
Now go to registry editor (i use WP7RootTools by heathcliff74)
The path to theme and accents folder is (Local Machine\Control Panel\Themes)..Enterthe themes folder
Now u get 3 folders named 0 ,1 and AccentDisplayName
Below that u get two files named Current Accent and Current Theme
If current theme value is 1 it represents dark background. If it is 0 then white background
Now if u want a custom accent in dark background go to folder 1 or if u want it with a white background got to folder 0....and then enter the folder ACCENTS located in Folder (0 or 1)
You will be given numbers from 1-10 or so....u can check the name in AccentDisplayName for which digit represents which colour.
Then select the respective file in folder 1 or 0 and edit its value to the 10 DIGIT CODE u got from calculator. Save it...RESTART!!
Now go to themes...u get a custom accent...u can also change the name in AccentDisplayName....Enjoy...Feel Free to thank me!!
This method still requires interop-unlock and has been known for sometime and if you are interop-unlocked there is a much easier way to make it work using Advanced Configuration Tool 1.5
This method is quite old, I've been doing it for like a year now or so. But I must warn you. Changing anything wrong with the themes in registry can make your phone get broken in software and will need a hard reset, so double check when you're changing the codes and adding/removing values of the registry.
Laquox said:
This method still requires interop-unlock and has been known for sometime and if you are interop-unlocked there is a much easier way to make it work using Advanced Configuration Tool 1.5
Click to expand...
Click to collapse
read the second line....for lumia users..advanced config tool and other such homebrew apps wont(mostly) work...so this is for dem
Gg, figured that out a couple days ago after messing up my phone and having to reset it 2 or 3 times lol.. I reset it with this 7.8gb phone dump I made also. Takes like 3 hours or so per reset/restore-from-backup
Very helpful tutorial!! Thank you!
But this doesn't change the color for 3rd party apps and also not for their Live Tiles.
There is already a thread up, where is also explained how to change it that it also works in 3rd party apps.
I used this method and my third party apps changed just fine. I'm actually quite pleased with it! I got "Base Converter" from the marketplace to do the converting between hex and dec on the fly and now I can change my colors anywhere. I really wish someone would figure out how to get beyond the restrictions of the second gen devices, but until then, I guess this works.
This tutorial will not include info on code, since that information is universal and there are tutorials everywhere already.
- an example of what you can do with this is here:Kronic BlueMod 4.3
- with this knowledge you can create a UI look that NOBODY else has, if you are so inclined, personally i like to share my work but i understand people who like to have unique stuff
this was done to H0!N0! v20f bell debloated/deodex rom.
- this tutorial is meant for ICS mod's but most of the concepts can be applied to other roms and android versions, however small things like file names and locations could change
requirements.
- common sense
- 7-zip installed (winrar can work too but i prefer 7-zip)
- apktool installed (which also requires jdk's etc, there is plenty of information available on how to install this already)
- here is the version of apktool i used and worked with v20f
- apktool Jar file thx to brut.alll
- paint.net (an open source paint program that can deal with transparency and .9.png files.
- working adb or some type of program to push and pull files from phone.
- windows environment (i used win8 64bit.)
Lesson 1 - setting up work environment.
the first thing you want to do when working with a new rom is install it's framework to apktool. This will help apktool know how to work with the files you are going to work with ( in lamens terms ) The command for install framework is "if".
the framework files are found in /system/framework/
- pull framework-res.apk and lge-res.apk, i also install systemui.apk too but i don't think this is needed. (systemui is found in /system/app/)
- make sure your command prompt is in the correct working directory then run the following commands
apktool if framework-res.apk
" " " lge-res.apk
" " " SystemUI.apk
it should install successfully and if you navigate to /users/yourname/framework/
you should see 1.apk 2.apk 127.apk (1 and 2 are the real framework files 127 is systemui and won't be there if you didn't bother installing it)
ok now apktool is setup.
Lesson 2 Repacking system files.
- once you have all the files for your new ****.apk system file, highlight them all, right click, go to 7-zip header, and select add to archive.
- set archive format: zip
- set compression level: store (this is 0 compression which is the best performance)
- set update mode: add and replace files
- once done, packing rename the file to the appropriate name with .apk extension.
- zipalign the file before adding it to a flashable zip or pushing to phone.
- flashable zip is recommended especially when pushing framework-res.apk to phone due to the fact you are replacing the framework app of the system it's better if the system is not running.
- always make a backup flashable with your original files in case you made a mistake.
there is a cool version of apktool that helps new users make flashable zips and zipalign files here:
Auto apktool - thanks to xavierjohn22 and brut.alll for this.
you can replace the files in a flashable zip with 7-zip on the fly by right click open archive, and drag and drop method.
lesson 3 - changing icons.
- this is the easiest part of UI moding if you know where the files are for the icons you want to change, just about anyone can do this, you don't even need to decompile.
- nitro hd uses apk/res/drawable-xhdpi/ resolution folder. so this is the folder you should edit files in, the other drawable folders don't change much.
- open the apk with 7-zip by right clicking it and using 7-zip menu, either extract the whole apk or just the res/drawable-xhdpi/ to view/edit files or you can use your decompiled folder if you are not just editing icons and are planning on rebuilding.
- as a general rule icons on the left side of the status bar are usually controlled by framework-res.apk and icons to the right side are controlled by SystemUI.apk
- for example adb status bar icon appears on left so it's found in framework-res.apk (even though the icon is also in the systemUI.apk that is not what will change the status bar icon.)
- wifi signal and battery etc, are on the right side so look in SystemUI.apk to change them.
- to edit the icons just right click the .png and open with paint.net the square checkerboard means transparent if you've never used paint.net before.
- there are multiple sets of icon styles so be sure you are editing the one your current rom is using (for example signal icons have about 5 styles) if you aren't sure which one you can change them all or do trial and error.
- when repacking the apk after icon changes, it is recommended that you repack your apk like done in lesson 2, although if you drag and drop into the archive and overwrite old files that should work too, although if you do it that way you should atleast zipalign it after.
Lesson 4 - .9.png files
- these files are used for making buttons and stretchable images, it's hard to explain and i'm by no means an expert on them, but when i edit them i only want to change color. I have had a few not work and you will get errors during compile if you mess up the formatting that's already done, this is some type of handle that tells the OS how to stretch the image i think. when i wasn't careful i got errors, when i just use the paint bucket and change the color and then save it, it usually works. if you want to change more there are lots of other guides that have better information. i recommend if you edit these you recompile your apk after every 2 or 3 files just to make sure there are no errors, this will make sure u dont edit a bunch then have trouble identifying which one caused the issue.
- some of the files on our phone that you might want to change the colors of are backgrounds, title bars, status bar pulldown menu buttons, etc. they are typically backgrounds that have different colors, sometimes it's hard to figure out which they are because their dimensions are not like how they show up on the phone, due to stretching. for instance a title bar can look like a vertical line | <--- like that because it is stretched to fill the screen horizontally, and usually it will be slightly faded and that fade will continue across which ever way it is stretched.
- you will also notice that divider bars show up as dots, in a .9.png, on these i just use a pencil and change the color of the CENTER of the dot only. if there is more than one pixel for the same color i just do it to each pixel, usually its 1 i think. (i think paint.net changed something since i updated i can use paint bucket in these and it seems to work)
some files you can look for that are useful to change are.
i will attach some example files that i blacked out like the example i linked at the beginning. if you want to see more just go to that link i posted and download the zip, extract the systemui.apk from it, unpack the apk, and you can see all the files and steal my painfully made homemade indicator that is 200+ file edits.
SystemUI.apk/res/drawable-xhdpi/
- indi_noti_btn_edit_normal.9.png
- indi_noti_btn_pressed.9.png
- indi_noti_progressbar_.normal.9.png
- indi_noti_title_list_divider.9.png
- These are just examples, there are some in framework-res too, usually the names describe what they do, you can try searching your folders for .9.png if you can't find what you are looking for, on different roms the names may be different, and it is possible for them to be in other drawable folders, but usually check xhdpi first as a general rule. you will also find statusbar backgrounds are usually not.9. files so you can put pictures and stuff in them just try to keep dimensions, it will get stretched to fit the status bar on most roms i believe.
Lesson 5 XML editing.
- install notepad++ it's free and its a must have unless you have another text editor designed to handle xml that you prefer.
- open command prompt, you can run in admin mode if you get file write errors or anything that will usually fix problems.
- navigate to folder where apktool is installed unless you have environment variables setup to handle apktool commands from other folders.
- make sure your SystemUI.apk and framework-res.apk are in the same folder, if not copy those files to that folder. for SystemUI.apk, open it with 7-zip and extract the file "classes.dex" to a folder for safe keeping, once that is done, delete it from the archive, as it will cause decompile errors. if you are running a v20c or earlier, you can try skipping this step because baksmali might work for you. if you want to edit classes.dex skip to lesson 6.
- once ready, go back to command prompt, you should still be in your apktool folder. type this.
- apktool d filename.apk
- it should decompile, if u get errors you can try another version of apktool or you can google the errors or post them here and people will try to help.
- it will create a folder named SystemUI and framework-res respectively, or the name of whatever apk you decompile. some other system files have classes.dex that has to be deleted for decompile to work. always back it up though cuz you need to add it back in later. framework-res doesn't have it on most roms i think.
- now you can open the xml's with notepad++ and edit them, save them and recompile. you can also edit images at this time if you wish in the /res/drawable-xhdpi/ folder. IF YOU MAKE MISTAKES IN THIS STEP YOU WILL GET COMPILE ERRORS, so backup original files if you are not confident in what you are doing. i can't list every xml edit here because there are millions of variations you can do, but these xml files control a number of things, from layouts to text color codes etc. variable names, calls to smali code.
- some guidelines are here.
/layout/
- status_bar.xml - edits the system status bar layout, these are fairly universal so if you want to edit this, lets say you want to move the clock to the center, just search the forums for how to center clock status_bar.xml or something, and you will find some example code's you can learn from. this goes for the others too, but here is an example.
/layout/status_bar_tracking.xml
- remove the line that starts with com.android.systemui.xxxxxxx.carrierlabel or something to that effect.
- add this line
- NOTE: for some reason the i can't make the code show up properly for the lines with textAppearance="atstyle/variablename" but that is how it should show up but replace at with the symbol for email at. xda site turns the symbol into a mention for some reason
Code:
<TextView android:textAppearance= [user=262514]@style[/user]/TextAppearance.StatusBar.Title" android:gravity="center" android:layout_gravity="bottom" android:paddingBottom="20.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content" android:text="ADD CUSTOM TEXT HERE" />
make sure that you don't edit anything from the other lines, save the file. This will add text to replace the old carrier label, whatever you want, you can also add other things here like time i think, but i haven't done it before. the textappearance arguement will set the textappearance so if you want to copy the color or style of something else, just read the file that it contains and call the same style as it does, for example you can open your status_bar.xml and copy the textappearance that calls the clock, if u want it to appear like the clock does (color/font etc)
- another important layout file is
/layout/status_bar_expanded.xml
- this file controls the expanded status bar, obviously.
- in notepad++ you can add stuff to the title above the notificatations, by adding it between insert your additions after the line that says
Code:
<RelativeLayout android:id="@id/setting_layout" android:tag="NO_R2L" android:background="@drawable/notification_header_bg"
...etc
- i added the clock here, after the date, so i skipped down one more line, made a new line and added this code:
Code:
<com.android.systemui.statusbar.policy.Clock android:textAppearance= [user=262514]@style[/user]/TextAppearance.StatusBar.Date" android:gravity="left|center" android:id="@id/clock" android:paddingLeft="3.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" android:layout_toRightOf="@id/date" />
- you also have to make sure the arguements "android:layout_toRightOf="@id/date" is the right id, you can tell which id is which because they are set in each line. you also have to check what used to be beside the date, and fix that too. so look for the text (you can use ctrl f to search) android:layout_toRightOf="@id/date" except not the one you just added, it will probably be the next line for me it's this.
Code:
<View android:id="@id/settings_divider" android:background="@drawable/ic_divider_blue_holo_dark" android:layout_width="0.6700001dip" android:layout_height="16.0dip" android:layout_marginLeft="8.0dip" android:layout_marginTop="15.0dip" android:layout_toRightOf="@id/date" />
- in this line, change "date" to "clock" without changing any other code this will make the divider appear to the right of the clock instead of ontop of it. if you make errors in this phase you can also get compile errors.
changing these layout files have endless possibilities, but this is how you do it, be careful though if you aren't confident make backups and compile often to check for errors, you can google most common errors and find help. or ask.
other things you can do in xml is change values of predefined variables, like colors, file calls, numbers for settings, boolean values, etc. for the purpose of theming focus on styles.xml and colors.xml first if you can't find what you want to change there check the same ones in framework-res/systemui or whatever you are in the corresponding app some apps call framework-res or system-UI and use the colors defined there
- to pick colors you can use Paint.net, go to more colors in color picker, find the color you want, to use it in xml put it in the following format
# aa bbbbbb aa -> transparency code 00 means transparent and ff means solid. you can lookup these codes on google for more specific values.
bbbbb-> is the code you get from Paint.net beside Hex: if it says for blue, 264AFF and i don't want it to be transparent, the color code i would use in xml is the follow "#ff264aff" where i have the letters in lower case and a # at the beginning, only have "" if they are there already, look at the preexisting code to determine, you can also change colors by changing what style something calls (change the @style) call to a style in the styles.xml that you want it to look like.
the integers.xml has some interesting things that are fairly self explanitory, or you can google them if you want to know them all i can't list everything.
- RECOMPILING ONCE YOU HAVE MADE YOUR XML EDITS.
- go back to command prompt in the correct work folder, that your SystemUI and framework-res folders are in.
type:
apktool b SystemUI.. youll see something like this. if you don't get errors.
W: could not find sources
I: checking whether resources has changed...
I: building resources...
then it will take some time to work, depending on cpu speed.
then youll see:
aapt: warning: string 'sp_dcm_gps_popup_body_NORMAL' has no default translation
or a combination of multiple errors like that about default translation, this is normal.
then youll see:
I: Building apk file...
this is good.
at this point type this line again:
apktool b SystemUI
this time it should be fast and no errors.
- YOU NOW HAVE YOUR COMPILED MODIFIED XMLS, to pack them up, navigate to apktoolfolder/SystemUI/dist/SystemUI.apk
open with 7-zip
extract the folders res, assets, and resources.arsc file to a folder called "done" or whatever name you wanna use, then add the original META-INF folder, AndroidManifest.xml file, and the classes.dex file you backed up from the original apk to the same "done" folder.
you should now have the files and folders like this
- assets
- META-INF
- res
- AndroidManifest.xml
- classes.dex
- resources.arsc
the assets, res and resources files, should be the new edited ones, and the classes meta and android files sould be originals, if u edited the smali then the classes.dex file is the edited one from that process.
if there was no classes.dex in the original file obviously you don't need it here.
at this stage, you pack your apk as per instructions in lesson 2.
Note: some SystemUI.apk files have some tricky compression (newer ones) that cause errors in apktool decompile process.
the error i kept getting was Exception in thread "main" java.lang.illegalArguementException: MALFORMED.
it's an instant error (the second you push enter) it happens, which led me to believe it's an unpacking error.
i found another clue when i tried to pull the classes.dex file out of the package with 7-zip and got a program freeze, had to end task it.
i found the solution when i downloaded the latest beta version of winrar and tried to work with the package, i was able to unpack classes.dex -----> progress.
i still got the error after deleting it and trying to decompile though. so i conlcuded that the androidmanifest.xml is also packed with strange compression (that only a very new zip utility will handle)
[fix] use winrar beta version to completely unpack every file, then repack everything except classes.dex, save that file for repacking after recompile. with 0 compression, store and replace (for this step you can go back to 7-zip) since the files are already unpack, you can let 7zip pack up the normal way, then rename the SystemUI.zip to .apk and decompile the file..... errorless =D.
this is a fix to decompile the SystemUI found in the V20F with new framework rom fond in the dev section.
lesson 6 is coming soon, smali editing.
i decided to delay smali editing, i am not good enough at it to teach, you can download jar files called smali and baksmali that you run using command lines in command prompt, such as
"java -jar baksmali.jar classes.dex" to decompile (usually goes into a folder called "out")
"java -jar smali.jar <foldername>" to recompile
omit the " " when input into command prompt.
once classes.dex is recompiled add it back into the apk, if u did your edit correctly you win, if not you will probably sit at lg screen, or the system will load and no change will occur, or some errors.
from what i understand smali code is unique but similar to closer to assembly languages like C or it's variations. i can't find alot of info on it i had done a couple small edits that i tried to copy from someone else but they partially worked because our smali's are so much differant than the people i'm trying to learn from, it was hard for me to learn anything. what little info i find would be better for you to learn from the same people i'm learning from until i have a better grasp which i can't see myself finding the time for anytime soon
i'm so close to having a full bluemod LGMms.apk 3 items i can't figure out how to change, have like 31 changed .. can't find the last 3
if anyone can figure out how to change the title bar backgrounds let me know, i tried like 5 differant ways and nothing worked i think it's set transparent in the smali and i don't know smali well enough to find it
by the way everyone i figured out how to mod lockscreen on LG stock roms, THEY ARE NOT located in framework-res like most roms, it's found in /system/app/lockscreen.apk if u need helping finding an xml for a specific lockscreen let me know
- RECOMPILING ONCE YOU HAVE MADE YOUR XML EDITS.
- go back to command prompt in the correct work folder, that your SystemUI and framework-res folders are in.
type:
apktool b SystemUI.. youll see something like this. if you don't get errors.
W: could not find sources
I: checking whether resources has changed...
I: building resources...
then it will take some time to work, depending on cpu speed.
then youll see:
aapt: warning: string 'sp_dcm_gps_popup_body_NORMAL' has no default translation
or a combination of multiple errors like that about default translation, this is normal.
then youll see:
I: Building apk file...
this is good.
at this point type this line again:
apktool b SystemUI
this time it should be fast and no errors.
Click to expand...
Click to collapse
I get to this part and all it does is create a build folder in the systemui directory.... nothing else.
mattman86 said:
I get to this part and all it does is create a build folder in the systemui directory.... nothing else.
Click to expand...
Click to collapse
interesting, i should have mentioned sometimes you don't have to build twice, but that might not have been the error anyways.
is there a dist folder after first build?
what version of apktool are you using?
i've never seen no dist folder except when the build doesn't complete.
are you sure that there wasn't an error that isn't a warning (the warning "no default translation x 2-4 is normal but if u have actual build errors that stopped the compile process there will be no dist folder, because dist is the LAST step in the process.
- if the xml you modded got compiled correctly, it's possible to impliment it by replacing the xml in the original apk with 7-zip, just check the xml in the build folder and if it's there u can try overwriting the original one in the original apk, we still need to get down to the issue with no dist though.
if you want you can try ziping the systemui directory you are trying to build, and post it here, i'll try compiling for you and see if i get errors, that way i can tell you if the problem is your apktool or an error in a mod you made.
if you do that i'll need your framework-res.apk and lge-res.apk, unless you are working on liquid nitro, i already have the framework for that rom installed if thats the case i just need the zipped systemui folder you are working on and i can see what's what.
mattman86 said:
I get to this part and all it does is create a build folder in the systemui directory.... nothing else.
Click to expand...
Click to collapse
did u figure it out?
Finally, I found this thread. This is very useful bro! Keep it up.