yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] a1exander:
I thought miui browser could download zip files, but ill try another browser. :)
[Galaxy S II Original Android Development] brack11:
in changelog of v2.6.2 says "added lulzactiveV2 (thanks to tegrak). you can new lulzactive tuner app from the market to tweak lulzactive parameters." but I can see only lulzactive governor, no lulzactiveV2 am I missing something? I use setcpu

---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------

Yeah you are right it shouldnt be a problem for miui. Did you try to download any other zip files?
[Galaxy S II Original Android Development] minidou-77:
Lulzactive IS lulzactiveV2

said about a thousand time before please read next time ;)
[Galaxy S II Original Android Development] a1exander:
Other files work. Ive even tried with opera and it doesnt work. Not .tar file either. Could u please mirror the file? :/

EDIT: It worked with "non-lite" opera browser. Thx!
[Galaxy S II Original Android Development] Crazy-Silver:
Is thi kernel compatible with cw9 ?

From my Samsung Galaxy S II - Rom : CheckRomRevolution HD 4.0 - Kernel : Siyah 2.6.1 - Theme : Ice Cream Sandwich Domination 1.7

CHECKROM REVOLUTION HD BETATESTER
[Galaxy S II Original Android Development] brack11:
Sorry gokhan, I upload your file only once for the sake of request. Here is the file: http://www.mediafire.com/?dp9bzfkaud9xuy7

---------- Post added at 11:36 PM ---------- Previous post was at 11:17 PM ----------

so, I'm unique with my problem? Lulz app for some reason even doesnt ask root access, dont know maybe it's not needed...

EDIT: NEVER MIND, I found solution - I made changes first and only after everything is finished I enabled "on startup" checkbox, and now its saved.
[Galaxy S II Original Android Development] KennyLegend:
Ok... I really thought 2.6.1 was really good until now. Im using 2.6.2, perfomance script and Pikachu01's Lulzactive v2 settings.

Very very nice....and insanely fast .

For anyone using these settings and still having a bit of lag, use 200mhz as ur lowest step and not 100mhz .

I had a little lag earlier and was quite a bit miffed till i upped my lowest clock speed to 200mhz.

Thanks Gokhanmoral , Pikachu01 and of course Tegrak for this little monster ;)
[Galaxy S II Original Android Development] oblivianz:
Is it normal to have to re-select governors and change lulzactive settings everytime I reboot? Mine seems to reset itself every time I reboot..
[Galaxy S II Original Android Development] alcurtis93:
No certainly not. Delete siyah01 script in etc/init.d and make sure you click set on boot in voltage control and in the lulzactive app
[Galaxy S II Original Android Development] Jodelaplaya:
The pikachu's settings are more battery or performance friendly?

Very nice kernel Gokhan.
[Galaxy S II Original Android Development] stevehkim:
pikachu's settings are a very balanced settings. If you want battery settings please look into droidphile's page as it gives you a list of performance, battery and balanced.
[Galaxy S II Original Android Development] RotesMeerJogger:
i know benchmarks are not representative but i'm interesting on camparison of my settings before and now and follow settings give me 3739 points in quadrant. new record without overclocking :cool: :)

voltage control setting

min: 200 MHz

max: 1200 MHz

i/o sheduler: noop

governor: lulzactive

lulzactive app

inc_cpu_load: 60 %

pump_up_step: 2

pump_down_step: 1

screen_off_min_step: 5@500 MHz

up_sample_time: 16000 µs

down_sample_time: 40000 µs

smooth and fast. great job once again gokhan!
[Galaxy S II Original Android Development] Jodelaplaya:
Ok thx, i'm gonna the pikachu's and see if i have to change or if i'm satisfied.
[Galaxy S II Original Android Development] busterdev:
Sorry for asking but what is this performance script you speak of?
[Galaxy S II Original Android Development] stylez:
http://www.gokhanmoral.com/gm/2011/12/19/siyahkernel-v2-6/

_____________________________________________________________________

gokhanmoral,

thx for the implementation of j4fs back

Running so smooth on bfq/luzv2 performance script..
[Galaxy S II Original Android Development] busterdev:
ahh i see. thanks for the link, stylez
[Galaxy S II Original Android Development] brack11:
Nah, lulzactive app resets after reboot, saved settings just once, and then keeps reset every reboot. Unusable.

Sent from my GT-I9100
[Galaxy S II Original Android Development] xavihernandez:
Hi,

I got freeze when I'm listening music - and often when i browsing mp3 library at the same time - on stock cm7 mp3 player. It happens since I have added around 7-8GB of mp3. All my mp3 files are stored on the external sdcard 32 GB from Kingston.

I/O scheduler might cause this.

It is set as sio (default setting).

I run Siyah v2.6.2. I have flashed siyah-battery.zip and have not changed anything.

Thanks for any help.
[Galaxy S II Original Android Development] CamoGeko:
Quite likely to be a CM issue, is your min freq set to 200Mhz?

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] stevehkim:
you need to set lulzactiv in voltage control to set on boot then the settings for lulzactiv app will stick. happened to me too.

miui+siyah = beast
[Galaxy S II Original Android Development] override182:
Thx mate.. now my siyah setup sticks!!!! Like finally i was looking for the solution.. didnt know that it would conflict with the generated script from VControl.
[Galaxy S II Original Android Development] :
must say after a day of using lulzactive governor with the lulzactive app and Pikachu's settings and Voltage Control settings of mine i have to say this is by far the best i have tried....Scrolling wise no issues battery tad drained but so far so good...Can not complain a bit.:)

Want to say (i know i already said it like three times today) thank you to Gokhanmoral for the excellent kernel. Now i know why it is the best around and why it is so popular and thank you to Pikachu for the settings...And to Droidphile for the sticky it gives me good reading at night to learn more...

Thank you
[Galaxy S II Original Android Development] remorema:
what about that 3rd gpu step. did you enable it ghokan? or is the max set to 267?
[Galaxy S II Original Android Development] stevehkim:
i believe the 3rd step will happen automatically.

miui+siyah = beast
[Galaxy S II Original Android Development] xavihernandez:
Yes it is set to 200Mhz.
[Galaxy S II Original Android Development] AndreiLux:
Actually Entropy is wrong and falsely convinced you too of the same in that regard.

Display controllers on LCD displays would be the ones which run on a passive matrix in the control of the transistors/pixels on the display and are those which close to non-relevant power-levels; there's also active matrix LCD screens on newer technologies but it's still irrelevant to my point: AMOLED (Active Matrix Organic Light Emiting Diodes) don't work the same and every subpixel has its voltage regulated by pulse-width modulation by the display controller and thus also logically is the component which has the power delivered to the screen. This is the difference between backlit transmissive technologies and emissive technologies, and why you always hear more about OLED driver/controller IC design wins, as they are quite more of a bigger deal and more complex than traditional controllers.

Now what would happen if you actually undervolt it in terms of power or if even that power rail indeed delivers electricity to the IC that feeds the LEDs on the screen is something I am not sure of without having data-sheets, but it makes sense that it is indeed like as I described above, and I would risk a bet on it.
[Galaxy S II Original Android Development] pikachu01:
I'm going to try and solve all the problems that you guys are having >.<

I tried BFQv3. Too much overhead and stutters while scrolling long lists. SIO is still the best governor. Based on its theory and practical tests that I've done. See more in my sig (Android Optimization Tips) for more info on SIO.

Did you try using other music players? Is it the same? Try refreshing the list. What governor are you using? Try deleting the init.d scripts and see if it solves your problem.

Siyah-performance.zip on gokhan's homepage.

It's actually more battery saving than performance based (believe it or not).

Don't think so.

Are you OCing/UVing? The aggressive CFS from ThunderBolt! might hasten the problems you'll get for aggressive OCing/UVing. Try not UVing too much and stay stock 1.2GHz and see if the problem still arises.

I will come up with scripts to tune Siyah's settings in ThunderBolt! soon. For now, the default with my lulzactive should be battery friendly enough.

This would be a little bit laggy sometimes, but still good anyways.

Did you enable battery saving when battery hits 10%? This would limit your frequency to 800MHz.

Delete the init.d script. The script itself is making the default governor as ondemand.

Use my lulzactive settings:

200-1.2GHz

inc_cpu_load: 95%

pump_up_step:4

pump_down_step:1

screen_off_min_step: 200MHz

up_sample_time: 10000us

down_sample_time: 40000us

lulzactive with my settings? :)

What caused the random reboots. Are you OCing/UVing? Is there an app you opened that caused it. Is it bootlooping? If he's a hater, then you're a moron. ;)
[Galaxy S II Original Android Development] chadouming:
You deserve a cookie for this post ^^
[Galaxy S II Original Android Development] PedroMRP:
My lulzactive settings:

100-1200MHz

inc_cpu_load: 95%

pump_up_step:4

pump_down_step:1

screen_off_min_step: 200MHz

up_sample_time: 40000us

down_sample_time: 30000us

I think that is very battery friendly and smooth, didn't experienced any lag.

Feedback about this?
[Galaxy S II Original Android Development] cwc3:
Quick question.

What gets better battery life? And why?

100MHz at 875mV (My Stable)

or

200MHz at 825mV (My Stable)

My assumption is: Clocked higher with less voltage = Finish task faster & with less juice?
[Galaxy S II Original Android Development] gh.rohit:
Very noob ques, 6 is higher value or 1 is higher value??
[Galaxy S II Original Android Development] PedroMRP:
Sorry I don't understand your question... What do you mean with 6 is higher value?
[Galaxy S II Original Android Development] koolshubh:
Which is the most stable version of Siyah kernal....
[Galaxy S II Original Android Development] gh.rohit:
When you adjust the value in lulzactive app, there you adjust 4 or something. I am asking about those values.
[Galaxy S II Original Android Development] droidphile:
1) @Those who complain about freezing/random reboots during HD Video Playback, Games or Maps before blaming the kernel, do this.

i) Set dynamic bus frequency scaling, the stock behavior

echo "disabled" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

ii) Set stock voltages for GPU

For this, simply comment out or delete the lines in your script which undervolt GPU. Or uncheck these options in Voltage Control

Too much UV on CPU or a badly tweaked governor can also cause problems, but if you have problems mentioned in Point 1, please perform i) & ii) first.

2) Before you complain about lag in app drawer or whatever, using lulzactive governor, please understand how lulzactive works.

Unlike other governors, lulzactive has only one threshold for making frequency change decisions. That's the parameter "inc_cpu_load".

This is a "cut-off-load".

If inc_cpu_load = 60 % which is the default,

when load on CPU is any value between 0 to 59, governor scales CPU down to a lower frequency (pump_down_step steps down).

and when load is between 60 to 100, governor scales CPU up.

As you noticed, load=60%: CPU scaled up and load=59% CPU scaled down. So there is only a narrow line sometimes to make scale up/scale down decisions. Clubbed with low sampling times, lulzactive tends to scale up and scale down rapidly, being the wildest of all governors.

This doesn't mean it's a bad governor. Tame it properly and it will be very loyal to you. With lulzactive app, it's easy and everyone can tweak lulzactive.

For reducing scrolling lags,

1) Increase down_sample_time (valid values are between 10,000 and 100,000)

2) Let pump_down_step take the default value 1.

This reduce the 'urge' for lulzactive to scale down very often staying on a frequency when it is required, like during scrolling.
[Galaxy S II Original Android Development] gh.rohit:
2.6.2 and 2.5.1
[Galaxy S II Original Android Development] gh.rohit:
Which is high value 1 or 6???
[Galaxy S II Original Android Development] droidphile:
What value are you talking about.

pump_down_step and pump_up_step are the no of steps to scale down or scale up. Higher these values, more steps cpu jumps down or up.
[Galaxy S II Original Android Development] PedroMRP:
I will try to answer your question...

The value 4 in the pump_up_step means that the cpu will scale up more quickly (jump 4 steps eg: if freq is at 100MHz and cpu load is at 96% the frequence will jump to 1000MHz).

The value 1 in the pump_down_step means that when the cpu load is less then 95% the cpu freq will decrease step by step.

The higher is the number the biggest is the jump.

In lulzactive app there is information about this that helps you choosing the values.
[Galaxy S II Original Android Development] gh.rohit:
Thanks for the ans

I wanted to say,

When you adjust pump_down_step or any, you get information there, higher value to performance,and lower for battery.

So i just want know, which value is higher?
[Galaxy S II Original Android Development] cwc3:
6 sheep jumped over the fence.

Pump_up_step? Higher = Less Steps to Fastest MHz

up_sample_time?: Higher = Slower. "how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency"
[Galaxy S II Original Android Development] pikachu01:
This should be battery friendly, but the 100MHz doesn't do anything much as screen of is still 200MHz. Also, the jump would be to 1GHz, which would feel a bit more laggy than 200MHz-1.2GHz.

Should be the 200MHz one?

2.6.2 is stable :) without the Siyah script (using default stock settings).

up_sample_time (lower is faster actually).
[Galaxy S II Original Android Development] cwc3:
Duh. :o

Someday I will proof read my posts. That was like me saying running the mile in 1 minute is slower then running it in 5 minutes.
[Galaxy S II Original Android Development] CamoGeko:
BFQ + Conservative is still an unbeatable combination for me. :D

SIO seems to drain slightly more battery when I test it.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] pikachu01:
The scheduler doesn't really affect battery life. It just manages which task to perform first (and group them together). BFQ tries too hard to perform backseek algorithms (when your hard disk spindle wants to spin one whole round to get to data that is at the back of the spindle). The issue here is flash disks don't have spindles nor there is any penalty in having backseeks.
[Galaxy S II Original Android Development] runedrune:
So which scheduler would you recommend? :p
[Galaxy S II Original Android Development] Auridran:
As he has said at least a couple times, SIO or noop.
[Galaxy S II Original Android Development] MistahBungle:
Yep second sio or noop.

Have tested both for extended periods and find they perform (really well) about the same. I've not found any evidence of schedulers having any effect on battery life either way in my couple months of testing. But they do definitely have a small effect on performance/smoothness.
[Galaxy S II Original Android Development] pikachu01:
SIO should be better when long I/O writes starves the CPU. It will allow the CPU to be pre-empted by other shorter tasks.
[Galaxy S II Original Android Development] AndreiLux:
So I checked the 3-stage Mali scaling and as we've known all along; the 300MHz step is indeed bollocks as it does not work and it's actually running at 267MHz at that step. The rule of "valid-frequencies-are-only-divisions-of-800MHz" still holds.

After playing around with it for an hour an 20 reboots; you can use it to scale up to 400MHz pretty finely but one has no idea what the DVFS brings since we don't have any means of actually measuring the GPU states meaningfully.

@Gökhan: it would be awesome if one could hack a time_in_state feature for the GPU. In mali_platform_dvfs.c there's the switch logic that gets executed once per "tick" and one would have just to output the current state to something à la time_in_state for the CPU, just that time doesn't really matter for us but more the percentages between states.

Anyway, I ended up with 40MHz/850mV - 133MHz/850mV - 267MHz/950mV with 90%-25%, 90%-45% as thresholds and everything is smooth and fine. I don't see any reason why you would have lower up-thresholds, unless loading up more of the GPU is more power expensive than clocking it up and keeping the units idle.
[Galaxy S II Original Android Development] pikachu01:
Have a question here:

echo 6 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel;

echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel;

Why must the default deepsleep level be set so high? 800MHz and 400MHz bus frequency.

They don't even correlate to the bus frequency control with 800MHz having 266MHz bus frequency by default.

They don't correlate to the
[Galaxy S II Original Android Development] ziroxs:
I changed the deepsleep levels as here

100Mhz/825mV CPU and 133 Mhz Bus at deepsleep is ok for me. No problems with wake ups
[Galaxy S II Original Android Development] mchu6am4:
Hi...can someone please explain why we're getting almost daily updates to this kernel...is it bugs or improvements or what?

I've been waiting for a couple of Weeks to update my phone with a stable/almost final version of the kernel but glad I've held back..
[Galaxy S II Original Android Development] ziroxs:
Thats the reason i didnt use Siyah for some weeks ;) but 2.6.2 with last improvements seems to be my standard kernel for a longer time.

"If you don't go forward, you go backwards." :D
[Galaxy S II Original Android Development] Auridran:
I thought 6 was 1200MHz? Or am I wrong here?
[Galaxy S II Original Android Development] ziroxs:
Thats depend of frequ_table you defined.

Mhz/ (CPU_ lvl)

1600 / 0

1400 / 1

1200 / 2

1000 / 3

0800 / 4

.

.

100 / 7
[Galaxy S II Original Android Development] Auridran:
My 01siyah script says 3 and 0, respectively.

EDIT: Not sure why this is a separate post. I edited my last one and it made a new post.
[Galaxy S II Original Android Development] droidphile:
+1 for that

You didn't complete the post?

Level 6 is 200 mhz and bus 2 is 133 mhz. Why're you referring to it as 800mhz cpu and 400mhz bus.

I think Siyah default is now level 4 (1000mhz) with bus 400.

Gokhan had incorporated a mechanism where voltages are set to stock while entering deep sleep and reverted to user config when device wakes up. (Don't know if it is removed in 2.6.2). Probably the bus is also statically set to 400 overriding original static bus scaling value for 800(266 or whatever) while entering deep sleep.
[Galaxy S II Original Android Development] ka2uki:
hmm....in 2.6.2 use stock rom ki3 TouchWiz luncher.IF you use voltage control app set the cpu gpu cpufreq and UV BUS and save the setting ..then reboot the phone and then go in "application" touch left led button and touch "edit" chose any one of the app move it..your phone will crash and got a FC with TOUCHWIZ...you must reboot the pnone and set the voltage control app to defult..then reboot the phone again.so the problem is gone..anyone have this problem? 2.6.1 don't have this problem~but i don't know what's cause this terrible problem.
[Galaxy S II Original Android Development] pangiotis24:
Hi gokhan.any progress on the siyah kernel 3 based on linux linaro kernel 3?
[Galaxy S II Original Android Development] ivangs1:
I have a question about "siyah-battery.zip" (from SiyahKernel v2.6_S99) and 2.6.2 kernel.

After setting pikachu01 settings in lulzactive.

Will there be a problem to flash with 01siyah and include pikachu01 settings:

At example:

#!/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 "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#Set deep sleep frequency & bus speed (L4=800 mhz and 0=400mhz bus speed)

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 "lulzactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#pikachu lulzactiveV2 tweaks

echo "95" > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load

echo "4" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step

echo "1" > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step

echo "10000" > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time

echo "40000" > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time

echo "6" > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step

#gpu clock, threshold and voltage

echo "100 267 300" > /sys/class/misc/gpu_clock_control/gpu_control

echo "65% 30% 95% 60%" > /sys/class/misc/gpu_clock_control/gpu_control

echo "900000 950000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control

#io scheduler

echo "sio" > /sys/block/mmcblk0/queue/scheduler

#brightness settings

echo "70" > /sys/class/misc/brightness_curve/min_bl

echo "0" > /sys/class/misc/brightness_curve/min_gamma

echo "19" > /sys/class/misc/brightness_curve/max_gamma

Thank you in advance.
[Galaxy S II Original Android Development] pikachu01:
Agh, sorry about that. Was working and didn't notice I left the post hanging. LOL,

And sorry about that values. Those values are from my own tweaks I'm setting up. :P

But you've answered my question about reverting to default config when waking up. Thanks!
[Galaxy S II Original Android Development] terenceleechan:
Where can I find battery and performance zips for 2.6.2? It's not in blog or OP
[Galaxy S II Original Android Development] el_liberator:
yes it's on Blog , in "SiyahKernel v2.6_S99" section ;)
[Galaxy S II Original Android Development] sierrafox:
has anyone noticed that GPU UV/OC settings don't stick between reboots? i've commented out the GPU lines in 01Siyah in init.d, except for the one set by VC. are there any other GPU tweaking scripts that are executed after init.d that could be overwriting the values?
[Galaxy S II Original Android Development] :
Those who are asking about what is highest value in the lulzactive app it actually explains to you when you set it up what is more beneficial for you. So for example. If you want more battery then the higher the value the better it is for you. Lower values better performance. That is dependant on what you are setting up though. So one setting it could be the other way round. If anyone has more questions i will gladly help. Changed scheduler to BFQ and it rocks. Smooth as hell better than sio in my opinion
[Galaxy S II Original Android Development] ziroxs:
They works very well within the init.d/ folder. No issues, you checked the syntax? I didnt use Voltage Control only the lulzactive app.
[Galaxy S II Original Android Development] sierrafox:
yup, i checked both 01Siyah and S91, and they're commented out in 01Siyah and uncommented in S91. weird.