Related
Introduction
I've made a Definite Guide on Android thread for i9000 that focuses on a few optimizations/scripts I've picked up over the months I've spent on XDA. I truly enjoyed sharing my knowledge with the i9000 community and since the tips/guide/scripts can also be applied here (save some exceptions that I would list down below),I would like to share this with the Captivate community too.
Exceptions
Take note that the guide is primarily for i9000 units. There are a few differences I can note here that you should be aware of:
1. The guide points out some kernels/ROMs that are for i9000. Hence the phones you are using may have different ROMs/kernels that may or may not correlate with the one in the guide.
2. The guide also mentions some apps/tweaks that are particularly alien to your unit and you may have never encountered it in your use of your phone or in XDA. Please ignore them for now, I'll make an effort to make the guide compatible in the future (with feedback from you guys of course )
3. Journaling scripts that are attached like the JournalingOn.zip and Acid Tweaks - Removed Useless Stuff and 00remount may not work well with your unit or it may completely brick it. I don't know this, but if you can post your mount partition configuration, I am willing to make the scripts work for you. You only have to type "mount" on your Terminal Emulator and provide the output to me, and I'll provide the rest. Zach's script however, have high compatibility towards a lot of phones, and thus can be used for your unit. Take note that there is a slight risk that it won't work well. If it doesn't, please post your problems here, and I'll try to fix it. Hence, it's best that you make a nandroid backup before attempting to use any tweaks here.
3. I've compiled a guide on a few notable tweaks in XDA here: LINK. If you would like me to evaluate scripts/tweaks/anything that you do not understand due to their terms being alien to you, I'll be glad to explain it here
Guide
You can refer to the guide here:
LINK
s98screenstate_scaling script (provided in attachment) works for any kernel ?
and thanks, for good stuff.
neobuddy89 said:
s98screenstate_scaling script (provided in attachment) works for any kernel ?
and thanks, for good stuff.
Click to expand...
Click to collapse
Yes, it should work if your kernel has conservative as well as ondemand governor implemented in the kernel, and the kernel supports init.d scripts.
If your kernel doesn't, you can edit the script and point to a governor of your liking. Instructions are in the script itself.
Would it be possible to use scary as sleep and smartass for awake? I'm using the dragonmodz kernel listed here http://forum.xda-developers.com/showthread.php?t=1049894 I tried to make the edits myself but just end up freezing my phone.
G00DFe77a said:
Would it be possible to use scary as sleep and smartass for awake? I'm using the dragonmodz kernel listed here http://forum.xda-developers.com/showthread.php?t=1049894 I tried to make the edits myself but just end up freezing my phone.
Click to expand...
Click to collapse
Yes, it's possible. However, the thresholds and other settings for it needs to be overwritten with scary/smartass default settings as the ones in there are default for conservative and ondemand respectively.
Made some pretty big changes to the guide.
Please refer to it when you have the time!
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!
just what i need
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?
Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.
Just when I thought this kitchen was a goner, you came along and made it work again
I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal
Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.
The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)
Awesome job mate :good:
tomorrow`s homework !
thanx !
Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!
Great.
Just what i was looking for.
dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps
Please link to download the kitchen, thank you very much.
misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.
This is great!
Thanks dsixda.
YZ.
Please not see me? can give direct link? thank you very much
misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.
Hey Guys
The following script enables init.d use on stock kernels. Your phone must be rooted, if you have a custom kernel with init.d enabled, there is no need for you to install this.
Credits
Ryuinferno
Thread
http://forum.xda-developers.com/showthread.php?t=1933849
XDA News Portal
http://www.xda-developers.com/android/init-d-support-for-any-rooted-phone/
I have tried various scripts, and they do work, what im looking for is a script that will optimize the Xperia T ( i don't really like using the same script from packages or from other devices), im not a dev by any means, but did create a single 'tweaks' custom script for my Xperia Arc.
Are there any devz out there who would know what best to set certain values at in a script? Looking to create or progress scripts for safe and necessary optimizations to network, sd card, vm, UI tweaks etc.
Regards
Thread closed as cross posting of threads posted on the portal/other xda forums is not allowed. Also this is not device specific.
Thanks
AvRS
Sent from my GT-I9100 using xda premium
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.
Uptil now i have been using 2.3.x roms only. recently i tried out the alchemists' rom which is 4.2.2 (http://forum.xda-developers.com/showthread.php?t=2227481)
but since this is my first time i have a lot of questions to which i can find no proper answers..
these are my doubts:
1)gaaps is 91 mb and that does not leave much space on internal memory...is there a lite version and can anyone post the link? (i searched on the net everywhere but i cant find it)
2) what are the scripts that can be used for internal memory?(like link2sd etc) i have a class 4 sd with 1gb ext 3 partition.
3)the rom like 2.3.x roms does not have the options in settingss "performance"(overclocking and all that) and "developer options". (i think its called oc and uc kernels...)
4)what performance enhancing scripts can be used? (adrenaline and stuff cannot be used coz they are only for 2.3) also can bravia engine 2 and beats audio be used?
5)can apps like swapper be used?(is it even recommended with class 4) can chainfire be used?
I know this is a lot but please bear with me...
1. use slimmed gapps, a lot of options in original gapps simply don't work on old devices, konstakang made good ones
2. i use link2sd, but i heard some others work, just look around and read few pages of discussion threads
3. again, looking around would solve your problem... tap on build number in about phone few times
4. what for? it will only clutter the system (just my personal opinion)
5. again, what for?
1-4 learn to read, 5 learn to search. Short and 100% correct answer
Tapatalk 2-vel küldve az én GT-S5570-ről
yackovsky said:
1. use slimmed gapps, a lot of options in original gapps simply don't work on old devices, konstakang made good ones
2. i use link2sd, but i heard some others work, just look around and read few pages of discussion threads
3. again, looking around would solve your problem... tap on build number in about phone few times
4. what for? it will only clutter the system (just my personal opinion)
5. again, what for?
Click to expand...
Click to collapse
1) i have searched for this a lot online but whatever i have found is either 90mb or not 4.2.2 but 4.1.2. there is no slimmed version
3)i actually wrote utter crap there what i meant was that like how in 2.3 u have all uc, oc options how to add those in this rom
thanks
TheStormBreaker said:
1) i have searched for this a lot online but whatever i have found is either 90mb or not 4.2.2 but 4.1.2. there is no slimmed version
3)i actually wrote utter crap there what i meant was that like how in 2.3 u have all uc, oc options how to add those in this rom
thanks
Click to expand...
Click to collapse
You can slim gapps for yourself! It really isn't that hard...
here, is it really that hard?