Hey
How can I change the icons of Android, Apps etc?
Maybe i have to edit the .kdz-file / system.img-file?
Which programs do i need?
Thank u!
You have to edit the /res folder in the apk file.
Joost
extract the framework-res.apk file from your rom via root explorer then use this to extract the contains from the framework file and you can also use that tool to repack the framework file
APK Manager
http://forum.xda-developers.com/showthread.php?t=695701
Adb pull the app then with 7zip extract. Look in res/drawable-mdpi and you will see all images in the apk. Look for icon and replace.
Repack all files in a zip then rename zip to apk. Adb push the apk.
MARK
Here is the compatibility file to add in to the kitchen. Here is also the new updated SU files to give root to the ROM. Here is also a plugin to add "Ad Free Hosts"
Unpack the folders withing the "Kitchen" folder to your root folder. Allow it to overwrite the files. It will add the stuff I specified.
Hopefully it all works and you guys can get started!
Credits to:
dsixda for making the kitchen
Chainfire - for his SuperSU files
Note: I'm just sharing the work of the XDA Member MatrixDJ96.
MatrixDJ96 said:
Would you like to speed up your rom, more stability, more battery life, no lag to open system app and better ram utilization? Now you can! (Only For Rooted Phone And Deodexed Rom)
This is possible with my Odexer Tool created myself.
I worked a lot of time to create this script.
What is ODEX and DEODEX?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These odex files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applicationsdifficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating theworry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
Another explanation is this:
If you odex the rom, you'll have also more space in data (this is important because if you don't have partition ext4 in sdcard, you won't have too free space), increase battery life, more stability and increase perfomance( the Rom is more faster to load system and app) but you can't modifie apk after odex (you can't mod program with classes.dex).
Infact ODEX is an OPTIMIZED-DEX and Android load system and app faster than deodexed (DEOPTIMIZED-DEX) app and system.
When you have a deodex file (a lot of roms are deodexed) you have File.apk in system/app and in data/dalvik-cache/[email protected]@[email protected], but with odex file you have File.apk in system/app and File.odex in system/app
With these explanation you can understand that:
Odexed Rom = +fast -difficult_customization +more_battery_life +better_stability +less_ram_utilization
Deodexed Rom = -slow +customization -less_battery_life -less_stability -worse_ram_manager
If you run my script with remove classes.dex and zipalign disabled your rom will be odexed without "-difficult_customization"
My script does (it depends by option):
- odex framework
- odex app in system/app
- odex app in system/priv-app (if you have android kitkat)
- remove classes.dex and zipalign from jar/apk (if you enable this option)
All commands of my script:
+ frame [odex all framework]
+ sysapp [odex all system apps]
+ all [odex framework and system apps]
+ set [change settings of the script];
> 1 [enable/disable remove classes.dex and zipalign]
> 2 [back]
+ exit [exit from the script]
WORKING IN ALL ROM (Froyo, GingerBread, IceCreamSandwich, JellBean And KitKat)
AOSP - AOKP - CM - MIUI - PA - PAC - BASE STOCK - ALL!
Credits:
- @MatrixDJ96 (Me)
- MrTony68 (Beta Tester)
- @Thyrus (Beta Tester)
- @angel.sea (For Support)
To Devs
If you want to use this script to odex your ROM, please give me credit in your ROM thread.
Thanks for the cooperation
For More Info Contact Me By Email: [email protected]
ENJOY WITH MORE STABILITY, SPEED AND BATTERY LIFE!!!
Please, give me a thanks if you like my script
By MatrixDJ96
Click to expand...
Click to collapse
MatrixDJ96 said:
IMPORTANT TO ODEX YOUR ROM:
To Odex Framework (Command 'dexo -fr') You Must Have At Least 16% Of Free Space In System.
To Odex System Apps (Command 'dexo -sys') You Must Have At Least 26% Of Free Space In System.
How to odex:
- download file
- go to recovery
- install zip
- reboot
- open terminal emulator (will be installed automaticaly)
- setting terminal type "Linux"
- type su to obtain root permission
- type odex and enjoy!
IF YOU HAVE ENABLED "REMOVE CLASSES.DEX & ZIPALIGN", A FLASHABLE ZIP BY RECOVERY WILL BE CREATED WITH OPTIMIZED SYSTEM SO REBUILD IN RECOVERY AND FLASH THIS FILE (You find it in sdcard and it's called "Optimized-System_NAMEOFYOURDEVICE.zip")
I hope that all are clear
+++++++++++++++++++++++++++++++++
Download link:
Odexer Tool
+++++++++++++++++++++++++++++++++
Click to expand...
Click to collapse
Nice thread bro:thumbdown::thumbdown::thumbdown::thumbdown::thumbup::thumbup::thumbup:
This is awesome tool.
But, i cant install ver beta 5.5 via cwm. Error: install abort...:banghead:
Send from USS Enterprise CVN-65 using Tomahawk
tuan.cse06 said:
This is awesome tool.
But, i cant install ver beta 5.5 via cwm. Error: install abort...:banghead:
Send from USS Enterprise CVN-65 using Tomahawk
Click to expand...
Click to collapse
Change the updater-script with any of the other CWM flashable zip.
aniket.lamba said:
Note: I'm just sharing the work of the XDA Member MatrixDJ96.
Click to expand...
Click to collapse
UPDATE
MatrixDJ96 said:
UPDATE
Click to expand...
Click to collapse
Will update it in evening
MatrixDJ96 said:
UPDATE
Click to expand...
Click to collapse
Does not work
Sent from my Galaxy Nexus
nice one bro
I want to add flashable zip contents to my aosp build. It contains some folders (check below image) with framework and build.prop addons. I don't know where to place these files. Although I've placed priv-app folder contents to packages/apps/here with each .mk file in it. Can any Developer help!
http://i63.tinypic.com/b6syyr.png
You place the folders normally like you place it in an existing rom using root explorer.
Basics:
What your updater script does is move the complete system folder to system partition
There is nothing such in the script which copies files individually from a given folder to destination
So if you want to copy something inside priv-app , place desired apk's in priv-app
If you want to do some symlinking or change permission , head to updater-script and edit it using Notepad++ only..
Good Luck Dev ,
Cheers
All credit goes to @Extreme_Ninja2099 and this post. Thanks so much
This method seems to work best for changing bootanimations on the OP8/Pro.
How to add your own bootanimation:
Download [Magisk]OPGoogle.zip
On computer, "Open Archive" of this zip with 7zip or similar program
Navigate to system>product>media in with this open
Pull bootanimation of your choice into this folder (must be named "bootanimation.zip")
Make sure it is similar ratio/description as original bootanimation in this folder!
Go back and make sure the archive is saved.
Now navigate to root of this zip and open module.prop in an txt editor (I use VSCodium but many will work like notepad++, etc)
Change information here to your own and
Save it somewhere on your computer before pulling it into the open archive to replace the one in it
Navigate back and make sure to archive saves and close
Now you have a flashable bootanimation module for OP8/Pro
The attached bootanimation is a Google/Pixel BootAnimation (black). Enjoy! ^o^
Again, big thanks to @Extreme_Ninja2099 . Hope they don't mind me making this guide lmk