Those who want to change something about its Android system, which sooner or later not avoid the relevant forums such as XDA and Android Help. Not only there ROMs and mods for many devices, but also good explanations about common issues.
in German Android Help-Forum has the User 4ndr0 sat down and make a statement about what &# 8220; Odex&# 8221; and &# 8220; Deodex&# 8221; mean very good and understandable translated into German. This has given us so much that we do not want you this withheld. If your interest in the relevant forums instructions and Explanations place or even self-written and would like to share with many users, it can simply write to us at [email protected]
Which does ______________ mean &# 8220; Odex&# 8221; and &# 8220; Deodex&# 8221 ;? A full explanation
Honestly, how many of you who read this, the ROM Board looked only to stumble again and again over these completely alien concept. Hey, is okay, felt the same to me. Strictly speaking, the terms and Odex Deodex bring the eyes of modders shine. So what they are talking to, anyway?
To understand deodex, we should first deal with Odex.
odex = Optimized Dalvik Executable
As you probably know, Android apps are on your device as .apk files (actually .zip archives) packed. Stock Android ROMs use a Odex file structure, for a odex &# 8220; optimized&# 8221; executable file is Dalvik. This means that for each APK exists an associated Odex file. The same goes for the Framework files in .jar (Java Archive) format.
Example: In this not rooted Galaxy Nexus you see the one following file
system / app / Phone.apk
system / app / Phone.odex
But what exactly are these Odex files?
If Android running your apps or use Framework components, it needs to read the compressed data contained in the .apk and / or .jar files and interpret. A Odex file structure accelerates this process by a .odex file, which stores the most important data uncompressed, so Android can process that data quickly before the rest, uncompressed portion of the data is processed. The purpose is to speed up boot times and letting apps load faster in general.
So what deodex?
The Odex file structure works beautifully as a tool for optimization, you want except modding / topics. Odexte apps and frameworks indicate a particular problem for anyone who modding / topics would like due to the fact that the split are to be changed in two resource files. Theming (modifying symbols / Lockscreen / status bar etc.) e.g. normally requires that system bitmaps are replaced by their own and that is almost impossible or extremely expensive to &# 8220; odexten&# 8221; Environments. The solution is to deodexen the file system, i.e. to integrate the outsourced uncompressed data in the .odex files back to their .apk or .jar files.
In this Galaxy Nexus, on the custom ROM running, we see the
system / app / Phone.apk
but not the corresponding .odex file.
The newly assembled data end up in the classes.dex within the .apk file.
So what should you use?
The only reason to be deodexen ROM, theming / modding is. They will make your device not faster. Technically, it should even slow down the device, but in practice the difference is imperceptible. In my experience, any custom ROM pre-DeOdexed comes along and zipaligned your apps on any boat.
Zipaliging is reorganizing and optimizing your APKs, so Android can process faster. It is comparable, if not better than the Odex file structure so you get the best of both worlds; A modifiable ROM with the speed of an optimized file structure. So the only difference lies in the modifications possible. It is up to you to decide what you need.
Source: Android Help