[Galaxy S II General] drabd:
Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.

What is build.prop:

- The build.prop file is your android handset’s ‘ID card’.

- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.

- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.

- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.

- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect

NOTE :- please if u have any other tweaks or some of this tweaks are busted tell me or pm me

i put all the tweaks togethers and i arrange them accordingly so u can find easily what u have and what u don't and what is working and what is not so hope it will be good help for u

​

WAIT REQUIREMENT BEFORE YOU START :-

- Make a NANDROID BACKUP

- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and

- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),

- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator

- If your build.prop has an additional build properties section the line of code needs to go in there

(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)

How to replace OR tweaks Build.prop :-

1. Download Es File Explorer ((OR ANY APP LIKE IT))

2.CLick menu, settings, check Root Explorer and Mount File System

3.Copy the Build.prop file into the sd card and copy with file manager

4.Click Favorites tab, Click Phone icon /

5.Navigate to system/

6.Rename build.prop to build.bak

7.Paste build.prop you copied earlier Reboot! Done! :good:

Build.prop tweaks((UPDATED 19-Oct))

Add these at the end of your build.prop

IN THE ATTACHMENT

~ Free Up More RAM, Make Apps Load Faster ~

1) Open Terminal Emulator on phone or adb shell from PC and type the following.

su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y

As shown:

((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))

​

2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite

.

(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)

dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y

As shown:

((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))

​

After this, run these two commands in adb shell or terminal emulator

rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot

3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:

rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*

**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**

How to UNDO this tweak

Type the following in adb shell or terminal emulator

((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))

su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot

So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.

Init.d tweaks ((UPDATED 19-Oct))

(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)

Note:1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh

2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work

I COLLECT A LOT OF THEM
AND I PUT THEM IN TEXT
IN THE ATTACHMENT
AND DELETED WHICH IS DUPLICATED
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASHABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASHABLE ONE

sysctl tweaks ((UPDATED 19-Oct))

To make them work:

1. make a new file in /system/etc/init.d, name it sysctl tweaks

2. make a new file in /system/etc, name it sysctl.conf

3. Paste the right code in the right file ;)

-

To activate sysctl tweaks

#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p

-sysctl.conf

IN THE ATTACHMENT