Develop Bugs

What's Deodex and Odex?

I've been seeing those words a LOT in recent threads.
Any detailed explanation on them please?

[search] deodex [/search]
Berzerker said:
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Click to expand...
Click to collapse

danknee said:
[search] deodex [/search]
[/I]
Click to expand...
Click to collapse
How does it matter to regular user?

donniezazen said:
How does it matter to regular user?
Click to expand...
Click to collapse
Themes mostly.

sk63 said:
Themes mostly.
Click to expand...
Click to collapse
Thanks. Are themes available in Deodex or Odex? Sorry for noob questions.

Related question also....
- Which can live with which? (Deodexed ROM + Odexed Theme? or Odexed ROM + Deodexed Theme?)
You know, like type O is universal donor and type AB is universal recipient...do these work similar or only deodexed with deodexed...?
(where is that darn wiki??)

sablesurfer said:
Related question also....
- Which can live with which? (Deodexed ROM + Odexed Theme? or Odexed ROM + Deodexed Theme?)
You know, like type O is universal donor and type AB is universal recipient...do these work similar or only deodexed with deodexed...?
(where is that darn wiki??)
Click to expand...
Click to collapse
Dear GOD,
Please come down from heaven and explain by some magic show what the hell these deodexed and odexed means?
Thank you,
A non-believer.

donniezazen said:
Dear GOD,
Please come down from heaven and explain by some magic show what the hell these deodexed and odexed means?
Thank you,
A non-believer.
Click to expand...
Click to collapse
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.
I think that's the general idea, anyway.

sablesurfer said:
Related question also....
- Which can live with which? (Deodexed ROM + Odexed Theme? or Odexed ROM + Deodexed Theme?)
You know, like type O is universal donor and type AB is universal recipient...do these work similar or only deodexed with deodexed...?
(where is that darn wiki??)
Click to expand...
Click to collapse
You will never find an odexed theme since the odex file would contain things that needed to be changed, thus themes are deodexed. Themes basically just replace the .apk or .jar with their version, which wouldn't work on an odexed rom.
donniezazen said:
Dear GOD,
Please come down from heaven and explain by some magic show what the hell these deodexed and odexed means?
Thank you,
A non-believer.
Click to expand...
Click to collapse
Basically, Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
Hopefully that cleared that up.
EDIT: Darn, beaten.

Thank you all. So...themes are deodexed. And only run on deodexed rom...got it. Meaning...I need a deodexed version of the new Froyo to keep my white Rosie. Cool.

faster3200 said:
EDIT: Darn, beaten.
Click to expand...
Click to collapse
Yeah, but you clearly know it better than I do.

if you install a de-odexed rom, will the system automatically rebuild the Dalvik cache and appropriately odex the apk's, or is this something that a dev needs to do manually beforehand? In other words, are there any disadvantages to a de-odexed rom other than an initially slower phone? will the phone eventually rebuild the cache and perform as an odexed system would?

^bump^
Same question as vinconti - will a deodexed ROM run slower than an odexed one?
Thanks

<InigoMontoya>You keep using that word. I do not think it means what you think it means.</InigoMontoya>
Thanks for the explanations, all. I just rooted my D2 but haven't done any themes yet. This helps, but only from the standpoint of I'll have to get back into flashing. I thought I left that behind when I trashed my Omnia.

I have a regular odexed ROM. I replace some of the apk+odex files by deodexed APK's, so that seems to be no problem. But I was wondering whether this would also work for jar+odex files (e.g. android.policy.jar)....

kasper_h said:
I have a regular odexed ROM. I replace some of the apk+odex files by deodexed APK's, so that seems to be no problem. But I was wondering whether this would also work for jar+odex files (e.g. android.policy.jar)....
Click to expand...
Click to collapse
If this does actually work without problems does that mean we'd only have to de-odex certain .apks rather than the whole ROM?

KrushR said:
<InigoMontoya>You keep using that word. I do not think it means what you think it means.</InigoMontoya>
Thanks for the explanations, all. I just rooted my D2 but haven't done any themes yet. This helps, but only from the standpoint of I'll have to get back into flashing. I thought I left that behind when I trashed my Omnia.
Click to expand...
Click to collapse
Thanks for the Inigo moment. You made my night.
Question to the room: Do I need this deodexing thing just to install apps and run the wifi tether (the whole reason I'm venturing into root territory to begin with)? I don't care what it looks like, I just want it to provide wifi to my soon-to-be-rooted Nook Color. Thanks in advance.

But... All I want is WiFi tethering!
lngwstx said:
Question to the room: Do I need this deodexing thing just to install apps and run the wifi tether (the whole reason I'm venturing into root territory to begin with)? I don't care what it looks like, I just want it to provide wifi to my soon-to-be-rooted Nook Color. Thanks in advance.
Click to expand...
Click to collapse
This is pretty much my question as well. This whole Odex/Deodex thing is totally frying my brain.
I'm not trying to do anything fancy, I just want to use the WiFi tether feature. Which one is good enough for just doing THAT?

keep your advice for yourself
donniezazen said:
Dear GOD,
Please come down from heaven and explain by some magic show what the hell these deodexed and odexed means?
Thank you,
A non-believer.
Click to expand...
Click to collapse
keep your advice for yourself

How to Deodex?

[Q] (GUIDE) How to make a theme template

This will guide you through making a theming template.
Why: it was requested
What is it for: This is the base in which you start your custome theming. If you have read through Dreamsforgotten thread on theming, you will see that he refers to a theming template to start with.
Be advised, This is not a rom. It is just a template that some dev/themers use as a base for their custome themes or to return to a stock deodex theme. Also, this assumes that you are on a stock rooted system
The Difference you ask:
Theming templates : do not have a modem or kernel, They do have a system folder with and App, font, and framework folder.
Rom: has everything needed to run the OS. Modem (sometimes), kernel, and a full system folder
This is how I do it. That is not to say it is right or wrong, but it works for me. There may be other/easier way developed by other devs.
EI22 Theme Template
Tools:
Rom kitchen form here ( follow the thread and set it up )
7zip from here
Notepad++ from here
Rooted device: if you are not rooted look in the dev section of your device for the instructions on that
Clockwork mod: if you don’t know what this is or don’t have it go to the dev section and research.
Instructions:
1: get a copy of the STOCK system folder. It really does not matter how you get it. JUST GET IT
HINT: if you are rooted already, use root explorer or equivlant and copy it to the sdcard….
Depending on how you got it, you may need to copy it to your computer desktop ( do so now)
2: now you will need to make a zip file (by now you should have 7zip installed)
r-click on system folder that you just copied to your desktop
choose 7zip > add to archive.
under archive change name to (build#).zip ( replace (build#) with the build you are using i.e ec05, ei22 ect….)
At this point you will need the rom kitchen. So, if it is not set up, DO SO!!!!!!!
3: copy to the zip folder to kitchen > original_update. Then open the kitchen.
Choose option 1, answer the next few questions as you need to. For me, I just hit enter at the 4 questions. You should be back at the main screen now
option 0 (enter) > option 11 (enter) > option b (enter) > enter ( best so that if there are errors you can troubleshoot) ( this takes a while: 20 min) assuming all went well, you should get
0 *.odex in system/app
0 *.odex in system/framework
Hit the enter key
option 99 > option 2
At this point, there should be a new folder named “output_zip” with your rom in it. (enter) you should be back to the mail menu. We are done with the kitchen so you can close that.
BUT your not done yet. 
4: go to the above mentioned folder. In the folder there will be a zip file.
r-click on it and rename theme_template_(build#) ( replace (build#) with the build you are using i.e ec05, ei22 ect….)
r-click> 7zip> open archive - There you will see two folders and a boot image.
delete the boot.img file
go into the system folder and delete everything except app, framework, and font folders
back out one level and go into meta-inf >com > google >android
Now delete the updater-script (leave 7zip open)
Now we need to write the updater-script for CMW to read
5: open notepad++
BE ADVISED, this portion is for the EPIC 4G and the updater-script may change formats based on your device. So do some research first. I tend to look at other script for my devices to see how it should be formatted.
You can copy and past this in or type it yourself:
show_progress(0.1, 0);
delete_recursive("/system/framework");
delete_recursive("/system/app");
delete_recursive("/system/fonts");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
delete_recursive("/data/dalvik-cache");
show_progress(0.1, 10);
unmount("/system");
Or use this: updater-script
file >save as
Name file: updater-script
File type: chose all types (*.*) you may need to scroll up or down to find it.
save to desktop
drag and drop the updater-script into the 7zip screen. ( you will be prompted with a ?. just hit yes.)
You should now have 3 files on the 7zip screen
Updater-script, update-binary, update-script.orig
close 7zip.
Connect phone via USB
Copy file to sdcard
Disconnect phone
Reboot to CMW
Choose: backup and restore >backup (when its finished you will have a nandroid to restore if you F.U.B.A.R. your phone.
Choose: install zip from sdcard and install your theming template.
Reboot.
Now use your favorite file explorer and go to system/framework and make sure it has been deodexed. If so, the flash was successful and your theme template works.
Congradulations you built your first theme. All be it a stock one. lol

mine for the thank you's
dreams - for all of his tuts
dsixda - for the kitchen.

Finally
Sent from my SPH-D700 using Tapatalk

Zeinzu said:
Finally
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
your welcome.... lol

Download doesn't work. Just downloads and empty zip.
Sent from my SPH-D700 using Tapatalk

You can use this thread or learn to do the XML code changes and mods by hand as most of the seasoned theme devs do... I find it a whole lot more rewarding than letting this kitchen or the UOT Kitchen do the work for me....
This also works hand in hand when something goes wrong with your theme you know where to look to fix the problem.
FYI, even with the various themes that myself and ZiggSVO have worked on we still don't know everything and we all do exchange ideas and trouble shoot among each other. That is what makes all this stuff fun and rewarding.
Just my opinion...

Zeinzu said:
Download doesn't work. Just downloads and empty zip.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
looking into it.
just dl'ed - worked fine for me.

Paul627g said:
You can use this thread or learn to do the XML code changes and mods by hand as most of the seasoned theme devs do... I find it a whole lot more rewarding than letting this kitchen or the UOT Kitchen do the work for me....
This also works hand in hand when something goes wrong with your theme you know where to look to fix the problem.
FYI, even with the various themes that myself and ZiggSVO have worked on we still don't know everything and we all do exchange ideas and trouble shoot among each other. That is what makes all this stuff fun and rewarding.
Just my opinion...
Click to expand...
Click to collapse
i tend to agree. but a noob has to have someplace to start. I wish there was the help i needed when i started doing these things a yr ago. I've learned alot throught the guids that i've found, but yes learning to do them by hand is great to.

Z..
what are you tring to dl. the template "worked fine for me" or the updater-script?

Paul627g said:
You can use this thread or learn to do the XML code changes and mods by hand as most of the seasoned theme devs do... I find it a whole lot more rewarding than letting this kitchen or the UOT Kitchen do the work for me....
This also works hand in hand when something goes wrong with your theme you know where to look to fix the problem.
FYI, even with the various themes that myself and ZiggSVO have worked on we still don't know everything and we all do exchange ideas and trouble shoot among each other. That is what makes all this stuff fun and rewarding.
Just my opinion...
Click to expand...
Click to collapse
I definitely agree, doing it by hand gives you a more broad understanding of how the xml code works. This allows you to perform other modifications as well, and like Paul said it is rewarding and also exciting.
Don't get me wrong, I definitely appreciate the guide! Perhaps you could divide it into a noob section and a more involved section.
Sent from my SPH-D700 using XDA Premium App

thomasskull666 said:
I definitely agree, doing it by hand gives you a more broad understanding of how the xml code works. This allows you to perform other modifications as well, and like Paul said it is rewarding and also exciting.
Don't get me wrong, I definitely appreciate the guide! Perhaps you could divide it into a noob section and a more involved section.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Paul627g said:
You can use this thread or learn to do the XML code changes and mods by hand as most of the seasoned theme devs do... I find it a whole lot more rewarding than letting this kitchen or the UOT Kitchen do the work for me....
This also works hand in hand when something goes wrong with your theme you know where to look to fix the problem.
FYI, even with the various themes that myself and ZiggSVO have worked on we still don't know everything and we all do exchange ideas and trouble shoot among each other. That is what makes all this stuff fun and rewarding.
Just my opinion...
Click to expand...
Click to collapse
Not sure what you are asking for. There is no XML editing involved here. If you are talking about the deodexing process, sure i can write out the long way to do it by hand. But there are alomost 200 odex files btween the apps folder and the framework folder to deodex. This process would take you all day to do if it wasnt for the kitchen.

spdwiz18 said:
Not sure what you are asking for. There is no XML editing involved here. If you are talking about the deodexing process, sure i can write out the long way to do it by hand. But there are alomost 200 odex files btween the apps folder and the framework folder to deodex. This process would take you all day to do if it wasnt for the kitchen.
Click to expand...
Click to collapse
Maybe some are misunderstanding the guide? I'm a little confused also lol. The way I read it...it comes across as just how to deodex your ROM? No actual themeing? Just to get a base template to start themeing...
Is that right?
Further clarification would be appreciated.
Sent from my Nexus S 4G using Tapatalk

I probably jumped the gun myself on thinking this was a theme guide. Only point I was trying to make was I hate seeing people use UOT Kitchen or other means to do themes or build a ROM using it and then put it out as their own work. These methods I think are great for personal use but to build an entire themed frameworks, etc and then expect to take credit for it is a bit overboard and trust me there has been plenty of work here in the past based off of UOT Kitchen and other means.
Bottom line, its more rewarding in the long run when you do as much as possible by hand and learn how its all done. Heck I even recently went back and learned how to use APK TOOL itself to decompile and recompile apks aside from just using APK Manager. Sure I know APK Manager is the tool of choice but I still wanted to see how others did it before the big move over to APK Manager.
Otherwise, this is a great thread having a tool to deodex a ROM. Personally I have never successfully deodexed a ROM myself, I've come close and had working ROMs but usually ended up with one thing or another broken in the deodexing process.

Paul627g said:
I probably jumped the gun myself on thinking this was a theme guide. Only point I was trying to make was I hate seeing people use UOT Kitchen or other means to do themes or build a ROM using it and then put it out as their own work. These methods I think are great for personal use but to build an entire themed frameworks, etc and then expect to take credit for it is a bit overboard and trust me there has been plenty of work here in the past based off of UOT Kitchen and other means.
Bottom line, its more rewarding in the long run when you do as much as possible by hand and learn how its all done. Heck I even recently went back and learned how to use APK TOOL itself to decompile and recompile apks aside from just using APK Manager. Sure I know APK Manager is the tool of choice but I still wanted to see how others did it before the big move over to APK Manager.
Otherwise, this is a great thread having a tool to deodex a ROM. Personally I have never successfully deodexed a ROM myself, I've come close and had working ROMs but usually ended up with one thing or another broken in the deodexing process.
Click to expand...
Click to collapse
Ya I will admit so did I lol, the xml portion is in reference to theme porting, not deodexing.
Carry on >_>
Sent from my SPH-D700 using XDA Premium App

Paul627g said:
I probably jumped the gun myself on thinking this was a theme guide. Only point I was trying to make was I hate seeing people use UOT Kitchen or other means to do themes or build a ROM using it and then put it out as their own work. These methods I think are great for personal use but to build an entire themed frameworks, etc and then expect to take credit for it is a bit overboard and trust me there has been plenty of work here in the past based off of UOT Kitchen and other means.
Bottom line, its more rewarding in the long run when you do as much as possible by hand and learn how its all done. Heck I even recently went back and learned how to use APK TOOL itself to decompile and recompile apks aside from just using APK Manager. Sure I know APK Manager is the tool of choice but I still wanted to see how others did it before the big move over to APK Manager.
Otherwise, this is a great thread having a tool to deodex a ROM. Personally I have never successfully deodexed a ROM myself, I've come close and had working ROMs but usually ended up with one thing or another broken in the deodexing process.
Click to expand...
Click to collapse
thomasskull666 said:
Ya I will admit so did I lol, the xml portion is in reference to theme porting, not deodexing.
Carry on >_>
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
And this is why im not in the field that i went to school for. lol (cysco networking) i got to the last class and they told me i had to document everything. I just dont have the skills to do that. I am going to edit the OP to better clarify what i was tring to do.
No worries to everyone. your opinions are wellcome. I am not all knowing, but i love to learn and share what i do know.

[Q] how do u make a custom rom

useing ubuntu what do i need to download

Glewis21 said:
useing ubuntu what do i need to download
Click to expand...
Click to collapse
What kind of rom? Stock based? Aosp/miui/cm7?
Are you going to be building from source?
Personally as a miui porter, I use 7zip, apktool, and notepad++
Sent from my SPH-D700 using Tapatalk

On Ubuntu there is already a good notepad. You need the android sdk (add it to path), apktool, smali, baksmaly, all of the crap needed for compiling cm7, eclipse and it's ADK plugin, 7zip, voodoo kernel repack tools, that's probably all...
Sent from my SPH-D700 using XDA App

I had a question along the same lines. But I'm a total noob to coding. What I really wanna do is take an already built rom and add some mods to it that I like and then save the package as a rom . In doing that I'm hoping to cut my teeth a little into the world of rom creation.
Sent from my SPH-D700 using xda premium

Xalky said:
I had a question along the same lines. But I'm a total noob to coding. What I really wanna do is take an already built rom and add some mods to it that I like and then save the package as a rom . In doing that I'm hoping to cut my teeth a little into the world of rom creation.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
What you are talking about Xalky is more on the lines of themeing. Customizing icons, layouts and adding in fixes, then repackaging it into the flashable. Check out the Themes subforum and the sticky at the top by Dreamsforgotten on How to theme. That may be what you are looking for. Then either Dreams, myself or the dozens of other helpful users here can help you repackage it. It is just a matter of swapping the finished product back into the ROM flashable and of course giving credit to all that contributed or developed the stuff you grabbed to mod.

kennyglass123 said:
What you are talking about Xalky is more on the lines of themeing. Customizing icons, layouts and adding in fixes, then repackaging it into the flashable. Check out the Themes subforum and the sticky at the top by Dreamsforgotten on How to theme. That may be what you are looking for. Then either Dreams, myself or the dozens of other helpful users here can help you repackage it. It is just a matter of swapping the finished product back into the ROM flashable and of course giving credit to all that contributed or developed the stuff you grabbed to mod.
Click to expand...
Click to collapse
You are correct. Thats what I'd like to do......for now. Thanks for the lead. It's mainly for myself to be able to save my phone setup as one flashable zip. Is there a way to take your current Rom/theme setup with mods and copy the entire thing from the phone and turn it into one flashable zip? minus my add on apps. I thought I saw someone do that around here.

Xalky said:
You are correct. Thats what I'd like to do......for now. Thanks for the lead. It's mainly for myself to be able to save my phone setup as one flashable zip. Is there a way to take your current Rom/theme setup with mods and copy the entire thing from the phone and turn it into one flashable zip? minus my add on apps. I thought I saw someone do that around here.
Click to expand...
Click to collapse
I believe there is a way to make an Odinable tar backup of your phone just how it is. But that would backup all your accounts and settings too. What you want is to just stuff your modded files back into the ROM zip.

[ICS][MOD][CWMR]Long Press volume changes music track

So after desperatley wanting this mod to work on my captivate glide at any cost, i went after it myself. It looked easy at first but turned out to consume a lot of hours figuring out how to compile decompile and understand basics of smali.
What it does ?
As in the title, pressing the volume buttons a little longer (400 ms) will make the stock music player skip to next track (up vol) or previous track (down vol). This only works while the screen is off and phone locked which is basically the purpose . Right now will work on deodexed ROMs only, meaning pepole having "android.policy.odex" file in the system/framewrok folder would not be able to use this mod.
Caution : The mod if goes wrong can/will make your phone stuck at the boot animation unless the mod is removed. Copy both the files so you can restore your original file back in case it doesn't work for you.
How to Install
1) Make sure you are rooted. and boot into CWMR.
2) Flash LongPressVol.zip - Installs the mod and takes backup
3) Wipe Dalvik and Cache partition
4) Reboot and "Upgrading android" screen should show up.
You are done and now test it and let me know if it works for you. Enjoy!!!
Restore original/Remove Mod :
1) Boot into CWMR.
2) Flash LongPressVolRemove.zip - Restores your original android.policy.jar file
3) Wipe Dalvik and Cache partition
4) Reboot
Tested to be working fine on following ROMs
Nardholio's NardROM 0.4
Thegreatergood's LiteROM .4
Credits : Ported with help from the guide posted by jakubklos -> http://forum.xda-developers.com/showthread.php?t=1770564
Next update :
CWM flashable zip (will need some time to learn how to do that - Done
Post the Diff and the code to make it easier for other roms to include it if the android.policy.jar changes. - In progress

Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium

Force closes PowerAMP and Nova Launcher.
Tested on ICS Leak.

Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.

Cool thanks for the tip!
Sent from my SGH-I927 using xda premium

ludacris1 said:
Force closes PowerAMP and Nova Launcher.
Tested on ICS Leak.
Click to expand...
Click to collapse
Strange works for me. Nova didn't quit at all throughout my testing. I tried Poweramp trial and works fine as well. Did you clear dalvik and cache after flashing in the Mod ?

Nardholio said:
Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.
Click to expand...
Click to collapse
Tried with no success stuck at boot screen. Thanks for the hint I'll try re odexing it and see if that will work next.
I like all the bloat that the stock has except the att apps, I would love to try your ROM but I would prefer a completely stock version of it with little modification and fixes. I have tried to do it myself with no success and simple don't have the patience for it. As my computer would end up at the muzzle end of a AR15. I really don't want to waste ammo or buy a new computer just yet. LOL ^o^
I'm very happy with the stock rom after applying the keyboard, tethering fix, and sdcard swap. It will be perfect when I get this working on it. And if its true that having it odexed is faster, I don't know but it is very smooth and battery is awesome.
Sent from my SGH-I927 using xda premium

enewman17 said:
Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
As evident from your last post, it does not work for you on UCLH2. As i said in my OP that i've not tested it on LH2 and it might not work as the android.policy.jar may be different. It should work on the UCLG9 and the ROM's based on it for sure.
I'll see later what i can do for the LH2. Can you post me a link of your whole system/framework folder, so i can download the same ? I'll maybe try later in the day to see the difference.

Thanks you, much appreciated! http://db.tt/0PnPOv4p
Sent from my Transformer TF101 using XDA Premium HD app

enewman17 said:
Thanks you, much appreciated! http://db.tt/0PnPOv4p
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Deodexed your files and compared the PhoneWindowManager.smali file with mine, they are binary equals. So technically this mod should work for you. As your ROM is odexed, you need to manually delete the android.policy.odex and android.policy.jar file and then copy the android.policy.jar file from the zip attached to the OP. Remember to clear dalvik and cache partition as the last step before rebooting your phone. As Nardholio suggested this should work and you don't need to deodex the whole ROM.

Updated OP with the name of the ROM's tested to be working fine with this mod. Will try some more and keep adding.
Sent from my SGH-I927

Nardholio said:
Just delete the odex file and clear cache and you should be fine. You don't have to deodex the whole ROM.
or for extra points you can reodex, which theoretically will boost speeds a bit (although I'm experiencing wonderful speeds on my ROM). Redodexing is pretty easy (just Google it) and doesn't require him to do his mod again.
Click to expand...
Click to collapse
Do not delete the odex file... in an odex ROM all the code, java and smali are located in the odex class until you deodex which pulls the classes out and compresses them into a classes.dex into the particular apk and/ or jar file. So, if you delete the odex file the jar or apk is useless as you just deleted all the java and smali code it uses to communicate with the DVM..
Sent from my SGH-I897 using xda premium

dman3285 said:
Do not delete the odex file... in an odex ROM all the code, java and smali are located in the odex class until you deodex which pulls the classes out and compresses them into a classes.dex into the particular apk and/ or jar file. So, if you delete the odex file the jar or apk is useless as you just deleted all the java and email code it uses to communicate with the DVM..
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Deodexing is all clear and i know the procedure, but can you let me know some link or tutorial to follow to odex it back again ? I think it needs the whole rom and needs some more files like framework etc. to be odexed again ?
Note: still learning and long way to go

In my trying to learn all of this too, seems you can re-odex a rom. But everything I found has to be done on the phone it self with terminal and a odex wrapper script. Haven't found a way of doing it on a computer yet.
Sent from my SGH-I927 using xda premium

enewman17 said:
In my trying to learn all of this too, seems you can re-odex a rom. But everything I found has to be done on the phone it self with terminal and a odex wrapper script. Haven't found a way of doing it on a computer yet.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I've read some tutorials as well, but lemme know if you find a easier way to do this. I'm almost certain that the odex files are specific to a specific rom, but i can be wrong as well. That's the reason i believe that the generic mods are only for the deodexed ROMs.

enewman17 said:
Awesome, been missing this mod since leaving my DHD
CWM Flashables worked great..... But since I'm using the stock rom which has not been deoxed it did not work.
It booted though didn't notice any adverse affects
Not to put you on the spot but do you think you could use the UCLH2 .jar and make a version that will use odex. not sure if anything would have to be done to the odex file but I have included the non odexed android.policy.jar files if you wouldn't mind taking a stab at it. If you could just modify the .jar file I'll test it. I would be forever in your debt!
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I don't realize there was a Dial Home Device on earth, I though it was never found
*stargatefan*

TheHow7zer said:
I don't realize there was a Dial Home Device on earth, I though it was never found
*stargatefan*
Click to expand...
Click to collapse
Lol love stargate
Sent from my Desire HD using xda premium
---------- Post added at 07:13 PM ---------- Previous post was at 06:47 PM ----------
ninthsense said:
I've read some tutorials as well, but lemme know if you find a easier way to do this. I'm almost certain that the odex files are specific to a specific rom, but i can be wrong as well. That's the reason i believe that the generic mods are only for the deodexed ROMs.
Click to expand...
Click to collapse
Yes the odex file is specific per app so if any changes were made, the odex file which contains most of the data for each app would also have to reflect those changes. As the changes you made were part of .smali which is part of the dex file. So on a stock rom the odex file is loaded into the Dalvik machine during boot. This is why when flashed on a odexed rom the mod does not take, because the non modded odex file was already loaded. I gave up as I'm happy using literom4 with your mod.
Edit: Ok here is why it has to be done using the phone, all has to do with BOOTCLASSPATH http://classictomatoe.net/dexo-universal-odex-tool/
If you wanted to make this mod for folks still using the stock rom. All that needs to be done is decompile the .odex file using baksmali make the changes to the necessary files and then smali ?I think? don't quote me on that.

Can you share the how to four this? I'm setting up a rom and would like to add this
Sent from my SGH-I927 using xda app-developers app

kick buttowski said:
Can you share the how to four this? I'm setting up a rom and would like to add this
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Would you use the new uclj3 ? Send me the androidpolicy jar from your rom and hopefully it should be the same. I've not upgraded to .8 literom yet so not sure if it will work as .8 is based on the newer uclj3 released by samsung.
Sent from my SGH-I927

ninthsense said:
Would you use the new uclj3 ? Send me the androidpolicy jar from your rom and hopefully it should be the same. I've not upgraded to .8 literom yet so not sure if it will work as .8 is based on the newer uclj3 released by samsung.
Sent from my SGH-I927
Click to expand...
Click to collapse
Here ya go

[Q] Question about deodex and odex

So as I understand it a odexed rom which is how it comes from the factory should have a .apk file and a corresponding .odex file. for example in the /system/app directory you would find a phone.apk and phone.odex. Right?
So when you deodex the rom it should take that .odex file and repackage it into the.apk so you would only see phone.apk in the /system/app directory. And if you open up the phone.apk there will be a file called classes.dex which is the odexed info that was put in the .apk is that right?
The reason I am asking is because I installed tesh rom. I chose the deodexed one. then I installed all the modds from tekhd mods thread. They all worked fine. My phone is running great. BUt I noticed that I have the .apk and corresponding .odex file and when I read the .apk it contains the classes.dex file. So is the rom deodexed or not. I was under the impression that the modds would not work if the rom was still odexed. So I am a little bit confused.
Can someone shed some light on what is going on here?
Thanks,
Charlie

mojorisin7178 said:
Can someone shed some light on what is going on here?
Thanks,
Charlie
Click to expand...
Click to collapse
You already answered your own question dude. If it was odexed you would not have working mods.

So then I should still have 2 files in /system/app one .apk and one.odex. because I was under the impression that when you deodex you take that odex file and put it into the .apk so there would only be one file. That is what is confusing me. I am sorry that I am not following this I am trying.

mojorisin7178 said:
So then I should still have 2 files in /system/app one .apk and one.odex. because I was under the impression that when you deodex you take that odex file and put it into the .apk so there would only be one file. That is what is confusing me. I am sorry that I am not following this I am trying.
Click to expand...
Click to collapse
so you downloaded the odex version of the ROM, then flashed a deodexed theme, and it worked, correct? this is what you are saying?
i would not be surprised if that was the case. a lot of our old ways of doing things in android is changing. jelly bean is a very cleverly designed OS..
for example, i have made changes to the framework before, flashing a deodexed theme on an odexed theme, and just to see what it would do, did not wipe dalvik cache (our old structure of doing this type of modification has told us this is REQUIRED, for obvious reasons). the script written in the zip file did not wipe it for me, checked after this happened:
i booted up, and guess what? in the log cat saw that android was doing some signature checks on the dvm and verifying them against the existing framework files. found they didn't match, and it automatically cleared the dvm files and rebuilt them.
interesting yes? well, what i am getting at, again, is that i am not surprised this worked for you just because of the way android has changed. it is becoming a lot "smarter" so to say.
verify you actually downloaded an odexed ROM, and that the /system/framework and /system/app directory contents are indeed odexed, and come back here. also, verify you did indeed flash a theme for DEodexed ROMs... if all of this is the case, it seems we might be able to throw out all we know about flashing odexed roms/themes in our newer versions of the OS.
good luck, and very interesting intriguing event!

When I vet home tonight I will do some investigating. But what I thought I did was download the deodexed version and then added modd to it that were only supposed to work on deodexed roms. But when I went to my /system/app it had both .apk and .odex. so then I thought I might have dowoaded the odexed version. Which then the modds should not have worked.
So when I get home I will do some cbecking and pkst back with links to what I used and sys images if that helps. And thank 6ou for helping me out.

mojorisin7178 said:
When I vet home tonight I will do some investigating. But what I thought I did was download the deodexed version and then added modd to it that were only supposed to work on deodexed roms. But when I went to my /system/app it had both .apk and .odex. so then I thought I might have dowoaded the odexed version. Which then the modds should not have worked.
So when I get home I will do some cbecking and pkst back with links to what I used and sys images if that helps. And thank 6ou for helping me out.
Click to expand...
Click to collapse
Yes that is exactly what you should do. Also don't forget to check the contents of the /system/framework directory as those are the ones specific to theming your UI (statusbar, etc etc)