yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gokhanmoral:
right, because I reverted back to "xz -1e" compression.

"gzip -1" version exceeds the tar file upload limit for this forum.

xz-1 is comparable to gzip-9 in decompression time and also provides a lot more compression.
[Galaxy S II Original Android Development] KcDaRookie:
You can decrease every frequency at the same time, but you can't tell the specific clock speed at which the phone crashed because of a current shortage...

But you can estimate the culprit: If the phone crashed while gaming or high ressource usage it's most likely the highest both values are to low.

If it stucks in screen off idle (SoD, ie won't wake up again after screen off for a while) its most likely the lowest value, if you have 25 MHz as first and 200 as second it can be one of the two or your phone can't handle the 25MHz step, mine can't even handle 100MHz.

If it reboots randomly while tabbin through homescreens or low ressource usage check the middle values.

You can see my settings in my sig.

The easiest way to find lowest usable freq for lowest used frequency is putting 800mV as current, if it is too low it will hang almost immediately, if it doesn't get stuck, put the screen off for at least a minute and check if it will unluck flawlessly, if it does, try going down in 25mV steps and go through the procedure again until the phone won't behave as expected, then go back to the last setting and test if for at least a day, if it gets stuck and only just for once I would still recommend to add another 25mV.

With the highest frequency just go down in 25mV steps and play something with high ressource usage until it gets stuck and than add back another 25mV and try for at least a day.

It also seems that if you use very low voltages at the lowest frequencies you also have to raise the highest frequencies, at least for me.

If I leave 200MHz at 825mV I have to set 1,6GHz to 1500mV (Stockvalue +50) else it will get stuck after a while.

If I put 200MHz to 850 or 875 I can decrease 1,6GHz to 1400mV, so if at some point you face issues you have to decide if your phone is more often on higher or lower frequencies and where you see it fit best that the currents are lower.

Hope this helps.
[Galaxy S II Original Android Development] westernmg:
Never before i had such an amazing batterylife like with CM7-117, Baseband XXKP1 and Siyah-v2.5.2b.

Great work gokhan!
[Galaxy S II Original Android Development] goldbergx:
I lose my IMEI every time I plug my phone into the car charger. This was with the KL1 modem, Siyah 2.1.1, CheckROM v2.0.

Any clue why this might have happened? Tried to reproduce it thrice and IMEI disappeared every time :o - will take a logcat if you guys think that would help.
[Galaxy S II Original Android Development] kobi63:
why is the performance.zip is on bfq and conservative? very surprising... another thing is the Charging current, isn't it dangerous it's on 900mA?(all of this according to voltage control app)
[Galaxy S II Original Android Development] KennyLegend:
Charging current is limited to 600mA on the device anyway so it doesn't matter.
[Galaxy S II Original Android Development] gokhanmoral:
charge current has two states: either >450mA or <=450mA

so, no. it is not dangerous.

your device won't exceed 650mA anyway.

EDIT: KennyLegend was faster than me :)
[Galaxy S II Original Android Development] KcDaRookie:
Conservative is a very powerful governor and can be set to very aggessive upscale-values so it will give you very high performance, but I'm not too familiar with the io scheds..

The phone won't charge at 900mAh, if you had searched the thread only once you would know why.. so no it is not dangerous to put it to 900

edit: wohow tripple nipple we should call ourselves ;)
[Galaxy S II Original Android Development] Vaedryn:
2.6 is your Masterwork Gokhan.

Absolutly fine. :thumbup:

Thank you for this and all other before.

SGS II Cyanogen Tapatalk
[Galaxy S II Original Android Development] kobi63:
thank you all for your fast answers :)

what's the best I\O Scheuler and governor for Gaming? Modern Combat 3 is kinda laggy on my I9100 and i want it to run smooth
[Galaxy S II Original Android Development] KennyLegend:
Think i prefer 2.6 without the battery script. Was using it earlier without any scripts and it was greAt. Might try performance script later.
[Galaxy S II Original Android Development] KennyLegend:
Performance?? With sio scheduler maybe.
[Galaxy S II Original Android Development] kobi63:
Yes, by gaming i ment gaming performance especially..
[Galaxy S II Original Android Development] Dennys_Santos:
I applied the Kernel 2.6_S99 now and do not need in my SGS2 performance, then I use the file: siyah-battery.zip, to have the lowest energy consumption? ?

Thank you guys.
[Galaxy S II Original Android Development] KcDaRookie:
I would say vr or deadline...

Read this thread and choose for yourself http://xdaforums.com/showthread.php?t=1369817
[Galaxy S II Original Android Development] Mutalisk:
I guess he ment performance governor,

should really be the best if you don't want to have ANY lag - as it locks your CPU at the highest frequency possible!

But not very battery friendly and might overheat easily ;)

Otherwise try conservative :)
[Galaxy S II Original Android Development] KennyLegend:
Yes exactly. I meant try performance governor.
[Galaxy S II Original Android Development] xcarecrow:
Please, can someone explain me what this line do in the script?

echo 524288 > /sys/module/pm_hotplug/parameters/freq_cpu1on

i understand almost all lines but not that.

and if someone can explain me to the lines of the brightness settings:

echo 50 > /sys/class/misc/brightness_curve/min_bl

echo 0 > /sys/class/misc/brightness_curve/min_gamma

echo 20 > /sys/class/misc/brightness_curve/max_gamma

thanks in advance!!
[Galaxy S II Original Android Development] Nexu$:
First and foremost THANK YOU to the developer. I used 2.5.2 over CM7.1 and Market used to freeze the device for no reason.

Just updated to 2.6_S99 and am hoping to see this issue gone. If not, I will just wait for the next release!!!

THANK YOU :D
[Galaxy S II Original Android Development] gokhanmoral:
freq_cpu1on is hotplug second core activation frequency

I put there 2^19 to make it look complex :P

you can use 500000 and it will have the same effect

if freq <= freq_cpu1on then cpu1 will not be activated.

for the second part:

we have lowest brightness until we have brightness level read from the sensor is > min_bl

sensor gives us a value between 0 and 255. we map it to 0-24 (we have 25 levels of brightness)

so, if we read anything between 0 and 50 from the sensor, we will have brightness level 0.

since I modified the first brightness level and made it darker, I also introduces min_gamma setting.

if you prefer brighter display (as in stock) for low light conditions, set it to 1.

sensor values between min_bl and 255 are linearly mapped between min_gamma and max_gamma.

so, if you set min_bl to 30 and min_gamma to 1, max_gamma to 24 you will have nearly stock brightness levels.

the settings I put in siyah-battery.zip file is the settings I use.
[Galaxy S II Original Android Development] stylez:
the additional zips are named to correspond with what they do..

battery for best battery life less performance

Performance is fast and will eat more battery

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] xcarecrow:
So if i put 800000 instead of 500000, second core only will activate when cpu reach 800mhz, right? so if i keep this line, are this line needed anymore if the activation is defined by frequency?

echo 80 > /sys/module/pm_hotplug/parameters/loadh

I know we can keep the screen off parameters but, can we remove any line more?

echo 35 > /sys/module/pm_hotplug/parameters/loadl

echo 90 > /sys/module/pm_hotplug/parameters/loadl_scroff

echo 100 > /sys/module/pm_hotplug/parameters/loadh_scroff

echo 400 > /sys/module/pm_hotplug/parameters/rate

echo 400 > /sys/module/pm_hotplug/parameters/rate_cpuon

echo 1000 > /sys/module/pm_hotplug/parameters/rate_scroff

and if i don't use autobright, can i only have just this line?

echo 0 > /sys/class/misc/brightness_curve/min_gamma

thanks in advance.
[Galaxy S II Original Android Development] CamoGeko:
With my cfg, conservative works perfectly even while playing latest HD games. Like GTA3 and 9MM for example.

So it's not necessarily a governor issue if someone gets lags in games. :)

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] fr3quency:
I clean installed XWKK5 and installed Siyah 2.6 But I don't see the CWM app and the superuser one. :( Tried to install titanium from market, but I get I dont have root access. Is it the kernel? Or should I use oneclick root?
[Galaxy S II Original Android Development] InnAl:
lol, i like that :)

Anyway, nice job again and really cool kernel !

(Maybe a DK version with possibility to change the voltage would be appreciated by many users.)

Thank you
[Galaxy S II Original Android Development] gokhanmoral:
oops :)

I think we will have a minor release for that.

meanwhile, flash cf-root first, reboot and then flash siyahkernel.
[Galaxy S II Original Android Development] SPACE ALIEN:
Sorry for stupid question, but.... What we have to do with this...?

“siyah-battery.zip“, “siyah-performance.zip” and “siyah-defaults.zip“

Have to flash one of those after flashing the Siyah's kernel? What first?

Someone please...:(:o:confused:
[Galaxy S II Original Android Development] seaweeduk:
Flash none of them if you want default config, battery for extra battery life or performance for more performance I wonder if you can figure out what the third one does
[Galaxy S II Original Android Development] gokhanmoral:
you can flash them before or after flashing the kernel.

but since they are init.d scripts, you have to flash them again if you flash a new kernel.

or do not flash anything if you try the default settings :)
[Galaxy S II Original Android Development] el_liberator:
first flash the kernel, then one of three scripts
[Galaxy S II Original Android Development] SPACE ALIEN:
ok, thanx a lot for your quick answer !!!

Try it now !

:)
[Galaxy S II Original Android Development] el_liberator:
This kernel is the best I've experienced, thanks Gokhanmoral ;)
[Galaxy S II Original Android Development] xcarecrow:
So Gokhan, if we can define the frequency in mhz when we want the second core activated, will the second core turn off when we reach a frequency below the defined? that frequency defined will act too in screen off mode? or there is a value we can modify too. Because it's easy just define one value than define all parameters of hotplug.

thanks.
[Galaxy S II Original Android Development] KennyLegend:
I've tried both battery & performance scripts now and it seems as though my phone was faster responding without any scripts flashed. Is this possible?
[Galaxy S II Original Android Development] stevehkim:
which zip are you using?

supercharged sgs2 i777 galnet rom/siyah kernel = beast
[Galaxy S II Original Android Development] el_liberator:
the battery script , because I prefer more battery life to performance ,

I don't play any games, so the battery is my priority :D
[Galaxy S II Original Android Development] cheewaca:
Thanks Gokhan, the last version is the best of all. Smooth very smooth.

Thanks again.
[Galaxy S II Original Android Development] Holgott:
Can any1 tell me whether i am right? I flashed siyah 2.6 and had lionheart script in init.d folder. I just wanted to have a stock 2.6 kernel, so i deleted lionheart from this folder and flashed default siyah script from gokhan to have it stock, right? The question in the end: if i delete now 01Siyah script from init.d folder-is it the same like stocked or should i let it alive? ;) ..its just a question to make things clear to me ^^

stock i9100XXKK5 with imba

Siyahkernel 2.6!!
[Galaxy S II Original Android Development] KennyLegend:
Delete your init.d folder,(assuming u are not using any other scripts), click on"remove boot settings " if you are using voltage control app and flash v2.6. this is default config.
[Galaxy S II Original Android Development] Holgott:
Ty bro for the fast answer!testing out but till now smooth for me with conservative and bfq

stock i9100XXKK5 with imba

Siyahkernel 2.6!!
[Galaxy S II Original Android Development] cloak:
Is it allowed running setCPU with the 2.6 kernel, or do I have to uninstall setCPU before flashing the 2.6 kernel?
[Galaxy S II Original Android Development] kobi63:
Is there a reason why 1600mhz isn't included in the performance.zip? Is it useless?
[Galaxy S II Original Android Development] cmd512:
Holy smoothness Gokhan... v2.6_S99 is AMAZINGLY smooth on lulzactive/sio. Cheers!
[Galaxy S II Original Android Development] poochewer:
Exellent technical writing by droidphile

BOY OH BOY !!! Those posts by @droidphile are unbelievably concise,comprehensive and simply written.

Definately mandatory reading for all noobs.

Thank you @droidphile!!!
[Galaxy S II Original Android Development] PedroMRP:
Awesome Kernel... Simply the best there is for Galaxy SII!

Thanks very much Gohkanmoral for the hard work and dedication
[Galaxy S II Original Android Development] poochewer:
What script are you using? cos on mine (performance script), I found sio/lulz to be not smooth(video playback and gui)

In fact I found bfq/ondemandx to be the smoothest.
[Galaxy S II Original Android Development] Entropy512:
Or just flash ChainsDD's latest Superuser package in CWM (this is the easiest method - and actually I've made it the recommended method for users of my kernel since that way I don't have to track his updates.)

Nothing about SetCPU should ever cause a problem for anyone, unless you explicitly choose a setting in SetCPU that is fundamentally unstable. (One exception - Choosing a screen-off profile below 800 MHz on a Samsung running a kernel that doesn't have an SoD fix for that. Which basically means only stock kernels on Samsung Hummingbird/Exynos.)

No, it's unstable on many devices. If it were stable on all devices, they would be sold as 1.6 GHz devices.
[Galaxy S II Original Android Development] tolis626:
Well,2.6 running heavenly here still,but I have to say,it doesn't like benchmarks!Linpack for example is down to 80-90MFLOPS from 120-130MFLOPS at 1600MHz! :eek:

Not that it matters,but just sayin'.We have to complain about something,right? :p
[Galaxy S II Original Android Development] noobsgs2:
Im just able to get around 2k with siyah 2.6 kernel on quadrant and only 44 on linpack when with 2.5.2 was able to get 4k+ and 90 or more on linpack...

I'm wondering if

is the problem

Trying to test more with dual-core benchmarks

---------- Post added at 10:47 PM ---------- Previous post was at 10:46 PM ----------

Could you try different bench pls?

Anyway moved back to 2.5.2 and able to reach 94MFLOPS with 1.2ghz smartassv2 - VR... seems another world..
[Galaxy S II Original Android Development] poochewer:
LOL you started this
[Galaxy S II Original Android Development] Thenetstriker:
Can someone please upload the complete source package somewhere else? This link does not work anymore: http://www.gokhanmoral.com/public/files/siyahkernel/source/siyahkernel-2.2.tar.gz
[Galaxy S II Original Android Development] oxwald:
Nothing with the charging current could be done? :(

I mean, override the MAX8922 limitation to increase it?

For me it's the only important thing that is left..
[Galaxy S II Original Android Development] cmd512:
I customized the bootup script that Voltage Control generated. Loving the phone on lulz/sio.
[Galaxy S II Original Android Development] tolis626:
Sigh...Why did I even ask? :(

Look,2.6 is superior to 2.5.2,get over it.Smoother,more battery-friendly,BETTER.It's not so good in benchmarks.Big f*cking deal.It's strange,yes,and I too liked the big numbers I was getting,but changing from such a good kernel for benchmark results is plain stupid.If you insist on changing for benchmarks,I think you should try another kernel.

@Gokhan

Have you tried overclocking the bus like you had said?Just curious. :)
[Galaxy S II Original Android Development] gokhanmoral:
then we finally had what we wished for :D a kernel which is smooth but also has low benchmark score to keep benchmark-slaves away ;)

well, it is strange. and I don't know why. is it also low with performance profile?

maybe I did something wrong...

no, I did not try it yet. but I will, I promise :)
[Galaxy S II Original Android Development] thecrater:
Hi,

Am I missing something?! with the latest version 2.6 I no longer have CWMManager and SuperUser so my ROM is no longer rooted? Please help.
[Galaxy S II Original Android Development] tolis626:
From that point of view,2.6 is even better than we thought then! :p

It's with your performance profile further tweaked for more performance or something.Yeah,I'm nuts and I like it. :D :p

Anyway,I take your promise seriously pal.If you want a tester I'll be around.Let's just hope we don't fry anything. :p
[Galaxy S II Original Android Development] noobsgs2:
Well, i could just say u enjoy ur useless 1600mhz device while calling and smsing or browsing...wondering if it's me the one who need a different kernel...kernels like this has only goal read first post pls
[Galaxy S II Original Android Development] KennyLegend:
Lol...i enjoy ur posts Tolis !!
[Galaxy S II Original Android Development] KennyLegend:
Can anyone tell me the name ill see on the battery and the performance scripts in my init.d folder pls.. as i want to delete them and flash v2.6 again ..

I also have other scripts in there from the rom Im using and i dont want to delete the wrong ones .
[Galaxy S II Original Android Development] tolis626:
All of Siyah's init.d scripts are named 01siyah when flashed.So delete that script and you should be a-okay. ;)
[Galaxy S II Original Android Development] tolis626:
I hope you're saying this seriously. :p

I hope YOU are NOT serious.If yes,I feel sorry for you,really.

And btw,you have no idea how much I enjoy my 1.6GHz device doing stuff normal human enthusiasts do.Have you heard about your device's ability to play games and HD videos for example?

Anyway,don't take this further for both our sakes.
[Galaxy S II Original Android Development] Cygnuss:
Flashed but in CPUSpy it says deep sleep its in unused mode like this: 1600,1400,100, deep sleep

is this normal?
[Galaxy S II Original Android Development] Simba501:
Depends on how much time has passed, but no. You should be utilizing deep sleep, and those frequencies will only be used if you've OC'ed (1400, 1600) or have the 100 mhz frequency enabled (I believe the lowest is 200 by default).
[Galaxy S II Original Android Development] KennyLegend:
I don't joke around :)
[Galaxy S II Original Android Development] KcDaRookie:
let it stay screen off for at least 5 minutes without touching, if your phone still does not get in to deep sleep this isnt normal, to be on the safe side you should also deactivate 3g/wifi and put phone to airplane mode.

if you have deep sleep time with these settings something is constraining your phone from going into deep sleep.
[Galaxy S II Original Android Development] Cygnuss:
OK i just flashed thats why its not in use :) thanks
[Galaxy S II Original Android Development] PedroMRP:
2.6 is just sick (in the very good way) I think its by far the best version that i've tested so far...
[Galaxy S II Original Android Development] Entropy512:
It's kind of buried in gokhan's blog - but he has started using distributed version control (Although using mercurial instead of git - which is in my opinion a little bit odd for Linux kernel work. :) )

http://www.bitbucket.org/gokhanmoral

The only possibility is if the device's internals are wired in such a way that control of charging can somehow be handed back to the MAX8997.

This is HIGHLY unlikely (The chances Samsung properly wired two different chargers in parallel with each other to the battery are VERY slim), and trying to mess with this has a very high risk of permanent damage to the developer's phone.

There is no way to change the MAX8922's current limit without physically modifying the hardware to change the current limit set resistor.

Unlike the MAX8997, the MAX8922's datasheet is publically available, so it's possible to know EXACTLY what it is and isn't capable of.
[Galaxy S II Original Android Development] oxwald:
Thanks for the info!

So, in a few words.. nothing can be done.. :(

It's a **** when you are using it as a GPS, with the screen on, bluetooth and music, but connected to the charger and you can see your battery draining...

Also it's a pity to wait almost 6h for a complete charge with the 2000mAh battery..
[Galaxy S II Original Android Development] whazi:
retard question abt voltage ctrl..

so: i flashed 2.6 then battery zip.. what happens now? ive to go to voltage ctrl and apply on boot the usual uv and governor\sched or doing that i messup the tuning made with battery zip? if i got it correctly that battery zip is making the init file just like the app?

PS: opening voltage ctrl i can see all my old settings but under the title says unsaved settings.. that means untill i dont press save as boot my phone is running with what gokhan set as default?

getting confused.. if u need some screenies just ask:P
[Galaxy S II Original Android Development] knightnz:
My phone now boots to the lockscreen before the bootanimation completes. Great work!
[Galaxy S II Original Android Development] beston94:
Lets see if you get where i'm going with this...

YOUR AWESOME
[Galaxy S II Original Android Development] stylez:
sounds like you didn't remove boot settings in VC before flashing battery.zip ;)

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] whazi:
what i should do then? from the app remove the boot settings then reflash battery zip and forget abt uv?
[Galaxy S II Original Android Development] lutanica:
deleted........
[Galaxy S II Original Android Development] stylez:
You can always use VC to tweak the settings battery.zip creates.

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] gokhanmoral:
good news and bad news:

good news: I fixed autorooting (and also CWMManager and ntfs-3g problems which are also related with the extraction of the payload) problem & tested autorooting by flashing stock KK5.

bad news: you have to re-download v2.6 if you need autorooting and/or ntfs-3g. there is no new version. just redownload it.

it's already 3:45am here and I did this to clear my mind from work. so, don't think I am nice & cool :p
[Galaxy S II Original Android Development] AJ.Rockwell:
Yes you are nice&cool, I've flashed 2.6 in CWM while in bed getting ready for sleep haha, good luck on your current endeavors! Once you go Siyah you can never go back :-D

Sent from outer space by aliens on tapatalk using SGS2
[Galaxy S II Original Android Development] veeruchinnu143:
Guys plz provide link for v2.6...sorry if its already there(but couldn't find it)
[Galaxy S II Original Android Development] sahidmiah:
Does one have to use performance zip.or battery zip.with 2.6 kernel. I thought its all in one complete
[Galaxy S II Original Android Development] AJ.Rockwell:
For links to kernels www.gokhanmoral.com should be saved in your browser's favorites. As for cwm-based settings it's up to you to decide.

Sent from outer space by aliens on tapatalk using SGS2
[Galaxy S II Original Android Development] danielsf:
How come to voltages have gone up in the 2.6 update please, like for 1200mhz it was 1250mv and now it is 1275mv, does 25mv actually do anything please?
[Galaxy S II Original Android Development] xysonata:
Everything used to work fine for me. But since v2.5.2, I've been having these fixed black horizontal lines on my screen. It appears for me on both CM7 and Samsung roms. I was hoping that the issue would be fix after the new update but it didn't. I'm not having this issue on others kernels.

I hope this problem gets fixed soon. Thanks!