Difference between deodexed and odexed? :S
Gesendet von meinem HTC EVO 3D X515m mit Tapatalk
I found this:
Odex:
Every android application comes with the extention 'k@. apk '. Packaged with every apk is a .odex file which contains parts of the application which helps speed up the boot process and preloads it.
an odex file is an optimized version of a classes.dex file that has optimizations that are device specific. In particular, an odex file has dependencies on every "BOOTCLASSPATH" file that is loaded when it is generated. The odex file is only valid when used with these exact BOOTCLASSPATH files. dalvik enforces this by storing a checksum of each file that the odex file is dependent on, and ensuring that the checksum for each file matches when the odex file is loaded.
Deodex:
Deodexing is a way of repackaging the apk such that it is reassembled into the classes.dex file. Everything is put together in one place, and this is helpful because it eliminates any chances of a modified apk conflicting with other odexed parts.
to deodex a file using baksmali, it has to load every BOOTCLASSPATH file that the odex depends on. By default, baksmali will try to find the 5 "core" BOOTCLASSPATH files in the current directory. It can use either a jar/apk (with a classes.dex inside), or an odex file
So to sum up everything, a .dex file contains the cache used by Dalvik VM during boot and this .dex file is located inside the application. On the other hand, .odex file is an optimized version of the same .dex file but it is located outside the application.
