Related
Well guys, I apologize for posting this here, but i've done a ton of research and i have no clue where to start. I look in the General Android Development here and it's all device specific.
I feel like it's about time for me to start contributing back to the community.
I want to create a deodexed take-and-bake ROM, but i have literally no idea where to start. I dunno if i'm supposed to use VirtualMachine, SDK, JDK, or what. I've done days of research, using my google-fu to the best of my ability. All i want to learn how to do right now is:
1. Deodex
2. Create ROM structure
3. Wrap up in a handy .zip package for installation
If any help could be given, that would be awesome. Plus, if this thread gets any attention, maybe it could be a reference point for new devs to start and maybe help out the community too.
So if you can lend a hand, thanks a million.
These post might help:
http://htcpedia.com/forum/showthread.php?t=1404
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=633246
thanks man, swooping up that kitchen up now. maybe by tomorrow i'll have a working ROM out of the little surprise Eugene's bringing for us
DOAlaboratories said:
thanks man, swooping up that kitchen up now. maybe by tomorrow i'll have a working ROM out of the little surprise Eugene's bringing for us
Click to expand...
Click to collapse
Huh? Eugege has something better than Frankin-Twiz?? Or is it F-Twiz with Froyo?
Do tell!
Hey let me know how those work. I've been looking for something like you and had pretty much given up. Here's some other links I've found.
http://forum.xda-developers.com/showthread.php?t=697938
http://forum.xda-developers.com/showthread.php?t=667298
I am also looking to learn cooking Will try and reply.
i would love to learn too should have more time on my hands and might actually get to dig in soon
Since then I've come a long way it just seems like every time i have something rready for release someone one-ups me
How to cook a ROM:
- Pre-heat your oven to 375
- Baste your framework-res.apk in a garlic and olive oil marinade, let stand for 30 minutes.
- Remove Twiz and set your launcher in /system/app
- Lightly salt and pepper your ROM and add a few miscellaneous apps. Change the apps you include every other day for best results.
- Stuff your ROM with giblets and random mods like the gingerbread keyboard or the one where you move the clear button up to the widget bar on the notification menu.
- Bake for thirty five minutes, or until the ROM reaches sufficient sexiness
- Let stand ten minutes, serve with white wine
Alternatively, just kang someone else's work and pass it off as your own, then just say you only used the build.prop from the other individual's ROM.
glitterballs said:
How to cook a ROM:
- Pre-heat your oven to 375
- Baste your framework-res.apk in a garlic and olive oil marinade, let stand for 30 minutes.
- Remove Twiz and set your launcher in /system/app
- Lightly salt and pepper your ROM and add a few miscellaneous apps. Change the apps you include every other day for best results.
- Stuff your ROM with giblets and random mods like the gingerbread keyboard or the one where you move the clear button up to the widget bar on the notification menu.
- Bake for thirty five minutes, or until the ROM reaches sufficient sexiness
- Let stand ten minutes, serve with white wine
Alternatively, just kang someone else's work and pass it off as your own, then just say you only used the build.prop from the other individual's ROM.
Click to expand...
Click to collapse
I just LOL'd real hard
DOAlaboratories said:
Since then I've come a long way it just seems like every time i have something rready for release someone one-ups me
Click to expand...
Click to collapse
Any advice to some one starting this journey.
Sent from my SAMSUNG-GT-I9000 using XDA App
I see what you did there glitterballs. I have so say, I am a fan sir.
Thanks for the above links guys! I haven't perused them very much yet, but I'm sure they will make for some great reads =D
glitterballs said:
How to cook a ROM:
- Pre-heat your oven to 375
- Baste your framework-res.apk in a garlic and olive oil marinade, let stand for 30 minutes.
- Remove Twiz and set your launcher in /system/app
- Lightly salt and pepper your ROM and add a few miscellaneous apps. Change the apps you include every other day for best results.
- Stuff your ROM with giblets and random mods like the gingerbread keyboard or the one where you move the clear button up to the widget bar on the notification menu.
- Bake for thirty five minutes, or until the ROM reaches sufficient sexiness
- Let stand ten minutes, serve with white wine
Alternatively, just kang someone else's work and pass it off as your own, then just say you only used the build.prop from the other individual's ROM.
Click to expand...
Click to collapse
LOL! You are the f-ing man! Really, I think this is a great idea for a thread. I have been trying to figure a way to keep track of all the stuff I have learned over the last few months and this could be it. Between noob and the premiere chefs here are... all the rest of us. I want to learn and share what I learn.
Thank you!!!!!"" Finally a good post on where I hopefully can start. Well ill take a look at the sites in the morning. Night!
Sent from my GT-I9000M using XDA App
What tool do you use to pull the img files out of a odin release? Like those released on samsung_firmware site?
They look like bin files not img files?
Thanks
try 7zip. It will extract just about anything.
lbbo2002 said:
What tool do you use to pull the img files out of a odin release? Like those released on samsung_firmware site?
They look like bin files not img files?
Thanks
Click to expand...
Click to collapse
glitterballs said:
How to cook a ROM:
- Pre-heat your oven to 375
- Baste your framework-res.apk in a garlic and olive oil marinade, let stand for 30 minutes.
- Remove Twiz and set your launcher in /system/app
- Lightly salt and pepper your ROM and add a few miscellaneous apps. Change the apps you include every other day for best results.
- Stuff your ROM with giblets and random mods like the gingerbread keyboard or the one where you move the clear button up to the widget bar on the notification menu.
- Bake for thirty five minutes, or until the ROM reaches sufficient sexiness
- Let stand ten minutes, serve with white wine
Click to expand...
Click to collapse
The best part is that it's actually the correct way to cook a ROM.
lbbo2002 said:
What tool do you use to pull the img files out of a odin release? Like those released on samsung_firmware site?
They look like bin files not img files?
Thanks
Click to expand...
Click to collapse
Magic ISO will open the two .rfs files.
First thing is choose what base you want to work with. Then load the rom and dump /system.
1 Install busybox to /system/xbin
2 cd /sdcard
3 chmod 777 /system/xbin/busybox
4 /system/xbin/busybox tar czvf dump.tar /system
On your sdcard will be dump.tar. Copy to pc. Unzip the dump.tar. Use xUltimate to deodex /system/apps & /system/framework. Now you can edit framework.res and add theme, battery icons & shutdown menu if needed. This requires Linux to dump the files and Linux to repack them if there are no themes, battery icons or shutdown menus available for your base rom. Add busybox & root. Add what apps you want preloaded to /data/apps. You can also include modem and kernel if needed. Now create update.zip that will flash the files you changed. I have been working on learning how to dump and edit framework.res. From this process I have learned its easier to make your changes to the source code then making changes after then rom is compiled. I read up on CM and they suggest making android apps before compiling from source to get use to android file system and what not. I am now learning android sdk with eclipse. Then I am going to start working with source code instead of making roms from dumps.
MikeyMike01 said:
Magic ISO will open the two .rfs files.
Click to expand...
Click to collapse
Thanks Mikey for the info that helps a lot so I don't have to load a Linux (still might since I have VMW. I assume Cygwin can do the reconstruction?
Well I got the Frameworks rfs to extract but not any others? What other .rfs file can Magic ISO open/extract?
OK the Cache.rfs file I was able to open and extract the zip. On the first ROM it wouldn't work so must be bad.
Thanks
======
Preface
======
The script is actually Base on Juwe11's RAM script
which you can found here... http://forum.xda-developers.com/showthread.php?t=1111145
==========
Main Content
==========
The adj value of his script is a bit too tight for Our O2X...
so the Launcher is killed quite often if many apps opened in the background.
Here's the adj value changes I made, originally, Juwe11's values are..
"0,1,2,4,6,15" and I change it to, "0,1,2,7,8,9"
the forth value is for HIDDEN_APP_MIN_ADJ, which including the Launcher (I'm using LauncherPro) belongs to this category when you open some foreground application.
the default android value for this is also 7, and I find the OOM value for Launcher is 6 usually... so Juwe11's "4" will lead to our Launcher being Killed, keep it at 7, never tried to have mine killed yet.
The last 2 vaule just make sure the last category EMPTY_APP_ADJ is kill earlier than the previous..
About the minfree vaule...
I change it to "1536,3072,4096,7680,8960,10240" which actually the same values of "Moderate preset" of autokiller
which is enough to ensure most RAM being use before killing for faster task switching...
=====
Credit
=====
!! Credit goes to Juwe11 for his mighty RAM script~ !!
Backup your RAMscript and remove it to somewhere before install this...
install via CWM, it will put the script into your /etc/inti.d/ that's it, boot and try
i just installed it,
i will let u know what are the results,
u are correct, the original script kills the launcher and apps specially XDA
will try this configuration on auto killer memory seems good m8 to set it to moderate
shpapy said:
i just installed it,
i will let u know what are the results,
u are correct, the original script kills the launcher and apps specially XDA
Click to expand...
Click to collapse
I'm not sure if other Launcher would have a different OOM value~
I have Autokiller memory optimizer which I paid before...so I can view OOM value easily..
But with this Script... I guess really no task killer needed for our 2X already.
antec123 said:
will try this configuration on auto killer memory seems good m8 to set it to moderate
Click to expand...
Click to collapse
so, just edit the minfree value according to the values inside AutoKiller if you find some other setting suits you more
but about the adj value... I guess that part is already good enough
now I find my phone already got around 60-90 free RAM at any time...
Multiple games running at the background while web browsing...
and the Browser usually got a higher OOM, which tends to kill earlier than Games..
it is reasonable.. as the WEB you can load again with the same URL..
while the game got killed, you lost the state... android is doing it's work nicely I guess.
best memory managment script i have tryed is v6supercharger http://forum.xda-developers.com/showthread.php?t=991276
I think its the best of the best.
orlox said:
best memory managment script i have tryed is v6supercharger http://forum.xda-developers.com/showthread.php?t=991276
I think its the best of the best.
Click to expand...
Click to collapse
I tried both V6 and Juwe11's before...
and I manage to be patient enough to follow step by steps...
for installing so many things... and it just put a script in init.d at the end...
And I found it do not contain adj value in it, so I come back to Juwe11's
but anyway, this is your choice...
thanks for that script
just a quick question
would this script also work on a sgs2, running oxygen aosp stock rom?
pa.pn2 said:
thanks for that script
just a quick question
would this script also work on a sgs2, running oxygen aosp stock rom?
Click to expand...
Click to collapse
same as Original Juwe11's version.
it was suppose to work on any ROM which support init.d
but the values may need some tweaking accordingly.
squide said:
I'm not sure if other Launcher would have a different OOM value~
I have Autokiller memory optimizer which I paid before...so I can view OOM value easily..
But with this Script... I guess really no task killer needed for our 2X already.
Click to expand...
Click to collapse
Sorry to let you down. But the results are the same......
Sent from my LG-P990 using XDA App
squide said:
I tried both V6 and Juwe11's before...
and I manage to be patient enough to follow step by steps...
for installing so many things... and it just put a script in init.d at the end...
And I found it do not contain adj value in it, so I come back to Juwe11's
but anyway, this is your choice...
Click to expand...
Click to collapse
adj values are in /data/SuperChargerAdj while minfree values are in /data/SuperChargerMinfree.
it's just a script in init.d at the end, you only need to follow it step by step...
squide said:
so, just edit the minfree value according to the values inside AutoKiller if you find some other setting suits you more
but about the adj value... I guess that part is already good enough
now I find my phone already got around 60-90 free RAM at any time...
Multiple games running at the background while web browsing...
and the Browser usually got a higher OOM, which tends to kill earlier than Games..
it is reasonable.. as the WEB you can load again with the same URL..
while the game got killed, you lost the state... android is doing it's work nicely I guess.
Click to expand...
Click to collapse
i set the preset to moderate and get about 126-128mb on free ram pretty impressive and the stock browser don't get close so quickly nice! i use v10e ESA and neoblaze kernel
Works on CM7?
_Vegas said:
Works on CM7?
Click to expand...
Click to collapse
it should work on all ROM supporting init.d
in case you don't like it, go to /etc/init.d to remove the script and reboot.
it wont modify your file system..
it just override some system value on boot.
if you removes the script.. your phone would back to the state before you install this.
so, just try see if u like, if not, delete it, reboot, that's it.
Works really nicely on CM7 nightly.
Sent from my Optimus 2X
Bit of a Dumb question but my phone still has the Stock rom and doesn't have the init.d Folder
if I created /system/etc/init.d and copied the script into that would this work?
waynefox said:
Bit of a Dumb question but my phone still has the Stock rom and doesn't have the init.d Folder
if I created /system/etc/init.d and copied the script into that would this work?
Click to expand...
Click to collapse
Sorry, no. You need a custom rom of some sort to get init.d support.
TrymHansen said:
Sorry, no. You need a custom rom of some sort to get init.d support.
Click to expand...
Click to collapse
You need a Custom Kernel supporting init.d to be more accurate.
and NeoBlaze is a good one to try with.
if you really need to keep your stock ROM..
First of all you still need to root your phone
Install ROM manager from market
flash the Clockworkmod via ROM manager
install NeoBlaze Kernel, then you're ready.
if warranty is your concern, take a look to the Nvflash thread..
O2X is ALMOST unbrickable, almost.
squide said:
You need a Custom Kernel supporting init.d to be more accurate.
and NeoBlaze is a good one to try with.
if you really need to keep your stock ROM..
First of all you still need to root your phone
Install ROM manager from market
flash the Clockworkmod via ROM manager
install NeoBlaze Kernel, then you're ready.
Click to expand...
Click to collapse
I'm pretty sure that won't work. You need ROM-support as well. (A Ramdisk script which starts the init.d. thing to be even more accurate.) Feel free to prove me wrong.
TrymHansen said:
I'm pretty sure that won't work. You need ROM-support as well. (A Ramdisk script which starts the init.d. thing to be even more accurate.) Feel free to prove me wrong.
Click to expand...
Click to collapse
Ramdisk is a part of the kernel, so if you bung a kernel that supports init.d on (any) rom it'll run what's in there assuming it's eXecutable.
You can do it on the stock rom even, as long as you have a init.d kernel (and create the entries in ../etc/init.d/).
Although I can't "prove" this to you at the moment...
THIS IS NOT MY WORK! I'M POSTING THIS WITH PERMISSION FROM zeppelinrox
Back in the ancient times (Eclair,Froyo,Gingerbread) the stock android launcher was....Slow to put it nicely. Zeppelinrox wrote a script that changes the oom values inside of android to put the launcher in it's rightful place. No more redrawing launchers weird lagging etc etc. He's done it again for ICS.
This is a little more involved than simply executing a script at boot time though. 4.0 is to Gingerbread what Froyo was to Cupcake! Pretty big differences but if you're up to the challenge then feel free to CLICK HERE http://forum.xda-developers.com/showthread.php?t=991276 and check it out for yourself!
I'm just posting this as an additional bit of information. Dropping in from the MyTouch 4G Forum as I recently got a "broken" vibrant from a customer. (Camera just needed reseating)
Oh boy, I think I'm entering this game! Wish me luck.
Arhg, it's really much to do! Any tutorial? I don't ever know what step I should take first! please, explain us what you did. Thanks!
Say why not attach a patched services.jar
Zeppelinrox, could you please provide us with updated info about the installation process?
I see too many files.
Enviado desde mi SGH-T959 usando Tapatalk
i am using the zenwich beta rom, tried this, but got errors during the script run, so i tried updating the SU binary. I ran into trouble setting permissions on the /system/xbin/su
i was using file expert to change permissions, but i guess that wasn't enough.
does this have to get pushed through adb?
ps, i just flashed the newest zenwich beta...#4, so i have a completely fresh machine.
i also understand that you shouldn't/cant change a file that is in use, aas is the case with the /system/xbin/su
and, does zenwich need this mod?
thanks, 1fd
a patched services.jar would be awesome.
Wouldn't it be....
G00DFe77a said:
a patched services.jar would be awesome.
Click to expand...
Click to collapse
I'm still learning how to do this myself. I posted this so the developers would be aware of it if they felt like incorporating it into a rom.
TwkdMod- The Rom that will speed your phone!
Tested for a week to test if it it stable.it is not my fault if this messes up your phone.
Features:
-based off of the latest cm10.1 nightly
-tweaked with different tweaks (seeder, supercharger, pimp my rom, and more!) (maybe in the next release i will include supercharger )
-fast
-stable
-light
-small
-faster 3g
-faster scrolling
-faster everything!
-better benchmarks
-debloated
Changelog:
v1
Credits:
all the developer in the this section
mods
::indie:: (helped a lot. Omega rom dev.)
salesale (NeatROM dev. a great person.)
westcrip (awesome rom which helped me learn about this.)
-people who run this
Downloads:
wup, wup!
i added the download link to the op. please let me know how it is!
what are the tweaks you added that made it faster scrolling/3g/etc?
jarjar124 said:
what are the tweaks you added that made it faster scrolling/3g/etc?
Click to expand...
Click to collapse
mostly init.d tweaks and some build.prop tweaks. build in the future will be supercharged. just try it and please let me know how it is!
does anybody download? how is it?
You need to flash gapps too I believe.
EDIT: error in zip could not install, will try again.
not install ...
Hi,
OMG!!!
I just looked into your init.d folder...
You collect lots of scripts to put in your ROM, fine, but put them all together, less good..., just my opinion. Would have had to sort out and look a bit some values, more than half are completely useless.
For the same tweak you have two, three or four times the same values in different scripts or even 2 different values in the same script...
For the same tweak you have x value in a script and y value in another one (and for some tweaks you have 2 different values in the same script!)...
At boot one erase another while a third erase yet the previous (according to the execution order at boot).
Your scripts for RAM "management" is the best example of against productivity, two scripts for zipalign, your scripts for "net speed" are also the same, etc...
30 init.d scripts running, obiously, at boot... it is not a bit much? Check the duplicates (or more) lines and tweaks, removes unnecessary scripts and makes a little cleaning...
It is not because you have 30 different scripts with multiple lines and values that is necessarily great, remove all your scripts (or keep one for the "RAM management" maybe (and still not sure ) and your ROM will runs perfectly.
Sometimes "more is the enemy of the good", here it's a good example... And don't say the user can choose or edit... probably the most (or all) people who flash this don't know the point of this or that script...They will flash the whole zip with all your scripts inside without knowing what they do... It's totally useless. People see "speed" "fast", "smooth", "performance", etc... ok GO GO GO! flashing! + placebo effect...
You'll have the same goal without the whole script , the ROM will runs perfectly without all this... bunch of scripts...
Ask some devs the usefulness of these scripts, you'll be surprised. I've already tested some of your scripts... Most do little or nothing, are not adapted to JB or needs to be reworked when we have 2 Go of RAM (the scripts for RAM "management"), or are not adapted to our phones (look at your "14enable_touchscreen", where do you find the path in our N4 ??? the path /sys/class/touch/switch/set_touchscreen does not exists... you are echoing a value wich does not exist-> totaly useless script), etc...
Just my opinion and some tips...
Keep the good works up !
Waiting for most features
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
Keep the good works up !
Waiting for most features
This was the same guy who posted a fake 4.2.2...
Sent from my Nexus 4 using Tapatalk 2
Imppy said:
This was the same guy who posted a fake 4.2.2...
Click to expand...
Click to collapse
build.prop and init.d hero :good:
You should be ashamed of yourself dude.. I really have no idea why mods are so easy on ppl like you.
I encourage new devs, honestly if you had compiled stock cm I would've congratulated you.. but if you're gonna skip the steps and just BS your way through then we'll shoot your plan full of holes.
Nobody flash this ROM it's junk..
Sent from my Nexus 4
Ok mate, I'm going to say this slow and easy.
Getting a cm10.1 base, removing apps and just collecting all init.d scripts is not the way to make a rom.
Go to guides, and read more until you know what exactly you are doing.
Or else, you'd see thousands of roms here.
Plus, changing the android version in build.prop doesn't make it Android 10.
mv_style said:
Guys dont bother downloading this
he just added like 10 different scripts which conflict
every values comes up like 5 times at least
he is banned cause of posting fake work
Click to expand...
Click to collapse
Moderator please close thread.
Hello everyone,
Galaxy A comes with much more bloatware than most other phones, it has apps preinstalled that some of us probably will never use.
Some of those apps may even run at boot and consume RAM and CPU. For this purpose I made a small very effective script and that will remove huge amount of applications. This script works on de-odexed and odexed ROMs and you can use it even for Marshmallow ROMs, so this is ALL-IN-ONE solution.
I created the script when Nougat came out and I'm using it all the time without any problems.
* You can easily edit script and add character ' # ' to exclude certain APP from deleting *
REMOVED STUFF:
https://docs.google.com/document/d/1UQ5RqlQSDXi9AZkKWhCdv21bTWNyDrx4Sf1jsbox-Nk/edit
Galaxy A 2016 and 2017 are both supported
wow, how to use that script please?
unzip and batch inside to hit up?
thx
punkrockfan said:
wow, how to use that script please?
unzip and batch inside to hit up?
thx
Click to expand...
Click to collapse
just flash it in recovery