What makes your phone even better?
If you use the stock kernel, then you may want to replace the build.prop and gps.conf files with attached files (unzip it).
These files are based on Calkulin's and Agat's Rom. Because I modified the files based on my demand, you may also want to change the files based on your situation.
Because these files are not changed after the reboot, you can replace these files with any tweaked files that you want to use.
(these files won't be changed by Kernel change but flashing rom will replace all these files)
You can use gps.conf and init.d scripts with any rom but build.prop is dependent on the rom. This build.prop is based on FD19. So, be sure that you need to modify it if it's used on different rom.
Attached file also includes the init.d scripts. These scripts are also same as on Calk's FD02 init.d scripts. I only changed few default option based on my requirement. So, if you want to original init.d scripts, please download Calk's FD02 v1.4 rom and extract the init.d scripts.
Again, all thanks should go to Calkulin and Agat if you use their tweaks.
Many thanks to sfhub for his auto root tools including init.d support
I've added one more script file (attached) which can be used alone with previous one or standalone. All these tweaks are tested on my phone and working version. If you need to edit, be sure that it's properly edited and tested before adding it to the init.d.
If you just want to use the script which runs init.d scripts during the boot without running sfhub's auto root tool, you may download the third attached file in here. Download, unzip it. Place the install-recovery.sh file to /system/etc with permission 550. This script will be executed by init.rc during the boot if you are on the stock kernel and this script will run the init.d scripts. If you are on the repacked kernel, which supports the init.d, this install-recovery.sh wouldn't do anything (init.d script will be executed by init.rc instead of this install-recovery.sh)
4/26/12 sfhub's auto root tool is updated. Check the updated information from top thread update section. http://forum.xda-developers.com/show...71&postcount=1
I've found that some attached tweaks is preventing the ondemand governer changes. So, until I find the issue and fix it, I dropped the attached files (you are still able to download the install-recovery.sh script).
:4/24/12 I fished testing Calk's CPU governor scripts and reposting it with minor changes. Adding my tweaks back to this post.
Update5: Extreme battery saver tweaks
I added one more zip file which can be used to save the battery life a lot more. If you are really concerning about your battery life and want to extend it, try this new set of tweaks. It's based on Calk's tweaks (I modified the values) and some other tweaks. If you want to use this, I highly recommend you to back up your old init.d files and replace those with the tweak files in init.d.zip files (unzip and move the files to /system/etc/init.d).
[Guide] How to mod Calk's 2cpufreq_governor
2cpufreq_governor script is quite simple/handy tool and it could replace many CPU governing tools. 2cpufreq_governor script can be used to define the CPU governor and change the options on selected governor.
1. The governor selected in this script works as a master governor to control the cpu.
Select the governor which one you want to use. In here, I used 'ondemand' as a default (value "1"). Only one governor works as master governor. If you want to use different governor, change the governor's value from "0" to "1" and reset the old governor's value "0".
(default governor on original Calk's tweak)
This governor uses more power and faster than ondemand. Under this governor, the following values are set.
If your kernel does not support this governor, it won't be enabled.
ondemand and lazy
If one of these governors is selected then the following values will be set -
interactive Performance Powersave smartass govenors
Just enables the governor. No value changes by these tweaks.
So, for most of you, only the thing you can do with this script is, just selecting the governor whichone you are going to use. If you want to change the detailed options then you can make those changes using 3cpufreq_screestate_scaling script.
[Guide] How to mod Calk's 3cpufreq_screenstate_scaling
3cpufreq_screenstate_scaling script can be used to decide how you want to deal with different phone states. Basically your kernel automatically controls most of it but if you want, you can also have a control over it using this script.
This script can be used as standalone or in conjunction with 2cpufreq_govenor script. The difference between these two scripts are , 2 works as a master governor and 3 is only based on the phone's state.
The things that you need to decide or know before using this script:
If the phone is on "awake" status then script uses the "ondemand" cpu governor and you can change the governor as you want (AWAKE_GOVERNOR). Battery save profile only can be used during this "awake" mode.
If the BATTERY_PROFILES_ON is set to "1", then script will use the various governor based on the phone's state and battery level (remaining percentage). For the most of the user, don't need to change the Calk's default settings. But in attached Calk's script, I changed a little to use only ondemand governor for any battery level.
This change would be benificial for the user who is frequently use the phones (not in sleep or lazy mode). If you want to use Calk's original script, you can extract the script from Calk's FD02 Tweaked rom.
As Calkulin already mentioned on this thread, if you are already using any CPI Tweak app like ANDROID OC, Over Click widget, Quick Lock, or SETCPU, then this script won't do anything during the awake mode and sleep mode.
Battery profile 1 and battery profile2 define how your phone reacts based on the battery level and I changed the script a little to use the same ondemand governor regardless the battery level. Regardless of battery level, this script will force to use the maximum 1000000 CPU frequencies.
If you want to differenciate the governor, you can change the governors, max CPU speed, and battery level values based on your demand. Battery profile 1 defines which governor will be used when battery level is above the value in BATTERY_PROFILE_1. Battery profile 2 defines which governor will be used when the battery level is below the value in BATTERY_PROFILE_2.
When the battery level is between BATTERY_PROFILE_1 and BATTERY_PROFILE_2, then the values defined in MAX_CPU_SPEED, MIN_CPU_SPEED and GPU_SPEED will be used.
When your phone goest to sleep mode, this script defines which CPU governor could be used. If you want to change the default CPU governor values during the sleep mode, keep the SLEEP_GOVERNOR_ON value to "1". Otherwise, set the value to "0" (this is Calk's default).
In there, the CPU Max speed will be changed to 800000 to save the battery during the sleep mode. But if you have any issues during the sleep mode, your can increase the SLEEP_MAX_CPU_SPEED value. If you want to save more battery, then you can decrease this value and this is what I'm goint to test for the next experimental test.
This is not a complete tutorial for Calk's CPU tweak but I just wanted to give you the idea how CPU tweak works. For any time, if this tweak does not work as you intended, you can change the values and/or increase/decrease the frequencies and threshold values.
The attached tweaks work on FD19 stock rom and kernel without any issues so far. But I'm not sure if it works on any other repacked kernel and customized roms. Before applying any tweaks, I recommend you to make full nandroid backup and test it. The risk of using these tweaks would be minimal at least you stay on with the values those are already tested and proven.
(attached snapshot shows the CPU times based on two modified Calk's tweaks)
(the last two snapshots are based on my extreme battery saver tweaks - CPU time & battery usage over about 10 hours)