[KERNEL][CWM] TerraSilent 1.3.5 for Galaxy 4.0 (YP-G1) INTL & USA (22/06/2012)

TerraSilent 1.3.5

Well sorry for the /data partition, I don't know why, but it's stuck at RFS. I format it, I tried everything, everytime you relaunch the recovery and try to mount the partition, it mount it as RFS and wipe it out.

I advice you to let it as RFS or, change it to ext4 when you are sure you won't need to do further change in it from the recovery.

Click to expand...

Click to collapse

• All features of R3 of Klin Kernel (see below)
• Battery life improvement using the patch of Entropy512
• Jhash3
• Optimized CFS (process scheduler)
• A lot of memory tweak
• TinyRCU
• New Governor created for the kernel (based on smartassV2) : TerraSilent (I recommend you to use it)
• CleanCache (using zCache) (see below for explanation)
• zRam (see below for explanation)
• Updated crc32 algorithm (that is quite used everywhere in the kernel)
• Using optimized Sha1 algorithm
• Lzma compressed initramfs
• Swap enabled
• New Boot logo (same image (but bigger) as the one in the begin of the Thread)

• V(R), BFQ, SIO Scheduler
• OC to 1.2GHz
• ClockWorkMod (recovery)
• interactiveX, smartassV2, ondemandX, and the default governors.
• Netarchy/coolbho3ks SoD patch from Entropy512's source (allows you to use screen off profiles of under 800Mhz)
• Ext4 support
• Voodoo Sound
• etc ... see http://xdaforums.com/showthread.php?t=1601773

• [RECOVERY] Optimization of the recovery with better use of the busybox
• [RECOVERY] Can save the /dbdata partition in nandroid
• [USA] Added VOODOO FM

• [CHANGE] Zram built-in not a module anymore
• [BUSYBOX] Updated busybox to last version 1.20.1 meaning any init.d script will be launched with that version.

• 
  [MAJOR BUG FIX]Corrected a bug with the recovery that wasn't able to mount correctly the /data partition, it was leading to a complete wipe of data when applying ZIP that needed that partition to be mounted
• [OPTIMIZATION]Using LZO Compression for ZRam also, after some test, I discover that Snappy compression is not really optimized on our device.

faux123 said:

CleanCache (via ZCache backend)

ZCACHE is a new technology I introduced to Sensation Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.

Source : http://xdaforums.com/showthread.php?t=1359951

Click to expand...

Click to collapse

faux123 said:

ZRAM (aka CompCache aka RAMZSwap)

ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.

Source : http://xdaforums.com/showthread.php?t=1359951

Click to expand...

Click to collapse

Dark_Balor said:

TerraSilent Governor

TerraSilent is completely based on the SmartAssV2 kernel with some improvement for the battery. When you are putting your device on sleeping/suspend, it's changing the frequency to 100Mz (if you set a minimum higher then that, it will be used instead) to avoid using too much battery when not needed, you can still listen to music without any lag. (if you experience some lag just change the minimum to 200Mhz).
It also less aggressive on ramp up the frequency, instead of always trying to reach the ideal frequency (400Mhz by default, I'll explain for tweaker all they can change if they want) it will try under frequency first (200Mhz if you were at 100Mhz before). Meaning using less battery.
By default when the load >= 85%, it will ramp up the frequency and if its lower than 35, ramp down it to an new frequency calculated using the current load.

Click to expand...

Click to collapse

insmod /lib/modules/zcache.ko

mkswap /dev/block/zram0
swapon /dev/block/zram0

 echo terrasilent > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

debug_mask            --> for debug (possible value 0(disabled),1,2,4)
up_rate_us             --> µs to wait before ramp up
down_rate_us         --> µs to wait before ramp down
sleep_ideal_freq      --> Freq used when sleeping/suspend
sleep_wakeup_freq  --> Freq use when waking up
awake_ideal_freq    --> Freq ideal for daily usage
sample_rate_jiffies  --> DON'T TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING
ramp_up_step        --> step used when ramp up in Hz (to calcule the new frequency) (0 = maximum freq will be used when ramp up)
ramp_down_step    --> step used when ramp down in Hz (to calcule the new frequency) (0 = using heuristic to found the best new lowered freq)
max_cpu_load        --> max load that trigger the freq change for ramp up
min_cpu_load         --> min load that trigger the freq change for ramp down

#! /system/bin/sh

chmod +x my-script.sh

• [BUG FIX] Should have corrected the bug with the /data corruption in recovery when in ext4 (but be careful)
• [CHANGE] Zram built-in not a module anymore
• [BUSYBOX] Updated busybox to last version 1.20.1 meaning any init.d script will be launched with that version.

klemmaniac said:

Someone else recommended Terrasilent over Steven's, but I'm just worried about performance issues from using Terrasilent after reading some posts about it. Why would you recommend Klin's R3 kernel over Terrasilent specifically? I notice in your sig you have the SGP 4.0 and are using CM11. Are there any side effects or issues that come with flashing that on the YP-G1 you've noticed? for instance, in the first post on the CM11 thread, there is a warning that the alarm may not work...I definitely need the alarm to work. have you noticed stuff like this? Any common problems I should watch out for if I flash it? Also, being a noob, I'm unsure if I need to flash a kernel with CM11 or if CM11 includes a kernel with it. Thanks for any advice and help again.

Click to expand...

Click to collapse