what is the difference between cleanrom and cromix from the features it seems the same? ok i found a thread that says they are the same but now i wonder why 2 names
also odex and deodex and which is better to have? OK this part i some what understand odex can be themed easier then deodex.
dady613 said:
what is the difference between cleanrom and cromix from the features it seems the same? ok i found a thread that says they are the same but now i wonder why 2 names
also odex and deodex and which is better to have? OK this part i some what understand odex can be themed easier then deodex.
Click to expand...
Click to collapse
1) sdbags would like a new name for JB 4.2.1 base so he called cromix and cleanrom or just cromi is for JB 4.1.1 base. The cromix is up to date and it will have more features than the old one, but the tweaks should be about the same.
2) In theory, Odex and deodex should be about the same in performance, but in real life, many ppl swore that Odex is definitely smoother. Finally yes, deodex can be themed eaiser than odex, but for the normal end users, we don't care about this too much.
thank you buhohitr
Related
This is supposed to be a universal method to ODEX:
http://forum.xda-developers.com/showthread.php?t=1476617
Safe for use to try?
Sent from my GT-N8013 using Tapatalk 2
I'm pretty sure the stock rom is already ODEXed. I've been trying to learn how to cook roms and just DeODEXed a UEALH2 stock rom. So I suppose if you wanted to ODEX a DeODEXed Note 10.1 rom you could with this method.
darksabre_x said:
I'm pretty sure the stock rom is already ODEXed. I've been trying to learn how to cook roms and just DeODEXed a UEALH2 stock rom. So I suppose if you wanted to ODEX a DeODEXed Note 10.1 rom you could with this method.
Click to expand...
Click to collapse
There's not much point to re-odexing a firmware. It saves a tiny bit of time on initial boot, but that's it. It has zero performance impact once the device has booted, and makes maintaining a firmware very difficult. (This is, for example, one of the reasons why Cyanogenmod doesn't odex builds.)
Hi all. I'm a little confused about the differences or cost/benefits of deodex vs odex roms. Are there major differences between the two or any contra-indications for using the different types?
My understanding is that deodexed roms are easier to theme, but take longer to boot. As there do not appear to be many theming options around right now,
I'm assuming that the latest deodexed stock ROM is for developers rather than average punters
Thanks for any help, Mike.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Mykew said:
Hi all. I'm a little confused about the differences or cost/benefits of deodex vs odex roms. Are there major differences between the two or any contra-indications for using the different types?
My understanding is that deodexed roms are easier to theme, but take longer to boot. As there do not appear to be many theming options around right now,
I'm assuming that the latest deodexed stock ROM is for developers rather than average punters
Thanks for any help, Mike.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Odex provides a tiny speed gain because the vital parts of some apps are decompressed for easier use whereas deodex, those parts remain compressed into one file allowing for easier themeing.
Hello,
I am using an unofficial AOKP JB build (25 Nov 2012), and it works quite well. However, some stock apps on it are not to my tasting (e.g., phone, contacts, etc). I really liked the feel and look of those apps in good old Gingerbread. Is there any way I could install/use them in AOKP JB? As far as I know, the stock GB is odexed, and the AOKP JB is deodexed, so it is impossible just to swap the apps in /system/app.
I would appreciate any suggestions or comments. Thank you.
E107946 said:
Hello,
I am using an unofficial AOKP JB build (25 Nov 2012), and it works quite well. However, some stock apps on it are not to my tasting (e.g., phone, contacts, etc). I really liked the feel and look of those apps in good old Gingerbread. Is there any way I could install/use them in AOKP JB? As far as I know, the stock GB is odexed, and the AOKP JB is deodexed, so it is impossible just to swap the apps in /system/app.
I would appreciate any suggestions or comments. Thank you.
Click to expand...
Click to collapse
Depends - some of the touchwiz-specific ones will require edits to framework (and maybe services) and likely a few other places to retain full functionality. Were such edits in place you could then drop in (as AOKP is deodexed) any of the deodexed system apps (I would rexommend pulling them from the stock ICS build myself) into /system/app - there's a zip full of said deodexed apps in the Tweaked OP (1.x has GB ones, 2.x has ICS ones) if you get to that point.
I tried to use apps from stock deodexed 2.3.6, but it did not work. Do you think I will have more luck with apps from stock deodexed ICS? Do I just put deodexed *.apk in /system/app or there is more to it? At what stage are binaries and other relevant files created from apk? Thanks!
E107946 said:
I tried to use apps from stock deodexed 2.3.6, but it did not work. Do you think I will have more luck with apps from stock deodexed ICS? Do I just put deodexed *.apk in /system/app or there is more to it? At what stage are binaries and other relevant files created from apk? Thanks!
Click to expand...
Click to collapse
More luck... most likely. The issue will be when the new-to-AOKP apk starts calling methods that don't exist in the jellybean-based framework - it will likely be an iterative process of try it, fail but get a logcat, see why it failed, try to track down what was missing from a tw framework, throw it in the aokp framework, and try again - and then lather rinse repeat. And that is all assuming no hiccups hit along the way, which never seems to be the case. While it sounds pretty labor-intensive, and will likely make you want to pull your hair out, it can be pretty fun trying to figure it all out. Good luck!
can anybody tell me if we can deodex our rom now that we have root? doesnt matter if it is using a pc or from within
I am pretty sure yes, although I could be wrong. Don't see why not though, you now have root level rights, and thus can deodex them. If you can read them, you can copy them. Good luck! I will try it out later too, and if anything goes wrong, no real harm done. Just reflash.
But why do you want to deodex? On average an odexed rooms is 10% faster then an deodexed rom. The reason behind having a deodexed rom is for theming purposes.
Sent from my LG-H900 using Tapatalk
I also read (somewhere) that when MM rolls out, the need for Odexing is completely gone.
MysteryEmotionz said:
But why do you want to deodex? On average an odexed rooms is 10% faster then an deodexed rom. The reason behind having a deodexed rom is for theming purposes.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Ive never seen which one is faster... I'll take ure word but I was under the impression that deodex in general is better? I know the main reason is to theme tho
Here is a good explanation. Deodexed is only good theming and modding but any good dev such as my self can work with an odexed system.
When I was actively developing Roms I would do both and they where identical in features and theming. Sometimes I offered to the public both but sometimes I would just order the deodexed version for the ease of theming back in the day and keep the odexed version for my self. I even have a script floating around that can odex your system after you flashed your ROM, mods, and themes.
Now with xposed and the right set of modules there no need to flash a theme like you did back in the day when it would replace the apk. So there is no need for a deodexed system.
http://www.redmondpie.com/odexed-vs-deodexed-the-difference-between-the-two-android-roms-explained/
Sent from my LG-H900 using Tapatalk
MysteryEmotionz said:
Here is a good explanation. Deodexed is only good theming and modding but any good dev such as my self can work with an odexed system.
When I was actively developing Roms I would do both and they where identical in features and theming. Sometimes I offered to the public both but sometimes I would just order the deodexed version for the ease of theming back in the day and keep the odexed version for my self. I even have a script floating around that can odex your system after you flashed your ROM, mods, and themes.
Now with xposed and the right set of modules there no need to flash a theme like you did back in the day when it would replace the apk. So there is no need for a deodexed system.
http://www.redmondpie.com/odexed-vs-deodexed-the-difference-between-the-two-android-roms-explained/
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
thanks i guess i wont deodex then
From trying Alexis to Xtralite and Xtrestolite MM roms, what do you find overall better stock or deodex, in terms of battery, UI, bloatware, speed etc.
Post screenshots of SOT or whatever you feel necessary.
Odex from will always be faster than a deodex rom.
Sent from my iPhone using Tapatalk
LNJ said:
Odex from will always be faster than a deodex rom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
what about battery
LNJ said:
Odex from will always be faster than a deodex rom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
if I remember good, just for first boot speed difference, later speed same.
LNJ said:
Odex from will always be faster than a deodex rom.
Click to expand...
Click to collapse
Some mods and tools don't work on Odex either. Which is why the majority of Ron's are deodex
[Complete Guide] What is Odex and Deodex ROM?
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.
Click to expand...
Click to collapse