Hi.
I found this thread speaking about another init.d script to optimise the system. Should be universal, regarding the modifications made.
http://forum.xda-developers.com/showthread.php?t=1380006
Didn't try it yet as I run a script dealing with memory, and it's not compatible it seems.
Zipalign fire example is also commonly present in some ROM or power pack.
So before using it check that there are no conflict between already present files in your ROM and those provided by the zip.
Related
I tried to word the title correctly to establish that I want to ask 2 different questions, but dont want to clutter up the board with 2 separate posts
Please help if you can
1. Kernel
Why do some kernels work with some roms and not others? I have taken a Sprint Rom, ran it through the kitchen, and tried flashing any number of kernels. The only one that works is Zenulators AnyKernel. I know at times only the stock overclocked worked, but I think at certain times I have gotten the no perf lock to work (though that may have been with an NFX Rom, and not one that I created myself). This leads me to ask why would a kernel work for a rom that is built from the same base that I am using, but not on mine? Is dsixda's kitchen not the one everyone uses? I just dont understand why I am limited to one kernel that is not undervolted and overclocked. I would like to put a 768 overclocked, undervolted kernel with this rom, but cant get any to flash. Should I just use the kitchen to "port" the kernel. How does nfinitefx45 get the kernels he posts to work with a Sprint base? Is the kernel edited in some way? Im not calling anyone out, just trying to learn how to get a good kernel to work with my rom.
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
I decided to take another cracked at a minimal Sprint 2.1 Rom. I used dsixda kitchen 0.107 to root, add busybox, remove boot sounds, deodex, add data/app, add nano + sysrw, sysro, bash, and zipalign the .7 Rom. I then removed all Sprint apps except for VVM, all google apps, all htc apps and widgets that were not explicity needed (need the contacts and ime apks among a few others), removed a ton of system apps (can provide a list of current system/app dir and a list of all that was removed if it will help). I edited the lockscreen so it wasnt in landscape mode all the time. Added an OMADM.apk file that didnt FC when I tried to update the prl (tested the update and it works). I did find an EPST.apk that adds ## codes back to the dialer (should I include that in the rom...wasnt intending on it as the only ## code that doesnt work is the prl...data works) OMADM.apk is smaller that the EPST...but EPST does exist already...and I might be able to pull OMADM meaning 0 firmware, profile, or prl updates...but you could do ##prl manual...I dont know, still thinking it through. I did end up creating a google apps zip file with the apps from the .7 rom so that market will work (removed maps as it wasnt up to date and the Streets.apk never worked, but left gmail, youtube, voice search to work with jonasl's htc keyboard, and of course gtalk). In doing this, I am thinking about creating some packs for the rom, but really need the above 2 questions answered to find out where to go from here.
evilvoice said:
1. Why do some kernels work with some roms and not others?
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
Click to expand...
Click to collapse
afaict, the 'kernels' are literally just the linux kernel that provides some basics to the os... altho linux IS a monolithic kernel, it is not a bsd-system that has all the tools completely-compiled for the system together...
thus, the answer to 2. is that you have deleted too much of the periphery, for instance the actual mount-table system that df uses to to check... (ie: some prog creates the mtab, and apparently it is not the kernel, i guess)
alternatively, the answer to 1. is that there is actually too much in the roms that are using something unique to each kernel that you are trying to install (altho that seems odd to me)... thus, the only way that the rom will work is if you give it the kernel with the tools that it (the rom) needs...
tbh - im not exactly sure - ive not gone into the depths of kernel-swapping that youre trying to explore... in full-linux-systems, the kernel is fairly easy to update without breaking all of the miscellaneous tools - however apparently the android-roms are more tied-together than a normal linux system...
gl and maybe someone with more experience will give an accurate (rather than a guessing) answer...
Dear All,
I created this thread in Wildfire Android Development for new Wildfire Owners that are new to Android OS, from my personal experience i noticed that at least 99.9% (this is not really calculated!) of the people that google anything relevant with the word Wildfire (i.e root,dalvik cache,deodexed,custom rom,rom,etc.) will not bother to go through XDA topics/threads outside the Wildfire Android Development to research and usually make unnecessary posts all over the topics in all different threads thus creating a chaos!
People new to Android OS want a cooked rom served in their plate while still hot and will complain a lot if something is not working as it should... sometimes they shout and even DEMAND from a sleepless chef all sorts of things that comes to their head.
PEOPLE WAKE UP! - This is THE place that development is being made, this is where willing beta testers test unfinished roms (these are called nightlies) until they become stable enough to be released to the public first as an RC (Release Candidate) and then when it reaches Final Stage (again after many nightlies) only then they will be released as a Stable Release.
Now people, read on...
What Is Odex And Deodex In Android
As any new Android user, what will bother you mostly is going across terminology beyond your comprehension. Not coming from a Linux background it will be hard to keep up with the oh-so-commonly-used words spread all across the development community. Since most of you probably don't understand the terms, consequently you will be unable to determine if something was of any use to you or not. From what I have seen, this problem extends to many novice and even average users.(But there will always be exceptions)
One commonly occurring word when playing with custom ROMs and firmware, and even themes is deodexed and odexed. Most users fail to understand what these terms actually imply, and while developers would boast again and again about their themes and ROMs being deodexed, the average user is left clueless as to what is going on.
In this article, we’ll try to explain what odexed and deodexed means, and what implications does it bring to a casual user.
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & 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.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
HAPPY FLASHING!
Using a deodexed rom also implies having less space available under /data (20/30MB), taken by the cache.
Kwen said:
Using a deodexed rom also implies having less space available under /data (20/30MB), taken by the cache.
Click to expand...
Click to collapse
Correct.
If I'm not mistaken then .odex system apps also can not simply extracted and copied from one device to another one (i.e. Desire to Wildfire) because the optimizations are device-dependend.
can i install different scripts at once will they.. ex i have loopy smoothness tweak script now can i install other script lyk dominic script.... etc hel
thank you
dheeraj93 said:
can i install different scripts at once will they.. ex i have loopy smoothness tweak script now can i install other script lyk dominic script.... etc hel
thank you
Click to expand...
Click to collapse
Dominic Script is a combination of multiple scripts, that is why he asked to delete the already installed scripts before installing Domscript. It all depends actually, if your new script has nothing to do with the old script files then i guess it is ok to flash the new script (If you are sure both scripts will not have a conflict in different tweak values). But even if it conflicts, most probably the new script will overwrite the old script anyway. Also some scripts like adrenaline engine, automatically delete previous scripts from init.d. I think you should not install multiple scripts and instead, try all of them which are compatible with your phone, one by one, and then decide which one works best for you :good:
btw, you can always take the best out of every script and create your own, but i guess dominic already did that
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.
@rovo89 Can you create a button to utilize /system/addon.d/ 's scripts to backup and restore the modified app_process file that xposed installer creates so that when cyanogenmod nightlies and new roms flash they don't overwrite the xposed framework. I noticed that you already have a script made up but it might be better for less experienced users if it was made into a button that writes the file to the right place
camerona said:
I noticed that you already have a script made up but it might be better for less experienced users if it was made into a button that writes the file to the right place
Click to expand...
Click to collapse
Not planning to do so, read my explanations here: https://github.com/rovo89/XposedInstaller/issues/143#issuecomment-42641987