yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] AndreiLux:
Huh? You put the ramdrive cheat into the kernel? That's bull****. Those differences between ROMs had nothing to do with that. Please remove...
[Galaxy S II Original Android Development] lpsi2000:
No confusion, 5.1 is the latest good beta for most.
[Galaxy S II Original Android Development] Kwakkel:
I almost bricked my phone, I used ROM-manager instead of CWM to flash this kernel. Got stuck at the yellow triangle. But I managed to flash another new kernel with ODIN. After that, the phone booted to CWM recovery and I was able to fix it.

In the end, I was able to flash 2.2b5.1 and this kernel is good. It is as smooth as a hot knife through butter. No more lags.
[Galaxy S II Original Android Development] :
To me it's io boost and/or tweak. Quadrant is bull**** anyway, but lot of n00bs use it and judge rom and kernel performance by it without any knowledge.

If I can vote, I vote to keep it.

Edit: you should judge kernel by real life performance anyway and anyone knowledgeable and using quadrant advanced can see whats boosted.. Clear from my screenshots.
[Galaxy S II Original Android Development] :
You'll hardly brick your phone flashing kernel. No worries.
[Galaxy S II Original Android Development] gokhanmoral:
that boot-time-configuration app will take longer than I think because I don't have enough free time.

I will prepare a script-based solution for v1.7 in this week

you are going to dump all the settings to a file in, lets say, /data/.siyah-settings. the script will parse that file and apply the settings.

file format will be simple. I am thinking about something like:

GPU-FREQ: 100-160
GPU-VOLT: 800mV 900mV
CPU-LOW: 100
CPU-HIGH: 800
CPU-VOLT@100: -50
CPU-VOLT@200: 900mV
AC-CHARGE: 1000mA
USB-CHARGE: 550mA

an application would be better but this will be very simple enough for everybody.

I think that people who cannot edit a simple text file should flash a custom kernel anyway :)
[Galaxy S II Original Android Development] gokhanmoral:
I could not apply arighi patch because it is based on min-max frequencies. applying it will put your cpu to 1600mhz when you turn your screen on. I modified it but then I remembered some people were still using setcpu profiles. I thought of a potential problem in that. therefore I removed it for now.

USB charging should be fixed now. when you echo 1000 1000 450 to charge-current the values will be parsed correctly.
[Galaxy S II Original Android Development] sasho36:
Yes, confirmed, they are parsed correctly, thanks!!!
[Galaxy S II Original Android Development] kwerdenker:
Flashed and currently running fine but the lockups with 1.7 took some time, so I'll have a sharp eye on my phone and report back if anything noteworthy occurs.

Thank you for your continued support! :)
[Galaxy S II Original Android Development] grisha1:
Thank you for the explanations.
[Galaxy S II Original Android Development] :
That's cool, but you know what I want :D BFS .. just kidding, take your time and get some rest.
[Galaxy S II Original Android Development] gokhanmoral:
I have added ntt version to the OP.

if you have EU device do not flash it.

for ntt users: please test your tv function. if it doesn't work please post a link to a stock kernel for your device so that I can check which module is required.
[Galaxy S II Original Android Development] ebliss:
just had a random reboot with 1.7.2 while using titanium backup.

after flashing 1.7.2 via cwm recovery, I booted up. without touching the phone, the phone rebooted to the Samsung galaxy logo.
[Galaxy S II Original Android Development] saikikyo:
thanks for sharing~~just updated to 1.7.2~~
[Galaxy S II Original Android Development] chadouming:
Dont know what you changed with 1.7.2, but now i'm able to use this kernel on 2.3.5 without having my internet droping every 30 sec ^^. Looking forward for your next release :D. Keep on your hard work.
[Galaxy S II Original Android Development] gokhanmoral:
was it dropping with the previous versions?

strange... it was a self-fixing bug maybe :) I love those bugs...
[Galaxy S II Original Android Development] :
Heheh those bugs are fun.. Flashed 1.7.2 of course and all seems ok. Thanks.
[Galaxy S II Original Android Development] chadouming:
Yeah, found it was most non-updated kernel that does drop internet every 30 sec on my phone. Only kernels not doing this for me now are : yours, cf-root and netchip superpower.

Got a suggestion while i'm here, can we have higher overclock? Would be nice to achieve 2Ghz on another kernel than tegrak.
[Galaxy S II Original Android Development] sasho36:
2 hours and no lockup so far. But I sometimes have a strange bug: when I reboot or boot with charger plugged it I have no signal, wifi is ok. If I unplug the charger and reboot, everything is fine... Had this with 1.7rc1 also.

Thanks for your time and work!!!
[Galaxy S II Original Android Development] uronfire:
1+

Same here
[Galaxy S II Original Android Development] cbeckstein:
Does this kernel support IPV6 privacy?
[Galaxy S II Original Android Development] paranoid2007:
Sorry, if I'm asking stupid questions, but how do I change the scheduler?
[Galaxy S II Original Android Development] gueutzilla:
Hi,

Does this kernel support tun.ko for openvpn usage???

Thanks for your help :)
[Galaxy S II Original Android Development] kwerdenker:
Use No-Frills as an app solution or if you are confident with adb shell/terminal emulator:

echo <name_of_scheduler> > /sys/block/mmcblk0/queue/scheduler

BTW: This has been posted already, so next time please use search function before asking questions.
[Galaxy S II Original Android Development] gokhanmoral:
I think it is related with increased charging current. I will set it to defaults in the next version. Maybe samsung has lowered it not to increase battery life but to solve this problem, who knows...
[Galaxy S II Original Android Development] Kwakkel:
Well, at least it felt so. I waited a couple of minutes but the phone did not boot further than the yellow triangle. I made some attempts to reboot again, but without any success.

You're saying that you can solve any kernel problem with ODIN and that is literally impossible to brick your phone? Or are other methods than ODIN?
[Galaxy S II Original Android Development] gokhanmoral:
yes, I did. those differences may be related with either patched sqlite library or the ramdrive cheat.

but patching libsqlite can only increase the quadrant a little..

I know that lots of people migrated to Lightning ROM just because having higher quadrant or they changed kernels tens of times just because the screenshots of those who use ROMs having that cheat.

that ramdrives can be removed by

umount /data/data/com.aurorasoftworks.quadrant.ui.standard
umount /data/data/com.aurorasoftworks.quadrant.ui.advanced

my point is to show quadrant-racing is meaningless.

and ok.. I'll remove it in the next version.

the "tweak" is in /sbin/siyah/tweaks.sh (last couple of lines)
[Galaxy S II Original Android Development] jona29:
i vote for higher o/c speed adding to kernel for those who dare to live on the edge !!!
[Galaxy S II Original Android Development] mariosraptor:
5.1 no lag here, 5.2 laggy as hell while opening folders on go launcher ex. Thanks for your work.
[Galaxy S II Original Android Development] Ogy77:
I cant flash zip from sdcard just write message Can't mount /sdcard/ and must go internal sd card and then can flash,no memory card in phone,any solution,becouse before I flash this kernel I can flash from sdcard?
[Galaxy S II Original Android Development] KennyLegend:
Heh heh heh I just tried cf bench on beta 5.1 o/c to 1.6ghz and halfway through the phone shut down and got hot ....wow!! Lol
[Galaxy S II Original Android Development] cmd512:
Agreed, anytime I see a Quadrant screenshot posted, I dismiss any further comments from them as useful.

Take it out or leave it in, doesn't make a bit of difference to those of us who actually appreciate your kernel's REAL performance and your solid support for it. Quadrant comparisons are a complete waste of time.
[Galaxy S II Original Android Development] :
Well as long as you can get to download mode you are good to go with odin. What's more dangerous is efs screwup so I hope everyone has efs backup.
[Galaxy S II Original Android Development] :
Lol, I tried the same, but at 1696 by modifying cpu_freq and the same happened :p
[Galaxy S II Original Android Development] shr33kant:
To be honest dude...I'd rather that you leave it in xD...It'll stop all the benchmark screenshots because everyone will just "Know" their device is fast :P.
[Galaxy S II Original Android Development] TecQuality:
hey fellows, someone use nofrills with this awesome kernel?
[Galaxy S II Original Android Development] maniacfb:
5.1 gets about 90 fps on glbenchmark pro offscreen

And 2800 on smartbench - game

5.2 gets ever over 100 fps

And over 3000 on smartbench - game

Both with gpu on 400

So its slightly noticeable on 3dgames (could be placebo but i think the improvement is present)

BUT only improved on 3d for now. 2d seems laggy on some apps

So the new drivers cant be such bad. Only buggy ?
[Galaxy S II Original Android Development] chadouming:
You can change the higher freq. OC to your need. Just one question to gokhanmoral : Could you make this table to have the internal voltage to tweak too and unlock the max freq cap or put it to 2.0 Ghz ? this would be awesome :D
[Galaxy S II Original Android Development] tolis626:
You dare to live on the edge?Yeah?YEAH?!?

Download GScript and make a script with the line echo "1696 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table.Now you're on the absolute edge.Feeling nice?Ok,then,while on the edge,jump.Hopefully it will be the first and last time you do it.

EDIT:With this post I don't aim to insult everyone who overclocks their phone to post-normal values.I am running 1624MHz and am happy with it.I'm just attacking the typical noob who measure their self-respect by numbers without knowing wtf they are doing.Btw,I agree with Chadouming! :D
[Galaxy S II Original Android Development] chadouming:
You don'T like living on the edge or high oc tolis ?
[Galaxy S II Original Android Development] tolis626:
Check my EDIT man.I figured out that this post could be misinterpreted. ;)
[Galaxy S II Original Android Development] alcurtis93:
Weird... I find the phone smoother on single core mode! Ha
[Galaxy S II Original Android Development] bragon2010:
What Tegrak app should i install? This? https://market.android.com/details?...t=W251bGwsMSwxLDEsImNvbS50ZWdyYWsubGFnZml4Il0.
[Galaxy S II Original Android Development] tolis626:
Not that I actually share your opinion,but it's f*ckin' fast for a single core.At 1.6Ghz Linpack's Single-Thread test gave about 76-77MFLOPS.Desire HD,same speed?45-50MFLOPS if I remember correctly.
[Galaxy S II Original Android Development] alphaola:
I think you looking for 2nd Core. https://market.android.com/details?id=com.tegrak.secondcore&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS50ZWdyYWsuc2Vjb25kY29yZSJd
[Galaxy S II Original Android Development] cmd512:
Could this be because there isn't real dual core support/utilization until ICS?
[Galaxy S II Original Android Development] bragon2010:
Yes! Thanks
[Galaxy S II Original Android Development] fasst:
Great to see that with 2.2.b5.1 we can use all functions in CWM3 app.

Thanks :)
[Galaxy S II Original Android Development] Moskiitto:
+1

Smoother yeah, but think about batterylife!! ;)

Sent from my GT-I9100 featuring Cyanogenmod and Siyah
[Galaxy S II Original Android Development] olifee:
@gokhanmoral:

Is

/sbin/siyah/modules.sh

supposed to be executed on boot "out of the box"? It works fine if I execute it after boot, but before I do so, I do not have a folder like

/lib/modules/2.6.35.14-Siyah-v2.2beta5.1

No problem if it is meant to be like that, I will just add it to an init-script for me then :).

I am not completely sure, but I think ntfs-3g was somewhere in a bin-path before some 2.2beta (I am not sure because I sometimes use the chrooted debian and sometimes android ;-) ).

Did you package it with busybox before, or was the $PATH different?

I can now only find a copy in /data/cifs along with a fuse-module which is different from yours, so I guess this is from the ROM or one of my experiments.

I always thought CheckRom RevoHD brought ntfs-3g in ;-).

Thanks for all your good work! By the way, the "lagging" was somehow unnoticeable for me, although I use a Samsung-based ROM, GoLauncher and have many apps in app-drawer. Maybe my animations are not fancy enough ;-).
[Galaxy S II Original Android Development] TecQuality:
What is the cwm3 app? Can you link me please?
[Galaxy S II Original Android Development] gokhanmoral:
it should be executed during boot. I will check it.

and I remember I put ntfs-3g in initramfs and thought about using hotplug script to automount ntfs formatted sticks.

it is still in my todo list. until then keep your ntfs-3g somewhere accessible :)
[Galaxy S II Original Android Development] kryptoner:
No lag at all on beta 5.1. Is it just me or the phone overall feels a lot more smooth when put on single core mode only using 2nd core app???

One more thing, will using a single core only affects second ineffective core in any bad way? Like will it affect the cpu efficiency or lifespan?
[Galaxy S II Original Android Development] fasst:
By flashing the kernel
[Galaxy S II Original Android Development] alcurtis93:
I agree. I think it feels smoother. Shouldnt effect the life. The CPU is still running at the same frequencies
[Galaxy S II Original Android Development] jona29:
wtf

i know exactly what the risks are by o/c maybe i dont know how to edit the script ! you know how to re write ecu map files ? i do . but i dont flame noobs for wanting to learn
[Galaxy S II Original Android Development] olifee:
One problem might be that when fixed to single-core, heat-dissipation will be slightly worse for the same workload (the heated area is smaller if only one "half" of the chip is active).

To countermeasure any such issues, a desktop-machine with multiple cores (and dynamic hotplugging disabled) automatically shifts high workloads from one core to the other after some seconds of 'heating' one core if only few high-perfomance-threads are active.

It appears that this does not happen with dynamic hotplugging activated, it seems that cpu0 is used all the time then (I may be wrong, but that's how it looks like at first sight).

I never saw a laptop with dynamic hotplugging active, but in case it might save some juice there too, I might try some time later ;-).

In general, CPU-wearing and the slightly worsened heat-dissipation should not be noticeable at all. As the second core is completely inactive, this might even improve the overall cooling, as our devices have a nice broad heatsink in the back.

Furthermore, I guess the OLEDs will be worn out ages earlier than our CPUs ;-).

---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------

I don't know either ;-).

I don't think he wanted to flame you, he meant it in a funny way, it was just put in some words that could be easily mistaken for flaming. And if you had no idea about o/c-risks, you might have even been happy with this 'warning'.
[Galaxy S II Original Android Development] TecQuality:
I've flashed the 5.1 but i haven't this app installed :-\
[Galaxy S II Original Android Development] gokhanmoral:
I confirm that using single core mode is more smooth.

but it is not normal. it means that something causes that during enabling or disabling second core.

I am now trying to find out the reason (have some ideas)
[Galaxy S II Original Android Development] CamoGeko:
CWM app comes with Chainfire's CF-Root kernel. :)
[Galaxy S II Original Android Development] energie:
now im sure next beta my sgs2 will be smooth as hell with 2 cores on :D
[Galaxy S II Original Android Development] fasst:
So, you didn't root with CF-kernel?

Anyway, here you go. CWMManager 3.0

http://db.tt/zUckVGYS
[Galaxy S II Original Android Development] Alienfreak:
I don't notice anything when running on the ICS Framework. But maybe its just me ;)
[Galaxy S II Original Android Development] incubus_fr:
/sbin/siyah/post-init.sh is called by init.rc

post-init.sh then calls the other /sbin/siyah/ scripts.
[Galaxy S II Original Android Development] tolis626:
Maybe I meant it so,maybe I didn't...I'll let his imagination work! :p
[Galaxy S II Original Android Development] tolis626:
There is definitely something wrong with the second core.When I force dual core mode,the device is kinda unstable,whereas Smartbench 2011(I use it after every kernel flash to ensure everything is still fast) just refuses to properly run.It always gives a message in the end saying that one of the tests didn't finish correctly.Single-core and hotplug modes are just fine.

That's on beta5.1,but beta5 had exactly the same behaviour.

Hope that helps! :)
[Galaxy S II Original Android Development] olifee:
Thanks, you made me find the reason why it does not work, a 'y' is missing in post-init.sh:

/sbin/busbox sh /sbin/siyah/modules.sh

However, a busbox might also be pretty useful when you are lost somewhere and need a way to get home ;-).

I'm glad it is such an easy fix for gokhanmoral and not something special to my setup :).

EDIT: Just checked Q&A-thread, apparently someone was faster than me in finding the missing 'y' ;-).
[Galaxy S II Original Android Development] crypticc:
Scrolling market place descriptions with graphics shows it best for me. Maybe this is memory contention, or as work is handed to the other core the first workload must still wait?
[Galaxy S II Original Android Development] chadouming:
I think that i worth what my phone can push in term of performance ! You got a problem with this ???? ! Just kidding, i c your point :P.
[Galaxy S II Original Android Development] olifee:
Is that with UV/OC? Does it also happen if you lock the frequency to a fixed value?

Maybe the second core behaves slightly different / worse for higher frequencies / lower voltages, and this causes the instabilites.
[Galaxy S II Original Android Development] TecQuality:
I know this mate, but i haven't the 3.0 version, i'm running the older 2.0 version.
[Galaxy S II Original Android Development] incubus_fr:
Ah ah! That was so obvious!

I was looking at init.rc to see if the call to post-init.sh was too early, mount wise.
[Galaxy S II Original Android Development] crypticc:
Shouldn't busybox be in /system/xbin any way?
[Galaxy S II Original Android Development] fasst:
Maybe it was just a coincidence that Market wanted to update my Busybox after flashing b5.1?

In /system/xbin.
[Galaxy S II Original Android Development] shanume:
this is so weird after I flash to 2.1+ siyah kernel my phone is so unstable with my undervoltage settings from setcpu! my settings work find without problem in siyah 2.0!

I can only use stock voltage now with 2.1+ kernel version :(

I want to use 2.2b5 becuz this support tregrak 2nd core apps..

do anyone has the same problem? or maybe someone can help me :)
[Galaxy S II Original Android Development] goose2600:
Sorry, post deleted
[Galaxy S II Original Android Development] TecQuality:
Just flashed for the first time a siyah kernel over the stock XXKI4 never seen my wifi like this, i don't know why, but now the wifi running like a charm!
[Galaxy S II Original Android Development] chadouming:
Everyone has this trouble man :/. Most of the people have gone back to Speedmod because of this :( and the rest are going to abyss kernel :'(
[Galaxy S II Original Android Development] shanume:
okay :( this is bad to hear that, I hope siyah kernel can get this fix or many people will leave then.. :/
[Galaxy S II Original Android Development] vnvman:
Not me...i got all the frequencies @-75/-100 mv compared to stock, not a single freeze, sod or anything. I'll never drop this kernel, it just gives me the best battery life i ever had on an android device. Come on people, don't go crazy for getting low voltages at the lower frequencies, this is pointless: uving the higher ones is much more effective, when in deep sleep the cpu will be power collapsed anyway regardless the voltage you set @200mhz. This kernel is a beast: it's faster than Lulz and has very similar functionality, and even better battery life, plus it works on every single rom...you can't really ask for more imho.
[Galaxy S II Original Android Development] TecQuality:
What governor and scheduler do you use?
[Galaxy S II Original Android Development] olifee:
Did you ever try to raise your voltages and then compare the runtime of your phone against other kernels with the lower voltages?

I did not try this yet (I love Siyah too much :) ), but my guess is that Siyah-kernel should still win.

UV-effects are not that big anyways (can't give you a number here), but the choice of governors and other features should compensate for the most different use cases.

The main reason the lower voltages do not work anymore are the newer Samsung-sources being used (which gives nice speed and should also conserve more power, I think there is even CPU-class-dependent UV already in there, invisible to the 'normal' user) and that the lower voltages are used in more places in the kernel.

Since the 2.1 betas, I completely stopped using UV and did not 'feel' any difference. But as I said, YMMV, so do your measurements yourself. But please do not judge a kernel by the UV-settings with which it is stable, but by runtime (which is the thing that counts...).

Oh, and that discussion (your question and my answer) would have been better placed in the Q&A-thread: http://xdaforums.com/showthread.php?t=1325831

After all, you should only do a 'bug-report' in dev-section after researching your problem first in Q&A or asking there if you are not sure there is something 'broken' ;-).
[Galaxy S II Original Android Development] vnvman:
Just ondemand with cfq scheduler, no sleep profile or anything, i like to keep it simple :cool:
[Galaxy S II Original Android Development] xsycox:
What is it with the Siyah kernel that it always stops the app "Perfect App Lock"? I have tried several versions of the kernel, but the app is always restarting every five seconds or so.

That does not happen on Ninphetamine, CR-Root or stock kernel. Only here on Siyah.
[Galaxy S II Original Android Development] jetpackjeff:
We need device settings for CM7 implemented for the perfect kernel!!
[Galaxy S II Original Android Development] cmd512:
No way, I came from another OC kernel that was tied to a paid app, and with the exact same settings, my phone is rock solid stable UV'd on Siyah... haven't had a single crash.
[Galaxy S II Original Android Development] shanume:
yes I still love this kernal :) and yes I have try and do every UC from +/- 25mv from stock voltage.. but no matter what settings I set it to my phone is freeze very fast and unstable. and I just wonder why is the only stock voltage work perfect in 2.1+? now I flash back to 2.0 again
[Galaxy S II Original Android Development] gokhanmoral:
I was planning to make some usb changes in beta6 but it's been released because that fixed (I hope) micro-stuttering problem while activating/deactivating second core is important. just test it please...

EDIT: even the unbearable lag with new GPU drivers in beta5 may be related with that problem. if it is fixed we may try the new drivers in the last beta. we'll have 2 or 3 more beta versions and I hope you all have enough patience before the release ;)
[Galaxy S II Original Android Development] runedrune:
Site keeps giving me a 404 error :o

Edit: Nvm. Its fine now. :)
[Galaxy S II Original Android Development] cmd512:
I don't know, your 500/200/100 mV settings are very aggressive, that's probably why you're getting crashes.
[Galaxy S II Original Android Development] ebliss:
I get SOD on beta 4 and beta 5.1, only when I set to lulz and leave the phone for along time. It's not really SOD, but when I finally managed to wake up the device, it will be in airplane mode and things will be sluggish for a while.

Will try beta 6 and see if it is the same.
[Galaxy S II Original Android Development] s2d4:
Are you still using screen off profiles on lulzactive?