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

Siyah Gingerbread kernel (v2.x)

Find the straight 2.2 better than nolog. But little on it I think.

I'm giving the, "straight" version a go for awhile using smartassv2 and I/O scheduler, sio to see how it compares with the nolog version on lulzactive with cfq.

No problems on either so far.
 
Why use different governors and schedulers?

Because the various governors and I/O schedulers can give differing results in performance depending upon your needs and usage.

For a full explanation of the governors used in Siyah, see here:-

xda-developers - View Single Post - [REF] Quasar kernel governors and I/O schedulers manual

and here:-

xda-developers - View Single Post - [KERNEL] SiyahKernel v2.2 - "One kernel to rule them all" (SAMMY&AOSP ROMs)

For details on the I/O schedulers and their attributes, see here:-

xda-developers - View Single Post - [REF] Quasar kernel governors and I/O schedulers manual

It may help to explain why some people endured lags, etc; whilst others did not. Certainly this was very noticeable in some of the betas I tried.
 
One to read through when I've got a bit more time I think. Thanks old boy.

I'm sure that someone like Slug or hawker who are, I believe, more knowledgeable on the subject could advise you better.

Me, I just use trial and error and try each combination until I find one that seems to be the best for me.
 
No, I set the CPU freq steps & voltages in an init.d script.



In the same way. There's a good primer with useful examples of syntax here.

Good pointer Slug, thanks!

Great stuff guys, I've got a heck of a lot to learn... gets quite daunting when the amount of data exceeds my attention span by 2000+%!! :D

I'm with Sydney on preferring straight 2.2 to nolog, smoother feel, plays nicer with the governors and better battery.
 
Why use different governors and schedulers?

As Ironass stated, different combos can subtly alter the way the device behaves.

Governors make a more obvious difference as they change the frequency ramp up/down parameters as well as the idle behaviour. I'm still fond of the "price vs performance" of smartassv2, but now I've got a baseline I'm going to run lulzactive for a few days as a comparison.

Schedulers are more of a black art.... my own limited experience gives little-to-no discernable difference between sio, cfq and vr in day-to-day use. The vr scheduler gives consistently better results in flat-out benchmarking in tandem with the performance governor though. The bfq appeared to induce a bit of lag in some operations but that may simply be a reverse-placebo effect as I had nightmares with bfq-enabled kernels on my Hero. I intend to try noop next.
 
Siyah 2.2i and 2.2i nolog are up! :D

"Consider this as a service pack release. there are some stability changes & bugfixes.
removed compiler optimizations. yes, almost all. and used older codesourcery compiler.
ondemandx features are removed from ondemand governor and re-enabled 40seconds init delay.
ondemandx governor added back as module.
some rollbacks to linux kernel 2.6.35.14 for some files which can improve the stability.
new mali drivers, although they do not improved performance for me, I kept them.
increased CIFS maximum buffer size to 64k
changed lowest brightness back to stock value but added some more steps to the gamma set to have lower (not as low as in the previous version) brightness for low light conditions. highest level will be a little lower than before. in this release, there is no potentially unsafe modified values for our amoled screens. all values used in this release are from samsung’s stock kernel.
"


Wakey! Wakey! Do try and keep up boys and girls. I wonder how many of you will be scrambling over breakfast to install these... all except Shotgun84 who will do it at work as usual!

(It might pay to use the Universal Kernel Script and to temporarily disable SetCPU changes to governors and voltage, when initially installing, to prevent any conflicts)
 
Wakey! Wakey! Do try and keep up boys and girls. I wonder how many of you will be scrambling over breakfast to install these...

Sod that.... copying to /sdcard as I type. :D

No doubt I'll be restoring from nandroid over breakfast. Oh well, nothing ventured nothing gained.
 
Sod that.... copying to /sdcard as I type. :D
Oh well, nothing ventured nothing gained.

:D:D:D

I am also reminded of that other well known maxim...

"Fools rush in where angels fear to tread" :eek:

I'm playing with it now in bed... not 100% convinced about it. May need to play with it a bit longer.

UPDATE

Played with it for a couple of hours and tried various governors and scheduler combinations... and I'm back on Siyah 2.2.

I'm afraid that, for me, 2.2i was jerky and laggy in scrolling and nowhere near as smooth as 2.2. Don't let me put you off though... it may be different for you.
 
Wakey! Wakey! Do try and keep up boys and girls. I wonder how many of you will be scrambling over breakfast to install these... all except Shotgun84 who will do it at work as usual!

However did you know? The app draw seems nice and smooth but there is definitely a noticeable lag with the browser. Will keep it on for a while though and see if I can get it sorted.

I'm playing with it now in bed... not 100% convinced about it. May need to play with it a bit longer.

Too much information mate. Oh sorry you mean your phone, my bad:D
 
Siyah 2.2 - works very well. no probs at all for the moment, thou i havent got time to test o/c but will do soon and we`ll see :)
 
Because the various governors and I/O schedulers can give differing results in performance depending upon your needs and usage.

For a full explanation of the governors used in Siyah, see here:-

xda-developers - View Single Post - [REF] Quasar kernel governors and I/O schedulers manual

and here:-

xda-developers - View Single Post - [KERNEL] SiyahKernel v2.2 - "One kernel to rule them all" (SAMMY&AOSP ROMs)

For details on the I/O schedulers and their attributes, see here:-

xda-developers - View Single Post - [REF] Quasar kernel governors and I/O schedulers manual

It may help to explain why some people endured lags, etc; whilst others did not. Certainly this was very noticeable in some of the betas I tried.


Cheers ironass/slug. I understand about governors, but not schedulers, so thanks for the link re these. Badly asked original question, what I really meant was why you seemed to prefer different governors/schedulers for the 2 different siyahs? Is there a reason, or just through trial and error. Or am I being lazy and all would be very obvious if I could be bothered to read xda properly??
 
I'm playing with it now in bed...

Too much information mate. Oh sorry you mean your phone, my bad:D

Ewwwww! Thanks for that.... even pouring neat bleach into my eyes won't erase the image that conjured up! :eek:

what I really meant was why you seemed to prefer different governors/schedulers for the 2 different siyahs?

I can't speak for Ironass, but in my case I'm still experimenting to see if one is preferable over the others in everyday use.

Today I will mainly be using cfq with the lulzactive governor. :)
 
Cheers ironass/slug. I understand about governors, but not schedulers, so thanks for the link re these. Badly asked original question, what I really meant was why you seemed to prefer different governors/schedulers for the 2 different siyahs? Is there a reason, or just through trial and error. Or am I being lazy and all would be very obvious if I could be bothered to read xda properly??

Governors, more so than schedulers, are like the racing car drivers of the phone kernels if you like.

With the different kernels, or different versions of Siyah even, they have different attributes put in or removed by the developer and are like your racing cars. However, due to these developer tweaks your racing cars performance can be significantly altered.

Your usage of the phone is like a motor race. It might be the Monaco Grand Prix for speed, the Indianapolis 500 for endurance or the Paris - Dakar for a combination of both.

So, if you want a Monaco Grand Prix race which is high performance and speed from your phone then you would perhaps select Lewis Hamilton as a driver (governor) rather than, say, Jeremy Clarkson. As he will accelerate quickly and go flat out in the straights.

On the other hand, if you were in the Paris - Dakar rally you might want to choose Timo Makinen for a combination of speed and performance as well as endurance. He may not accelerate quickly but he will get you there in the long run without breaking the vehicle but still getting the most from it in the long run.

The schedulers can be likened, I suppose, to the tuning of the engines of the vehicles and can enhance their performance one way or another.

I like to run my phone like the Paris - Dakar and have the best of both speed and performance. So I tend to choose a governor (driver) like smartassv2 or lulzactive and then see which tune-up (scheduler) works best with that combination.

On the Siyah 2.2 I'm using smartassv2 and the vr scheduler which work well for me.

However, when I loaded the 2.2i last night/this morning, I found that the only combination that came close to working for me were either ondemand or performance with most of the schedulers. Even then it was, for me, not as good as the 2.2 combo.***

I postulate that this may be why Siyah beta6 was so popular in that it worked well with most drivers and liked the scheduler that came with it as most people don't tend to change their scheduler, or even their governor for that matter.

Then, as gokhanmoral tried to get the most out of his kernel and introduced a whole series of additions, omissions and tweaks to improve it we saw that more and more people were dissatisfied until, in the later betas, he started to revert and re-tweak the kernels.

This is why, when posters ask, "What is the best kernel", that there is no simple answer.

I apologise if this doesn't make complete sense as I am trying to explain it in very simple terms.

I will quite happily allow Slug or anyone else to correct me on the above but I hope it does go some way to explain the use of governors and schedulers in laymans terms... the only sort I understand.

I need more coffee! :rolleyes:

*** See following post #366
 
Siyah 2.2i revised is up! ;)

For anyone, like me, who are experiencing, "stutter" or "lag" in 2.2i, gokhanmoral, has redownloaded 2.2i with a couple of tweaks.

He has also withdrawn the nolog version as it did not seem to make any difference.

Re-downloading 2.2i to see if it is an improvement for me as I was getting a lot of, "stutter" last night.

Here is gokhanmoral's post:-

xda-developers - View Single Post - [KERNEL] SiyahKernel v2.2i - "One kernel to rule them all" (SAMMY&AOSP ROMs)


UPDATE

Just purely on a performance basis, this revised version of 2.2i is much better, for me, than the original from last night/early this morning.

In my case it works well with all governors and schedulers. :D

To paraphrase Slug, and the TV show whose name escapes me, "Today I will mostly be using vr with smartassv2".

I need more coffee!!!
 
I apologise if this doesn't make complete sense

Oh it made very good sense, but I'm still rotfl at the Timo Makinen reference. You're showing your age there, although I have a Scottish Rally programme from (I think) 1982 ticked away somewhere signed by the original Stig. :D

p.s. It was "The Fast Show".
 
Oh it made very good sense, but I'm still rotfl at the Timo Makinen reference. You're showing your age there, although I have a Scottish Rally programme from (I think) 1982 ticked away somewhere signed by the original Stig. :D

p.s. It was "The Fast Show".

That's right... the character was Jesse, played by Mark Williams. Cheers!

I racked my brains, such as they are, for a rally drivers name and the only one that filtered through was the "Flying Finn".

So glad that you think it made sense... could you explain it to me now please! :confused:
 
Tried that ICS theme and got a boot loop...the boot screen did look amazing though. :D

I don't know if it's a conflict with Launcher Pro, Green Circle Battery Mod or even the Zedge lock screen or the kernel itself... I didn't have a Nandroid backup and had deleted the ROM zip so had to flash and re-root via Odin then download and flash the zip in recovery.

Got apps and settings back via Titanium and then did the kitchen mods. One good thing, they all installed fine without going into CWM... I've been doing a second reboot after each install though to minimise the potential for boot conflicts.
 
I've tried installing those ics themes on numerous occasions and have always got boot loops no matter what I tried. I downloaded a very similar one from elsewhere which worked. I didn't like it too much anyway so I put it back to "stock" soon after.

Back on topic, i'm now trying out 2.2I revised with no issues so far.
I have a few major lags on playback of 1 or 2 hd videos, but its certainly not a kernel related problem. It may perhaps be a check ROM with camera mod problem but not sure.
 
I find lag free and conservative governors fab, get stutter on all others with 2.2i. Bit confused as to why conservative is smooth yet smart ass jerky. Doesn't seem to make sense to me. (especially when smart ass the best on beta 6). I hate things when I can't see logic behind it!
 
I racked my brains, such as they are, for a rally drivers name

Five words are all you need to know. Michelle Mouton.... driving a Quattro. :D I had a serious teenage crush on that woman. :o

Btw, 2.2i (revised ed) is performing like muck off a spade here. Smooth as silk using smartassv2/cfq, and no wakelock issues.
 
Five words are all you need to know. Michelle Mouton.... driving a Quattro. :D I had a serious teenage crush on that woman. :o

michelemouton.jpg


Somebody get a bucket of water to throw over Slug!

Btw, 2.2i (revised ed) is performing like muck off a spade here. Smooth as silk using smartassv2/cfq, and no wakelock issues.

I'm feeling the same way about smartassv2 with sio at the moment.

2.2i (revised) is definitely an improvement. I feel vindicated on my call about the original release now.
 
Back
Top Bottom