I attempted to ask a few questions in the Project Odex thread but was promply told to "search for it it is easy to find".... Kind of agrivating when you just got done doing just that, especially considering the title specifically states "for those that want mods"...
Anyhow I was hoping I could bug those that do for some ideas of the mods you use for Odex roms etc, and maybe any warnings about mods that do not work so well.
Morkai Almandragon said:
I attempted to ask a few questions in the Project Odex thread but was promply told to "search for it it is easy to find".... Kind of agrivating when you just got done doing just that, especially considering the title specifically states "for those that want mods"...
Anyhow I was hoping I could bug those that do for some ideas of the mods you use for Odex roms etc, and maybe any warnings about mods that do not work so well.
Click to expand...
Click to collapse
That completely depends on the rom and the mods that you want to change. System mods don't matter on odexed or deodexed. The individual app mods will have to be made for the odexed rom though since they need both jar and apk files to work. Hope this answered your question.
I am just not finding much of anything, some of the basic things I would love to find are something to remove the wifi nag, and something like Wanam xposed that will work on 4.1.2
Related
I just updated my firmware to STOCK 2.2 (KA6) which I downloaded from CHAINFIRE's thread. Now I rooted my phone and its working fine for me.
Than I see another post for Deodexed KA6 from Whitehawkx. what is that. that also says original stock. am confused now.
can any one please explain me difference between both stock & Odex & deodex things.
Also how to flash this Deodexed KA6 (same as ODIn or any other method).
I was wondering the same thing....so i googled it...
Sent from my SGH-T959 using XDA App
This maybe inaccurate but I have a reasonable idea of what it is... it's just hard to explain.
If you look in the system/app and system/framework you will see the filename.apk along with it's counterpart filename.odex. With a deodexed rom it places the filename.odex and converts it to filename.dex (not odex) and places it within filename.apk. But most importantly the framework MUST support the deodexed files! If the framework is looking for filename.odex files that aren't there you will end up in a bootloop. It just won't work. But the benifits of having deodexed files is that it's easier to theme and replace. In some cases you can take a app.apk and replace it with differentappfromdifferentrom.apk. When you have a odexed rom you just can't do that.
You will notice that many themes and modifcations will not include support for odex roms so having a deodexed rom is definitly the way to go!
Some people have argued that having an odexed rom causes your device to perform better! But I have never noticed any difference personally and frankly I'm skeptical. Tasters choice.
I googled it as well. Here was one of the better hits....
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Binary100100 said:
This maybe inaccurate but I have a reasonable idea of what it is... it's just hard to explain.
If you look in the system/app and system/framework you will see the filename.apk along with it's counterpart filename.odex. With a deodexed rom it places the filename.odex and converts it to filename.dex (not odex) and places it within filename.apk. But most importantly the framework MUST support the deodexed files! If the framework is looking for filename.odex files that aren't there you will end up in a bootloop. It just won't work. But the benifits of having deodexed files is that it's easier to theme and replace. In some cases you can take a app.apk and replace it with differentappfromdifferentrom.apk. When you have a odexed rom you just can't do that.
You will notice that many themes and modifcations will not include support for odex roms so having a deodexed rom is definitly the way to go!
Some people have argued that having an odexed rom causes your device to perform better! But I have never noticed any difference personally and frankly I'm skeptical. Tasters choice.
Click to expand...
Click to collapse
Good explanation, thanks.
shrapnelx said:
I googled it as well. Here was one of the better hits....
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Click to expand...
Click to collapse
oooohhhhhhhhhhhh! thx now I know and knowing is half the battle GI JOE... GO COBRA!
My head is bleeding inside from all the reading and searching. I still consider myself a green when it comes to the makeup of android. I am a 40+ windows hacker who is not afraid to take a stab at anything. But I really need a few pointers here.
I am a stock ROM bare bone junkie. I like them clean with just a touch of modding for flare. And Electron, BigFau, and Flapjaxxx has already conquered the UCLF6 ROM. High Five for you 3. :highfive: Since nobody is thinking outside of ATT, I wanted to get a zipaligned, deodexed Rogers UXLF4 version going. It seems to have less bloat to start, has less restrictions (ex: hotspot activated even when using on ATT), and has features such as being able to select Network Mode (Ex: GSM only, HSPA only, GSM/HSPA, or LTE/GSM/HSPA) which the ATT ROM does not. What I have to start is a combine tar file. It includes amss.bin, boot.img, cache.img.ext4, mdm.bin, recovery.img, and system.img.ext4.
I finally ended up creating a version with Dsixda kitchen. Haven't installed it yet, but I am about to. Is the Dsixda a good way to start for a newb like me? Or should I be looking at xUltimate instead?
2 things right off the top that has me betwiddled is how to add the radio to the ROM with Dsixda. Seems everyone else has the AMSS and MDM in a tmp folder and these lines in the updater-script:
package_extract_dir("tmp", "/tmp");
run_program("/sbin/dd", "if=/tmp/mdm.bin", "of=/dev/block/mmcblk0p17");
run_program("/sbin/dd", "if=/tmp/amss.bin", "of=/dev/block/mmcblk0p13");
Is it as simple as that? Now take it easy guys on the answer.......
And the other is everyone's updater-script is similiar to each other, but way different than the one created with dsixda. Almost from the same template. So I know these weren't created completely from scratch. Almost leads me to believe that everyone is using different software/kitchen.
So how bout a firm but gentle kick in the right direction?
Nobody has anything to say??
You would be better off posting in the dev's section.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
wish I could help brother..... but if your green, I'm glow in the dark neon green!!
I would ask a dev direct...
Bold yes, but if done politely, the are very helpful...
I wish you good luck sir!!!.....g
P.s......I'll test for you if you need them.....g
True
I was thinking the same thing, maybe ask a dev. I am sure that some might be more than willing to help/share their knowledge ?
Some list an IRC so you can chat. Its a little easier to troubleshoot code in a chat sesh rather than passing PM's back and forth.
It would'nt have to be a note dev.
curious did anythign come of this... i am interested in a rogers ics based rom myself
Did you receive any help yet ? I'm not a devloper, but I will try and help you.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
No sir, or should I say BigSir, I received no help yet. First post pretty much says it all. Every ROM I checked out on here has the same updater script. I used Dsixda kitchen and mine was not the same. Plus after reading almost every page in the kitchen thread I saw no way to add the modem. Was going to hack away at it this weekend again. Would really like to get this stock ROM going for everyone and to give something back to XDA. I just need some pointers.
Agoattamer said:
No sir, or should I say BigSir, I received no help yet. First post pretty much says it all. Every ROM I checked out on here has the same updater script. I used Dsixda kitchen and mine was not the same. Plus after reading almost every page in the kitchen thread I saw no way to add the modem. Was going to hack away at it this weekend again. Would really like to get this stock ROM going for everyone and to give something back to XDA. I just need some pointers.
Click to expand...
Click to collapse
Start off with xUltimate. I have used it in the past and it's pretty decent for a beginner or novice. Whatever. Lol. Honestly if you just need the updater-script,you could use the updater-script from another rom. Just make the appropriate changes.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I will give xUltimate a try. Just seemed all ROMs had almost the same updater script and were much bigger than the 1 had created. I wouldn't know what to use from another updater script. I am totally a newb here.
Will xUltimate create a CWM install file? Doesn't that just deodex an installed odex ROM?
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
I have a new Samsung Galaxy device and the 15 step volume for music is driving me nuts. 15 is not enough choices for volume level.
I have tried 30/45 step volume mod for xposed framework and it does not seem to work correctly on TouchWiz roms.
Can someone please explain to me a simple way to deodex the framework on my stock Touchwiz rom and odex it back.
I know how to get the framework off the device and how to put it back. I also know how to edit it with notepad++
Better yet can someone please explain how to modify framework to properly increase volume steps on Touch wiz roms????
Same question here. But for me i think we cannot change it. Until we use other phone like HTC... Samsung volume is 15 for every phone. So i think we cannot change it.
Sent from my GT-S7270 using xda app-developers app
Davin093 said:
Same question here. But for me i think we cannot change it. Until we use other phone like HTC... Samsung volume is 15 for every phone. So i think we cannot change it.
Sent from my GT-S7270 using xda app-developers app
Click to expand...
Click to collapse
That's right, we cannot change it.....until we know how that is. Anything can be done. It is just a matter of figuring out how. This is how people become developers.
I was able to deodex the framework.jar and have a look at the Audioservice.smali in my TW firmware. The parameters relating to volume steps in the file are different than those in the AOSP framework which explains why the xposed step mod does not work correctly.
I know what to change to creat the desired steps. However my only problem is re-compiling the edited framework into either a .jar file or an original .odex in such a way that it will work on the device. This is supposedly simple however the tutorials online relating to this are very convoluted, make no sense and do not work. Additionally despite having a network of developers across several countries, nobody is interested in replying to my numerous posts regarding this deodexing and re-odexing nightmare.
mdelaney1986 said:
That's right, we cannot change it.....until we know how that is. Anything can be done. It is just a matter of figuring out how. This is how people become developers.
I was able to deodex the framework.jar and have a look at the Audioservice.smali in my TW firmware. The parameters relating to volume steps in the file are different than those in the AOSP framework which explains why the xposed step mod does not work correctly.
I know what to change to creat the desired steps. However my only problem is re-compiling the edited framework into either a .jar file or an original .odex in such a way that it will work on the device. This is supposedly simple however the tutorials online relating to this are very convoluted, make no sense and do not work. Additionally despite having a network of developers across several countries, nobody is interested in replying to my numerous posts regarding this deodexing and re-odexing nightmare.
Click to expand...
Click to collapse
I was able to make the framework.jar changes, but the way I did it I was only able to visually change to 30 steps, after the first 15 the volume would go out of range and mute. Very curious to get this working too.. I imaging we need someone who can edit this in the kernel or deeper in the ROM.
Shame you never got this working. It can't be the kernal as I've used multiple kernals with touchwiz ROMs. Looks like you had a good stab at it though
I figured I would convert this mod to our device using code in the unified thread. (Props to original author and Rompnit).
It took a bit of tweaking to get it to work on the Sprint variant but it seems to be functioning as intended.
This is for Odexed stock(ish) roms only!
It replaces services.jar and build.prop. If you have tweaks to your build prop that you don't want set to defaults then I recommend you install the jar and odex file manually and edit your build.prop with whatever tool you see fit
A lot of mods affect the services.jar as well, noteably the unlock hotspot mod. That's why it's included FREE with this mod.
What a deal!
The changes I made to the build.prop are simply these additions. The rest is stock
#CRT Mod
persist.sys.screen_on=fade
persist.sys.screen_off=crt
These can be changed to set your on/off animation type. Options are CRT/FADE/NONE
Standard Use at Your Own Risk stuff Blah Blah
Enjoy
It's usually better to provide a deodexed copy as odexed relies on the same exact framework that it was odexed with to be present for the files to function at all
On the other hand, deodexed will function on any rom including odexed roms (when yup delete/move the odex files affected)
CNexus said:
It's usually better to provide a deodexed copy as odexed relies on the same exact framework that it was odexed with to be present for the files to function at all
On the other hand, deodexed will function on any rom including odexed roms (when yup delete/move the odex files affected)
Click to expand...
Click to collapse
I provide Odexed mods mainly because nobody else is doing it. And because odexed versions are usually the first thing people ask for, and because deodexing seems to break too many functions I use like private mode and S-Health issues.
I'll post the edited smali if anyone wants to use it for anything.
townsenk said:
I provide Odexed mods mainly because nobody else is doing it. And because odexed versions are usually the first thing people ask for, and because deodexing seems to break too many functions I use like private mode and S-Health issues.
I'll post the edited smali if anyone wants to use it for anything.
Click to expand...
Click to collapse
I wasn't criticizing, merely commenting
CNexus said:
I wasn't criticizing, merely commenting
Click to expand...
Click to collapse
np, It's all good.
Return to Stock
How can I go back to stock? remove the CRT animation and changes you made to Services
ramik911 said:
How can I go back to stock? remove the CRT animation and changes you made to Services
Click to expand...
Click to collapse
Replace the services.jar and services.odex with a stock version and remove the added entry in build.prop
thnx
Is this only for root devices? Are there any CRT mods for none roots? I did a search and so far this is the only thread with CRT.
dwss said:
Is this only for root devices? Are there any CRT mods for none roots? I did a search and so far this is the only thread with CRT.
Click to expand...
Click to collapse
You would need root access to flash the completed product to your device.
What would it take to port the crt mod to moar 7 rom.i had it on stock rom with xposed. I want to get it back without xposed.