Odexed vs. Deodexed

reigndropz · #1 (**permalink**) 08-01-2010, 04:23 PM

I been reading up a little bit on this over at XDA and on here as well, but maybe you guys can throw out a better explanation for me. From what I read, Odexed ROMS use less memory but some of the tweaks, such as battery percent in battery icon, can not be installed. Deodexed takes up more memory but everything is modifiable. Am I on the right track?

olimar814 · #2 (**permalink**) 08-01-2010, 06:04 PM

Quote:

Originally Posted by reigndropz

I been reading up a little bit on this over at XDA and on here as well, but maybe you guys can throw out a better explanation for me. From what I read, Odexed ROMS use less memory but some of the tweaks, such as battery percent in battery icon, can not be installed. Deodexed takes up more memory but everything is modifiable. Am I on the right track?

+1...?

**apristel** · #3 (**permalink**) 08-01-2010, 06:09 PM

Basically if you want themes and stuff you want Deodexed.

from a post on XDA..

Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.

Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.

So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.

If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.

reigndropz · #4 (**permalink**) 08-01-2010, 09:08 PM

Yeah I understand that part, but why would a chef NOT want to use a Deoxed ROM? Is it only because of memory reasons?

tj.iscool · #5 (**permalink**) 08-01-2010, 09:53 PM

deodexed roms run fine for me

**bradart** · #6 (**permalink**) 08-02-2010, 01:59 AM

Quote:

Originally Posted by reigndropz

Yeah I understand that part, but why would a chef NOT want to use a Deoxed ROM? Is it only because of memory reasons?

Like he said, you're choosing a bit more memory use for theme/mod-ability as opposed to the most efficient but more locked down method. The consensus in the dev community is a resounding "deodexed".

ddark4eva · #7 (**permalink**) 08-02-2010, 06:59 AM

ahh so thats it, since i just started making themes i guess ill be looking specifically for Deodex now

MrDSL · #8 (**permalink**) 08-02-2010, 07:14 AM

My understanding was Deodexed only used more memory and took longer on initial boot but after that it used less memory. I could be wrong though its been awhile since I read about it.

**bradart** · #9 (**permalink**) 08-02-2010, 02:22 PM

Quote:

Originally Posted by ddark4eva

ahh so thats it, since i just started making themes i guess ill be looking specifically for Deodex now

Correct

Sent from my PC36100 using Tapatalk