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

Siyah Gingerbread kernel (v2.x)

hawker said:
*** Word of warning with Gokhan's battery,performance and default scripts. ***

If you have set defaults on boot with voltage control or SetCPU, then it will be these settings that take precedence, as Gokhan's init script is run first (01Siyah), but for example, voltage control's (S91voltctrl) will be run AFTER this, so it is this that will set the default governor etc.

Gokhan's battery.zip's default governor is lulzactive for example, so if you have set another in voltage control, you will notice this to be the one active on bootup.

You will need to remove voltage control's boot settings (or untick set on boot in SetCPU) for Gokhan's parameters to take effect.
Click to expand...

I guess I'm not using the battery zip then. Will see how it performs when I remove my settings.
 
ironass said:
Interestingly, I can set Max: down from 1200MHz down to 800MHz in both SetCPU and Voltage Control but after rebooting, CPU Spy is showing 1000MHz and 1200MHz, albeit with minimal or no usage.
Click to expand...

Same here. I think is because when the phone boots up it will be running at default for a few seconds before the init.d script changing the voltages kicks in. So the phones default will show in cpu spy as it was running at that for a few seconds but the seconds on that step shouldn't increase after your phone has fully booted.
 
hawker said:
I'm having a bit of an argument about this on the xda thread.
Why are most XDA members so up themselves? :(
Click to expand...

Rise above it old bean!

I've been following your, "discussion" and it makes perfect sense. Even to me!

Ever was it thus on xda. Which is why I reluctantly post on there, and mainly just observations, as I know my limitations.

Whilst I appreciate that it is a developers forum, there does seem to be a lot of one-up-man-ship and, in some cases, down right rudeness and bad manners
.
Makes me wonder if they ever take the time to actually enjoy their phones.

It only but helps me appreciate this forum all the more.


Shotgun84 said:
Same here. I think is because when the phone boots up it will be running at default for a few seconds before the init.d script changing the voltages kicks in. So the phones default will show in cpu spy as it was running at that for a few seconds but the seconds on that step shouldn't increase after your phone has fully booted.
Click to expand...

That's the conclusion I've come to after reading hawker's post. It doesn't affect my custom settings after that but I just thought it was worth mentioning on here and, God forbid, xda. :rolleyes:
 
Ok, cool.... So a couple of questions then, assuming flashing 2.6 kernel and the battery saving mod:

1) If I set the phone to, say, 100Mhz - 1400Mhz on Ondemandx, the phone will boot up using Gokhan's prefs (Lulzactive, etc) and then flip over to mine as above, UNLESS I set my prefs to kick in on boot in which case the phone will both boot up and maintain my prefs?

2) What is Gokhan's preferred settings for 2.6?
 
Gokhans tweaks will be applied first
then if you have any voltage control/set cpu settings that are set to load on boot, these will then be loaded. Now these settings may be different ones to the ones that are tweaked in siyah's battery zip, but then again, some may clash.
so for example, battery.zip sets min 100 max 800 lulzactive (and lots of other stuff too)
if you have voltage control saved settings to 200 min 1200 max ondemand, then these settings (not Gokhan's) will be active after the bootup has completed.
 
turbohobbit said:
Ok, cool.... So a couple of questions then, assuming flashing 2.6 kernel and the battery saving mod:

1) If I set the phone to, say, 100Mhz - 1400Mhz on Ondemandx, the phone will boot up using Gokhan's prefs (Lulzactive, etc) and then flip over to mine as above, UNLESS I set my prefs to kick in on boot in which case the phone will both boot up and maintain my prefs?

2) What is Gokhan's preferred settings for 2.6?
Click to expand...

1) Correct. It would appear that the default kernel settings kick in for a second or two before your custom settings, Set on Boot, take affect.

2) The settings contained in the 3 optimisation .zip's.
 
I thought so, but wanted to make sure. I don't think that's a huge issue to be honest, unless you like things reeeeeeeeeeeeeeally squeeky clean with regards CPUSpy readings.
 
turbohobbit said:
I thought so, but wanted to make sure. I don't think that's a huge issue to be honest, unless you like things reeeeeeeeeeeeeeally squeeky clean with regards CPUSpy readings.
Click to expand...

Shouldn't affect you as such if your Max: MHz setting is higher than default.
 
hawker said:
Gokhans tweaks will be applied first
then if you have any voltage control/set cpu settings that are set to load on boot, these will then be loaded. Now these settings may be different ones to the ones that are tweaked in siyah's battery zip, but then again, some may clash.
so for example, battery.zip sets min 100 max 800 lulzactive (and lots of other stuff too)
if you have voltage control saved settings to 200 min 1200 max ondemand, then these settings (not Gokhan's) will be active after the bootup has completed.
Click to expand...

So if I use my own startup script so I can undervolt a bit more and change the governor, it will only be these which change from the battery script. Everything else in the battery script such as deep sleep bus frequency and hotplug settings won't be overwritten?
 
Shotgun84 said:
So if I use my own startup script so I can undervolt a bit more and change the governor, it will only be these which change from the battery script. Everything else in the battery script such as deep sleep bus frequency and hotplug settings won't be overwritten?
Click to expand...

Correct.
all settings in battery.zip will apply
saved boot settings in voltage control will overwrite any previous settings.

Battery.zip:
#!/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
#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 1 > /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 lulzactive > /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

So for example, this amongst other things sets default governor to lulzactive, min 100 etc.
All the above will be set.
If however you have told voltage control min 200 max 1200 with conservative, these will then get precedence, along with any other different settings in voltage control (eg gpu etc)
My advice would be to unset voltage control's boot setting, boot up with battery.zip to get Gokhan's defaults, and THEN make your own tweaks
 
Silly question. I just installed the new kernel but where are the 3 other zips to instal after? I want to try the battery version but can't find it.
 
So am I right that to get my kernel working I should:
flash the kernel file and then choose to flash one of the battery/performance/default zip files??
 
I disabled setcpu boot settings and stopped the app in settings > applications > manage apps, then rebooted into recovery and cleared the cache and dalvik before running the cleaning script, then I flashed the S99 kernel followed by the battery zip.

Initial impressions are very good running the kernel and battery script as is, without further clocking or volting. It's ultra smooth and the screen brightness (set on auto) is more stable than it's ever been on my phone.

It's not smartass snappy but it's a heck of a lot smoother which makes the extra few nanoseconds delay in opening apps virtually unnoticeable with little or no discernible change in browser page loading speeds.

Battery seems good too, though I only had 20% during flashing so I've had to put it on charge after only minimal testing.
 
I haven't noticed any difference in battery life with the battery script, so I can imagine I had it on the battery-saving settings already. However, i'm liking my newly founded 30hr lasting battery with gaming usage since my unfortunate restoring failure :D
 
Siyah v2.6_S99 revised release.

gokhanmoral said:
good news and bad news:

good news: I fixed autorooting (and also CWMManager and ntfs-3g problems which are also related with the extraction of the payload) problem & tested autorooting by flashing stock KK5.

bad news: you have to re-download v2.6 if you need autorooting and/or ntfs-3g. there is no new version. just redownload it.

it's already 3:45am here and I did this to clear my mind from work. so, don't think I am nice & cool :p
Click to expand...

Says it all really.

This has been revised since post #740 here.

If you are not sure whether you need it or not... just flash it anyway. :D
 
Just had some impressive overnight stats. After 8 1\2 hours my battery dropped 1% and deep sleep was at 99%. I'm using the battery zip but slightly more undervolted
 
Shotgun84 said:
Just had some impressive overnight stats. After 8 1\2 hours my battery dropped 1% and deep sleep was at 99%. I'm using the battery zip but slightly more undervolted
Click to expand...

I'm getting roughly the same performance o/n. Very nice to not have to leave it charging for fear it'll die, along with my alarm. I had my phone at 1% remaining recently and managed to play 3 angry birds levels and still have time to close all apps and charge the phone!

Also my previous comment about wanting to enable deep sleep was stupid so ignore it, I must've been in a deep sleep when I posted it! :D
 
Shotgun84 said:
Just had some impressive overnight stats. After 8 1\2 hours my battery dropped 1% and deep sleep was at 99%. I'm using the battery zip but slightly more undervolted
Click to expand...

That's bl**dy good old son!

Not so much a Deep Sleep... more a short course of death! :D

I'm running mine at stock battery optimisation settings to get a feel for it before playing. I must say, that even on stock, it is very impressive.

Thinking back to when I first got the phone, 7 months ago, my battery life has roughly trebled.

Not all due to Siyah but it does play a major part along with bloatware removal and app management.
 
You must log in or register to reply here.
Back
Top Bottom