[REF]SIYAH KERNEL - non dev issues and questions about kernel

Search This thread

desean

Senior Member
Oct 29, 2008
364
214
  • Like
Reactions: jimeslovelyy

It_ler

Recognized Contributor
  • Aug 23, 2011
    12,160
    16,946
    Samsung Galaxy S8
    Samsung Galaxy S10
    Results for SpeedMod / Phenomenal / N.E.A.K. / Siyah / RedPill / stock kernels

    Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
    For all custom kernels, I was running on Frankenstein XWLA4 ROM (Modem: XXKL1).
    For stock kernels, I was running on the corresponding stock ROM.
    Always using the Samsung's standard / stock 1650mAh battery.
    For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
    For N.E.A.K. I tested VR schedule, Lulzactive governor, only enabled sched_mc (and AFTR idle mode) and the rest unchanged defaults.
    For RedPill kernel, I tested completely default settings (deadline / ondemand) without any change.
    For RedPill (sio/conservative) kernel, I tested completely default settings, only changed io sched to sio and governor to conservative.

    Just tested Siyah v2.6.13 and added its results.


    Here are my current results:


    Benchmarks (in Performance governor if available)
    Quadrant Standard (3rd run)

    Phenomenal 4.0: 4780
    SpeedMod K2-21: 4771
    N.E.A.K. v1.3.3: 4616
    Siyah v2.6.12: 4345
    Stock XILA2 kernel: 4259
    Stock XWLA4 kernel: 4076
    Stock XWKL1 kernel: 4036
    Stock XWKK5 kernel: 3899
    Stock XWKK2 kernel: 3852


    Quadrant Standard 2.0 (3rd run)

    N.E.A.K. v1.4: 3860
    Siyah v2.6.13: 3692
    RedPill rev1.3: 3282


    NenaMark2 (best of 3 runs)

    Stock XILA2 kernel: 54,3
    Siyah v2.6.13: 54,2
    N.E.A.K. v1.4: 54,2
    N.E.A.K. v1.3.3: 54,2
    Stock XWLA4 kernel: 54,2
    Siyah v2.6.12: 54,1
    SpeedMod K2-21: 53,5
    RedPill rev1.3: 52,7
    Stock XWKK5 kernel: 47,8
    Stock XWKK2 kernel: 47,6
    Phenomenal 4.0: 44,4
    Stock XWKL1 kernel: 38,1


    Vellamo (best of 2 runs)

    Siyah v2.6.13: 1237
    Stock XILA2 kernel: 1225
    SpeedMod K2-21: 1224
    Siyah v2.6.12: 1221
    N.E.A.K. v1.4: 1219
    Stock XWLA4 kernel: 1216
    Phenomenal 4.0: 1214
    N.E.A.K. v1.3.3: 1213
    Stock XWKL1 kernel: 1173
    RedPill rev1.3: 1172
    Stock XWKK5 kernel: 1160
    Stock XWKK2 kernel: 1080


    Linpack (best of 10 runs): Single / Multi thread

    Phenomenal 4.0: 57.342 / 102.346
    SpeedMod K2-21: 57.224 / 98.062
    Siyah v2.6.12: 57.816 / 95.725
    N.E.A.K. v1.3.3: 57.499 / 95.454
    N.E.A.K. v1.4: 57.302 / 95.077
    Stock XWLA4 kernel: 57.816 / 93.548
    Siyah v2.6.13: 57.459 / 92.572
    Stock XILA2 kernel: 57.302 / 91.667
    RedPill rev1.3: 57.499 / 80.663


    CF-Bench (best of 2 runs): Native / Java / Overall score

    N.E.A.K. v1.3.3: 11530 / 3623 / 6785
    Stock XWLA4 kernel: 11396 / 3539 / 6681
    Phenomenal 4.0: 11522 / 3409 / 6654
    Siyah v2.6.13: 11441 / 3427 / 6632
    N.E.A.K. v1.4: 11400 / 3374 / 6584
    SpeedMod K2-21: 11428 / 3355 / 6584
    Siyah v2.6.12: 11413 / 3313 / 6553
    RedPill rev1.3: 11271 / 3229 / 6445
    Stock XILA2 kernel: 11285 / 3187 / 6426


    AnTuTu (1st run)

    N.E.A.K. v1.4: 6177
    N.E.A.K. v1.3.3: 6149
    Stock XILA2 kernel: 6110
    Siyah v2.6.12: 6072
    Siyah v2.6.13: 6012
    Stock XWLA4 kernel: 6009
    SpeedMod K2-21: 4986
    Phenomenal 4.0: 4966
    RedPill rev1.3: 4832


    Battery stats
    Night use (wifi, synch, Talk and Skype on)

    RedPill rev1.3 (sio/conservative): Battery loss of 0,72% per hour, Awake: 4,8%, Deep sleep: 93%
    Phenomenal 4.0 Extreme: Battery loss of 0,82% per hour, Awake: 5,6%, Deep sleep: 93%
    SpeedMod K2-21: Battery loss of 0,86% per hour, Awake: 6,0%, Deep sleep: 93%
    XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
    RedPill rev1.3: Battery loss of 1,00% per hour, Awake: 6,3%, Deep sleep: 92%
    N.E.A.K. v1.4: Battery loss of 1,02% per hour, Awake: 5,8%, Deep sleep: 92%
    XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
    XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
    N.E.A.K. v1.3.3: Battery loss of 1,28% per hour, Awake: 9,2%, Deep sleep: 90%
    Siyah v2.6.13: Battery loss of 1,30% per hour, Awake: 9,8%, Deep sleep: 89%
    XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
    Siyah v2.6.12: Battery loss of 1,52% per hour, Awake: 9,6%, Deep sleep: 89%


    Mixed (day and night) usage (*)

    RedPill rev1.3 (sio/conservative): Battery loss of 1,76% per hour, Wifi: 100%, Awake: 15,8%, Deep sleep: 84%, Screen: 9,7% => loss*(1-screen): 1,59%
    SpeedMod K2-21: Battery loss of 1,91% per hour, Wifi: 100%, Awake: 16,7%, Deep sleep: 83%, Screen: 10,2% => loss*(1-screen): 1,72%
    RedPill rev1.3: Battery loss of 2,02% per hour, Wifi: 100%, Awake: 16,5%, Deep sleep: 83%, Screen: 10,3% => loss*(1-screen): 1,81%
    Phenomenal 4.0 Extreme: Battery loss of 2,05% per hour, Wifi: 100%, Awake: 18,6%, Deep sleep: 81%, Screen: 9,8% => loss*(1-screen): 1,85%
    XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
    N.E.A.K. v1.4: Battery loss of 2,26% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 11,4% => loss*(1-screen): 2,00%
    Siyah v2.6.13: Battery loss of 2,29% per hour, Wifi: 91,6%, Awake: 19,9%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,04%
    XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
    XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
    XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
    Siyah v2.6.12: Battery loss of 2,94% per hour, Wifi: 100%, Awake: 23,3%, Deep sleep: 76%, Screen: 10,5% => loss*(1-screen): 2,63%
    N.E.A.K. v1.3.3: Battery loss of 3,05% per hour, Wifi: 100%, Awake: 24,3%, Deep sleep: 75%, Screen: 11,4% => loss*(1-screen): 2,70%


    (*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
    loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
    So, it would be the battery loss in % (per hour) for the screen off time.
    That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)

    Siyah v2.6.13 seems to be a good version.
    It is stable and smooth on my phone. Battery savings in mixed usage are better than for other Siyah kernel version, only in over-night usage, I had a little bit more drain.
    Still analyzing the causes.

    Overall, Siyah v2.6.13 is the most configurable kernel I have tested so far ... and I am sure that I will come back to test the configuration interface/app as well.
    Thanks gokhanmoral for all your great work !
     

    komsa

    Senior Member
    Feb 11, 2007
    809
    190
    Subotica
    @It_ler i really love your tests..... bookmarked all .....thanks for your work.....based on your earlier tests i tried Siyah 2.6.7 and i love it,this is my favorite kernel.Now i am testing Redpill 1.3 as it is ( already tested with conservative governor but i don't like the response,it's a kinda sleepy)......i must mention the Speedmod kernel as the best all rounder without any scripts governors,etc...........but i as i like custom boot animations i dont use it now.Thanks again and waiting for new tests from you.............:)
     

    TheFaixy

    Senior Member
    Sep 17, 2011
    707
    53
    Lahore
    regarding the new application extweaks can someone guide me how to get most performance put of it I'm using conservative + noop and I'm lagging a bit so please help I don't really want battery that much

    Sent from my GT-I9100 using xda premium
     

    veyka

    Retired Forum Moderator
    Oct 26, 2007
    5,590
    2,662
    Norfolk
    www.veyka.co.uk
    regarding the new application extweaks can someone guide me how to get most performance put of it I'm using conservative + noop and I'm lagging a bit so please help I don't really want battery that much

    Sent from my GT-I9100 using xda premium

    Change to ondemand, that should help, also see the sticky thread that lists info about what all the tweaks do, it's by droidphile (sp)

    Sent from my GT-I9100 using Tapatalk
     

    It_ler

    Recognized Contributor
  • Aug 23, 2011
    12,160
    16,946
    Samsung Galaxy S8
    Samsung Galaxy S10
    Just for those interested in benchmarks and tests for ICS Siyah and stock kernel version:

    Results for ICS Siyah / stock kernels

    Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
    For all custom kernels, I was running on stock ICS XXLPQ ROM (Modem: XXLPQ).
    For stock kernels, I was running on the corresponding stock ROM.
    Always using the Samsung's standard / stock 1650mAh battery.
    For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.

    I just flashed Siyah v3.0beta4 and added its benchmark results.


    Here are my current results:


    Benchmarks
    Quadrant Standard 2.0 (best of 3 runs)

    Stock XXLPQ kernel: 4063
    Siyah v3.0beta3: 3983
    Siyah v3.0beta4: 3953


    NenaMark2 (best of 3 runs)

    Stock XILA2 kernel: 54,3
    Stock XWLA4 kernel: 54,2
    Stock XXLPQ kernel: 51,3
    Siyah v3.0beta3: 50,3
    Siyah v3.0beta4: 50,0
    Stock XWKK5 kernel: 47,8
    Stock XWKK2 kernel: 47,6
    Stock XWKL1 kernel: 38,1


    Vellamo (best of 2 runs)

    Stock XXLPQ kernel: 1247
    Stock XILA2 kernel: 1225
    Stock XWLA4 kernel: 1216
    Siyah v3.0beta3: 1174
    Stock XWKL1 kernel: 1173
    Stock XWKK5 kernel: 1160
    Siyah v3.0beta4: 1081
    Stock XWKK2 kernel: 1080


    Linpack (best of 10 runs): Single / Multi thread

    Stock XWLA4 kernel: 57.816 / 93.548
    Stock XILA2 kernel: 57.302 / 91.667
    Stock XXLPQ kernel: 48.208 / 80.013
    Siyah v3.0beta3: 47.390 / 78.816
    Siyah v3.0beta4: 47.633 / 77.370


    CF-Bench (best of 2 runs): Native / Java / Overall score

    Stock XWLA4 kernel: 11396 / 3539 / 6681
    Stock XILA2 kernel: 11285 / 3187 / 6426
    Siyah v3.0beta4: 11135 / 3265 / 6413
    Stock XXLPQ kernel: 10862 / 3044 / 6171
    Siyah v3.0beta3: 10716 / 2906 / 6030


    AnTuTu (1st run)

    Stock XILA2 kernel: 6110
    Stock XXLPQ kernel: 6075
    Stock XWLA4 kernel: 6009
    Siyah v3.0beta4: 5654
    Siyah v3.0beta3: 5414


    Battery stats
    Night use (wifi, synch, Talk and Skype on)

    XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
    XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
    XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
    XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
    Siyah v3.0beta3: Battery loss of 1,14% per hour, Awake: 8,1%, Deep sleep: 91%
    XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%


    Mixed (day and night) usage (*)

    XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
    XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
    Siyah v3.0beta3: Battery loss of 2,45% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 9,7% => loss*(1-screen): 2,21%
    XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
    XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
    XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%


    (*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
    loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
    So, it would be the battery loss in % (per hour) for the screen off time.
    That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)

    Siyah v3.0beta3 is already stable and has better battery savings on my phone than stock kernel (still on default settings ... no UC/UV).
    Hope that Siyah v3.0beta4 can be even better.
    Will post my results as soon as my tests are finished.

    I like the CWM touch recovery, VC and ExTweaks support.
    Siyah v3.0 feels a little bit smoother than stock kernel, although some benchmark results are lower.
     

    It_ler

    Recognized Contributor
  • Aug 23, 2011
    12,160
    16,946
    Samsung Galaxy S8
    Samsung Galaxy S10
    Results for Siyah / stock kernels

    Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
    For all custom kernels, I was running on ICS XXLPQ ROM (Modem: XXLPQ).
    For stock kernels, I was running on the corresponding stock ROM.
    Always using the Samsung's standard / stock 1650mAh battery.
    For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.


    I have flashed SiyahKernel v3.0beta5 and added its results.
    Then I flashed SiyahKernel v3.0beta6 and added its benchmark results.


    Here are my current results:


    Benchmarks
    Quadrant Standard 2.0 (best of 3 runs)

    Siyah v3.0beta6: 4166
    Siyah v3.0beta5: 4156
    Stock XXLPQ kernel: 4063
    Siyah v3.0beta3: 3983
    Siyah v3.0beta4: 3953


    NenaMark2 (best of 3 runs)

    Stock XILA2 kernel: 54,3
    Stock XWLA4 kernel: 54,2
    Siyah v3.0beta6: 52,0
    Stock XXLPQ kernel: 51,3
    Siyah v3.0beta5: 50,4
    Siyah v3.0beta3: 50,3
    Siyah v3.0beta4: 50,0
    Stock XWKK5 kernel: 47,8
    Stock XWKK2 kernel: 47,6
    Stock XWKL1 kernel: 38,1


    Vellamo (best of 2 runs)

    Siyah v3.0beta6: 1273
    Stock XXLPQ kernel: 1247
    Stock XILA2 kernel: 1225
    Stock XWLA4 kernel: 1216
    Siyah v3.0beta3: 1174
    Stock XWKL1 kernel: 1173
    Stock XWKK5 kernel: 1160
    Siyah v3.0beta5: 1138
    Siyah v3.0beta4: 1081
    Stock XWKK2 kernel: 1080


    Linpack (best of 10 runs): Single / Multi thread

    Stock XWLA4 kernel: 57.816 / 93.548
    Stock XILA2 kernel: 57.302 / 91.667
    Stock XXLPQ kernel: 48.208 / 80.013
    Siyah v3.0beta3: 47.390 / 78.816
    Siyah v3.0beta4: 47.633 / 77.370
    Siyah v3.0beta6: 47.850 / 76.702
    Siyah v3.0beta5: 47.150 / 75.800


    CF-Bench (best of 2 runs): Native / Java / Overall score

    Stock XWLA4 kernel: 11396 / 3539 / 6681
    Siyah v3.0beta6: 11144 / 3359 / 6473
    Stock XILA2 kernel: 11285 / 3187 / 6426
    Siyah v3.0beta4: 11135 / 3265 / 6413
    Stock XXLPQ kernel: 10862 / 3044 / 6171
    Siyah v3.0beta3: 10716 / 2906 / 6030
    Siyah v3.0beta5: 10529 / 2790 / 5885


    AnTuTu (1st run)

    Siyah v3.0beta6: 6136
    Stock XILA2 kernel: 6110
    Stock XXLPQ kernel: 6075
    Stock XWLA4 kernel: 6009
    Siyah v3.0beta4: 5654
    Siyah v3.0beta5: 5593
    Siyah v3.0beta3: 5414


    Battery stats
    Night use (wifi, synch, Talk and Skype on)

    XXLPQ: Battery loss of 0,92% per hour, Awake: 7,0%, Deep sleep: 91%
    XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
    Siyah v3.0beta5: Battery loss of 1,05% per hour, Awake: 8,4%, Deep sleep: 90%
    Siyah v3.0beta4: Battery loss of 1,08% per hour, Awake: 7,8%, Deep sleep: 91%
    XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
    XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
    Siyah v3.0beta3: Battery loss of 1,14% per hour, Awake: 8,1%, Deep sleep: 91%
    XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%


    Mixed (day and night) usage (*)

    XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
    XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
    Siyah v3.0beta5: Battery loss of 2,45% per hour, Wifi: 89,9%, Awake: 19,6%, Deep sleep: 80%, Screen: 9,9% => loss*(1-screen): 2,21%
    Siyah v3.0beta3: Battery loss of 2,45% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 9,7% => loss*(1-screen): 2,21%
    XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
    Siyah v3.0beta4: Battery loss of 2,50% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,4% => loss*(1-screen): 2,24%
    XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
    XXLPQ: Battery loss of 2,71% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 80%, Screen: 10,7% => loss*(1-screen): 2,42%


    (*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
    loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
    So, it would be the battery loss in % (per hour) for the screen off time.
    That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)

    SiyahKernel v3.0beta5 feel a little bit smoother than previous versions.
    Gokhanmoral, you are on the right way.
    Keep on doing your great work.
    You seem to be the first one publishing a stable custom kernel for ICS ... at least here in XDA.
    The one which will set the new measurement for all other custom ICS kernels.

    SiyahKernel v3.0beta6 feels even smoother than beta5, and has got better benchmark results than stock kernel (the only exception is Linpack).
    That's the way I want a custom kernel to be.

    Will update my test results as soon as my battery tests are finished.
     
    Last edited:

    planetf1

    Senior Member
    Jan 25, 2010
    842
    90
    I'm currently running Siyah 3.3.2 on stock LPG on my SGS2. It generally works well with just a glitch I've noticed. May not be kernel related but am interested if others have seen this and believe it is

    GPS toggle

    after "a while" (days I think) I notice my GPS gets into a state where the quick setting will no longer toggle the gps, nor will the samsung provided power widget, nor will the main setting menus.

    As an aside would any hardened Siyah user care to give an opinion on either
    * N.E.A.K -- picks up many off GMs changes, incorporates a few other fixes from different kernels. May be a little less stable
    * Speedmod - I always used this pre-ICS and it was solid and efficient. No fancy features though and seems to stick very close to stock with few updates pulled from elsewhere

    No surprise, but it seems the developers of each of these are also now working with their SGS3s (as would I!) so I'd guess development may close to stop on them. Currency with samsung updates would be by main concern

    to be honest even the stock kernel on the SGS2 is pretty solid. My main uses of the alternate kernels are
    - faster USB charging (ie from a power pack 450 mA -> 650 mA)
    - toning down the screen brightness
    - efficiency, may include underclocking, undervolting, change of scheduler etc fairly conservatively
     

    arunreturns

    Senior Member
    Mar 10, 2012
    241
    39
    Chennai
    Question on Odin Flash

    Hi I have a question..

    I am dual botting with Siyah.. Now I have primary ROM as RR and Secondary as CM10
    Now if i have a stock firmware which i can flash via Odin.. And i flash it..

    What happens..??

    1.) Does Siyah Kernel's dualboot get removed..
    2.) Can Odin Flash be done directly to Second ROM (Like for B2G)
     

    CamoGeko

    Forum Moderator
    Staff member
    Hi I have a question..

    I am dual botting with Siyah.. Now I have primary ROM as RR and Secondary as CM10
    Now if i have a stock firmware which i can flash via Odin.. And i flash it..

    What happens..??

    1.) Does Siyah Kernel's dualboot get removed..
    2.) Can Odin Flash be done directly to Second ROM (Like for B2G)

    Yes, if you flash any other kernel. Dual boot will be removed.

    No, ODIN cannot flash second rom. You can only do that within Siyah CWM recovery.
     
    • Like
    Reactions: arunreturns

    arunreturns

    Senior Member
    Mar 10, 2012
    241
    39
    Chennai
    Yes, if you flash any other kernel. Dual boot will be removed.

    No, ODIN cannot flash second rom. You can only do that within Siyah CWM recovery.
    Thanks man.. Nice to see you still helping out folks in the S2 forum.. Though u switched to One X.. Keep up the great work :D:D

    One more small doubt.. In Siyah there are data.img and cache.img files that are created in the sdcard right.. Do they get removed as well..
    If they dont does that mean we can flash Siyah and the second ROM will be available.. ??
     

    Darkmind1

    Senior Member
    Jun 13, 2012
    142
    23
    Does the latest Siyah from http://www.gokhanmoral.com/ support Stock Samsung ICS 4.0.3 ROMs? I know that these latest versions are designed with Jelly Bean in mind, but I'd like to know if I can use latest version or I need to switch to an older version? If this is the case, which version would you recommend?
     

    Darkmind1

    Senior Member
    Jun 13, 2012
    142
    23
    Y mate you can flash

    Sent from my GT-I9100 using xda premium

    Great thanks, also, I am curious about another thing. As I see, this new version of Siyah uses CWM-Based Touch Recovery v6.0.1.2. Some user has been mentioning on the forum that CWM Recovery v6.0.1.2 may have the safe erase option disabled so it wouldn't use the MMC_CAP_ERASE if it's enabled in the Kernel, but I couldn't find more precise information whether this is true or not. Now I know that Siyah Kernel itself has MMC_CAP_ERASE disabled so it's a safe Kernel, but if the recovery is now also safe (according to Entropy512's post, most ICS recoveries were not safe), it's an extra layer of safety, that's why I wanted to know. :)
     
    Last edited:

    gyurman

    Senior Member
    Jan 12, 2009
    90
    3
    usb modules

    Hello,
    I have otg cable for mine phone, and I have a 16 GB pen drive with USB3.
    How can I connect? Maybe need to me modules for siyah? How can I download this?
    Could you help me?
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 23
      NON DEV ISSUES AND QUESTIONS ABOUT KERNEL POST HERE. THIS IS A WORK IN PROGRESS THREAD


      HISTORY

      I have been given Permission by the Kernel's Author (Gokhanmoral) to create this thread. Please put your issues or questions you have with the Kernel in this thread. Also functional request should also be made here. The aim of this thread is to filter out excess questions regarding the use and experience from the development thread. The author of the kernel and many experience users\testers and primary dev contributors need to use the Development thread in order to help Gokhan to implement his kernel. Would also request the community to contribute in terms of info to compile a knowledge base if you will. Many Thanks Gokhan and future contributors.



      THANKS:
      Samsung, supercurio, hardcore, Hacre, RAvenGEr, tegrak, cattleprod, codeworkx, hellcat, creams, vitalij, arighi, ninpo,netarchy .. Any others that I missed.



      SiyahKernel v2.6.12

      FEATURES
      Can be flashed on Samsung ROMs and AOSP Based ROMS. Currently all Samsung 2.3.4, 2.3.5, 2.3.6, 2.3.7 based ROMS, CM7 (CM9 or any other ICS based ROMs are not supported) and MIUI ROMS are supported.
      Based on linux kernel 2.6.35.14 + drivers from Samsung sources
      Auto-Rooting
      Custom CWM compatible Redpill Recovery from af974 (For more info: http://forum.xda-developers.com/showpost.php?p=21727136&postcount=9680 )
      Custom boot animation support
      Supports SetCPU (OC upto 1600MHz, UC downto 100MHz)
      User customizable frequency steps. You can edit "freq_table" and use 25MHz as the lowest step and 1696MHz as the highest. You have 8 steps (it is fixed) but the frequencies can be set.
      Supports undervolting (UV between 800 mV and 1500 mV)
      Supports voltage control via SetCPU (thanks to netarchy, ninpo, hacre)
      Stock voltages as default
      smartassV2, lulzactiveV2 governors. and lots of other governors which are available as modules
      Default governor is lulzactive (200-1200MHz)
      Tweaked ondemand and conservative governors
      no compiler optimization. it is just a myth.
      Touchscreen fix (thanks to vitalij)
      Increased touchscreen sensitivity
      GPU clock (thanks to netarchy), voltage and scaling thresholds control interface.
      I/O, scheduler, hotplug and vm tweaks
      automatic battery calibration. (removed. thanks to Entropy512. we do not need battery calibration for SGS2)
      Available I/O schedulers: noop, deadline, CFQ, BFQV3r1, V(R), SIO(default)
      Available CPU governors: see this thread for the list of available governors and modules (thanks to droidphile)
      /system/etc/init.d startup scripts support
      Automatic backup of efs partition. You will have the files in your sdcard as well as /data/.siyah directory. copy them to a safe location in case you may need them later.
      BLN (thanks to creams), liblights is autoinstalled if the existing one doesn't support BLN
      supports advanced touch tune driver. thanks to vitalij Link. the control app from Web, from Mobile. Thanks to tegrak for the driver patch file download
      2nd core application support (thanks to tegrak)
      Automounting of NTFS volumes for USB sticks (ntfs on external card is not supported). although your rom says "clear storage", just check /mnt/usb folder. ntfs drives will be automatically mounted in read-only mode.
      LZOP compression for the kernel to have very fast decompression. We have a VERY BIG kernel image because we have ntfs-3g, CWMManager and lots of other things both in initramfs and payload.
      Integrated new&faster sha-1, crc32 slice-by-8, crc32c, jhash and rwsem algorithms
      SCHED_MC enabled to have less power consumption.
      Lower brightness levels for low-light conditions to save battery.
      Brightness behaviour modification via setting min_bl, min_gamma and max_gamma values. you can control the lowest and hightest levels used in autobrightness.
      Native BLN support for CM7 based roms.
      Three GPU stepping (160-267-300) instead of two
      optimized and configurable hotplug thresholds and rates.
      Thunderbolt! script integrated (thanks to pikachu01)
      Voodoo louder app support (thanks to supercurio)
      Current Widget support while charging the device.
      Charging the battery stops when the battery draws less than 100mA (stock value is 200mA).
      CIFS, SLUB, FUSE, NTFS, cgroup_timer_slack, autogroup,... and lots of other mambojambo that I forgot...



      TO FLASH ZIP:
      Use CWM Recovery and install zip file. Wiping cache&dalvik cache is recommended for those who use BLN.
      if you lose root after flashing the kernel (unlikely), flash http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip in CWM.


      FAQ (WIP)

      General

      Q: Does this kernel support latest i9100 ROM which is based on android 2.3.5 -2.3.7?

      A: Yes, it does.

      Q: Can I use this kernel on I9100G?

      A: No, you cannot. Only International i9100 and Canadian (Bell Mobility) models are supported (Chinese or AT&T T-Mobile US are not supported). Also, I compile ntt-docomo version for each release but beta versions do not support gps and digital tv on ntt-docomo devices.

      Q: Does this kernel support CM7 or any other AOSP based roms?

      A: Yes, but it only support CM7 or MIUI based roms for now from 2.0 and above. If you are using another AOSP based Rom tell me and I will support it.

      Q. What is the latest version of the Kernel?

      2.6.3 is the latest and can be found here:

      SiyahKernel Edition v2.6.12 (Please ensure you choose the right one for your phone)

      Q. I have an International i9100 can I flash NTT version?

      A. Important Notice: the one with "ntt" in the filename is NTT DoCoMo SC-02C version. do not flash it if you have EU version

      Q. Where can I get the latest Kernel Source for this Kernel?

      A. It can be Found Here: Kernel Source

      Q.Are there any Variants based on this Kernel?

      A. Yes there is DK SIYAH KERNEL

      Q: Can I use app protectors with this kernel?

      A: Yes, you can. But you have to flash EnableLogger.zip using CWM after flashing the kernel.

      TO ENABLE ANDROID LOGGER USE THIS:
      ENABLE LOGGER

      TO DISABLE ANDROID LOGGER USE THIS:
      DISABLE LOGGER IF IT IS INSTALLED


      Battery & Performance Factors

      Q: What is battery life like on this kernel?

      A: Some have said the battery life has improved. Others said not as good as others, this however maybe down to rogue apps creating wakelocks. Could be the rom is does not take advantage of the kernels features or could be a bad battery. Let's just say your Mileage may vary...

      Q. I keep hearing about AOS having a factor on performance, whats all this about?

      A. The Android OS using quite a lot of resources. AndreiLux wrote and in depth reference post about this which you can find here: [REF][Rewrite 26/10] What the Android OS usage is and what it's not

      Q: What can I do to improve battery life?

      A: put your phone into airplane mode or do not use packet data when you are not using it. Check for Rogue Apps and also check for unnecessary wakelocks and close them.


      Q: I get random reboots or freezes. What should I do?

      A: Make sure you boot in Recovery wipe cache and dalvik, then reflash the kernel. Although the kernel will do this if you apply the CWM.zip of the Kernel. It can still leave data behind.

      If you are undervolting revert back to stock values. Then start reducing voltage by.25 and test. If that does not work make a note of:

      1. When did it happen?
      2. Which rom are you using, can you reproduce it
      3. do you have any custom init scripts which changes kernel parameters such as freq voltage or anything else?

      Post in this thread and we will try and help you.

      Q: My phone doesn't go into deep sleep. What is wrong?

      A: Make sure that you have cleared cache and dalvik-cache after you install the kernel. Also, reboot once more after the flashing. the phone doesn't go into deep sleep if it is connected to a charger or to a computer. There may be an application running in the background which is preventing deep sleep. In that case you can check which app causing the problem with "BetterBatteryStats" application (search in Google).


      Q: do I need to recalibrate the battery?

      A: You don't need to calibrate battery for SGS2. Thanks to Entropy512 to pointing out that our device uses MAX17042 which is specifically designed not to require calibration.




      OC/UV and init Scripts

      Q. What tools can be used to manipulate the clock speeds of this kernel?

      SetCpu : http://www.youtube.com/watch?v=X9Sn4Uz4pkM Just an overview

      Voltage Control: http://www.youtube.com/watch?v=XkhBFVUKBTQ Just an overview

      No-frills cpu: More Info here about the tool

      And Initialization Scripts

      Tegrak Overclocking app is currently NOT SUPPORTED by this kernel


      Q: What is an init.d script?

      A:init.d scripts are the scripts which are executed during the boot time. actually, they are meant to initialize and deinitialize system daemons and manage some startup/shutdown tasks. but in android world they are just "autoexec.bat"s. so, it is a mix of rc.d and init.d directories in linux distros. everything in /system/etc/init.d are executed during the booting process. since it is not standard in every android device,some developers choose to execute files starting with "S" and some execute everything. in this kernel, everything in /system/etc/init.d is executed. you can create a script to change, lets say, voltages, schedulers, apply tweaks, run overclocking daemon or run anything else you can imagine.

      Q. Okay how do I start to create my own Init.d Script for the kernel?

      A: KWERDENKER has written a reference guide to help you get started. You can find his excellent Guide on POST #2 of this thread.
      example of Kwerdenker scripts are also in Post 2.

      DROIDPHILE'S NOOBS SCRIPTING GUIDE:

      http://forum.xda-developers.com/showpost.php?p=19519757&postcount=10699

      Here are other examples of init.d scripts supplied by Fenomeno83:

      Another couple of nice init.d scripts created by fenomeno83



      Q: where is the interface to change GPU clock and voltage?

      A:There is now a GUI to change GPU voltage and Charging current it's voltage control and probably one by Gokhanmoral soon

      For Undervolting your GPU use this Script from AndreiLux as a Reference:

      Example CWM-flashable /system/etc/init.d/99gpuv script

      Q: Which governor is the best? Which I/O scheduler is the best?

      A: You have to try them and select the one you like. There is a very good explanation about governors and i/o schedulers here:

      http://forum.xda-developers.com/showthread.php?t=1242323

      HERE IS DROIDPHILE CONCISE GUIDE TO GOVERNORS

      http://forum.xda-developers.com/showpost.php?p=19339524&postcount=10023

      More info might help those you get a better understanding for schedulers:

      https://github.com/CyanogenMod/cm-k...m-2.6.37/Documentation/cpu-freq/governors.txt Source: Cyanogenmod Githubs

      Info about Lulzactive Governor.

      http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html


      Q: What is smartassV2 governor?

      A: It is a governor to control CPU frequency. This governor has a built-in "profile" similar to SetCPU but the profile has no upper frequency limit. It tends to stay on lower frequencies when the screen is off and scale up very slowly, so screen off will use lower clock rate thus conserve more battery, but it also has a fast wake up feature so that user interaction will not see the lag when switching from Sleep to Wake state.... (So SetCPU Profiles are sorta redundant when using this governor, you can still use SetCPU to OC to higher than default Clock frequency).


      Q: What is the best UV settings?

      A: There is nothing as best UV settings. You have to find the best settings for your device for yourself. Start by decreasing 25mV on each freq and decrease it every day until your device becomes unstable.

      Q. I notice one of the features is the ability of customizing Voltages for Charging?

      A. Gokhan has written a script which he converted to be applied using CWM recovery (PLEASE BE CAREFUL WHEN APPLYING THIS, IF YOU ARE UNSURE PLEASE ASK IN THIS THREAD BEFORE DOING IT)

      Set AC and MISC charging current to 1000mA - CWM flashable (keeps USB charging current at 450mA)


      Q. I read that different frequencies would assist in better battery performance do you have any examples of this so I can use it my script?

      A. Bene2K11 Created some scripts which allows you modify the bus frequencies when using this kernel, they can be found here:

      3 flashable zips for the lowest, mid and highest bus frequencies


      MISCELLANEOUS

      Q: Which version is the best?

      A: supposedly, the latest version is the best. But if the latest version is beta there may be unstable code in it. testing the beta version and reporting bugs will help me. but it's your choice... try and see... maybe this kernel is not stable for your device at all, who knows... I will not answer any "what is the best?" questions and I kindly ask you not to ask that kind of questions since there is no answer to that.



      My Thanks for their contribution to this thread to Gokhanmoral, AndreiLux, ChadouMing, Nilste, Matriak31,Ger5,Kwerdenker,Fenomeno83, Bene2k11,Droidphile






      __________________
      Reproduce with permission from Gokhan by Dragon546
      6
      Results for SpeedMod / Phenomenal / N.E.A.K. / Siyah / stock kernels

      Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
      For all custom kernels, I was running on Frankenstein XWLA4 ROM (Modem: XXKL1).
      For stock kernels, I was running on the corresponding stock ROM.
      Always using the Samsung's standard / stock 1650mAh battery.
      For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
      For N.E.A.K. I tested VR schedule, Lulzactive governor, only enabled sched_mc and the rest unchanged defaults.

      Just tested Siyah v2.6.12 "out-of-the-box" and added its results.


      Here are my current results:


      Benchmarks (in Performance governor if available)
      Quadrant Standard (3rd run)

      SpeedMod K2-19 (XILA2): 4779
      Phenomenal 3.0 black (XILA2): 4759
      Phenomenal 2.2 black (XILA2): 4640
      N.E.A.K. 1.3.3: 4616
      Phenomenal 4.0 (XILA2): 4478
      N.E.A.K. 1.3.2 (XILA2): 4384
      Siyah v2.6.12: 4345
      Siyah v2.6.11 (XILA2): 4280
      Stock XILA2 kernel: 4259
      Stock XWLA4 kernel: 4076
      Stock XWKL1 kernel: 4036
      Stock XWKK5 kernel: 3899
      Stock XWKK2 kernel: 3852


      NenaMark2 (best of 3 runs)

      N.E.A.K. 1.3.2 (XILA2): 54,3
      Stock XILA2 kernel: 54,3
      N.E.A.K. 1.3.3: 54,2
      Stock XWLA4 kernel: 54,2
      Siyah v2.6.11 (XILA2): 54,2
      Siyah v2.6.12: 54,1
      SpeedMod K2-19 (XILA2): 53,8
      Stock XWKK5 kernel: 47,8
      Stock XWKK2 kernel: 47,6
      Phenomenal 2.2 black (XILA2): 44,6
      Phenomenal 3.0 black (XILA2): 44,4
      Phenomenal 4.0 (XILA2): 44,3
      Stock XWKL1 kernel: 38,1


      Vellamo (best of 2 runs)

      N.E.A.K. 1.3.2 (XILA2): 1229
      Phenomenal 2.2 black (XILA2): 1227
      Stock XILA2 kernel: 1225
      Siyah v2.6.12: 1221
      SpeedMod K2-19 (XILA2): 1217
      Stock XWLA4 kernel: 1216
      Siyah v2.6.11 (XILA2): 1214
      N.E.A.K. 1.3.3: 1213
      Phenomenal 4.0 (XILA2): 1213
      Phenomenal 3.0 black (XILA2): 1212
      Stock XWKL1 kernel: 1173
      Stock XWKK5 kernel: 1160
      Stock XWKK2 kernel: 1080


      Linpack (best of 10 runs): Single / Multi thread

      Phenomenal 2.2 black (XILA2): 57.381 / 99.157
      SpeedMod K2-19 (XILA2): 57.420 / 97.608
      Phenomenal 4.0 (XILA2): 57.185 / 96.713
      Phenomenal 3.0 black (XILA2): 57.224 / 96.657
      Siyah v2.6.12: 57.816 / 95.725
      N.E.A.K. 1.3.3: 57.499 / 95.454
      Siyah v2.6.11 (XILA2): 56.759 / 95.184
      N.E.A.K. 1.3.2 (XILA2): 57.302 / 94.175
      Stock XWLA4 kernel: 57.816 / 93.548
      Stock XILA2 kernel: 57.302 / 91.667


      CF-Bench (best of 2 runs): Native / Java / Overall score

      N.E.A.K. 1.3.3: 11530 / 3623 / 6785
      Siyah v2.6.11 (XILA2): 11510 / 3586 / 6755
      Stock XWLA4 kernel: 11396 / 3539 / 6681
      SpeedMod K2-19 (XILA2): 11498 / 3353 / 6611
      Phenomenal 3.0 black (XILA2): 11490 / 3352 / 6607
      Phenomenal 4.0 (XILA2): 11472 / 3344 / 6595
      Phenomenal 2.2 black (XILA2): 11439 / 3352 / 6586
      Siyah v2.6.12: 11413 / 3313 / 6553
      N.E.A.K. 1.3.2 (XILA2): 11257 / 3304 / 6485
      Stock XILA2 kernel: 11285 / 3187 / 6426


      AnTuTu (1st run)

      N.E.A.K. 1.3.3: 6149
      N.E.A.K. 1.3.2 (XILA2): 6125
      Stock XILA2 kernel: 6110
      Siyah v2.6.12: 6072
      Siyah v2.6.11 (XILA2): 6025
      Stock XWLA4 kernel: 6009
      SpeedMod K2-19 (XILA2): 4971
      Phenomenal 3.0 black (XILA1): 4944
      Phenomenal 2.2 black (XILA2): 4899
      Phenomenal 4.0 (XILA2): 4863


      Battery stats
      Night use (wifi, synch, Talk and Skype on)

      Phenomenal 2.2 Extreme black (XILA2): Battery loss of 0,75% per hour, Awake: 5,6%, Deep sleep: 93%
      XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
      Phenomenal 3.0 Extreme black (XILA2): Battery loss of 0,96% per hour, Awake: 6,4%, Deep sleep: 93%
      XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
      XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
      Phenomenal 4.0 Extreme (XILA2): Battery loss of 1,14% per hour, Awake: 7,9%, Deep sleep: 90%
      SpeedMod K2-19 (XILA2): Battery loss of 1,15% per hour, Awake: 6,3%, Deep sleep: 93%
      N.E.A.K. 1.3.2 (XILA2): Battery loss of 1,18% per hour, Awake: 7,4%, Deep sleep: 92%
      Siyah v2.6.11 (XILA2): Battery loss of 1,21% per hour, Awake: 9,3%, Deep sleep: 90%
      N.E.A.K. 1.3.3: Battery loss of 1,28% per hour, Awake: 9,2%, Deep sleep: 90%
      XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
      Siyah v2.6.12: Battery loss of 1,52% per hour, Awake: 9,6%, Deep sleep: 89%


      Mixed (day and night) usage (*)

      Phenomenal 4.0 Extreme (XILA2): Battery loss of 1,66% per hour, Wifi: 100%, Awake: 16,6%, Deep sleep: 83%, Screen: 8,3% => loss*(1-screen): 1,52%
      Phenomenal 2.2 Extreme black (XILA2): Battery loss of 1,67% per hour, Wifi: 100%, Awake: 14,9%, Deep sleep: 84%, Screen: 8,5% => loss*(1-screen): 1,53%
      XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
      Phenomenal 3.0 Extreme black (XILA2): Battery loss of 2,36% per hour, Wifi: 100%, Awake: 20,1%, Deep sleep: 72%, Screen: 10,7% => loss*(1-screen): 2,11%
      XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
      N.E.A.K. 1.3.2 (XILA2): Battery loss of 2,45% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,3% => loss*(1-screen): 2,20%
      Siyah v2.6.11 (XILA2): Battery loss of 2,51% per hour, Wifi: 100%, Awake: 21,0%, Deep sleep: 78%, Screen: 11,8% => loss*(1-screen): 2,21%
      XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
      XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
      SpeedMod K2-19 (XILA2): Battery loss of 2,67% per hour, Wifi: 100%, Awake: 19,7%, Deep sleep: 77%, Screen: 11,99% => loss*(1-screen): 2,35%
      Siyah v2.6.12: Battery loss of 2,94% per hour, Wifi: 100%, Awake: 23,3%, Deep sleep: 76%, Screen: 10,5% => loss*(1-screen): 2,63%
      N.E.A.K. 1.3.3: Battery loss of 3,05% per hour, Wifi: 100%, Awake: 24,3%, Deep sleep: 75%, Screen: 11,4% => loss*(1-screen): 2,70%


      (*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
      loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
      So, it would be the battery loss in % (per hour) for the screen off time.
      That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)

      Hmm ... Siyah v2.6.12 does not have as good battery savings as v2.6.7 (on XILA2 ROM) on my phone ... even on completely default settings (no UV, UC, etc.).
      The rest is good as always ... very, very stable, smooth and highly configurable !
      5
      The siyah settings cheat sheet (redux)

      [Info: This is a repost of the one I did in the original kernel thread. I realized to late, that this information and the discussion around it is better kept to this thread so I relocated it here.]

      I hope some of you find this useful as a reference for creating your own init-scripts. This contains everything I use or at least remember about the options in this kernel. If I forgot something or made an error somewhere, please send me a PM and I will gladly correct it.

      How to use these settings:
      If you want to test some settings before you commit them to a script, you can use either the adb shell if your on a pc with adb installed or you can use Terminal Emulator directly on your phone. Remeber to enter superuser mode by entering su in the terminal before you try to set anything or you will get errors. After that just enter the line you want with the values you want to test (if the values are incased in "", keep them that way!). If you want to see if it worked just enter cat followed by the part behind the > of the lines and you will get the values that are currently set. Everything you do in this fashion will not survive a reboot of your phone, if you want to make them permanent you'll have to use an init-script. A how-to on that is (currently) out of the scope for this post. Have a look/search in the kernel release thread as there are many examples for that there. I'm sure with this post and these examples you can figure it out by yourself :)

      The values in the echo commands are the stock values (from 2.1.1 version) if not noted otherwise

      [CPU]
      [Frequency]
      [Steps]
      # Controls which frequency steps are available
      # Should probably only be used to set the lowest step to 25 and/or the highest to 1696
      echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table​
      [Scaling Min]
      # Controls which frequency is use by the governor as the minimal frequency (has to be a valid value in the frequency table!)
      echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq​
      [Scaling Max]
      # Controls which frequency is use by the governor as the maximal frequency (has to be a valid value in the frequency table!)
      echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq​
      [Voltages]
      # Controls with what voltages the frequency steps are supplied
      # Highest step is to the left, lowest to the right
      echo "1425 1325 1275 1175 1075 975 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table​
      [Governor]
      # Available governors: ondemand, lulzactive, smartassV2, conservative, userspace, performance, powersave, brazilianwax, savagedzen, smartass, lagfree, ondemandx
      echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor​
      [GPU]
      [Frequency]
      # Controls with what frequencies the GPU works
      # Valid frequency steps are 100 114 133 160 200 267 400
      echo "160 267" > /sys/class/misc/gpu_clock_control/gpu_control​
      [Voltages]
      # Controls with what voltages the GPU works
      # Lowest possible value is 800000, maximum is 1200000
      # Changes are only possible in 50000 steps
      echo "950000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control​
      [IO]
      [Scheduler]
      # Controls how IO requests are scheduled.
      # Available schedulere: noop deadline cfq bfq sio vr
      echo sio > /sys/block/mmcblk0/queue/scheduler​
      [BUS]
      [Frequency]
      # Controls with what frequency the bus operates
      # Valid values are: 0 (400MHz), 1 (266MHz), 2 (133MHz)
      # Highest frequency step of cpu is to the left, lowest to the right
      echo "0 0 0 0 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
      echo disabled > sys/devices/system/cpu/cpu0/cpufreq/busfreq_static # Use enabled to activate this feature​
      [Charging Current]
      # Controls how much power the phone is willing to draw from a specific charger type
      # Values are from left to right: AC Misc USB
      # !This is a dangerous setting. Use with caution and never change the USB value and never set the other ones higher than 1000!
      echo "650 550 450" > sys/devices/virtual/misc/charge_current/charge_current​

      I will try to keep this post up to date with any relevant changes in the kernel.

      P.S.: I will not respond to request what settings you should use to achieve the highest score in a benchmark or how you get the most battery life. This is just to gather the information that is already floating out there. What you do with it is up to you ;)
      4
      [REF]Init-Script Reference Guide By kwerdenker

      MANY THANKS KWERDENKER FOR THIS. REPRODUCED WITH HIS AUTHORIZATION.

      Original post from kwerdenker here.

      I hope some of you find this useful as a reference for creating your own init-scripts. This contains everything I use or at least remember about the options in this kernel. If I forgot something or made an error somewhere, please send me a PM and I will gladly correct it.

      How to use these settings:
      If you want to test some settings before you commit them to a script, you can use either the adb shell if your on a pc with adb installed or you can use Terminal Emulator directly on your phone. Remeber to enter superuser mode by entering su in the terminal before you try to set anything or you will get errors. After that just enter the line you want with the values you want to test (if the values are incased in "", keep them that way!). If you want to see if it worked just enter cat followed by the part behind the > of the lines and you will get the values that are currently set. Everything you do in this fashion will not survive a reboot of your phone, if you want to make them permanent you'll have to use an init-script. A how-to on that is (currently) out of the scope for this post. Have a look/search in the kernel release thread as there are many examples for that there. I'm sure with this post and these examples you can figure it out by yourself :)

      The values in the echo commands are the stock values (from 2.1.1 version) if not noted otherwise

      [CPU]
      [Frequency]
      [Steps]
      # Controls which frequency steps are available
      # Should probably only be used to set the lowest step to 25 and/or the highest to 1696
      echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table​
      [Scaling Min]
      # Controls which frequency is use by the governor as the minimal frequency (has to be a valid value in the frequency table!)
      echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq​
      [Scaling Max]
      # Controls which frequency is use by the governor as the maximal frequency (has to be a valid value in the frequency table!)
      echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq​
      [Voltages]
      # Controls with what voltages the frequency steps are supplied
      # Highest step is to the left, lowest to the right
      echo "1425 1325 1275 1175 1075 975 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table​
      [Governor]
      # Available governors: ondemand, lulzactive, smartassV2, conservative, userspace, performance, powersave, brazilianwax, savagedzen, smartass, lagfree, ondemandx
      echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor​
      [GPU]
      [Frequency]
      # Controls with what frequencies the GPU works
      # Valid frequency steps are 100 114 133 160 200 267 400
      echo "160 267" > /sys/class/misc/gpu_clock_control/gpu_control​
      [Voltages]
      # Controls with what voltages the GPU works
      # Lowest possible value is 800000, maximum is 1200000
      # Changes are only possible in 50000 steps
      echo "950000 1000000" > /sys/class/misc/gpu_voltage_control/gpu_control​
      [IO]
      [Scheduler]
      # Controls how IO requests are scheduled.
      # Available schedulere: noop deadline cfq bfq sio vr
      echo sio > /sys/block/mmcblk0/queue/scheduler​
      [BUS]
      [Frequency]
      # Controls with what frequency the bus operates
      # Valid values are: 0 (400MHz), 1 (266MHz), 2 (133MHz)
      # Highest frequency step of cpu is to the left, lowest to the right
      echo "0 0 0 0 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
      echo disabled > sys/devices/system/cpu/cpu0/cpufreq/busfreq_static # Use enabled to activate this feature​
      [Charging Current]
      # Controls how much power the phone is willing to draw from a specific charger type
      # Values are from left to right: AC Misc USB
      # !This is a dangerous setting. Use with caution and never change the USB value and never set the other ones higher than 1000!
      echo "650 550 450" > sys/devices/virtual/misc/charge_current/charge_current​

      I will try to keep this post up to date with any relevant changes in the kernel.

      Example GPU/CPU undervolting and underclocking scripts by kwerdenker please just use for Reference

      Improved version of CPU undervolting script by kwerdenker please just as a reference

      P.S.: I will not respond to request what settings you should use to achieve the highest score in a benchmark or how you get the most battery life. This is just to gather the information that is already floating out there. What you do with it is up to you ;)
      4
      BLN Problems

      to fix it you can use the lib in /res/misc (lights.GT-I9100.so)
      copy it to /system/lib/hw reboot and you can use BLN Control :):):):):):):):):)

      PS: yeah, CM7 native bln are not YET working...but it is being worked on it
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone