I recently bought a Galaxy Mini 2, and the first thing I wanted to do was modding it!
But I couldn't do it on an odexed ROM, currently available ROMs are only the 4.x builds by TheWhisp and some tweaked ones I don't like, and xUltimate throws errors.
Also, the stock ROM contains 100+ packages to deodex, so I couldn't do it by hand quickly.
I wrote this script to do it for me. I'm not really experienced, and I don't know how far this can be from being optimized, clean and readable, but it works, and it should work for any device and ROM if used correctly.
This script deodexes all the apk and jar packages for system apps and framework, then zipaligns them for better memory optimization (memory consumption is a half of what's normally used on stock ROM). After that, it writes an updater-script and packages everything in a shiny flashable zip to use in recovery.
WARNING: Might cause boot-loops or force-closes. It's recommended to check that the cwm_deodex.zip file contains the .apk and .jar files and pick some random APKs and JARs to check that they contain the classes.dex file in their root. The APKs from framework should not contain the classes.dex, while the JARs should. It's also recommended to do a backup before flashing the deodex package, in case the cwm_restore.zip fails.
HOW TO USE:
Extract the attached zip wherever you want.
Pull all the files from /system/app and /system/framework from your phone and put them respectively in the directories"app_odexed", and "framework_odexed" (they're located under the extracted directory).
Check the API level for your device's Android version (if you don't know, check this). In deodex_app.sh and deodex_framework.sh there are four lines (two in deodex_app.sh and two in deodex_framework.sh) which begin in "java -jar baksmali.jar" and "java -jar smali.jar". Those lines contain an option "-a", followed by a number (by default "10"): you should change that number to your API level. If you are on ICS or later, you can just delete the "-a" option and the consecutive number.
Open a terminal in the directory where the deodex.sh file is and type "./deodex.sh", then you can have a coffee (or more, depending on how many files to deodex are there).
When you come back, you should find the cwm_deodex.zip waiting to be pushed to your device and flashed, and a cwm_restore.zip to flash if you need to restore the previous odexed files.
Notes:
The script doesn't stop on errors.
The cwm_restore.zip package doesn't really odex your ROM: it restores the odexed files you pulled from your device before deodexing. So yes, your ROM will get back to it's previous odexed state, but that package won't odex any ROM.
Changes:
-v1.1: Scripts and binaries moved to a "tools" subdirectory; now also creates a flashable zip to restore the old odexed files; reduced the amount of screen output.
-v1: Initial.
If you can suggest any correction to the script, please do it.
Also, since English is not my language, feel more-than-free to point out if there's something wrong or unclear in the post .
Great work
Could you write such a script for odexing too ?
Sent from my BL-S5570 using xda app-developers app
May be... But I don't see any benefits in an odexed ROM. It's just quicker when booting the first time.
Gspin96 said:
May be... But I don't see any benefits in an odexed ROM. It's just quicker when booting the first time.
Click to expand...
Click to collapse
The .odex file is kept in memory ...so higher ram usage but apps open a lot faster as they are already in memory ....also your internal memory is almost completely empty so you don't need to use sd-ext....
Sent from my GT-S5570 using Tapatalk 2
hsay said:
The .odex file is kept in memory ...so higher ram usage but apps open a lot faster as they are already in memory ....also your internal memory is almost completely empty so you don't need to use sd-ext....
Click to expand...
Click to collapse
Here is a quote from http://forum.xda-developers.com/showthread.php?p=39393263
R_a_z_v_a_n said:
Advanteges & Disadvantages
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
Click to expand...
Click to collapse
Also, keeping things in memory is an Android feature: if an app ran once, it is then kept in memory until you use a task killer (which is not recommended, as Android then would have to reload the app in RAM, slowing down and draining battery) or the system gets out-of-memory.
It's more correct to say that odex files are, ready to be loaded in RAM, because the Dalvik Machine doesn't need to optimize them. However, after the DM optimizes them on the first boot, they're kept in the dalvik cache, as ready to be loaded as an odexed app would be.
Anyway, for who wants to re-odex, there's an easy solution: you can use Titanium backup (menu->Integrate sys Dalvik into ROM).
Gspin96 said:
Anyway, for who wants to re-odex, there's an easy solution: you can use Titanium backup (menu->Integrate sys Dalvik into ROM).
Click to expand...
Click to collapse
That is not odexing ...its just an alternative.
Sent from my GT-S5570 using Tapatalk 2
Did you try? I did. It does indeed create the .odex files you want in /system/app.
Gspin96 said:
Did you try? I did. It does indeed create the .odex files you want in /system/app.
Click to expand...
Click to collapse
I stand corrected ...
But does it odex the framework files and other things?
Sent from my GT-S5570 using Tapatalk 2
I was editing that post because i saw that framework was not odexed.
Hell, I had found a link to a to a re-odexing script/tutorial here on xda in the galaxy 3 (not galaxy s3) forum, but I had to go leaving that post unedited.
I'll add a link to that tutorial on first post as soon as I'm on my PC again.
Thanks.
EDIT: this is the tut: http://forum.xda-developers.com/showthread.php?t=1402233
Gspin96 said:
I was editing that post because i saw that framework was not odexed.
Hell, I had found a link to a to a re-odexing script/tutorial here on xda in the galaxy 3 (not galaxy s3) forum, but I had to go leaving that post unedited.
I'll add a link to that tutorial on first post as soon as I'm on my PC again.
Thanks.
EDIT: this is the tut: http://forum.xda-developers.com/showthread.php?t=1402233
Click to expand...
Click to collapse
Btw even universal odex script by matrixdj96 works good and its here in the mini Dev section and bro hope no hard feelings.
Sent from my GT-S5570 using Tapatalk 2
I didn't see that script, it looks good (I won't try it, I'm going to mod framework).
bro hope no hard feelings
Click to expand...
Click to collapse
No, man. I've been feeling attacked somehow, but I know I shouldn't have.
New update: now it's a bit (really, just a very little bit) cleaner and also creates a .zip flashable which restores your ROM to its previous state (usually odexed, if it wasn't odexed, then you wouldn't have used the script).
Related
Our devices don't have very much flash memory and it's easy to fill up /data with apps but here is a quick solution that can give you a bit more space.
In /data is a directory called dalvik-cache, this is a cache of the classes.dex from every app on the device, including those in /system.
On most android devices this doesn't happen, the system applications and the framework are stored as optimised dex files with a .odex extension.
People have spent a lot of time figuring out how to recreate the apks from the odex files and this is good if you have enough space to put all your apps on the device twice because it allows them to be easily swapped for theming.
The attached script goes through each app and jar in /system, creates an odex file and deletes classes.dex. It will give you about 30M extra space on /data while making /system about 10% bigger.
To run it do the following:
Backup you device
Make sure you have at least 15% free on /system, this is important because if you run out of space things will go badly wrong.
unzip odex.zip and then do:
adb push odex /data/odex
adb shell /data/odex/odex.sh
Wait till it finishes and then reboot the phone.
Another reason for odexing is that it boots very quickly and when testing kernels its nice not to have to wait too long.
If you want to see a simple odexed system try this:
http://www.mediafire.com/download.php?qjyniynyqzz
Rename it to androidinstall.tar and it will give you the donut system in the attached screenshots.
The main disadvantage of odexing is that it means you can't change the theme without reinstalling /system so find a theme you like before doing this to your device.
Thanks to Paul O'Brien for writing the original script.
Have fun.
dzo, once again, Thank you.
This should provide ALOT more breathing room in Eclair and Sense builds. Not to mention more flexibility for ROM devs too.
Thanks!
so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry
Unfortunately with my eclair build, /system is almost full
App2SD or /data on sd card look better
but that's device dependant
thank you for the tip anyway
I was about to ask if this will mess up the zipaligning but then I looked a the script and it also does zipaligning.
jadenj5 said:
so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry
Click to expand...
Click to collapse
The end user could run it, too...
Any thoughts on adding this to the install menu? That way you could install system, apply themes, then odex.
I updated the system tar in the first post to fix the broken calendar. I've been running this on my primary phone for a few days now and it seems much faster than it was. Perhaps there's are fewer file accesses with an odexed system and it needs to keep less data in the fs cache. Whatever the reason, give it a try.
is there anyway to do this from the phone without adb?
Include in vogue tools?
Thanks DZO, great that more performance can be squeezed out of our aging devices!
Just a thought: Could this be included in Vogue tools?
Two strange things with this build (on a Kaiser and I've added Wifi so maybe that has to do with it?)
- It never sleeps, I haven't run any Donut build for very long but I think I had this issue when trying the Warm Donut once.
If I turn off the screen (or if it times out by itself) this shows up in /dev/kmsg:
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
- When I run GPS Test and use the time screen the updates are irregular and sometimes skips a couple of seconds and sometimes several updates comes quickle after each other (with less than a second between them). I actually spent some time debugging my GPS code before I tried on eclair and realized it was not the GPS code that was causing it.
Perhaps both issues are related. I've a panel 1 Kaiser.
Other than that it feels very quick and snappy but no sleeping is terrible for the battery life.
Oh, and I tried turning off both wifi and background transfer but that doesn't help.
Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.
preardon said:
Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.
Click to expand...
Click to collapse
it might have something to do with most of the apk's already being odexed
I've posted an odex:ed and zipaligned CM5.0.7 port here: http://forum.xda-developers.com/showthread.php?t=700669
It also odexes every app in /data/app on boot (and clears the dalvik cache).
great donut build!
Thanks Dzo, you managed to pull together a great, snappy no frills donut build! it is fantastic on my Kaiser - and it is only a by-product of yet another great contributions of your! Thanks!
how is this donut build for use?
thoughtlesskyle said:
how is this donut build for use?
Click to expand...
Click to collapse
Great, I am using it daily on my kaiser at the moment. I understand that Kalt_Kaffe had problems with sleeping and battery life, but it works fine for me.
yea i shouldnt have the sleep and battery life problems because i run a vogue and they do things a little differently.
i wish i wasnt changing builds like every other day anymore
this is an excellent vanilla donut build dzo. it's very responsive and stable running from my sd card on the vogue so far. i really like myn's warm donut rom but it would frequently lock up requiring a restart; not the case with this build. thanks.
edit: is it possible to run the odex script again considering that i've been funning this build on my sd card? i wanted to odex the additional apps i added since the first install. also, would i have to manually remove the odexed files after updating an apk?
Had this running for a day on my old Kaiser and it's nearly as fast as my Hero! Fantastic work! Thanks!
This is the "snapiest" android build I have run on my vogue.
loving it thus far.
Hello,
I was wondering, what are the advantages of deodexing, aside from theming?
I've done some tests with my everyday stock ROM and found an odex ROM was faster. I understand that odex files are basically classes.dex, but specifically made for my platform, Android version and is not compressed, thus accelerating the start times.
I went as far as pushing the system apps updates in /system directly (by hand, I can tell you it gets old fast). But I still had low memory in /data. Then I remembered, automatic odex files are stored in dalvik-cache, and thus, when Maps, which has a very big odex file or so, first starts, even if it's on /system, you end up still needing space in /data to start.
So I searched how I could hand-do these odex files, and came across dexopt-wrapper. I loaded it up on my phone, and started odexing all these system apps that used to be odexed.
All in all, you lose room in /system (because odex+apk is slightly larger than the apk, but you're not supposed to have /system writable anyway), or you lose valuable space in /data, where you could put all your apps.
Basically:
I backed up my stuff with Titanium (after cleaning the cache). I was on Geo411m's ROM. I had around 25MB left on my phone.
I then reflashed FRG33 from the PASSIMG.zip
then updated with the FRG83D OTA (straight from Google, not through update.zip)
I updated all system apps through the Market
I used rageagainstthecage to shell root, to read the system and data partitions
I used dexopt-wrapper to create odex files for all the updated apks I had
I pushed everything in /system
Finally, I restarted. Before this, I booted Amon-RA's recovery to clear all the user data
I rooted (permanently this time), restored all my apps through Titanium Backup. I had 65 MB left. That's a 40 MB difference, just by odexing.
So now I wonder, knowing I don't plan on theming, is deodexing useful outside of this, and should I give up some space for something that eluded me?
Sorry for the lonnnnnng post
Thanks!
I'm not aware of any benefit of deodexeding, other than theming.
i've heard people say there is definitely a performance difference between the two, but i really dont know from personal experience. it probably doesnt matter for general usage...
I believe you're right, deodex takes up more of your internal space, which to me is a problem
Sent from my Nexus One using XDA App
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Aside from the first load, deodexed system runs at the same speed as odexed, or with negligible differences (not 100% sure if system-odexed files that are created in Dalvik-cache are the same as .odex that are in the apks).
The disadvantage of deodexed system is extra size of Dalvik-cache. While it can be quite a difference for those using N1's tiny internal space w/o any sort of A2SD solution, it's negligible for those running A2SD or on phones with proper internal memory size.
The advantage of deodexed system is being able to modify the apps themselves, and the framework. In addition to theming, it allows for different kinds of modifications - like trackball wake, or RTL (Hebrew/Arabic) framework patching.
Quite an old thread you managed to dig...
kingdragonfly said:
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Click to expand...
Click to collapse
Way to bump a 1.5 years old thread, lol.
Theshawty said:
Way to bump a 1.5 years old thread, lol.
Click to expand...
Click to collapse
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
magik300 said:
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You felt it was worth a two year bump just to convey that? Oh, ok.
Sent from my HTC One using Tapatalk
I don't know about a 2 year bump, but a 1 year bump to agree that this is a nice simple thread that is exactly what it says on the tin.
Lol
Lol
Is there any good resource I can be pointed to learn about the difference between Odex/Deodex?
nice info from this thread, thanks!
Hi
I would like to start automatically my Htc n1 when i put in the charger.
There are some methods on the internet,for some other phones.
Can someone tell me wich and how the folder i must modify?
My phone doesn't start when it's plugged in and take the battery out and put it back(i dont know why).
Sorry to write to you here, but I see you are very good at what you do.
I thought you could help me.
Thanks
This is not only my first Android app, but this is also my first dive in Java. Please be gentle as I expect there are several uncaught / improperly handled exceptions.
This app will backup selected files to a zip file that can be restored via cwm. For now, that is all it does. It can be handy for the oc/uv crowd since it will allow you to keep a backup of a good S_volt_scheduler init file to flash in case your new setting are too aggressive. It does not currently restore permissions, nor does it assume root permissions.
todo:
Obtain root to copy any file
Integrate a file selector so read permissions will not be an issue.
Detect/Restore permissions
Possible feature additions:
Create a restore.zip from current files based on an update.zip you want to apply. Could save you from boot loops when messing with system files.
Create a restore.zip given a file, a target directory, and permissions.
I will probably add this to the market once I get through the todos and initial bugs.
Changelog:
20110303
Multi-file capable. OIFileManager does not yet support multi-select, so each file must be selected seperately
Exception caught for mission OIFileManager
_delete.zip file seems to work correctly in recovery
Since I am not yet using root and OIFileManager will not assume root, there are some directories that cannot be viewed, /data/app for example. There are also some files that can be selected but cannot be copied due to their permissions.
Requires OIFileManager
Nice, will be useful
This looks like it could be a useful/powerful app. It could definitely benefit from some features (more than one file/location would be great) but I can see myself using this.
Thanks!
gibson3659 said:
This is not only my first Android app, but this is also my first dive in Java. Please be gentle as I expect there are several uncaught / improperly handled exceptions.
This app will backup 1 file to a zip file that can be restored via cwm. For now, that is all it does. It can be handy for the oc/uv crowd since it will allow you to keep a backup of a good S_volt_scheduler init file to flash in case your new setting are too aggressive. It does not currently restore permissions, so the uses are currently limited.
todo:
Figure out why the _delete.zip does not delete the target file when run via cwm.
Detect/Restore permissions
Possible feature additions:
Enable backup/restore of multiple files
Create a restore.zip from current files based on an update.zip you want to apply. Could save you from boot loops when messing with system files.
Create a restore.zip given a file, a target directory, and permissions.
I will probably add this to the market once I get through the todos and initial bugs.
Requires oifilemanager.
Click to expand...
Click to collapse
Can u load the java app here? I can try to look into that and see if I can improve on the exception handling part.
fantastic idea
good job
Thanks for taking a look. Have anyone of you actually tried it?
It fc. On me... :'(
Sent from my SGH-I897 using XDA App
Do you have oifilemanager?
Sent from my SGH-I897 using XDA App
gibson3659 said:
Do you have oifilemanager?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Forgot that
Sent from my SGH-I897 using XDA App
Works like a charm! thank you so much! Perfect cause I love the stock music player and not all rims have it so this is great for installing it!
Sent from my SGH-I897 using XDA App
I am working on multiple file support, so look for a new version in a day or two.
Sent from my SGH-I897 using XDA App
just installed it, however it force closes as soon as I try to choose a source or destination file (happens as soon as I press the buttons.
Herp derp Captivate XDA app.
Make sure you install OIFilemanager from the market. I need to catch this exception and provide a link to OIFileManager.
Great App
Want to say thank you for making this. I've had all sorts of trouble getting apps from different roms to install to the system folder on my current rom. Now I can mix and match different apps easily without much pain. Thanks!
bpurkapi said:
Want to say thank you for making this. I've had all sorts of trouble getting apps from different roms to install to the system folder on my current rom. Now I can mix and match different apps easily without much pain. Thanks!
Click to expand...
Click to collapse
You are welcome. I actually have another app in mind to fully address that need, but I want to get further along with this one first. Since I am working on these on stolen time (I don't have any free time), it will take a while.
Since the apps seem to restore without permission issues, I may put that on the back burner. After I complete multi-file support, which of the future features from the op would you like to see first.
gibson3659 said:
Make sure you install OIFilemanager from the market. I need to catch this exception and provide a link to OIFileManager.
Click to expand...
Click to collapse
And I need to learn how to read through a thread for answers to my problems before I post about them.
New Version
Changelog:
20110303
Multi-file capable. OIFileManager does not yet support multi-select, so each file must be selected seperately
Exception caught for mission OIFileManager
_delete.zip file seems to work correctly in recovery
Since I am not yet using root and OIFileManager will not assume root, there are some directories that cannot be viewed, /data/app for example. There are also some files that can be selected but cannot be copied due to their permissions.
Can I get a gauge on the interest level for this app? Should I move this to the I9000 forum?
I think it's really useful when working whit OC/UV.
gibson3659 said:
Can I get a gauge on the interest level for this app? Should I move this to the I9000 forum?
Click to expand...
Click to collapse
I think you should get with rom devs, this should become an integrated feature for all rom upgrades, regardless of phone
at least get with the AIO dev, if you arent already
I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.
I am to faceing the same problem but on other device
Sent from my HTC Glacier using xda premium
sideways86 said:
I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.
Click to expand...
Click to collapse
I open the ROM zip up and add .apks to the /system/app/ folder all the time..I also delete the ones I know I can and won't use..
There are some apps that won't work like this but its very uncommon..For example I can never include quickpic I always have to manually install it from the market.
sideways86 said:
I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.
Click to expand...
Click to collapse
Well my problem is solved
Check the app name of apps ur adding they should not include space in them ( like xda primium.apk) if there r space then remove the space (like xdaprimium.apk) it should work fine
Sent from my HTC Glacier using xda premium
MrDSL said:
I open the ROM zip up and add .apks to the /system/app/ folder all the time..I also delete the ones I know I can and won't use..
There are some apps that won't work like this but its very uncommon..For example I can never include quickpic I always have to manually install it from the market.
Click to expand...
Click to collapse
Thanks man.
One more question - as far as launcher apps go, is there any way to set the default launcher in the .zip file?
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?
sideways86 said:
Thanks man.
One more question - as far as launcher apps go, is there any way to set the default launcher in the .zip file?
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?
Click to expand...
Click to collapse
no you will prbably need to makea script to get it to work
How can i make the required script??
plz help
---------- Post added at 09:41 PM ---------- Previous post was at 09:37 PM ----------
And ive heard "the TouchWiz launcher included in the rom has hardware acceleration for better graphics performance while the launchers we use like GO LAUNCHER etc depends totally on cpu. They consume cpu power only and no GPU"
IS THAT SO??????????????
that would not mean a good thing
cause GO launcher or n other launcher are way better than Stock TWiz launcher.
I don't want someone to do all the work for me, but if anyone could direct me to some kind of resource with the relevant syntax and such that'd be amazing.
sideways86 said:
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?
Click to expand...
Click to collapse
You can delete any launcher in the original zip and replace it with Nova and it will work. You don't need any script to do that, as suggested before.
thanks chasmodo - this worked flawlessly.
Had some free time recently so finally got round to opening my OYUA and having a looksy.
ROMCleaner 3.5 works splendid with CWM and OUYA.
Why use it with the OUYA?
Its a fast and easy way to pre-install all your apps and games through a single zip flash in CWM.
No more sideloading Dropbox to download and install everytime you flash a new StockPlus or OTA, have them all ready and waiting for you upon the first boot of the ROM.
If your familiar with ROMCleaner on one of the many devices we ported it to, you'll feel right at home!
As certain design decisions were overlooked with the OUYA and it didt get the following it was expected, I didnt wont make a big deal aout the release but couldnt help playing about with to see what I could get working on it. It worked fine so here we are
Notes
More detaililed guides and instructions can be found in any of the device specific threads for ROMCleaner if you want to have a look at its features but for now Ill leave this little guide for us OUYA users.
I doubt there will be a Aroma version due to its reliance on touch input but will slowly be looking at going through the other individual tools we created before Patrics83 put the Aroma AIO toolkit together.
It starts at v3.5 as this was the last version before moving to Aroma and we kept that consistent across devices.
Any changes will only be visually to the updater-script and the default romcleaner.txt included in the zip as at its core, RC works. I will keep a dated chagelog for you though for any updates to the zip.
Basic Guide
Pre-Requisetes:ClockworkMod Recovery
On your on the root of /sdcard create a (case sensitive) folder structure as so:
Code:
/sdcard/ROMCleaner/FirstBoot/data/app/
/sdcard/ROMCleaner/FirstBoot/system/app/
Place any apks in these folders which you want installed after flashing in the relevent folders
After flashing the ROM, flash ROMCleaner 3.5.zip
Reboot as normal
First boot of the ROM will take extra time due to the apks being sorted by Android when its up and running you will find all the apps in the usual place all ready and waiting!
If you install another launcher I recommend loading OUYA Launcher first and following the setup (wifi, username etc) to get it all sorted before using your preferred launcher.
You can use RC to install other files such as bootanimation.zip (system/media/) as well and are not limited to just apks. I add TwitcyEye's KeyMap mod for example so the mapping is done with no copying files about.
It will set the correct permissions for all the files and folders so dont worry about that.
Cleaning
ROMCleaner has the ability to remove files from the system after the ROM has been flashed, but before first boot, using a text file in a simple user-friendly format.
The default list has not been optimized for OUYA and I have not got round to checking through it yet. I haven't noticed any thing important if it does but you have been warned Ill take a proper look when I get the time.
You have the ability to define a custom list for RC to use by creating a ROMCleaner_user.txt file in /sdcard/ROMCleaner/ and Ive attached a blank one with some detailed instructions on its layour and format. I recommend you use this file until I have time to cross reference the default list with the OUYA files to avoid anything being deleted.
All in all its an easy way to get your apps installed when flashing a ROM be it StockPlus or an official OTA. It requires no special access as its all done in recovery and uses its own busybox.
Anyway, Have a play and let me know how it works for you.
Like a lot of people on XDA I have very little free time these days due to my job and so-called life but will be keeping my eye on this thread and the OUYA in general
#probably for formatted guide
#just in case
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
TadeoNYC said:
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately thats a completely different thing. All this is done in recovery where as TB etc are app specific done while the OS is up and running.
RC installs (and can remove) the apps before the OS has loaded for the first time.