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

Siyah Gingerbread kernel (v2.x)

I know GB kernels wont work on ICS, but will ICS kernels still work on GB?
Somehow I doubt it, but does anyone know for sure?
 
I know GB kernels wont work on ICS, but will ICS kernels still work on GB?
Somehow I doubt it, but does anyone know for sure?

Nah they don't. I remember helping a guy out who had flashed an ics kernel on GB firmware. They were stock in a bootloop until they flashed a GB kernel.
 
Sounds great Gokhan.
Looking forward to developments over the next few weeks. :D

And thanks Gokhan for all your work especially for our GS2 device over this last 10 months or so. You are truely appreciated, and good luck on your new ICS ventures! :)
 
By the way Gokhan, I've just been playing about with ExTweaks. There's an awful lot in there, and its going to open the device far more for fine tuning and tweaking. Great job as usual you and xan are doing.

A couple of suggestions for ExTweaks:

1. Can you include 2 profiles, one for battery, the other for performance, that set all the related options according to what you consider to be the optimum settings. These would form a good basis for us to perhaps tweak some more if desired.

2. It is VERY easy to inadvertently adjust settings without realizing when scrolling through the screen. If a setting has been changed deliberately and you have unwittingly changed a few others, all these settings will of course be saved when you apply them. Can you include in the app an option to revert ALL settings back to kernel defaults. I know that there is a default.prop.bak in /data/.siyah that can be copied back, but it would be nice to be able to do this within ExTweaks.

3. Due to the problem in point (2) sliders are very easy to change by mistake. Perhaps text input boxes would be better here than the sliders?
 
By the way Gokhan, I've just been playing about with ExTweaks. There's an awful lot in there, and its going to open the device far more for fine tuning and tweaking. Great job as usual you and xan are doing.

A couple of suggestions for ExTweaks:

1. Can you include 2 profiles, one for battery, the other for performance, that set all the related options according to what you consider to be the optimum settings. These would form a good basis for us to perhaps tweak some more if desired.

2. It is VERY easy to inadvertently adjust settings without realizing when scrolling through the screen. If a setting has been changed deliberately and you have unwittingly changed a few others, all these settings will of course be saved when you apply them. Can you include in the app an option to revert ALL settings back to kernel defaults. I know that there is a default.prop.bak in /data/.siyah that can be copied back, but it would be nice to be able to do this within ExTweaks.

3. Due to the problem in point (2) sliders are very easy to change by mistake. Perhaps text input boxes would be better here than the sliders?

the app has profile support and there will be 3 profiles I think (xan will decide on that). in the test version I had performance, battery and default profiles. but since there were some problems and missing parts in the implementation he postponed the profile support.

there will be a resetting button, also in the next version. we have added a special tag for that in the xml. you will be able to reset all the settings back to default. there is actually a default.profile file in /res/customconfig folder which is used during data saving and trimming the unused variables and it is also used during the first creation of /data/.siyah/default.profile. when you delete /data/.siyah/default.profile and /data/.siyah/.active.profile, new profile will be created with default settings. you can also flash siyah-resetdefaultprofile.zip from my blog to delete those two files by flashing it in CWM recovery.

and you are right. sliding is a little tricky in voltage control app as well.
you need to select an appropriate region to slide. I tried to put some long descriptions to let you slide easier. for now, I have no solution for that. textboxes are a little more tricky way to parse those kind of inputs, and harder to use. I generally apply settings one by one and when something changes when I was going between pages I just discard the last change.

we were thinking about more advanced scenarios and some export/import functionality to let users to share profile settings, but those were too complicated and would break the compatibility with other kernels.
that is why I use /data/.siyah and some other kernel will use /data/.whatever or somewhere else.. this way, you will find your settings unchanged (unless you wipe data) when you try another kernel and come back to siyah.

I talked (actually wrote) too much :)
anyway.. I hope I answered them all.
 
My two cents worth gok...

I would like to be able to save the ExTweaks settings in a named Profile, much in the same way that you can with Voltage Control. This makes it easier to switch all the settings back if a profile doesn't work or if you need to use them on future Siyah releases. :)
 
My two cents worth gok...

I would like to be able to save the ExTweaks settings in a named Profile, much in the same way that you can with Voltage Control. This makes it easier to switch all the settings back if a profile doesn't work or if you need to use them on future Siyah releases. :)

If I was the one developing that app I could tell you for certain which features would be implemented.
but I don't have enough java skills to implement such an app.
I am thinking about implementing the same either in python or mono, but it will take some time.
also, I don't want to go too much to the application side because it is the dark side :)
I was working on an OTA app but then I realized that I am doing it just because I hated knzo :p "anger leads to hate, hate leads to suffering and suffering leads to the dark side" :)
then I thought having an OTA app will just increase the overhead on me (to edit some json files which describes the filenames and versions and so) without giving the user too much advantage.

but extweaks are very useful I think, and it is very customizable.
Entropy512 could adopt it to his kernel in a day.
and it is all I need as a kernel developer: a dynamically generated interface which changes depending on implementation in the kernel and I can define the interface by editing an xml file and the actions are simple shell scripts.

I hope there will be some other extweaks implementations to set us free of "dumb-but-paid" school-project type apps.
 
Thanks for taking time to explain all that gokhan.

If sliders are the easiest to implement in this app, how about including a checkbox to the left of each slider that enables it to be changed, thus freeing up the screen to allow safer screen scrolling.....or just make the sliders narrower to free up the right hand side of the screen to allow scrolling without touching the sliders?

I hope you don't think i'm criticising mate, just trying to throw in some suggestions.
 
Thanks for taking time to explain all that gokhan.

If sliders are the easiest to implement in this app, how about including a checkbox to the left of each slider that enables it to be changed, thus freeing up the screen to allow safer screen scrolling.....or just make the sliders narrower to free up the right hand side of the screen to allow scrolling without touching the sliders?

I hope you don't think i'm criticising mate, just trying to throw in some suggestions.

you can criticize as well :)

I need to ask that to xan because he is the one who maintains the app.
the app is an implementation of the interface and we will publish a documentation describing the details. I hope there will be other implementations which, maybe, change tabs using another method (volume keys + some arrow keys on the screen, maybe)
 
Two great kernels!

NEAK and Siyah!

Two great, "developers"!

simone and gohanmoral!

Young lion... old lion!

Simba and Mufasa!

When gohanmoral launched Siyah 2.6.13, 10 days ago. I was already on the new NEAK v1.4 kernel from simone and wanted to give it a week of testing before switching to Siyah.

I gave my glowing opinion of NEAK v1.4 here:-

http://androidforums.com/4027839-post269.html

.... and I ended my review of with...

Bottom line, IMHO... if you are using a Samsung based ROM... this is the kernel to beat. :D

Well, IMHO, the old lion has not disappointed! :)

Siyah 2.6.13 is gokhanmoral's swan song for Gingerbread kernels and he is going out with a bang and not a whimper. This kernel really delivers the business.

After wiping with hawker's GS2Blitzer kernel cleaner from here:-

http://androidforums.com/galaxy-s2-...ot/469630-my-gs2-kernel-cleaning-scripts.html

I installed Siyah 2.6.13 and downloaded ExTweaks from the Market... sorry... Google Play Shop, here:-

https://play.google.com/store/apps/...SwxLDEsImNvbS5kYXJla3hhbi5leHR3ZWFrcy5hcHAiXQ..

I first of all took the easy way out and used Voltage Control to restore the very heavy u/v'ing and u/c'ing that I'd used on NEAK v1.4, thinking that this would break it... it didn't!

I then tackled the myriad of settings on ExTweaks which can be quite daunting at first... which is why you will see earlier posts on here, suggesting some stock settings for Best Battery life and Best Performance to be included in future releases.

As it turned out, I didn't end up changing too much in ExTweaks for my first test over the weekend and it seemed to work fine.

This is the result of my first run with Siyah 2.6.13 with what I call moderate usage.

Siyah2613.png


Bottom line... I said in my NEAK v1.4 review that it was the kernel to beat and, although there isn't much in it, both in terms of battery and performance...

mufasa-and-simba.jpg


... IMHO, Mufasa is still king!
 
actually there were lots to try in the kernel but I had to stop at some point.
it is an endless journey and I chose to continue my journey with ICS.
new kernel will have lots of improvements (the stock one I mean) which will already fix lots of problems with our old base.
in the meantime, I am working on the application side (as other developers do actually, except for Entropy512, Arighi and similar real low-level guys).
thank you for the review. actually you don't have to say anything good about the kernel because it was my playground and I already had enough fun.
but I am happy that you actually liked it.
remember that the battery life depend on lots of other options.
yesterday, I left a post to a turkish forum about some recommended settings.
if I were you, I would use sched_mc=0, make sure AFTR+LPA is selected.
set load_l to a little higher (such as 35), and also load_h to 80.
set rate's (all) to 100.
use ondemand governor, or use conservative with 800MHz. (conservative gives a little bit better performance than ondemand and using 800MHz may save a lot of juice if you use your device a lot)
also, I noticed that I use more GPU voltage than stock (about 50mV). you may want to underclock it.
you can use Entropy's settings. use 3-step and set frequencies to 66-16-267, thresholds to 85-25-80-40. and voltages to 900-950-1000 (or any other stable voltages that you have experienced before)
set min_bl to 50 (samsung default is 30) and min_gamma=0, max_gamma=19
if you find the screen too dim, just decrease min_bl a bit and maybe set min_gamma to 0, but using max_gamma lower than 24 will also save a lot of battery juice.

actually, you will get almost the same battery performance with any kernel using similar settings, but these can be set easily now, with ExTweaks :)
 
Thanks gokhanmoral!

Those settings will save me a lot of time and effort. :)

At least now I have a base to start with.

Would never have guessed that you would select sched_mc = 0.

Will run those settings for awhile to see how they behave.

Now, let me see... what can I do this evening with all the time I've been saved. ;)
 
Super bit of info there, thanks gokhan.

Now, can anyone help the resident thickie. I'm not 100% sure I know what I'm doing. But if I'm uv and got an init.d script for voltage control, I need to edit this script so that the gpu settings from extweaks aren't overridden. how is this done, and which bits do I remove?
 
This may be a stupid question, but I will ask it anyways.

Should I be running both Voltage Control and ExTweaks. The reason I ask is simple, both apps have schedulers and governors. I was wondering, will they conflict with each other? Or do I merely need to have them both set the same?
 
This may be a stupid question, but I will ask it anyways.

Should I be running both Voltage Control and ExTweaks. The reason I ask is simple, both apps have schedulers and governors. I was wondering, will they conflict with each other? Or do I merely need to have them both set the same?

think of extweaks (when it is used in siyahkernel's context) as an app which sets kernel defaults.
the defaults are set way before executing any init script or any service.
therefore, it will not conflict with anything.
you can use it together with voltage control or setcpu or any other tweaking app.
if you change a setting, it will be effective immediately but if you reboot the setting will only be effective before executing init scripts, and init scripts or other services may override the settings.
 
Super bit of info there, thanks gokhan.

Now, can anyone help the resident thickie. I'm not 100% sure I know what I'm doing. But if I'm uv and got an init.d script for voltage control, I need to edit this script so that the gpu settings from extweaks aren't overridden. how is this done, and which bits do I remove?

you can keep the script. but you are right, that will overwrite the gpu voltage and clock devices and extweaks will not be useful for configuring gpu settings.
if you want to remove the gpu settings part, you should have gpu_voltage_control and gpu_clock_control in some of the lines. remove those lines only.
if you don't have some fancy undervolting settings and tweaks, remove the script alltogether :)
using voltage control to undervolt is way more easier.
 
you can keep the script. but you are right, that will overwrite the gpu voltage and clock devices and extweaks will not be useful for configuring gpu settings.
if you want to remove the gpu settings part, you should have gpu_voltage_control and gpu_clock_control in some of the lines. remove those lines only.
if you don't have some fancy undervolting settings and tweaks, remove the script alltogether :)
using voltage control to undervolt is way more easier.


what a gent you are :)
 
Thanks again Gokhan.

Just curious, but if someone here was to have a dose of brain freeze and flashed your ICS kernel when still on GB, do you know what would happen?
 
Thanks again Gokhan.

Just curious, but if someone here was to have a dose of brain freeze and flashed your ICS kernel when still on GB, do you know what would happen?

the device will not boot (or bootloop, I don't know) but he will lose nothing.
he can just flash another GB kernel to get the device working again.
there is nothing destructive in the kernel's initramfs.
 
Anyone tried siyah 3.0 ICS kernel yet? What are your thoughts, i'm itching to try but I want to put the stock kernel (LPQ) through its paces first.
 
I flashed 2.6.13 *(through CWM) yesterday after running the GS2Blitser and everything seemed good. Worked great last night and half of today, then I encountered a problem. Keep in mind I never adjusted any settings.

It was about half way through the day when I pulled the phone out to use it. My screen was black no matter what I pressed, the home button, power button, or volume + or -. But I know my phone was on and working, because when I took a screen shot, I heard the camera noise.

I ended up pulling the battery out, then it powered on as normal and has been fine since......or maybe so far.

Has anyone else had this happen, or what the hell happened to mine?
 
Back
Top Bottom