yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] bundi22:
Gokhan if you can change touch sensitivity settings to GB like fluxi rc4 then you're kernel will be the best and I will come back to it. I have been on siyah since the beginning but implementing better touch is really what completes the ICS experience on the galaxy s2!
[Galaxy S II Original Android Development] gokhanmoral:
we already have GB sensitivity values (the ones in Siyah GB kernel) when on battery.

and I think it is the default since some 3.2beta version.

I will try to change the sensitivity when on charge in the next version. but I will not change the other one.

in other words, you are suggesting something without knowing that we already have those values.

more importantly, I am not in a competition. I do not aim to develop the best kernel.

please do not come back to siyah if you aim to use the best.

there are already lots of other kernels which claim they are the best.

I do this for fun, and share.

fluxi's kernel is good. if I was a user I would either use his kernel or hardcore's.
[Galaxy S II Original Android Development] confusedmuse:
Please read what is going on in the thread at least on the page you are posting on...

And Siyah has GB touch sensitivity since 3.2b6... :rolleyes: (except on charger)
[Galaxy S II Original Android Development] bundi22:
If you flash it and test his settings it is very good. I want to be on siyah as I prefer it, especially with dual boot, and yes your settings are good since the past few versions but you have to feel the difference to know what I am talking about. This is the only reason why I am using another kernel right now. I believe he has implemented bln breathing and other things AFTER you, so I think its good if you take something good from his as well?
[Galaxy S II Original Android Development] tolis626:
Man,now I understand why you didn't make it configurable.Imagine all the fuss people would create. :eek: :p

On another note,is wifi direct kernel related?CM added it and it's kinda not working.Not that I care that much,but just asking. :)

He didn't "take" anything.Open-source means something.He is free to do so.Everyone is in fact.That's why most kernels have similar features.
[Galaxy S II Original Android Development] bundi22:
I really respect your work, have used your kernel since gingerbread roms. The setting I selected is called xxkernel gingerbread, so maybe while you may do have GB values, his setting includes his own further tweaking on top? All I'm saying is that if you can get the touch to feel as good as he did, I guarantee that you will receive positive feedback from the users of siyah kernel including myself. No hating and much respect.
[Galaxy S II Original Android Development] gokhanmoral:
it is opensource world. nobody should keep track of which is done by who.

I have already took lots of patches from myfluxi's repository. maybe he did or did not take anything from mine, or maybe he had some inspirations.

this is not a race, this is cooperating.

I only have problems with those who change author names (download abyss kernel and compare ld9040.c with the one in my repo), put their signature to scripts/sources without making anything and talking like "I did this, I did that, I fixed it, I will fix it in the next version" blah blah...

I started with compiling hardcore's kernels, cloning supercurio's repos, the most important fix in ICS kernels was made by Entropy512, and even extweaks interface is designed based on the suggestions of AndreiLux... so, the kernel is not mine. I only make small changes and control the repository.

after making this explanation, what you feel is right or wrong, but unless you come here with a sensitivity value set your post belongs to general thread. I will not dig in those to make some users happy while I am already happy with the current sensitivity.

and it is your free will to make a choice.
[Galaxy S II Original Android Development] d3l1:
is a "import/export settings" feature planned for extweaks, because since RC2, everytime siyah is flashed all the settings are reset.

if that is necessary/forced in order to boot corretly with the updated kernel for the first time, then never mind my question. but if it's just a precaution to rule out false settings, maybe that feature would be helpful.

I'm posting this here, because imho it's closely related to the way siyah kernel behaves recently by resetting all the extweaks settings. please don't be mad or flame if you believe this post doesn't belong here.
[Galaxy S II Original Android Development] bundi22:
ok then here is my sensitivity value:

sgs2 settings: 20

vitalj value: 1 pixel

on battery:

threshold contact: 40

threshold noise: 30

motion filter: 90

on charge:

threshold contact: 50

threshold noise: 40

motion filter: 46

the motion filter setting is what needs adjusting as it is what affects how responsive the touch is (scrolling up and down)
[Galaxy S II Original Android Development] gokhanmoral:
you can backup /data/.siyah/*.profile and restore them after flashing a new kernel.

I override them because I sometimes change defaults (as in upcoming 3.2.4 version... default governor will be pegasusq)

you can compare and replace them.

there is a .ccmd5 file in /data/.siyah and it stores md5sum of /res/customconfig/customconfig.xml and if I change anything in that the profiles are reset.

but you can always write your backup back and restart.

it is as simple as: adb pull /data/.siyah/default.profile

and then "adb push default.profile /data/.siyah"
[Galaxy S II Original Android Development] gokhanmoral:
this is the first time I see movfilter being 90.

I will try that

in the next version, noise threshold values will be 40 and movfilter will be 11 for both battery and charge.

and touch threshold values will be 50 and 55 respectively.
[Galaxy S II Original Android Development] rlorange:
REPEAT:

Post all future requests, trivial musings and off topic discussion here:

http://xdaforums.com/showthread.php?t=1658647

If you are new to Siyah or noobish POST IN THE NEW THREAD LINKED ABOVE NOT HERE because I guarantee your post will not be DEV thread worthy.

PLEASE GIVE OUR MAIN MAN A BREAK. Clearly he has finally had enough. Development is stalling with useful posts being lost in the background noise.

This thread has been a polite and civilized joy full of many helpful and ecpetienced users more than willing to help with general issues....

SO LONG AS YOU DON'T POST THAT STUFF ON THIS THREAD. POST HERE INSTEAD FROM NOW ON.

http://xdaforums.com/showthread.php?t=1658647

Of course this reflects the mature and good nature of our DEV. We are in danger if ruining all of this goodwill if we don't give him some space to breathe here.
[Galaxy S II Original Android Development] spaxx24:
I cant change the auto brightness levels in settings, does that have something to do with the kernel? Im on latest Siyah and insanity.
[Galaxy S II Original Android Development] rlorange:
GM I will make a FAQ in the new Discussion thread using answers you have already posted here (often more than once) by cutting and pasting your exact words.

You can always cut and paste them again from there to here for the inevitable same question appearing here if you like lol!
[Galaxy S II Original Android Development] SPBoss:
If your on 3.2.3 try lulzactive as its been redone :) I'm using sio scheduler and its butter smooth :D smart ass gave me lag problems aswell
[Galaxy S II Original Android Development] firefox1991:
it, s only me or the last kernel is more hot thant other before,

deadline

lulzactive

up_threshold 95%

up_step: 1

down_step:3

10000 up

30000 down
[Galaxy S II Original Android Development] runedrune:
http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] SPBoss:
Hey guys just wanted to know if anyone uses 133mhz for step. I'm using it at 800mv but I'm not sure if my gpu ever throttles to that speed. Is there any way to check frequencies/temps with an overlay app?
[Galaxy S II Original Android Development] runedrune:
Post. Above. You.
[Galaxy S II Original Android Development] sachinaik:
Gok,

When you clock at 100MHz do u apply less voltage than 200MHz ?

Are each 100MHz CPU frequency steps have different voltages applied to CPU ?
[Galaxy S II Original Android Development] Bluetoth10:
call and network drops. 2G only network (900 + 1800MHz)

using wanamlite i9100xwlp9 with SiyahKernel v3.2.3 and SiyahKernel v3.2.2

modems are i9100xxlps or i9100xxlp1

2G mobile network.

Massive call drops and networks drops. I mean every 1 of each 3 calls is dropped unexpectedly and than phone is re-registering in network (no network sign and than some signal bars). Also after unlocking often I can see that phone is registering (no network sign and than some signal bars). Working area is covered with not so good 1800MHz GSM network, but at home coverage is very good (900 and 1800). And call drops happens in both areas.

Reverting back to 3.2.1 no call drops at all.

Never used dual boot (but I will in nearest future). BLN disabled (don't care about it).

I've read here few posts about call drops, but didn't see any helpful response.

I started to use SiyahKernel because with this kernel I have best connection (fast speed and rock stable) on my work and home wifi network. Tryed different modems.

And issue with calldrops in SiyahKernel v3.2.3 and SiyahKernel v3.2.2 is really important for me.

Will try new SiyahKernel v3.2.4 as soon as it becomes available
[Galaxy S II Original Android Development] tenchi0205:
Does the latest HydrogenICS 12.05 have wifi problem with siyah 3.2.3?
[Galaxy S II Original Android Development] ICDeadPpl:
2nd rom cache wipe

I noticed that in the dual boot options in recovery, it says "wipe data/cache".

Does it delete all apps and app data as well, in addition to wiping cache?

I'd like to have them separated, so I can wipe cache and dalvik, without wiping the data partition.
[Galaxy S II Original Android Development] runedrune:
Ah come on.

http://xdaforums.com/showthread.php?t=1658647

That's the thread you're looking for.
[Galaxy S II Original Android Development] SPBoss:
Check thread above my previous post. This thread is not for discussing tweaks
[Galaxy S II Original Android Development] tenchi0205:
:p sorry!~
[Galaxy S II Original Android Development] gokhanmoral:
v3.2.4 is up.

the main difference is the pegasusq governor.

and touch screen sensitivity value when on charge.

I did not modify the main logic of the pegasusq governor. but I thought there was a problem in up/down evaluation and sampling so I modified those a little.

let's see how it works.
[Galaxy S II Original Android Development] Frozenthunder:
What exactly is the pegasusq governor? I can't find anything about it. Also I noticed that it spends much time on the highest CPU frequency according to CPU Spy. What's the advantage of this governor?
[Galaxy S II Original Android Development] Crescendo Xenomorph:
I'm gonna test the new v3.2.4.. :cool:

But, long time ago someone said that this PegasusQ(Quad) governor is effective on quad-core only? Or you already tuned it to suit dual-core?

And I want to report about TweakGS: changing the user_mode in /sys/devices/platform/samsung-pd.2/mdnie/mdnie/mdnie directory to 1 didn't help also. The SakuraMilk's TweakGS still unable to recognize the mDNIe things. (or maybe that app is only for Sakura's kernel)

So, it only configurable via script manager for now.

The rest is working OK, no complaint at all... You're the man!! Keep up the good work!! :D

---------- Post added at 01:18 AM ---------- Previous post was at 01:17 AM ----------

Its Samsung's governor designed for multi-core CPU.

Again, do search before asking and please post this kind of question here: http://xdaforums.com/showthread.php?t=1658647 Thanks... and no offence...
[Galaxy S II Original Android Development] confusedmuse:
Great Gökhan, i could barely wait till the boot had finished to test this.

And yes - it's exaxtly as responsive as on battery now. Thanks!
[Galaxy S II Original Android Development] SPBoss:
Anyone tried 3.2.4 yet?
[Galaxy S II Original Android Development] Samhain77:
Just installed new 3.2.4... it's wonderful!! I've used it for 24hrs and still have 53% battery remaining!!

******** Obviously I'm kidding!! I wonder this is the last "stupid reply"!!!!
[Galaxy S II Original Android Development] Vaedryn:
Very nice. I am in suspense how it works :) Thanks for the new release :)
[Galaxy S II Original Android Development] naveediftikhar:
ok jus installed 3.2.4...early bug report...nothin to count upon but if i set my min freq to 100mhz...pegasusq jumps directly to 500 after 100...200-400 steps are not used at all...may i ask y..?..otherwise smooth as butter..there are few other things that i would love to knw abt in pegasusq parameter terms...but guess ill have to wait for droidphile to update his thread for us to xactly what those parameters are about...!!

awesome work again gm!!!
[Galaxy S II Original Android Development] iepurasu_poznas:
I have moved post
[Galaxy S II Original Android Development] confusedmuse:
Uhm... Pegasusq never drops below 500MHz with screen on??

On lulzactive i'm between 100MHz and 400MHz most of the time and it's smooth.

This is just extreme battery waste.

But the scaling between 500MHz and 1200MHz is so even and fast! And it's staying exactly on the needed frequenzy all the time!

Please, please let it use also the lower frequenzies!
[Galaxy S II Original Android Development] naveediftikhar:
mine does drop to 100mhz...but nothing in between..ive tried echoing few parameters to mold to my liking but still 200-400 steps no used at all...both cpu spy and volt control show 200-400 as unused steps..!
[Galaxy S II Original Android Development] gokhanmoral:
it cannot work with 25 and 50 (and maybe 100 is not a good idea) because of it's ondemand nature.

load will be high on those frequencies and it will jump to a higher freq very quickly.

I have added a small workaround to prevent that but I think it is not enough.
[Galaxy S II Original Android Development] ephraim:
@GM: Touch sensitivity on the latest version while on charger has is a little bit jerky while holding the screen down. Other than that it's good.
[Galaxy S II Original Android Development] confusedmuse:
Yes, i've read your statement about 50MHz, but i would be happy enough if it would use at least 200, 300 and 400MHz sometimes.

But i'm staring at my launcher for minutes now and it won't drop below 500MHz.

Also when opening a plain menu it doesn't drop. :(

I hope you can improve that workaround without loosing the fast scaling.

I can finally get good highscores in Pinball Arcade with pegasusq! No single dropped frame! :)
[Galaxy S II Original Android Development] Vaedryn:
Only 300/400 is not in use. Most Time my Phone is on 200 , its ok. I can't se more battery use at the moment. Looks like battery when use the phone is better now but after 1 hour no statemand.
[Galaxy S II Original Android Development] confusedmuse:
You get 200MHz?? with Pegasusq? Man... what's up now... :(
[Galaxy S II Original Android Development] Vaedryn:
Yes, 200 works finde here. Only 300- 400 dosn't work but i think this is ok. After 1 Hour use i feel the phone needs lees Battery than before. But this could be placebo.

---------- Post added at 06:34 PM ---------- Previous post was at 06:28 PM ----------

Phone most time in use , 200 works fine.
[Galaxy S II Original Android Development] Samhain77:
Mine is also using 200Mhz...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] naveediftikhar:
how come u getting 200 dude...whats ur lower freq?..if its 200 then its alrite..coz my lower is 100 and iam getting 100 but not 200 300 400!!

edit: ok jus saw the pic u uploaded...jus as i thut...pegasusq will use only ur lowest freq set through whatever app but after than its next step is 500...nothing in between!!
[Galaxy S II Original Android Development] Sepharite:
I keep getting ROM control app crashing. I don't even use it. I'm using hydrogenics ROM with this Kernel.
[Galaxy S II Original Android Development] Vaedryn:
You mean me ? i use 200/800 no 100 , look the screen ( i addet ) in my last posting.
[Galaxy S II Original Android Development] confusedmuse:
Hmmm... i'll move to discussion thread with this.
[Galaxy S II Original Android Development] Samhain77:
I'm on the default configuration... No changes... so the lower freq is 200

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] bleuxeon:
Is FREQ_MIN still a revelant value in ExTweaks? Does it still have any effect on pegasusq governor?

thanks

EDIT : answer
[Galaxy S II Original Android Development] rlorange:
Actually this brings up a good question:

There are countless apps able to display real-time and acumulated CPU freq step use but I have been looking for an app capable of showing GPU step use and do far haven't found anything.

If there was such an app it would help set thresholds better I'd imagine. Any thoughts?
[Galaxy S II Original Android Development] gokhanmoral:
I have already answered this question in general discussion thread.
[Galaxy S II Original Android Development] runedrune:
Posting in one thread only is good enough tbh.
[Galaxy S II Original Android Development] AndreiLux:
I think the UP_THRESHOLD_AT_MIN_FREQ and FREQ_FOR_RESPONSIVENESS are useless values. We never had responsiveness problems on the normal Ondemand without that code, and plus, it's hardcoded into the governor here.

if (freq_next < policy->min)
freq_next = policy->min;

[COLOR="Red"]down_thres = UP_THRESHOLD_AT_MIN_FREQ
- dbs_tuners_ins.down_differential;

if (freq_next < FREQ_FOR_RESPONSIVENESS
&& (max_load_freq / freq_next) > down_thres)
freq_next = FREQ_FOR_RESPONSIVENESS;[/COLOR]

if (policy->cur == freq_next)
return;

__cpufreq_driver_target(policy, freq_next,
CPUFREQ_RELATION_L);

And here even though you tried to circumvent the code with the edit, I think you can remove the whole block altogether:

[COLOR="red"]/* Check for frequency increase */
if (policy->cur < FREQ_FOR_RESPONSIVENESS) {
up_threshold = UP_THRESHOLD_AT_MIN_FREQ;
//up threshold result in too much fluctuation when the lowest level is < 200000 -gm
if(policy->cur < 200000)
{
up_threshold += max(DEF_FREQUENCY_UP_THRESHOLD, ( 200000 / policy->cur ) * 10);
}
}[/COLOR]

So either kill those things and keep it as it was in Ondemand (Scaling was perfect in my opinion), or make devices to make those two things configurable or even disable-able.
[Galaxy S II Original Android Development] rlorange:
GM I added your recent discussion thread post to the OP so people can better understand why you got fed. Once the message has stuck and things improve here I will tone down the "Sterness" of the language I've used because it's not your style to be confrontational or sarcastic and overly harsh on the inexperienced, so I don't want to portray you like that.

Btw. You OK with it so far? Please PM me if you want something changed or to correct any inaccuracies
[Galaxy S II Original Android Development] gokhanmoral:
I agree. those has to be configurable and maybe default value should be 85.

also, I will remove cpu_down_freq and cpu_up_freq because they are not used.

I think we will see whole new governor when sgs3 sources are released because I don't think this could be the default governor in sgs3...
[Galaxy S II Original Android Development] :
Unfortunately that doesn't work because the system does not have a way of giving out gpu-values. And from what I hear that can't be changed. Hate it too btw xD
[Galaxy S II Original Android Development] lyndonguti:
The screen sensetivty is too jiletering...;(

Always back to 3.2b5 which for me is the most perfect beta ever....
[Galaxy S II Original Android Development] AndreiLux:
I'm also wondering if you can just turn off smooth scaling for it as it has a default freq_step of 40 (40% of policy->max) as a frequency jump, making it more useful than default 100 used in Ondemand which made that value have no effect at all. It doesn't give me the apparent lags Ondemand used to when trying to set that to a lower value. This means we have then two mechanisms trying to do the same thing.

And as I wrote you in the chat, I'm also curious about the S3 governor. If they did really implement asynchronous frequencies on the CPU then for sure this governor is not part of any of that.
[Galaxy S II Original Android Development] rlorange:
Andreilux

Based on your tests on CPU power consumption, do you expect this to roughly translate to the GPU?

Since the question was raised about the merits of using a slower than stock 1st freq step. With none of normal data available like we have for the CPU, your tests and thoughts on this might be our best insight
[Galaxy S II Original Android Development] AndreiLux:
I couldn't measure any differences in 2D when lowering frequencies, but it's also hard to measure such minute differences with a multimeter. That said, I'm running on 40/133/267 since months and have no issues with it. 2D rendering on the GPU is stupidly easy and even at abnormal low frequencies it should run smooth. The GPU has I think even internal power management on the four pixel processors turning them off when in low load. And if it makes you sleep better at night, know that the upcoming T-604 has 5 to 6 steps with a minimum frequency of 50MHz, so it can't be bad.
[Galaxy S II Original Android Development] It_ler:
For those who are interested in kernel benchmark and battery tests:

Here are my latest results including SiyahKernel v3.2.3 => http://xdaforums.com/showpost.php?p=26222174&postcount=36
[Galaxy S II Original Android Development] droidphile:
If at all anyone is interested, here is a small write up on pegasusq. It would be better if you read after XDA recover from this weird font, font-size and some BB code issues.
[Galaxy S II Original Android Development] Crazy-Silver:
On cm9 when i press on the screen durin scrolling the screen "vibrates".....

Sorry for my bad english

Samsung Galaxy S II Powered by CyanogenMod 9 + siyah
[Galaxy S II Original Android Development] rlorange:
Great info man! You're the frequency myth buster. What is it with Samsung using so few frequency steps? For both CPU and now GPU.
[Galaxy S II Original Android Development] crisgen:
I have a little and unusual problem with my device since I installed version 3.2.2 and later with 3.2.3.

Before going to bed I put the phone to charge and select the alarm.

The next morning the alarm did not work and time on the lock screen remains stationary since the battery has finished charging.

Just unlock the phone and adjusts itself time and the alarm begins to ring.

it is as if the phone is unable to wake from deep sleep. Sorry, I'm a noob and my english is very bad.

I had thought that the cause could be the default frequencies too low of the versions 3.2.2 and 3.2.3 and then the phone could not get the power needed to resume normal operation.

Now I put the 3.1.2 which did not give me any problems but there is someone who has had a similar problem?

The cell is as in signature, and I have already tried to reinstall the rom, various wipes and fix permission.

Sorry again and thx for eventually help about this issue:)
[Galaxy S II Original Android Development] It_ler:
As I am curious, I recognized two little changes not mentioned in the changelog for SiyahKernel v3.2.4 and I want to know if there is a special reason for changing it:

1.

Busybox is back on "old" 1.19.4-cm9 version.

On previous SiyahKernel v3.2.3 it was 1.20.0-cm9.

Any reason for going back?

2.

And in SiyahKernel v3.2.4, I can no longer find the simple CPU undervolting option (-x mV for all levels) in ExTweaks you indroduced in v3.2.3.

Any reason for removing this option?

EDIT:

I made a mistake and flashed SiyahKernel v3.2.b4 instead of v3.2.4.

After flashing SiyahKernel v3.2.4, everything is fine - simple CPU undervolting option in ExTweaks and new BB version 1.20.0-cm9.

Sorry for inconvenience.
[Galaxy S II Original Android Development] runedrune:
Undervolting still there for me.
[Galaxy S II Original Android Development] :
@it_ler

Sure you flashed the right kernel? I don't know about busybox, but I sure have the undervolting.