What's the point of deodexing?
Sent from my SGH-T999 using xda app-developers app
HG! said:
What's the point of deodexing?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
themes
---------- Post added at 01:13 AM ---------- Previous post was at 01:06 AM ----------
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.
jamcar said:
themes
---------- Post added at 01:13 AM ---------- Previous post was at 01:06 AM ----------
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.
Click to expand...
Click to collapse
Thanks man! Best answer.
So besides themes, it doesn't really optimize the OS, huh?
Sent from my SGH-T999 using xda app-developers app
Related
I was looking in Q&A forum to find the answer to the differences of deodex vs. odexed ROMs, if I missed it in my searches just a simple link to the correct post will help thanks.
If there isn't already the topic, it has peek my curiosity on the differences of deodex vs. odexed. Do each offer there own advantages and disadvantages on the 3D?
And my main question is, what are the differences between the 2 and why are two different types of ROMs needed over one style. Thanks for clarifications.
Odex is faster (mik himself makes his rom odex for the reason) , deodex is better for theming and is slower yo boot just cause of some heavy mods some developers run. Which one is better? That'd up to you, I usually go with odex unless the rom has some great customization that I like
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.
Sent from my PG86100 using Tapatalk
Thanks jgalan14 for the response, greatly appreciate it
jgalan14 said:
. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
yes, individual apps can be deodex and loaded on the system with other odex apks.
only concern i would have is to make sure to remove the odex file for that specific apk when loading the deodex version.
great explanation on odex/deodex!
joeykrim said:
yes, individual apps can be deodex and loaded on the system with other odex apks.
only concern i would have is to make sure to remove the odex file for that specific apk when loading the deodex version.
great explanation on odex/deodex!
Click to expand...
Click to collapse
Are you developing for 3d? Man I remeber you from the moment days lol
Sent from my PG86100 using Tapatalk
Thanks for this! I have always wondered but couldn't find anything
Sent from my PG86100
jgalan14 said:
Odex is faster (mik himself makes his rom odex for the reason) , deodex is better for theming and is slower yo boot just cause of some heavy mods some developers run. Which one is better? That'd up to you, I usually go with odex unless the rom has some great customization that I like
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.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
thanks that helps me out alot
jgalan14 said:
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.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
That isn't 100% accurate.
Sent from my PG86100 using Tapatalk
EricSS619 said:
That isn't 100% accurate.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Yup is not I didn't have the time to explain it all
Sent from my PG86100 using Tapatalk
Just as title of post says.... I'm in need of a stock rooted copy of 2.17.651.5. The only place I found it has a broken link. Thanks in advance!
whoshodade said:
Just as title of post says.... I'm in need of a stock rooted copy of 2.17.651.5. The only place I found it has a broken link. Thanks in advance!
Click to expand...
Click to collapse
Shooter_S_Sprint_WWE_2.17.651.5_deodex.zip
http://dev-host.org/hqkar642vqrn
Shooter_S_Sprint_WWE_2.17.651.5_odex.zip
http://dev-host.org/60nw6kjevvto
BOOKMARK ME!
thank you sir!
eXplicit815 said:
Shooter_S_Sprint_WWE_2.17.651.5_deodex.zip
http://dev-host.org/hqkar642vqrn
Shooter_S_Sprint_WWE_2.17.651.5_odex.zip
http://dev-host.org/60nw6kjevvto
BOOKMARK ME!
Click to expand...
Click to collapse
What's the difference between deodex and odex?
Thanks
Sent from my A500 using xda premium
ahernandez4110 said:
What's the difference between deodex and odex?
Thanks
Sent from my A500 using xda premium
Click to expand...
Click to collapse
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. Deodexing will create longer boot times, but should be equal after that and it gives you the ability to make changes otherwise impossible to do.
Odexed roms are smaller, and have a faster boot time. The only problem with them is they're harder to theme / mod. De-odexed roms are slightly larger, and boot slower, but you cam mod the crap put of em. Just about all themed roms are deodexed. But not all. We're starting to see some odexed roms with themeing included. Not really sure how this is accomplished, but I'm still learning the ropes of modding.
Sent from my PG86100 using xda premium
brandonmaze 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. Deodexing will create longer boot times, but should be equal after that and it gives you the ability to make changes otherwise impossible to do.
Odexed roms are smaller, and have a faster boot time. The only problem with them is they're harder to theme / mod. De-odexed roms are slightly larger, and boot slower, but you cam mod the crap put of em. Just about all themed roms are deodexed. But not all. We're starting to see some odexed roms with themeing included. Not really sure how this is accomplished, but I'm still learning the ropes of modding.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Igotthis from another site but I couldn't put the url in my post since I'm new here
Sent from my PG86100 using xda premium
hi im currently in process of porting a stock deodexed rom.
i have changed system files and the update script.for out i9305. at moment i am able to install the rom fine and loads up with or without wipe. i also included the ee modem.
my issue is that when the rom starts all is ok and there are no force closes however i get no network and imei shows null. to resolve this i just flash param.tar in odin and stock file and all is back to original with imei restored.
any ideas on whats causing the loss of imei number
in setting imei and baseband showbas unknown
edit whilst restoring to stock i did not have to restore imei backups so am asuming efs part is fine
Sent from my GT-I9305 using Tapatalk 2
Check 9500 partition layout and update install script. Dont rewrite the efn part.
Sent from my GT-I9305 using xda app-developers app
have done that part rom installs fine baseband is unknown
Sent from my GT-I9305 using Tapatalk 2
I think u need to Flash a baseband from our i9305 after flashing The Potter rom
but wouldnt that be the modem file iv tried flashing it on radio partition
Sent from my GT-I9305 using Tapatalk 2
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
i am really into this thread. I opened a thread similar at the beginning but they moved it, hope this one stays in here otherwise it will get lost in the i9300 section...... this is really good lets all try get into this, like i said I am going to play around on monday when i return home, so far we got everything going exceept the Modem is not connecting to the Imei correctly, We need an experienced dev.
---------- Post added at 09:25 AM ---------- Previous post was at 09:14 AM ----------
Just think how many roms we can have if we get this going
Sent from my GT-I9305 using xda app-developers app
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
going to check ril today see if that sorts it
Sent from my GT-I9305 using Tapatalk 2
Great thread, wish I could contribute more.
At the moment I'm hanging to see what the more clued up guys around here work out!
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
chwads2k8 said:
right iv ported wanam lite rom to our device, the aroma works i boot up fine but baseband still unknown so annoyin
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Basically there are some intensely different changes within the services.jar, framework.jar, android-policy.jar and so forth. 4G LTE is sooo much different than the stock i9300. I am not saying it CAN'T be done. But I am saying it is going to be a complete bastard to do. Put it this way, you'd be better off looking into all of the modifications that have been done to create these ROMS and re-doing them to the i9305.
Trust me, I have looked into doing this with a "customised" build to from sources for ICS for the P7320T tablet that I had. It is the only 4G tablet released here in Australia. The closest I could find in sources for being able to make the connection was grabbing settings systemUI and the others I have listed above ^^^ from the S2 4G LTE. Then I was going to have to modify the systemUI specifically for tablet mode.
I no longer have the tablet nor the patience to want to take on anything like it again.
All I can say is good luck. Feel free to check my threads to confirm that my choices are not a conflict of motivation or lack of determination...god I can assure you that much
Just for a tip. I started today with decompiling the android-policy.jar file to see if I could enable the torch app double click home from lock screen feature....this has been done on i9300 right? Go take a look at the full guide on how to do it...go decompile 1 file that I am talking about and you will see just how different the methods are in all of the smali code. JOY!
---------- Post added at 03:34 AM ---------- Previous post was at 03:23 AM ----------
chwads2k8 said:
added the ril files and qualcom ril files but basebands the same
also the serail number has changed on device tried reflashing modem but doesnt help
Click to expand...
Click to collapse
What tools are you using to "port" this ROM to our device?
I have tools that can port ROMs in about 30-40min.
What have you got in the build.prop for this thing? Do you want to upload the ROM for me to take a look at? The least I could do is offer some help before raining on your parade lol.
Have you considered doing maybe a "splice" of the ROM. Rather than porting the full version, you could do a diff/compare of the modded ROM against it's stock counterpart. Then you migrate those changes over to your "stock i9305" base. That is going to be your best chance of doing this I reckon? also you won't be able to copy across the firmware version. That won't work. Your framework and the firmware version are going to be device specific.
The absolute best thing I can think of suggesting is to go with a known base equivilant?? Like it seems that there is a release of XXALI5 (for touchwiz at least?) on both devices. That would be where I would start first and foremost. I would port with that common version using what I described above and then migrating any further or additional functionality (developer made i.e. Wanams mods) that have been done since the XXALI5 release.
That is going to be your best bet.
Or you guys could just wait for me to release my ROM haha...subtle promotion? I think not.
btemtd said:
Try merging our system and framework so it picks it up as our xxali5 or xxali9 you have to get rid of there base and put our base instead but leave the edited files so maybe the system apps folder stays the i9300 as the apps are the same i think but change the rest into our firmware hmmmm so maybe a better idea would be to have a blank deodexed and zipaligned xxali5 rom move and overwrite our files with the edited files of the i9300 that way all our efs and imei doesnt get touched
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Exactly
I have a methodology that does this very easy. I wanted the OP to upload his work so far to save me a download. But I might just go ahead and do it anyway.
Have you guys got permissions from Wanam to use his work? I will ask on your behalf if not. He is a great contributor to this forum, I don't wish to have him offside.
What I mean is that I will go ahead and play, but I won't re-upload any test files to the forum without his consent This shouldn't be too hard
---------- Post added at 12:40 PM ---------- Previous post was at 11:53 AM ----------
Contacted Wanam. I will wait to see what he says and recommends. I have claimed I am not releasing anything of his, so this can be owned by you guys who want it. I am happy to help get the ball rolling to help yous though. I have my own dev team that I work with so that makes me kinda busy. That is why I haven't released my own ROM on here yet lol
Downloaded XXLAI5 Wanam, Downloaded XXLAI5 stock i9300, have already downloaded XXLAI5 stock i9305 and I am currently deodexeding it as we speak.
Will deodex i9300 XXALI5 next and then do a comparison to Wanams. Segregate changed files - > port to stock deodexed base = Wanam i9305 for you guys
That's if Wanam approves of course?
EDIT: Hey Mr OP can you please contact me? I cannot send you PMs? Holy smokes you've been around this place since 09!
Ok Analysis done on Wanam compared to stock XXALI5 and have all the of the files seperated and within their directory structure that had changes.
There is going to be some work needed to be done on these main files:
/system/framework/android.policy.jar
/system/framework/framework2.jar
/system/framework/services.jar
/system/app/systemUI.apk
As I expected
Now the fun n games start I will decompile all of these files and then diff them against the standard i9300 smali coding and then *attempt* (and I say that with all great intension too) to migrate the changes across into decompiled i9305 files.
I can tell this is going to be a head ache!
Otherwise though....I can honestly say that what I have got so far I know for certain will boot and you will not have baseband issues. You won't however have 15 toggle mod as it stands. Services.jar and Android policy.jar both control this feature. I see that this *IS* available as a mod already on this forum but I am not certain that the creators realise that these modifications (mentioned here) actually do need to be performed.
Lidroid-res.apk within framework will have no rights to control the toggle on the systemUI cause it won't have permissions due to conflicting signature checking. note...toggles may appear, but they won't do anything when you touch the widget toggle, it will be non-responsive.
Thanks guys
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
btemtd said:
Thats what i said we should just try copying over the whole system app folder and replacing it with our deodexed rom. Try doing that as the firstt step
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
System app is fine, but that isn't where the changes are that make Wanams ROM. You'd have your self a standard ROM otherwise. As in no difference. Or if you just copied the system/app folder ROM would boot but systemUI would force close. You would also have no reboot menu and no USB read from the phone. That would equal disasterous....cause as we all know we don't have SD mount in recovery do we?
Fancy doing an adb push on a phone that doesn't install USB connection files?
See I wouldn't be stupid enough to do that without having at least a clockwork recovery backup lol.
It's ok. for the android.policy.jar they are identical (well for XXALI5 they are anyway) to the i9300. So simple trade in there.
Only 4 more files to go and I will have you guys a port
Wanam still has not contacted me back yet though so I we need approval before anything.
Reset scrolling caches. In framework2.jar
This took a bit of work because my notepad++ kept crashing running compare. If you guys ever have this issue, right click the executable in program files go to properties and compatibility and then check the boxes for:
- disable visual themes
- disable desktop composition
- disable high dpi scaling.
Apply.
No more crashing. Windows 7 aero apparently doesn't like the compare dll?
Anyway not related. I am back on track. last jar file and then it should be ready to package up and it will be the same as Wanam ROM XXALI5
Got approval from Wanam. Just about to test flash now. Will upload it here if everything works out
Well, I had a few mishaps with my own device. Namely no root access and also lost hardware ID...meaning no Android Market. This all happened sometime during my lengthy list of modifications so I was not sure where. That mean flash back to stock and restore my data bit by bit until I was set up again. This take for EVER!
So yeah no real feedback from anyone in here so have decided to finish off my own ROM instead. XXALI9 (newer) and a heap more mods than stock Wanam. So far so good.
I can upload what work I did on getting Wanam's up and running (I have not flashed it yet) but will wait till someone actually wants before I go ahead and do that.
Thanks guys
James
First, thanks to tommytomatoe for creating the awesome dexo script! I have only automated the process. For more info on the dexo script check TT's thread here.
Also, thanks to volk9029 for all the ROM testing, he tested a majority of the ROMs.
In theory, this script will re-odex any completely deodexed ROM, BUT it depends on the modifications the dev has done to their ROM. ie..if framework.jar is missing "preloaded-classes", the script will abort. preloaded-classes is needed for odex ROMs to boot.
Each of the ROMs listed below as "incompatible" have "preloaded-classes" missing from /system/framework/framework.jar. Each of these ROMs would be compatible if framework.jar is modded correctly. For more info see post # 8
Requirements:
-You need to have the HTC usb drivers installed. If you have HTC Sync installed, you're good to go.
-You need to have usb debugging enabled on your phone. Settings, Dev options, usb debugging.
-I recommend doing a backup before running this script (just in case)
Install:
-Extract zip to pc
-Phone must be booted
-connect phone to pc
-run "Odex my ROM.bat"
The script only takes a few minutes, your phone will appear frozen during the process. When the script is done, your phone will reboot.
DOWNLOAD
Compatible ROMs:
-OMJ's
-Superjelly
-meanbean 3.01
-Viper's ROM 3.10
-Hatka LTE ROM
-Digital Bath ROM
-Micromax A75
-Red Line ROM by billbowers
Incompatible ROMs:
-Flex's Stock w/ Goodies
-Tranquility ROM
-Timberwolf671 ROM
These are the only ROMs tested, if you use this script on another ROM, please post your results & I'll update the list.
reserved
Thanks for sharing man!!!!!
Sent from my EVO using xda premium
Awesome job. Thank you.
Sent from my lair.
Thanks so much for this. I just odexed the new HatkaLTE ROM and it's running great! I had read TT's thread but was a little intimidated by it. Great job automating this!
This works perfect! Thanks
This its awesome. Great idea. I knew tommy had made the script, and now you have automated it. Nice work from both of you. Thanks. Any reversal method being designed yet? I suppose do a nandroid before using the script would be best.
Sent from my EVO using xda app-developers app
some good info from TT about the preloaded-classes issue...
tommytomatoe said:
Good stuff To bring a little more clarification as to why those rams are in the incompatible list.
"Preloaded-classes gets accidentally compiled into classes.dex by sloppy devs
Framework.jar should only be modified using baksmali and smali, never apktool or any other tool.
The bad framework.jar, its classes.dex contains the code and instructions for preloaded-classes already. So when you odex, framework.odex contains preloaded-classes and classes.dex codes - which causes the system not to boot. Odex files should only contain classes.dex code.
How to resolve? Take a fresh framework.jar and baksmali it. Edit it. Then smali. This will ensure preloaded-classes were untouched, as baksmali is smart enough to leave it alone.
Another alternative is to pull classes.dex from fresh framework.jar and baksmali it. Smali when finished and insert back into jar file.
Then, when you odex, framework.jar will contain only preloaded-classes and framework.odex is the optimized classes.dex. "
Of course, autogeeks suggestion works but that is not ideal for the obvious reasons. Mods done to framework.jar would no longer be available, all dependencies on those mods would of course be broken.
...then again, I haven't touched android in a long long time. What do I know
Click to expand...
Click to collapse
Thanks bro.
TT is the man too.
Just executed this script. Flawless. Thank you
Sent from my EVO using xda app-developers app
Thanks for this Script i made my ROM Odexed but few of my app are not working properly may be the problem of the app as there are only few apps like Root Browser opening but not working properly giving forceclose after few clicks when i try to open system it just doesnt open and when i close the app and again try to open system it opens and when i click on app it gives forceclose, Zeam Launcher not showing dock but other then this all are working fine so thanks for the script will try to change the apps which are not working and then check if i still get the problem i think i wont and now i think that i can release my first custom ROM as i was waiting for this Odex script so that i can release the first ROM of mine in Odex version although its a ROM from another developer but i moded it and made compatible with my device thats MICROMAX A75 so will test it fully and once confirmed everything working perfectly then will release it so just wanted to know if i can release the ROM with Odexed version made by your script i will add proper credits in the credit section if you permit me to go ahead. will be waiting for your permission. Once again thanks for your script yaar its just awesome.
shahabazas said:
Thanks for this Script i made my ROM Odexed but few of my app are not working properly may be the problem of the app as there are only few apps like Root Browser opening but not working properly giving forceclose after few clicks when i try to open system it just doesnt open and when i close the app and again try to open system it opens and when i click on app it gives forceclose, Zeam Launcher not showing dock but other then this all are working fine so thanks for the script will try to change the apps which are not working and then check if i still get the problem i think i wont and now i think that i can release my first custom ROM as i was waiting for this Odex script so that i can release the first ROM of mine in Odex version although its a ROM from another developer but i moded it and made compatible with my device thats MICROMAX A75 so will test it fully and once confirmed everything working perfectly then will release it so just wanted to know if i can release the ROM with Odexed version made by your script i will add proper credits in the credit section if you permit me to go ahead. will be waiting for your permission. Once again thanks for your script yaar its just awesome.
Click to expand...
Click to collapse
no permission needed, anyone is free is use this script for whatever.....
"Odex any ROM"
"List of incompatible ROMs:"
Lol ^ made me laugh
Hey u can add Micromax A75 in the compatible list as i have tried this script on it and its working totally fine no problem at all.
Thanks for this amazing script yaar i was looking for it since past 6months.
shahabazas said:
Hey u can add Micromax A75 in the compatible list as i have tried this script on it and its working totally fine no problem at all.
Thanks for this amazing script yaar i was looking for it since past 6months.
Click to expand...
Click to collapse
Whats wrong with using titanium backup to odex?
youdug said:
Whats wrong with using titanium backup to odex?
Click to expand...
Click to collapse
As titanium backup doesnt odex the framework folder it only odex the apps folder.
shahabazas said:
As titanium backup doesnt odex the framework folder it only odex the apps folder.
Click to expand...
Click to collapse
Did not know that. Never checked. +1 to you sir.
Does this work on aosp rom? I see the list of compatible and incompatible ROMs. Just didn't see if it says sense only. Thanks
I would actually assume not. But i had to ask to see if ianyone has tried
Sent from my Nexus 7 using xda app-developers app
treIII said:
Does this work on aosp rom? I see the list of compatible and incompatible ROMs. Just didn't see if it says sense only. Thanks
I would actually assume not. But i had to ask to see if ianyone has tried
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure.....all the script does is odex all the deodexed apks in /system/app & /system/framework, and this script is not specific to HTC....you could be the guinea pig
do a full backup & give it a try! worst case u restore your backup
O.M.J said:
I'm not sure.....all the script does is odex all the deodexed apks in /system/app & /system/framework, and this script is not specific to HTC....you could be the guinea pig
do a full backup & give it a try! worst case u restore your backup
Click to expand...
Click to collapse
Right now. Report back in a few
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 10:08 AM ---------- Previous post was at 09:49 AM ----------
treIII said:
Right now. Report back in a few
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried. USB debugging enabled. Computer noticed phone immediately and HTC sync popped up so that didnt seem to be the problem. When i tried the odex my rom bat script and it says press any key to continue nothing happened other than the cursor in the command prompt dropping down a line.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 10:13 AM ---------- Previous post was at 10:08 AM ----------
I just used titanium backup to odex system apps. It had no problem doing that. I know that doesn't involve framework though. If you have any suggestions on anything i might try to get the script to work let me know
Sent from my Nexus 7 using xda app-developers app
I've read into the subject of Deodex vs Odex many times before, so I know general differences as well as supposed advantages/disadvantages to both. So my question is this, besides the general ability to theme every aspect of a ROM, what other major uses are there for Deodexing a touchwiz based ROM? I know that some mods require you to be deodexed, which isn't a big deal to me because all of the mods I flash regularly do not require that. Hopefully someone knowledgeable in this area can clarify for me:good:
There aren't any besides modding.
Sent from my SGH-I717R using xda premium
like agoattamer said only use for a deodex rom is to theme it. if you like the themeing of deodex but want speed and smaller file size of odex you can set up your deodexed rom with all changes you want made to it and then run the script found here( http://forum.xda-developers.com/showthread.php?p=44228706 ) to reodex the rom. you can also odex apks in data/app. just keep in mind that not all downloaded apps like to be odexed but most will not give issue. i think only apps i had to reinstall to get back to deodex was amazon app store and a game downloaded from amazon
Agoattamer said:
There aren't any besides modding.
Sent from my SGH-I717R using xda premium
Click to expand...
Click to collapse
s89281b said:
like agoattamer said only use for a deodex rom is to theme it. if you like the themeing of deodex but want speed and smaller file size of odex you can set up your deodexed rom with all changes you want made to it and then run the script found here( http://forum.xda-developers.com/showthread.php?p=44228706 ) to reodex the rom. you can also odex apks in data/app. just keep in mind that not all downloaded apps like to be odexed but most will not give issue. i think only apps i had to reinstall to get back to deodex was amazon app store and a game downloaded from amazon
Click to expand...
Click to collapse
Thanks to both of you. You confirmed what I thought originally. And thanks s89281b, I actually have that script already and use it on all of my ROMS except the touchwiz ones. So now that my question is confirmed, I'll use this on touchwiz ROMS as well. I have tried digging into theming a little, but I'm putting that on pause so no need for deodex atm
Sent from my SAMSUNG-SGH-I717 using Tapatalk HD