Modding all app's design was an oportunity to delete all unused locales.
Conclusion : I just want to inform any crazy people like me that : (re)building all system apk's without unused locales does not improve performances, neither RAM space !
- you will just have a sensible space gain in /system (about 15Mb)
Note: having a compressed resources.arsc in apk's files is not a problem at all ! (informations about this on the forums are confused)
So ... don't waste your time !
Seeing the many people all the time asking the same questions about the size of the system I decided to describe an extremely simple way to check it for yourself. It's also a way to change the font for example or remove unwanted applications before flashing rom. Believe the all you need to do is install the "7zip" and open rom.zip without unpacking and check the size of the folder system. Now you can change, delete, add content rom also. That's all, really
Sent from my HD2
Sent from my HD2
Great info. Didn't know that!
I suggest to add following info:
-Apk´s added to system/app don´t have to be signed.
-app´s/apks could be also in data/app folder
-Some apk´s like Rosie apk (Sense Roms) have to stay there
.....
Ohh and if you add big and much apk´s you will have to increase the system partition when flashing CWM
Hope i could complete your info
WHAT IS AN ODEX FILE?
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 applications difficult 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 the worry 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.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Source From www.addictivetips.com
This looks to be a copy and paste from the description here.
If you are not the original author its usually a wise idea to acknowledge the original author/source.
And optimized dex files (odex files) may also depended on the framework classes interfaces. This means that you may end up with bootloops or FCs if you change the interface of framework files. The odex files have therefore been given a signature that all files must match.
Deodexed apks can on the other hand be used on several roms as they may only be depended on the resources in the framework-res.apk file.
So you can have an odexed framework with deodexed apks! But if you want to change the interfaces in the Framework then it is easier to deodex all instead of re-odex all.
Sent from my GT-N7000 using xda premium
Thanks for it! For me more clear now.
I need to verify this, So on an ODEXED STOCK ROM, Can I make changes like
editings png's inside System APK files,
Decompile and compile framework-res.apk,
Make changes to the framework-res.apk to enable crt screen effect ... ?
Clears another thing up for me...
Thank you for your post.
Sorry guys for posting a stupid question, but i'm not clear on one point.
I have the htc one S [s3]. How can I understand if /system/framework/framework-res.apk (and/or) framework-htc-res.apk are already deodexed? (in a practical manner)
I mean...since is an apk and I'm not seeing any framework-res.odex are they already deodexed?
Can I straightly modify it?
Thx in advance!
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Emothic_Reagan said:
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Is not that one is better than the other. They have different characteristiocs. Odexed are smaller and faster while deodexed are easily customizable but needs more space.
Guys I still need somebody to answer my question...plz...anybody?
true that the odex offers lower booting time (when the dalvik VM first loads) and stuff but reducing the internal memory usage?? i mean wth??
it states here on this webpage - addictivetips(dot)com/what-is-odex-and-deodex-in-android-complete-guide/
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 applications difficult because a part of the coding has already been extracted to another location before execution.
Click to expand...
Click to collapse
To all the newbies- a final solution to the deodex blues!
incase you guys dont know about deodex this is what it is
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 the worry 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.
Click to expand...
Click to collapse
so here it is and there you go you are now running around finding posts to help you deodex to get you the ultimate themeing experience well theres this guide i found out in the question and answers sub-section
I have a mod 4.3 TW ROM that has been themed with a zip that was flashed on top of it. If I flash another theme on top of it, it messes up the phone. The only way I have found to re-theme is to dirty flash the initial ROM on top while purging the system files prior.
What happens is that the phone keeps all my data, the theme is gone, yet all the system files are back including bloat which takes a very long time to remove. Then after purging a large amount of system files I don't want that were reinstalled, then I can finally flash a new theme.
Wasn't sure if there was an easier way.