• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Siyah Gingerbread kernel (v2.x)

Note
For those who downloaded the first _S99 release that was taken off, Gokhan has also updated his tweak scripts. For example, the battery zip is now using ondemandx as its default governor, along with a few other adjustments.
Therefore it is worth downloading these zips again.

Battery.zip: (v2)
#
!/sbin/busybox sh

#hotplug parameters
echo 35 > /sys/module/pm_hotplug/parameters/loadl
echo 80 > /sys/module/pm_hotplug/parameters/loadh
echo 90 > /sys/module/pm_hotplug/parameters/loadl_scroff
echo 100 > /sys/module/pm_hotplug/parameters/loadh_scroff
echo 400 > /sys/module/pm_hotplug/parameters/rate
echo 400 > /sys/module/pm_hotplug/parameters/rate_cpuon
echo 1000 > /sys/module/pm_hotplug/parameters/rate_scroff
echo 524288 > /sys/module/pm_hotplug/parameters/freq_cpu1on

#cpu freq
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#deepsleep levels
echo 4 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel

#smooth scaling parameters
echo 3 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step

#cpu governor
echo ondemandx > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#gpu clock, threshold and voltage
echo "100 267" > /sys/class/misc/gpu_clock_control/gpu_control
echo "60% 30%" > /sys/class/misc/gpu_clock_control/gpu_control
echo "850000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control

#io scheduler
echo sio > /sys/block/mmcblk0/queue/scheduler

#static bus frequency
echo enabled > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

#enable sched_mc
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings

#enable AFTR
echo 3 > /sys/module/cpuidle/parameters/enable_mask

#brightness settings
echo 50 > /sys/class/misc/brightness_curve/min_bl
echo 0 > /sys/class/misc/brightness_curve/min_gamma
echo 20 > /sys/class/misc/brightness_curve/max_gamma
 
Lovely and smooth on s99. Very quick boot. What a nice kernel! Let's give it a few days to see about battery
 
I'm leaving it on stock battery.zip settings at the moment with no problems
I'll assess battery drain tonight....
 
Cheers, when I remember to I do do that :) Just wondered if I needed to do the dalvik & cache thing also, but from reading the link I guess that file does it for me anyways.

I also would like confirmation on whether clearing dalvik and cache are necessary after using the Kernel Cleaning Script or if running that script is all that's required before installing a new kernel?
 
I also would like confirmation on whether clearing dalvik and cache are necessary after using the Kernel Cleaning Script or if running that script is all that's required before installing a new kernel?

Hawkers post further up just says to run the kernel cleaning script. When reading the notes on the link he provides it mentions dalvik, so I'm assuming that the Kernel cleaner clears the dalvik & cache ready for the new kernel.
 
No need.
The script script does it. (twice in fact)

If you're updating a previous Siyah version that's all it does - none of the files scripted to be deleted exist, at least not on my handset.

I've got 06tweaks, 11link2sd, 90GTalkfix, S01sysctl, S95sdcardspeedfix, S96complete, S97ramscript, S98kickasskernel, and s99acidext4tweak in my init.d folder, presumably either from previous custom kernels and/or DlevROM. :confused:
 
hey guys,

i installed the BLN control app, but no notifications after enabling it, is there something else i need to do before, to make it work?
 
hey guys,

i installed the BLN control app, but no notifications after enabling it, is there something else i need to do before, to make it work?

No, that should be about it. Activate BLN and check your schedule BLN settings. You can use the Test section to test Led notification to ensure that it is working.

(I believe that for anyone using the CM7 ROM that you have to activate BLN in Device Settings as well.)
 
No, that should be about it. Activate BLN and check your schedule BLN settings. You can use the Test section to test Led notification to ensure that it is working.

(I believe that for anyone using the CM7 ROM that you have to activate BLN in Device Settings as well.)

now its working :D

all i did is enable the schedule and activate the led notification in the GOSMS app, thanks man
 
Hey guys am back, just been so busy. I'm moving up north back to the folks in couple of months then at somepoint going abroad, maybe for 8 months I will have the phone with but getting local sim. Now as for Siyah I installed the battery.zip and don't have any CPU set in JD, after 9hrs of lightish use in at 50% so pretty happy so far
 
No need.
The script script does it. (twice in fact)

I always wipe the cache and dalvik manually before running the script because I have found that, on my phone at least, flashing numerous kernel updates without doing a full wipe progressively increases the time it takes to reformat the cache manually, whereas the script running time is consistently just a few seconds... maybe it just deletes without reformatting?

Clearing the dalvik is always pretty much instantaneous but I manually wipe it anyway, just to make sure.
 
Just out of interest, if you flash the battery (or, indeed, the performance) tweek, is it worth using SetCPU to set your own requirements or is that in essence undoing the good work Gokhan has put in to writing the tweek in the first place? Is it better to keep the tweek and freeze SetCPU for the time being?
 
If you're updating a previous Siyah version that's all it does - none of the files scripted to be deleted exist, at least not on my handset.

I've got 06tweaks, 11link2sd, 90GTalkfix, S01sysctl, S95sdcardspeedfix, S96complete, S97ramscript, S98kickasskernel, and s99acidext4tweak in my init.d folder, presumably either from previous custom kernels and/or DlevROM. :confused:

I've noticed this slug and I've been contemplating updating the script to delete the init.d folder
 
Just out of interest, if you flash the battery (or, indeed, the performance) tweek, is it worth using SetCPU to set your own requirements or is that in essence undoing the good work Gokhan has put in to writing the tweek in the first place? Is it better to keep the tweek and freeze SetCPU for the time being?

I'm seeing how Gokhan's tweaks run before trying other governors/volt settings... seems pointless to do anything else immediately unless you flash the default zip (200-1200 MHz)
 
Oh well Syd. It was good while it lasted. :D
Your kernel will be no more soon.....:(

SiyahKernel v2.6.1
Posted on December 23, 2011
no new features, just fixes

changelog:

fixed wifi driver causing boot loops when receiving a packet before being registered.
corrected the voltage level of 200MHz (should not be a problem but I did not want to have that silly [last_level-1]=[last_level-1] line. It should have been [last-level-1]=[last_level])
disabled ARCH_POWER sched feat. (just like in v2.5.2b)
enabled CONFIG_RCU_FAST_NO_HZ (just like in v2.5.2b)
reverted back to gzip -9 compression (2 seconds faster than xz -1)
fixed auto-rooting and CWMManager app disappearing. This should also fix ntfs mounting issues because ntfs-3g binary extraction problem was also related with the same bug.
some other config cleanups.
 
Back
Top Bottom