Originally Posted by jklong03
Interesting, so are you saying from your research this morning, you have found that Dalvik-Cache is something that arises out of using de-odexed ROMs, and not something that would exist in an odex version of the same ROM? I could see this I guess, since once we rooted our phones and started playing with flashable roms, they were all de-odexed and hense I got used to seeing dalvik-cache on all of them.
Well, I still don't have a full grasp on it yet. I talked with mik and he answered some questions. I did a little googling too. Stock roms come odexed as far as the system and frameworks go. The odex files are short for optimized dalvik executables. They tell the system what to do. In a deodexed rom, the dalvik virtual machine has to pull/decompile (looking for correct wording) the classes.dex from within each apk at boot up, thus long boot up times. With odex, it cones precompiled and thus need not decompile. The dalvik still exists even in stock roms. It is an android thing. So market apps and data appa still use it. Deodexing just allowed the system and framework files to utilize the dalvik and make theming easier because the apks are more or less all inclusive since the classes.dex are within the apk. So jeff, that is what I gathered. Our mik is changing the game.
Edit: also, the odex files are more device specific and not as easily toyed with. Thats why most devs have used deodexed from the old days. Mik said that the new devices are different. We can do more with them now then we could then. Its time to invent some new creative ways of doing things instead of utilizing the same old tricks over and over. I see it like that.
Sent from my PC36100 using XDA Premium App