[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ReedX50v:
Scripts

Updated August 18: v2.6! New Scripts! Updated Old Scripts! Compatible with Cymbaline v2.6+​

Because apps are unreliable, I've written a bunch of init (i.e. boot) scripts to configure the OC / UC / GPU / Governors / Scheduler / UV / BLN / etc. in Cymbaline v2.6. They are loaded into flashable zips for you to easily install and uninstall as you please.

You can simply flash it and forget it… OR customize them… OR use the scripts as an example to make your own.

The advantages of using an init script include:

Settings are applied every boot.

No need for a background program / app eating CPU cycles and RAM.

Guaranteed compatibility with Cymbaline v2.6/v2.7 [and any future version so long as the features (MHz, Govs, IO, etc.) are still there.]

You can still mess with the settings with an app / adb / terminal once you have booted (just don't choose "set at boot").

Nothing is permanent! Simply remove the scripts & reboot to return to stock settings.

The disadvantages:

A slightly greater hassle installing, than touching a dial in an app.

Your apps may override the script's settings (i.e. you told the app to set at boot, but it won’t cause problems otherwise).

============================

- CWM_Cym_AllScripts-Uninstall_REVERT_v2.6.zip - Uninstalls any and all of the scripts ever included here. Use it in the unlikely event you have a problem or just want to go back to the defaults. This zip will ONLY remove the scripts included here, while leaving your ROM's original init scripts intact.

============================

[Directory: /01_Back_Light_Notifications/]

- Simple enable (ON) script for Cymbaline v2.6. More advanced features (like time-outs & blinking) require an app to run them.

- Since BLN is disabled by default, simply flash the "CWM_Cym_2_BLN_OFF_Script-Uninstall_REVERT" Zip to disable it again.

============================

[Directory: /02_CPU_Frequencies/]

- Four types: Dual core OC/UC with 192MHz as the minimum, Dual core OC/UC with 384MHz as the minimum, Single core OC (CPU0) with the second core (CPU1) set at the default 1,512MHz, OR Single core UC (CPU1) with the first core (CPU0) set at the default 1,512MHz.

Dual core UC/OC with 192MHz as the minimum:

- CWM_Cym_CPU_192-XXXXMHz.zip - Where "XXXX" is the max frequency.

- Max frequency options include: 1026 MHz, 1080 MHz, 1134 MHz, 1188 Mhz, 1242 Mhz, 1296 MHz, 1350 MHz, 1404 MHz, 1458 MHz, 1566 MHz, 1620 MHz, 1674 MHz, 1728 MHz, 1782 MHz, or 1836 MHz. (1,512 is the Default, so don’t flash a CPU zip to keep it).

Dual core OC with 384MHz as the minimum:

- CWM_Cym_CPU_384-XXXXMHz.zip - Where “XXXX” is the max frequency.

- Max frequency options include: 1026 MHz, 1080 MHz, 1134 MHz, 1188 Mhz, 1242 Mhz, 1296 MHz, 1350 MHz, 1404 MHz, 1458 MHz, 1512 Mhz, 1566 MHz, 1620 MHz, 1674 MHz, 1728 MHz, 1782 MHz, or 1836 MHz..

Single Core Over-Clock Only:

- CWM_Cym_CPU_OneCoreOC_192-XXXXMHz.zip -Where “XXXX” is the max frequency. ONLY CPU0 is over-clocked. CPU1 remains at the default 1,512MHz.

- Max frequency options include: 1566 MHz, 1620 MHz, 1674 MHz, 1728 MHz, 1782 MHz, 1836 MHz.

Single Core Under-Clock Only:

- CWM_Cym_CPU_OneCoreUC_192-XXXXMHz.zip -Where “XXXX” is the max frequency. ONLY CPU1 is under-clocked. CPU0 remains at the default 1,512MHz.

- Max frequency options include: 1026 MHz, 1080 MHz, 1134 MHz, 1188 Mhz, 1242 Mhz, 1296 MHz, 1350 MHz, 1404 MHz, 1458 MHz,

- CWM_Cym_CPU_Uninstall_REVERT.zip This zip only removes the CPU Frequencies Script and returns you to default frequencies.

** 1,728MHz should be stable for everyone. 1,782MHz should be stable for many. 1,836MHz may be stable for some. It simply depends on your particular chip. **

** Some governors may over-ride the frequency settings here; see tunings in Advanced Scripts. **

============================

[Directory: /03_CPU_Governors/]

- CWM_Cym_GOV_XXXX.zip - Where “XXXX” is the governor. These are the governors available by default.

- Includes: Conservative; IntelliDemand; Interactive; OnDemand (Default, no need to flash this to stay with OnDemand); OnDemand_Sammy; Performance; PowerSave; & UserSpace. [ All of the standard govs will be applied to both cores, which SystemTuner & SetCPU won't do.]

- CWM_Cym_GOV-Uninstall_REVERT.zip Only removes the Gov Script to return you to default, OnDemand.

[Directory: /03_CPU_Governors/Additional_Modular_Governors/]

- Cymbaline v2.6 also comes with additional kernel modules that can be installed to use even more governors.

- CWM_Cym_GOV_01_Enable_ALL_Modules.zip This Script will install ALL the governor modules on boot. This is not necessary if you are using another script to enable a specific governor, but it is useful if you want them all to be available for your apps, or whatever, to determine what you like. Don't use it for the long-term to save some RAM and preserve stability.

( CWM_Cym_GOV_02_Disable_ALL_Modules.zip simply removes this script, but will otherwise leave your governor settings intact).

- CWM_Cym_GOV_XXXX.zip - Where “XXXX” is the governor. These scripts install and set only that particular governor.

- Includes: Adaptive; Badass; BrazilianWax; HotPlug; LagFree; Lazy; Lionheart; LulzActive; OnDemandX; PegasusQ; SavagedZen; SmartassV2; & Wheatley.

** NOTE: ONLY Badass, Lagfree, lazy, Lionheart, & Wheatley will apply to both cores (CPU0 & CPU1); All the other modular governors became unstable when applied to CPU1. This won't really affect your performance because CPU1 should only be kicked on when needed and, at that point, OnDemand ramping it up quickly is probably preferable anyhow. This behavior may be related to the multi-core-aware nature of these governors or their own hot-plugging logic conflicting. The code is still there, but commented-out if you want to experiment with it. **

============================

[Directory: /04_GPU_Frequencies/]

2D-Mode GPU Freqency:

- CWM_Cym_GPU_2D_XXXXMHz.zip - Where "XXXX" is the max frequency.

- Max frequency options include: 96 MHz, 160 MHz, 228.57 MHz, 266.67 MHz, & 270 MHz. [ 200 MHz is the Default, don't flash a 2D zip to stay on it.]

3D-Mode GPU Freqency:

- CWM_Cym_GPU_3D_XXXXMHz.zip - Where "XXXX" is the max frequency.

- Max frequency options include: 177.78 MHz, 200 MHz, 228.57 MHz, 270 MHz, 300 MHz, & 320 MHz. [ 266 MHz is the Default, don't flash a 3D zip to stay on it.]

- CWM_Cym_GPU_REVERT_2D-200_3D-266.zip - Uninstalls both the 2D and 3D frequency scripts to return you to the default, 200MHz in 2D-mode and 266 MHz in 3D-mode.

============================

[Directory: /05_IO_Schedulers/]

- CWM_Cym_IOScheduler_XXXX.zip - Where “XXXX” is the scheduler. Includes: CFQ (Default, no need to flash this if you want to stay on it); Deadline; Noop; BFQ; SIO; & VR.

- CWM_Cym_IOScheduler-Uninstall_REVERT.zip - Only removes the IO Script and returns you to the default, CFQ.

** Recommended: SIO or BFQ. Noop is probably the fastest, for benchmarks, BUT it will cause lags in the user interface because it will not gracefully interrupt its current task to process UI tasks (like scrolling). **

============================

[Directory: /05_Under-Volting/]:

Device makers resort to higher voltages than necessary because it allows them to use chips that come off the manufacturing line with varying degrees of quality and they cannot cater to each individual chip’s ability. Chances are good your chip can perform fine with lower voltages. If so, it will run cooler and use less power. (Volts * Amps = Watts).

- CWM_Cym_UV_Optimal.zip: The previously posted voltages. After weeks of daily-driver use and per frequency stress testing, they seem to be about perfect.

- CWM_Cym_UV_Conservative.zip: Slight UV for some benefit with greater chances it will be fully stable on the majority of phones (25500-50000mV)

- CWM_Cym_UV_Aggressive.zip: As LOW as I can go and still be stable; this is now my personal daily-driver UV profile.

- CWM_Cym_UnderVolt-Uninstall_REVERT.zip: Only removes the UV script.

** Recommended: CWM_Cym_UV_Optimal.zip. If you are cautious, start with “Conservative,” then try “Optimal,” and then, if still stable, try “Aggressive.” **

** Your system may not be stable on the same voltages, if it isn't, delete "x23_Cym_UV" from your init.d folder or flash the revert zip. **

That said, I have extensively tested all frequencies with the voltages provided here. Each frequency and voltage survived multiple Quadrant, AnTuTu, Chainfire’s Benchmark, SuperPI dual-thread, KFS, RayTracer, and multi-threaded LinPack runs before it was added to the scripts.

Voltages Compared to Cymbaline’s Defaults:

MHz:	Default mV:	Conservative:	Optimal:	Aggressive:
192:	812500	812500	812500	812500
384:	875000	825000	812500	812500
432:	887500	825000	812500	812500
486:	912500	850000	837500	812500
540:	925000	875000	850000	812500
594:	937500	900000	862500	812500
648:	950000	900000	875000	812500
702:	975000	925000	900000	825000
756:	1000000	950000	925000	825000
810:	1012500	975000	937500	825000
864:	1037500	987500	962500	850000
918:	1037500	1000000	962500	862500
972:	1037500	1000000	962500	862500
1026:	1050000	1000000	975000	900000
1080:	1062500	1012500	987000	900000
1134:	1075000	1050000	1000000	912500
1188:	1087500	1062500	1012500	937500
1242:	1100000	1075000	1025000	962500
1296:	1125000	1100000	1050000	975000
1350:	1150000	1125000	1075000	1000000
1404:	1175000	1125000	1100000	1037500
1458:	1200000	1150000	1112500	1062500
1512:	1225000	1150000	1125000	1087500
1566:	1225000	1175000	1150000	1112500
1620:	1250000	1200000	1175000	1150000
1674:	1275000	1225000	1200000	1187500
1728:	1300000	1275000	1250000	1212500
1782:	1300000	1300000	1275000	1250000
1836:	1350000	1337500	1337500	1337500

============================

[Directory: /07_Touch_Screen_Sensitivity/]:

- Changes the tsp_threshold. Cymbaline’s default is now between the “Moderate” and "High" options. Five options are provided here: Very Low < Low < Moderate < High < Very High.

** “CWM_Cym_TouchSense_3_High.zip” is recommended. **

- CWM_Cym_TouchSense-Uninstall_REVERT.zip Only removes the sensitivity script to return you to default; again: Moderate < Default < High.

============================

[Directory: /08_SD_Card_Speed_Tweak/]:

- This tweak affects the amount of data that is cached in RAM in anticipation of it being called. Reading from RAM is, of course, much faster and it works well for larger files (like media), but may waste IOs by reading data that is never used.

- Many ROMs already change this, but this script should over-ride that. You can choose between 128, 256, 512, 1024, 2048, 3072, & 4096 KB.

** Recommended: CWM_Cym_SD_ReadAhead_1024KB.zip. **

** To find out your current setting use ADB or a terminal emulator and enter: “cat /sys/block/mmcblk0/queue/read_ahead_kb” (without the quotes). **

============================

[Directory: /09_Advanced_Scripts/]:

============================

[Directory: /09_Advanced_Scripts/CPU_Governor_Tuning/]

--- Generally, two configurations provided for each governor: battery and performance. Since these are CPU governors, battery saving settings will necessarily cause performance drops and vice-versa. Modular Gov. Tunings are also included and will install that particular kernal module too.

--- These scripts are primarily examples, but they have all of the “tune-ables” there for you to customize. Values I didn’t change may be commented-out with “#”. Just remove the pound sign if you want to change those values.

** If you flash any of these, there is no need to flash the scripts in /03_CPU_Governors/ because these will over-write those scripts and vice-versa **

============================

[Directory: /09_Advanced_Scripts/GPU_Power_Napping/]

- A simple enable script that will prevent the GPU from lightly sleeping between rendered frames. This MAY improve framerate, BUT WILL eat power.

- Simply flash the "CWM_Cym_GPU_No-Sleep_Uninstall_REVERT" zip to return to the default behavior of sleeping between rendered frames.

============================

[Directory: /09_Advanced_Scripts/IO_Scheduler_Tuning/]

--- Tuned versions of BFQ, CFQ, Deadline, Noop, SIO, & VR. For example, CFQ has seek settings that are largely irrelevant in flash (since there are no moving parts, back seeks take as much time as forward seeks and those settings in CFQ are unnecessary). Any of these scheduler tunings are good enough to flash without further customization.

**If you flash any of these, there is no need to flash the scripts in /05_IO_Schedulers/ because these will over-write those scripts.**

============================

[Directory: /09_Advanced_Scripts/Sleep_Wake_Profiles/]

--- These profiles run a basic script that waits for the awake / sleep states to be announced and then changes certain settings. “Sleep” in this context means the screen is off, but the phone is still active and doing background tasks like updating your apps, pushing emails, playing music, GPS, taking to the network, etc. These scripts won’t solve an issue where an app is preventing the phone from going into Deep Sleep or waking it from Deep Sleep too much.

--- CWM_Cym_Sleep-Wake_384Slp-1Core_XXXXAwk.zip - Locks the maximum frequency to 384 MHz when sleeping and restores a single core overclock while awake (where XXXX is the specific maximum frequency of CPU0, and CPU1 is set to 1512 max).

--- CWM_Cym_Sleep-Wake_432Slp-XXXXAwk.zip - Sets both cores to a max of 432 MHz when the phone is asleep, on awake it sets the max clock back to “XXXX” MHz.

--- CWM_Cym_Sleep-Wake_486Slp-XXXXAwk_UV.zip – Like above, but it also changes the voltages for 192, 384, 432, & 486 MHz to “Conservative” levels while asleep and back to “Optimal” / ”Aggressive” levels while awake (812500 mV). You still need to flash an UV script from /06_Under-Volting/ to affect the other frequencies’ voltages.

--- CWM_Cym_Sleep-Wake_UV_XXXXSlp_XXXXAwk.zip – Changes the voltages based on whether the phone is awake or asleep. Where “XXXX” is the voltage profile used for each state (Cons = Conservative; Aggr = Aggressive; Opti = Optimal; Stock = Cymbaline’s default.)

--- CWM_Cym_Sleep-Wake-Uninstall_REVERT.zip – Only remove the Sleep-Wake script.

** Recommended: If you use a profile at all, use the profiles that only change CPU frequency and stick with the same voltages regardless of awake or sleep states. **

** Anything used in the Sleep-Wake profiles, like MHz, Governors, volts, etc., will over-ride those choices in the other scripts if they are different.**

** IMPORTANT: Do NOT use Sleep-Wake profiles that change the max CPU frequency with BrazilianWax, Lazy, LulzActive, SavagedZen, OnDemandX or SmartassV2 governors. Those have their own integrated setting for sleep/wake states. Tune the governor instead; See above. **

============================

CWM_Cym_Compatibility_Patch.zip - The "Compatibility Patch" script sleeps all scripts in init.d folder for 2 minutes from the start of boot. This helps with certian ROMs / Kernels (including stock) that would begin to run init.d scripts too early in boot and caused boot-loops.

This is NOT required UNLESS you have problems booting, random reboots, or your settings are not sticking after flashing a script.

CWM_Cym_Compatibility_UN-Patch_REVERT.zip - Removes only the compatibility script, of course.

** While this patch helps these scripts run on stock / "modded" kernels, please do not post in the Cymbaline thread about it. Post in Q&A, the other kernel's thread, or PM me.**

============================

1) Extract the contents of Cymbaline_All_Flashable_Scripts_v2.6.zip to your internal or external SD.

2) Boot into recovery (CWM or TWRP) and flash what you want.

3) Reboot

** Version 2.6 Scripts do not have to be uninstalled before you flash another of the same type; they will overwrite each other.**

** BUT, if you used an earlier version of these scripts: run the REVERT zip or manually delete the old scripts. **

OR:

1) Extract Cymbaline_Scripts_Manual_Install_v2.6.zip to your SD.

2) Use a file explorer with root access and copy your desired scripts to:

/system/etc/init.d/

3) Set the permissions so that the script can execute (rwx-rx-rx).

4) Reboot.

** Don't change the file names and keep the REVERT zip handy in-case you run into a problem! **

OR:

1) Extract Cymbaline_Scripts_Manual_Install_v2.6.zip to your SD.

2) Use Script Manager or Root Explorer's Linux script handler to execute (i.e. run) the scripts.

3) Settings will return to stock / defaults on Reboot.

============================

============================

1) Flash CWM_Cym_AllScripts_Uninstall_REVERT_v2.6.zip.

OR:

1) Delete the scripts manually from /system/etc/init.d/

- There may be up to 13 scripts, depending what you have installed:

--- Version 2.6: "00_1_BootWait"; "x19_Cym_GOV_Mods"; "x20_Cym_IO"; "x21_Cym_GOV"; "x22_Cym_CPU"; "x23_Cym_UV”; “x24_Cym_SlpWake”; “x25_Cym_BLN”; “x26_Cym_SD_KB”; “x27_Cym_Touch”; "x28_Cym_GPU_Pwr"; "x29_Cym_GPU_2D"; & "x30_Cym_GPU_3D".

--- Version 2.0: "x20_Cym_IO"; "x21_Cym_GOV"; "x22_Cym_CPU"; "x23_Cym_UV”; “x24_Cym_SlpWake”; “x25_Cym_BLN”; “x26_Cym_SD_KB”; & “x27_Cym_Touch”.

--- Original Scripts: "20_Cym_IO"; "21_Cym_GOV"; "22_Cym_CPU"; & "23_Cym_UV”.

============================

============================

- Editing is simple. Just follow the example of my scripts. Any of the values can be changed by modifying whatever is in the quotes.

- But, DO NOT use windows notepad or similar text editors that won’t preserve the Linux end of line formatting. Instead, use Notepad++ (which is also good for looking at smali code).

- If you don’t know what something does, just copy & paste the string into Google.

=============================

=============================

NEW: Version 2.6 for Cymbaline v2.6/v2.7:

- All init scripts in flashable zips:

Cymbaline_All_Flashable_Scripts_v2.6.zip

- Just the scripts for editing or manual install + REVERT Flashable Zip.

Cymbaline_Scripts_Manual_Install_v2.6.zip

OBSOLETE: Version 2.0 for Cymbaline v1.5/v1.6:

- All init scripts in flashable zips:

Cymbaline_All_Flashable_Scripts_v2.zip

- Just the scripts for editing or manual install + REVERT Flashable Zip.

Cymbaline_Scripts_Manual_Install_v2.zip

=============================

Version 2.6 Change Log

Version 2.0 Change Log

=============================

Hope this is useful. :)

Please remember to hit Mohan's "Thanks" button for the awesome Kernel and tech support!