Database Users

NO LONGER ACTIVE PLEASE CLOSE [devs] deodex version of ivanmmj Eris_Official 1.0

All,
per positive response below is a link to a copy of ivanmmj Eris_Official 1.0 ROM that I have fully deodexed. This is more meant for devs for continued play time, but it is a flashable ROM. PLEASE NOTE that ivanmmj himself looks to be coming out with the next version of Eris_Official 1.0 per his thread http://forum.xda-developers.com/showthread.php?t=652044.
Hope this is helpful and Enjoy
Link: REMOVED FROM HOST SERVER
P.S. please let me know of any issues as this is my first full deodex also I would like to encurage using this tread to exploring moding some of the system files on Eris ROM builds as it has been fun to tweak things
P.P.S. If you want the Zanfer kernel let me know and I will look at adding it in however ivanmmj's new version should have it...

what is Deodex?

I'm definitely interested, but I also think Ivan is working on the same project himself. I'm pretty sure his "1.1" is deodexed and has Zanfur's kernel. Not sure what other changes he has in mind, but you might want to check with him before posting since you'll end up being the one getting all the PM's from people wanting help. ;-)

Yes please I'm looking for exactly that
-------------------------------------
Sent via the XDA Tapatalk App

That would be awesome.
Sent from my Eris using XDA App

BTW jcase's plain jane1.0 has zanfur overclocking kernel.....
i dont know what you think but it might be a better platorm than ivanmmjs
a deodexed version of that would be tight....

kernels are easy to compile and swap out, a different kernel isnt going to influence the build at all

i always seem to get better battery life from the non oc'ed kernel.

Morkai Almandragon said:
what is Deodex?
Click to expand...
Click to collapse
Yes, what does that mean ?

hallstevenson said:
Yes, what does that mean ?
Click to expand...
Click to collapse
it means you have a classes.dex file rather than a .odex file
it makes things easier, its also possible to metamorph these builds and its possible to install a deoexed app on multiple platforms.

anonomouse said:
it means you have a classes.dex file rather than a .odex file
it makes things easier, its also possible to metamorph these builds and its possible to install a deoexed app on multiple platforms.
Click to expand...
Click to collapse
Means I can finally modify Rosie.apk to my liking.

hallstevenson said:
Yes, what does that [deodex] mean ?
Click to expand...
Click to collapse
A more experienced developer can add more but a few quick basics:
.odex files are precompiled class flies that correlate to a .apk or .jar file. In an odex ROM an .apk/.jar file will not function without it's correlated .odex.
a deodex build takes all of the .odex files converts them to a classes.dex and puts them into the .apk or .jar file package
deodex ROM are easier to mod because each .apk or .jar is a "complete" package and can be more easily decompiled and ported (i.e. you do not have to worry about the .odex files)
A deodexed build requires less space in /system, but more space in /data
A deodexed build requires a longer initial boot because they must regenerating those odex files from the dex files in the .apks/.jars and save them to /data/dalvik-cache
Thats a quick list of what I know

odex only help speed up app loading time and first time boot. Think of this as Windows' prefetch.
If you want to re-create odex for apk for porting, etc... I suggest only do this to /system/app not /data/app because when you do update from market and your app will break, unless you wipe out dalvik-cache.

zach.xtr said:
This is more meant for devs for continued play time, but it is a flashable ROM.
Click to expand...
Click to collapse
Would this be ok for an every day ROM? Or should it just be used by dev's as a base ROM?

Hey guys I've been testing this for Ivan. same thing he has a version deodexed.
I edited this
http://forum.xda-developers.com/showthread.php?t=664951
to work for this rom. which works great, but I get an error of
com.htc.bgp because of it, does anyone have any idea why?

Romparoo said:
Would this be ok for an every day ROM? Or should it just be used by dev's as a base ROM?
Click to expand...
Click to collapse
Technically it is fine as an everyday ROM, however I do not recomend using it for such because it is not support and will have no additional features over ivanmmj origional 1.0.
So I guess, yes it meant to be used as a base ROM or "spare parts" for devs.

BlazeD OnE said:
Hey guys I've been testing this for Ivan. same thing he has a version deodexed.
I edited this
http://forum.xda-developers.com/showthread.php?t=664951
to work for this rom. which works great, but I get an error of
com.htc.bgp because of it, does anyone have any idea why?
Click to expand...
Click to collapse
Someone else did this, on androidforums.com. I haven't replied to his posting, but it's in like page 19 of the 'show off your UI layout' thread there. I'm working on a modified Rosie.apk right now, as soon as I get this de-odex'd Ivan's on my phone running. Titanium backup here I come.

FYI, I was able to flash the deodexed version over the original Eris_Official 1.0 Alpha without having to do a full wipe (just wiped dalvik-cache). Naturally, I went back and re-flashed Zanfur's overclock kernel after that.

Adding FriendStream to a Custom ROM ?

Can anybody help me in adding Friendstream to a Custom ROM, which doesn't has FriendStream

can you not just find the App and add it after installing your Rom??

will not work!

Short answer: it's likely not going to be easy
A few days ago I found a detailed guide about porting HTC apps to non htc-ROMS. It was a ****load of work, but doable I guess. In the example he ported an htc app (music player?), by using nice constructions with opening and resigning apk's, pulling necessary parts of the htc.framework and more "mojo jojo".
Problem is: I really can't find the guide anymore, and I have been testing that search function for way to long....
So is there anybody that remembers where I am referring to perhaps?

I tried pushing the .apk's to /system/app/ I knew this wouldn't do, But still gave it a try
EDIT : Maybe a Dev would be able to help us out, Please Any Dev

It *could* work for a deodexed rom... so try asking your rom dev to deodex it and give it a try which rom are we talking about?

killer4o said:
It *could* work for a deodexed rom... so try asking your rom dev to deodex it and give it a try which rom are we talking about?
Click to expand...
Click to collapse
MCR r5, But I have tried pushing the .apk's but still it doesn't work, I have tried this on both deodex and odex ROM's.

Tried to add "FriendStream.apk" and "com.htc.FriendStreamWidget.apk"
to a custom ROM and sign the ROM again,but don`t works,too!

How to deodex a ROM?

I'm planning to create my own custom rom based on 2.1. I have tried the Android Kitchen but have had no luck, I get lots of errors about java exceptions, etc. Please could anyone tell me a WORKING way to deodex the stock rom.

JackG256 said:
I'm planning to create my own custom rom based on 2.1. I have tried the Android Kitchen but have had no luck, I get lots of errors about java exceptions, etc. Please could anyone tell me a WORKING way to deodex the stock rom.
Click to expand...
Click to collapse
Try wait some time... kitchen try use old smali version and deodex rom correctly
or
Try xUltimate deodexer (find in google )

JackG256 said:
I'm planning to create my own custom rom based on 2.1. I have tried the Android Kitchen but have had no luck, I get lots of errors about java exceptions, etc. Please could anyone tell me a WORKING way to deodex the stock rom.
Click to expand...
Click to collapse
Why don't you just remove the odexed apps? It's easier than deodexing.

despotovski01 said:
Why don't you just remove the odexed apps? It's easier than deodexing.
Click to expand...
Click to collapse
So that means removing, Phone.apk, Settings.apk, and pretty much every system app.

Search daneshm90
Mark

I am trying this script but getting bootclasspath errors. If I could retrieve the bootclasspath then i would have no trouble de-odexing. Thanks

[INFO] Note to all ROM makers

There seems to be issues with baksmali/smali v1.2.6 when deodexing latest samsung roms (2.3.4 maybe also some 2.3.3!).
If you baksmali framework.odex and smali it back to a dex file (without changing anything) your ROM will become laggy!
Some people say its the hardware acceleration that no longer works.
The web browser becomes unusable. There have been reports that video player and camera also seems laggy.
My suggestion is NOT to deodex framework.odex! I'm sorry to say this...
I know this means no custom deodexed roms! But I do believe you will run into more problems we don't know about yet!
But you can still do mods!
Just not deodexed framework mods. You can deodex apk files in the app folder. You can also try and deodex files in the framework folder as long and you dont deodex the framework.odex file! But here you have to convert them back to odex files!
As proof I have made this mod for stock XXKG1. I have the odexed the files back to odex using the dexopt-wrapper tool.

It is not just 1.2.6, I have built from the latest source and still has problems.

I disagree 100% fwiw with OP
I have no speed issues beyond that stupid browser, and that looks just like a baksmali bug. I don't do the "quit" attitude - I will fix it...
But anyway, there is no lag or anything here, even on 2.3.4 deodexed and underclocked.
So while there may be a browser issue, I would not suggest to people not to deodex. I can provide thousands of posts of people happy with a properly Deodexed and optimised ROM...

do we know why this happens? Is there an logic explanation

stian230 said:
do we know why this happens? Is there an logic explanation
Click to expand...
Click to collapse
Most likely minor baksmali bug

designgears said:
It is not just 1.2.6, I have built from the latest source and still has problems.
Click to expand...
Click to collapse
Maybe if we can debug using source we can figure out what goes wrong!

pulser_g2 said:
I disagree 100% fwiw with OP
I have no speed issues beyond that stupid browser, and that looks just like a baksmali bug. I don't do the "quit" attitude - I will fix it...
But anyway, there is no lag or anything here, even on 2.3.4 deodexed and underclocked.
So while there may be a browser issue, I would not suggest to people not to deodex. I can provide thousands of posts of people happy with a properly Deodexed and optimised ROM...
Click to expand...
Click to collapse
I hope you are right... But alot people also complains about all sorts of problems with the custom roms... and we dont really know if its related to this or not...

I spent all yesterday thinking about that...
The odex file is only valid when used with the exact BOOTCLASSPATH files. dalvik enforces this by storing a checksum of each file that the odex file is dependent on, and ensuring that the checksum for each file matches when the odex file is loaded.
When you are deodexing an apk, even if you don't need to set BOOTCLASSPATH for it (because you don't get any error msg while baksmali), by default these 5 jar are already included in the classpath: core.jar, ext.jar, framework.jar, android.policy.jar and services.jar. This means that an odex file has dependencies on every "BOOTCLASSPATH" file that is loaded when it is generated.
So i was thinking about to deodexing every apk in /system/app a part Browser.apk (i.e leaving Browser.odex) and try to figure out which jar file inside /system/framework has to remain odexed.
Maybe we can still have overscroll glow mod, renounce to have the extended power menu in order to get an HW accellerated Browser!
I don't know if it make sense for you as my english need to be improved

_JKay_ said:
I hope you are right... But alot people also complains about all sorts of problems with the custom roms... and we dont really know if its related to this or not...
Click to expand...
Click to collapse
You got any examples to hand?
The common issues I see are
- failing to read my install instructions
- trying to come from some other ROM without following the instructions
- trying to restore titanium backups entirely, depositing apps that are codes like half-polished turds in the phone
- pushing incorrect files into rom without knowing what they are doing
- stupid setcpu config
Am interested to see if you have found other issues, as camera and video player are confirmed by a fair number to be fine...
I swapped my phone with one running stock, and I had to tell my friend what I had done, as he was sure it was his oh, and I was underclocked to 800 max too at the time

pulser_g2 said:
You got any examples to hand?
The common issues I see are
- failing to read my install instructions
- trying to come from some other ROM without following the instructions
- trying to restore titanium backups entirely, depositing apps that are codes like half-polished turds in the phone
- pushing incorrect files into rom without knowing what they are doing
- stupid setcpu config
Am interested to see if you have found other issues, as camera and video player are confirmed by a fair number to be fine...
I swapped my phone with one running stock, and I had to tell my friend what I had done, as he was sure it was his oh, and I was underclocked to 800 max too at the time
Click to expand...
Click to collapse
The frameword.odex is not compiled correctly!! That's a fact!! The laggy browser proofs it. Framework.odex the largest most important file in the android framework!! And that does not concern you? Is that not a bit naive?

_JKay_ said:
The frameword.odex is not compiled correctly!! That's a fact!! The laggy browser proofs it. Framework.odex the largest most important file in the android framework!! And that does not concern you? Is that not a bit naive?
Click to expand...
Click to collapse
I believe what I see. I have asked HomerSp if he can take a look at it, when he can, as he knows a lot about the deodexing process.
But at the end of the day, while there is clearly something not working in baksmali or smali, this seems a good opportunity to fix it and pass on the fix to JF
I know what is in framework.jar, and that it covers most things...
I do genuinely have interest in seeing the issues you raised, as perhaps there is disparity between methods of deodexing??? I am interested to see if I can reproduce any here too, as that would highlight a wider issue.

pulser_g2 said:
I believe what I see. I have asked HomerSp if he can take a look at it, when he can, as he knows a lot about the deodexing process.
But at the end of the day, while there is clearly something not working in baksmali or smali, this seems a good opportunity to fix it and pass on the fix to JF
I know what is in framework.jar, and that it covers most things...
I do genuinely have interest in seeing the issues you raised, as perhaps there is disparity between methods of deodexing??? I am interested to see if I can reproduce any here too, as that would highlight a wider issue.
Click to expand...
Click to collapse
Well.... I will not use deodexed custom roms so I won't find any issues!!! But some people probably will or already has...
I'd rather spend my time on fixing this and create odexed mods until its fixed!
As soon as I see that the framework.odex can be compiled without breaking the browser... I might try some custom roms again..

That's weird. I'm using Lite'ning 1,5 ROM (which is deodexed) since i bought this phone and everything runs very smooth (including browser, video playback, gaming, launcher and so on). Before i had HTC Desire Z with CM7 on it and it was freezing slow if compared to my current setup. It's just flying.

AllWin said:
That's weird. I'm using Lite'ning 1,5 ROM (which is deodexed) since i bought this phone and everything runs very smooth (including browser, video playback, gaming, launcher and so on). Before i had HTC Desire Z with CM7 on it and it was freezing slow if compared to my current setup. It's just flying.
Click to expand...
Click to collapse
I know that version (2.2) does not include the original stock browser but a patched version.
Sent from my GT-I9100 using XDA Premium App

_JKay_ said:
I know that version (2.2) does not include the original stock browser but a patched version.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
You're basing all your points on 1 main problem, the browser.
That's hardly the way to go. Rather, they will work to solving the problem regarding the browser, then we can continue to have proper custom roms. Besides, KG1 is a leaked rom. Deodexing didn't affect KF2, it might not cause problems for later leaked or "official" roms.
Rather than directing others to your odexed mods, the way for things to move on is to see the problem being fixed. There's a reason why custom roms are almost always deodexed. Don't rock the boat if you don't like the status quo.

kenkiller said:
You're basing all your points on 1 main problem, the browser.
That's hardly the way to go. Rather, they will work to solving the problem regarding the browser, then we can continue to have proper custom roms. Besides, KG1 is a leaked rom. Deodexing didn't affect KF2, it might not cause problems for later leaked or "official" roms.
Rather than directing others to your odexed mods, the way for things to move on is to see the problem being fixed. There's a reason why custom roms are almost always deodexed. Don't rock the boat if you don't like the status quo.
Click to expand...
Click to collapse
That's actually exactly what I am saying!! Don't spend time on fixing the browser! Spend time on fixing the baksmali/smali tools!!
But until that's fixed I believe you can't really rely on the deodexed roms because framework.odex does not compile correctly!!
Some people said that you can't do mods that are odexed!! Thats the reason for the example! You actually don't need to deodex the framework!! But I admit.. it's easier not to odex files...

BTW guys, following the OP IDEA i got my own custom rom working with the odexed stock Browser (i.e. HW accellerated).
Basically all the apps have been deodexed apart Browser, and i left the framework jar files odexed!
Basically i got the same features/mod as before, the only think i have to renounce is the overscroll glow effect (i don't like it at all, i prefer the stock Samsung bounce effect) and the extended power menu (we can easily replace it by using quickboot).
That's it
thanks _JKay_ for the IDEA!

But I do think the problems wont fix itself in the future. The SGS facing the same problems with XXJVQ!!

LeoMar75 said:
BTW guys, following the OP IDEA i got my own custom rom working with the odexed stock Browser (i.e. HW accellerated).
Basically all the apps have been deodexed apart Browser, and i left the framework jar files odexed!
Basically i got the same features/mod as before, the only think i have to renounce is the overscroll glow effect (i don't like it at all, i prefer the stock Samsung bounce effect) and the extended power menu (we can easily replace it by using quickboot).
That's it
thanks _JKay_ for the IDEA!
Click to expand...
Click to collapse
No problem! Actually my mod gives you the extended power menu

_JKay_ said:
But I do think the problems wont fix itself in the future. The SGS facing the same problems with XXJVQ!!
Click to expand...
Click to collapse
I agree with you, but at least, since a lot of people complain about the stock browser, we can stay happy with it!
I reckon we need new tool for deodexing, smali backsmali are dated now...

cm7 settings menu

is there any zip out there that can throw this on any aosp rom? if not, would someone like to teach me how to do it?

There wouldn't be any way to do this. There has been some serious modification to the actual framework of Android to get CM Settings working. It isn't something you can just drop into a new ROM. That ROM has to be coded to support all the options in there, otherwise you will probably just end up with a bunch of force closes.

bassmadrigal said:
There wouldn't be any way to do this. There has been some serious modification to the actual framework of Android to get CM Settings working. It isn't something you can just drop into a new ROM. That ROM has to be coded to support all the options in there, otherwise you will probably just end up with a bunch of force closes.
Click to expand...
Click to collapse
okay thanks. i thought i could just pull some files and push them into another rom but if theres coding involved id rather not get into it lol