-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Siyah kernel - Dummies Guide
- Thread starter ironass
- Start date
-
- Tags
- samsung galaxy s2
ironass
Extreme Android User
If, like me, you want to give the basic Siyah 6.0beta4 or Siyah 6.0beta5 a go on JB but find it lacks Profiles, (Profiles in Recovery are disabled in these beta versions), in the STweaks app, then here are some quick settings that you can configure...
DEFAULT
Basically this is the setting that the kernels come with and is, by-and-large, the stock settings that will give you a balance between battery and performance. As they stand, they are an improvement on the stock, Samsung, kernel IMHO.
You may want to enable BLN, (Back Light Notificaion) or increase sound in Sound on STweaks.
PERFORMANCE
CPU
DEFAULT CPU GOVERNOR = ondemand
CPU MAX FREQUENCY = 1300 MHz
CPU MIN FREQUENCY = 200MHz
MISC
DEFAULT I/O SCHEDULER = sio or vr
(Do not enable JB Power Saving in JB Settings)
BATTERY
CPU
CPU UNDERVOLTING = -50mV
DEFAULT CPU GOVERNOR = conservative
CPU MAX FREQUENCY = 800MHz
CPU MIN FREQUENCY = 100MHz (200MHz on beta5 only)
MISC
DEFAULT I/O SCHEDULER = noop
(Do enable JB Power Saving in JB Settings)
ALL CONFIGURATIONS
I uncheck in CPU, GENTLE_FAIR_SLEEPERS
DO NOT, in CPU_UV check, "Set on boot", until you are confident with your settings.
The above are just basic settings for each state that you can adjust to suit your needs accordingly. Proceed with care.
DEFAULT
Basically this is the setting that the kernels come with and is, by-and-large, the stock settings that will give you a balance between battery and performance. As they stand, they are an improvement on the stock, Samsung, kernel IMHO.
You may want to enable BLN, (Back Light Notificaion) or increase sound in Sound on STweaks.
PERFORMANCE
CPU
DEFAULT CPU GOVERNOR = ondemand
CPU MAX FREQUENCY = 1300 MHz
CPU MIN FREQUENCY = 200MHz
MISC
DEFAULT I/O SCHEDULER = sio or vr
(Do not enable JB Power Saving in JB Settings)
BATTERY
CPU
CPU UNDERVOLTING = -50mV
DEFAULT CPU GOVERNOR = conservative
CPU MAX FREQUENCY = 800MHz
CPU MIN FREQUENCY = 100MHz (200MHz on beta5 only)
MISC
DEFAULT I/O SCHEDULER = noop
(Do enable JB Power Saving in JB Settings)
ALL CONFIGURATIONS
I uncheck in CPU, GENTLE_FAIR_SLEEPERS
DO NOT, in CPU_UV check, "Set on boot", until you are confident with your settings.
The above are just basic settings for each state that you can adjust to suit your needs accordingly. Proceed with care.
ironass
Extreme Android User
Not a lot of choice Syd! Dorimanx wasn't doing the business for me on NEAT LSD and I needed a BLN kernel. I must say that I really had forgotten just how good Siyah is. Better battery on these settings than I had with the last 3 Dori releases.
Thanks for the compliment old bean!
My Battery settings are fine with HD video playback. I don't play intensive games on my phone. A tip I had from gokhanmoral was that you could save a lot more battery by u/c'ing than by u/v'ing. Hence my 800MHz with a -50mV across the board. Power Saving in JB Settings runs at 800MHz anyway.
sntaylor
Android Expert
The only thing I query about it, and I suppose as dorimanx is based on it.....
Isn't this version based on the lsj leak so won't necessarily be as buttery etc?
I don't know for definite as its just something I read elsewhere, I also like the bln so may just flash siyah again tomorrow, but I'll wait and see.
Thanks iron ass though for the guide
Isn't this version based on the lsj leak so won't necessarily be as buttery etc?
I don't know for definite as its just something I read elsewhere, I also like the bln so may just flash siyah again tomorrow, but I'll wait and see.
Thanks iron ass though for the guide
ironass
Extreme Android User
I wouldn't worry about that sntaylor... by the time gokhanmoral has worked his magic on it, it bears as much resemblance to the original as Slug does to a member of the Brazilian Women's Beach Violleyball Team!
Hawker
Android Expert
You're not wrong there syd old boy! This is the best piece of news since the lsj leak.
Been on beta4 now for a week or so now after a spate of trying out the rest of the also-rans. It's been the best of the lot for me, and I'm not just talking siyah here.
Be interesting to see what gok will put in beta5.
And I bet curiously enough, working dori kernels won't be too far behind....?
Been on beta4 now for a week or so now after a spate of trying out the rest of the also-rans. It's been the best of the lot for me, and I'm not just talking siyah here.
Be interesting to see what gok will put in beta5.
And I bet curiously enough, working dori kernels won't be too far behind....?
ironass
Extreme Android User
arty:What a gent gokhanmoral, the developer, is. He hasn't forgotten his old SGSII chums. Just read the proposed changelog, here. Looks good!
In the meantime, Siyah 6.0beta4 is doing great by me.
Now that Sammy has released the kernel source, it should make a difference for gok. As Hawker says.... Dorimanx shouldn't be too far behind.
Syd... stay away from it until the rest of us have installed it! You know what I mean. :vamp:
sntaylor
Android Expert
SiyahKernel | "One kernel to rule them all" for download.....
only tested on Samsung JB ROM. Although the kernel boots CM10.1 I will not support it until I fix dualbooting.Changelog:thanks to*mbwatson@XDA*for sending me an international Samsung Galaxy S2. Although the screen is cracked it is perfectly readable and also the touchscreen digitizer is working flawlessly.based on latest I9100 JB Kernel sourcehome key is fixed. now it works both in recovery as well as CM10.1 and Samsung ROMsincreased default gpu freqs a little bit. the lowest freq is now 108MHz.updated SuperSu.fixed CPU and I/O scheduler changes in STweaks not being applied after reboot.possible workaround for bootloop bug.added boot animation supportremoved custom CPU steps. the kernel has 6 CPU steps now (1400, 1200, 1000, 800, 500, 200)fixed stock video playerpower saving mode is now workingTODO & Known Problemsdual-boot code (both recovery and ramfs) needs to be refactored to support Samsung JB.I need to find another trick to get cam working on both Sammy and CM ROMs without losing 50MB+ RAM.cypress modifications (BLN, BLNWW, touchpad led timeout etc) should be moved to new driver sourceneeds to be tested moreTARZIP*(asserts are taken from cm10.1. if you cannot install cm10.1 with the recovery you are using then you won’t be able to install the kernel using CWM-flashable zip. the asserts are there to prevent curious&dull users hard-bricking their device and it is NOT a bug)
only tested on Samsung JB ROM. Although the kernel boots CM10.1 I will not support it until I fix dualbooting.Changelog:thanks to*mbwatson@XDA*for sending me an international Samsung Galaxy S2. Although the screen is cracked it is perfectly readable and also the touchscreen digitizer is working flawlessly.based on latest I9100 JB Kernel sourcehome key is fixed. now it works both in recovery as well as CM10.1 and Samsung ROMsincreased default gpu freqs a little bit. the lowest freq is now 108MHz.updated SuperSu.fixed CPU and I/O scheduler changes in STweaks not being applied after reboot.possible workaround for bootloop bug.added boot animation supportremoved custom CPU steps. the kernel has 6 CPU steps now (1400, 1200, 1000, 800, 500, 200)fixed stock video playerpower saving mode is now workingTODO & Known Problemsdual-boot code (both recovery and ramfs) needs to be refactored to support Samsung JB.I need to find another trick to get cam working on both Sammy and CM ROMs without losing 50MB+ RAM.cypress modifications (BLN, BLNWW, touchpad led timeout etc) should be moved to new driver sourceneeds to be tested moreTARZIP*(asserts are taken from cm10.1. if you cannot install cm10.1 with the recovery you are using then you won’t be able to install the kernel using CWM-flashable zip. the asserts are there to prevent curious&dull users hard-bricking their device and it is NOT a bug)
sntaylor
Android Expert
Try again......
SiyahKernel S2-v6.0beta5
Posted on February 17, 2013
only tested on Samsung JB ROM. Although the kernel boots CM10.1 I will not support it until I fix dualbooting.
Changelog:
thanks to mbwatson@XDA for sending me an international Samsung Galaxy S2. Although the screen is cracked it is perfectly readable and also the touchscreen digitizer is working flawlessly.
based on latest I9100 JB Kernel source
home key is fixed. now it works both in recovery as well as CM10.1 and Samsung ROMs
increased default gpu freqs a little bit. the lowest freq is now 108MHz.
updated SuperSu.
fixed CPU and I/O scheduler changes in STweaks not being applied after reboot.
possible workaround for bootloop bug.
added boot animation support
removed custom CPU steps. the kernel has 6 CPU steps now (1400, 1200, 1000, 800, 500, 200)
fixed stock video player
power saving mode is now working
TODO & Known Problems
dual-boot code (both recovery and ramfs) needs to be refactored to support Samsung JB.
I need to find another trick to get cam working on both Sammy and CM ROMs without losing 50MB+ RAM.
cypress modifications (BLN, BLNWW, touchpad led timeout etc) should be moved to new driver source
needs to be tested more
TAR
ZIP (asserts are taken from cm10.1. if you cannot install cm10.1 with the recovery you are using then you won’t be able to install the kernel using CWM-flashable zip. the asserts are there to prevent curious&dull users hard-bricking their device and it is NOT a bug)
SiyahKernel S2-v6.0beta5
Posted on February 17, 2013
only tested on Samsung JB ROM. Although the kernel boots CM10.1 I will not support it until I fix dualbooting.
Changelog:
thanks to mbwatson@XDA for sending me an international Samsung Galaxy S2. Although the screen is cracked it is perfectly readable and also the touchscreen digitizer is working flawlessly.
based on latest I9100 JB Kernel source
home key is fixed. now it works both in recovery as well as CM10.1 and Samsung ROMs
increased default gpu freqs a little bit. the lowest freq is now 108MHz.
updated SuperSu.
fixed CPU and I/O scheduler changes in STweaks not being applied after reboot.
possible workaround for bootloop bug.
added boot animation support
removed custom CPU steps. the kernel has 6 CPU steps now (1400, 1200, 1000, 800, 500, 200)
fixed stock video player
power saving mode is now working
TODO & Known Problems
dual-boot code (both recovery and ramfs) needs to be refactored to support Samsung JB.
I need to find another trick to get cam working on both Sammy and CM ROMs without losing 50MB+ RAM.
cypress modifications (BLN, BLNWW, touchpad led timeout etc) should be moved to new driver source
needs to be tested more
TAR
ZIP (asserts are taken from cm10.1. if you cannot install cm10.1 with the recovery you are using then you won’t be able to install the kernel using CWM-flashable zip. the asserts are there to prevent curious&dull users hard-bricking their device and it is NOT a bug)
ironass
Extreme Android User
Let the fun begin!
This version of Siyah will have a lot to live up to after Siyah 6.0beta4.
Well done sntaylor... managing a baby and posting a changelog! :congrats:
(Nice to see you've got your priorities right )
UPDATE
No problems installing Siyah 6.0beta5 to NEAT ROM Full LSJ after a GS2KernelWipe.
Had to re-install STweaks again.
CPU MIN FREQUENCY now 200MHz
Wi-Fi connects OK
PowerAmp music Player OK
MX Video Player on HD videos OK
Stock camera OK
Stock video camera, record and playback OK
Using battery settings from post #602
Have done 5 reboots with no problems.
This version of Siyah will have a lot to live up to after Siyah 6.0beta4.
Well done sntaylor... managing a baby and posting a changelog! :congrats:
(Nice to see you've got your priorities right
)UPDATE
No problems installing Siyah 6.0beta5 to NEAT ROM Full LSJ after a GS2KernelWipe.
Had to re-install STweaks again.
CPU MIN FREQUENCY now 200MHz
Wi-Fi connects OK
PowerAmp music Player OK
MX Video Player on HD videos OK
Stock camera OK
Stock video camera, record and playback OK
Using battery settings from post #602
Have done 5 reboots with no problems.
Hawker
Android Expert
ironass
Extreme Android User
Well, very early results are very good so far. No freezes, FC's or SoD's. Deep Sleep, 95%, is more like a short course of death on this release and is one of the best I've ever had on a kernel, with under 1% per hour battery drain.
How are you finding it Hawker old bean?
How are you finding it Hawker old bean?
Hawker
Android Expert
Very good so far my old committed belcher.
Everything is silky smooth (in fact, it may be placebo, but I think its smoother than before, not noticing one single lag up to now), getting good deep sleep so far so battery should be favourable (obviously will test over the next few days), and all seems to be working fine ie. camera/video/wifi/bluetooth.
Early signs are that we are getting another Gokhan masterpiece.
And now he has an S2 again, in the immortal words of D:Ream, Things can only get better!
Hawker
Android Expert
Yazz-sir-ee
ironass
Extreme Android User
Oh crikey! Another Hawker/Syd bandwagon!
Right! Back to life.. back to reality, in my original post earlier today, I said...
Well, I know it has only been on for about 14 hours so far, for me, but I can say that this release from the kernel master, gokhanmoral, is not disappointing me so far.
Normally I reserve judgement for 2 or 3 days at least, to allow the kernel to, "bed in", but at this rate, unless there is a spectacular failing that I'm totally unaware of, this kernel will not only equal the previous beta4 but may even surpass it. I can say that it is certainly no worse so far.
In the 14 hours, with 4 hours sleep and 10 hours moderate usage, my battery has dropped by 23% which, for me, puts this ahead of all other kernels released for JB so far. I just hope it is compatible with NEAT Full MS1.
Since this is a, "Beta", release, the configurations for Profiles is non operative in Recovery > kernel and so therefore all settings must be done manually. Also there is no Backup/Restore feature for the beta releases. I am sure that gok will rectify these in the final release, now that he has an SGSII to test it on.
So far... a big :thumb:
EDIT It is fully compatible with JB, NEAT ROMM Full, MS1.
Right! Back to life.. back to reality, in my original post earlier today, I said...
Well, I know it has only been on for about 14 hours so far, for me, but I can say that this release from the kernel master, gokhanmoral, is not disappointing me so far.
Normally I reserve judgement for 2 or 3 days at least, to allow the kernel to, "bed in", but at this rate, unless there is a spectacular failing that I'm totally unaware of, this kernel will not only equal the previous beta4 but may even surpass it. I can say that it is certainly no worse so far.
In the 14 hours, with 4 hours sleep and 10 hours moderate usage, my battery has dropped by 23% which, for me, puts this ahead of all other kernels released for JB so far. I just hope it is compatible with NEAT Full MS1.
Since this is a, "Beta", release, the configurations for Profiles is non operative in Recovery > kernel and so therefore all settings must be done manually. Also there is no Backup/Restore feature for the beta releases. I am sure that gok will rectify these in the final release, now that he has an SGSII to test it on.
So far... a big :thumb:
EDIT It is fully compatible with JB, NEAT ROMM Full, MS1.