yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] shr33kant:
Well fellow siyah users, I guess it's an end of an era. Good luck on all your endeavors Gokhanmoral. You made an awesome kernel for us all. I am truly grateful for all your hard work.

We should name the final sgs2 version of this kernel after his wife as it was made for her :-D.

Sent from my GT-I9100 using Xparent ICS Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Maybe it's because everyone is freeking out because gokhan is leaving!!!! :eek:

I hope so much that gokhan stabilize everything.

Thanks gokhan, excelent kernel, huge difference u have made in S2!
[Galaxy S II Q&A, Help & Troubleshooting] PedroMRP:
This is indeed a sad day. We knew it inevitably would come but never thought it was so soon...
[Galaxy S II Q&A, Help & Troubleshooting] drahad110:
Friends I am new to this forum, I have a question. I m using RR v2.1, today I updatedmy Siyah kernel to 3.2.8 and got bootloop... any idea????
[Galaxy S II Q&A, Help & Troubleshooting] PedroMRP:
Flash 3.3.
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Its a known issue, you will most likely have to restore from backup. Then flash v3.3.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] Akhara:
glad he give his i9100 to his wife, always wish to see a stable kernel made by him, and we all know that his 3.3 is not stable.

He will be back at the minute when his wife complain about it ;)
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
v3.3 not stable? Can I ask, by what measure do you arrive at that conclusion?

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] beastobadness:
GOK!! What do I do now for my kernel testing insanity fix!?

I mean don't get me wrong, this kernel has reached a point where it is stable and working perfectly but I am an android user, it is not the same unless we can get a fresh change every now and again, that's what CWM was created for!

My s2 weeps and spits in the eye of your s3 ;)

Gok, enjoy your i9300 and keep up the good work! (Just remember, your wife still has an i9100)

From PALM PRE to GALAXY S2... From HOPE to RELIEF!
[Galaxy S II Q&A, Help & Troubleshooting] Akhara:
because it's 3.3 and he must have his own reason to titled it 3.3 and not a Final version or even mentioning that it's his last Kernel on GS2 ;)
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Its not his last kernel, its just designed to be as stable and as close to stock as possible. Simply because he isn't going to be back for a while.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] PedroMRP:
Maybe it's not the final version but the development of this kernel will stop for a while...
[Galaxy S II Q&A, Help & Troubleshooting] Zikor:
Off Topic:

If you don't have anything nice to say then dont say it at all.

but this doesn't give you the right to insult people.

you just broke one of xda's rules... good on you mate! Cheers!
[Galaxy S II Q&A, Help & Troubleshooting] vertrag:
Can someone summarize git diff between 3.2.8.2 and 3.3 >__< maybe to make everything clear.. i saw previous posts are horrible of concluding, regarding gokhan's experimental patch removal... LOL
[Galaxy S II Q&A, Help & Troubleshooting] duykhang524:
Hey guys I'm having a problem with the camera app, when I open it I just freezes my phone when it tries to focus... I can see the image but when I touch the screen the touch just doesn't respond anymore... I've tried reflashing the rom. Full wipe + reflash still can't help it. I tried clearing the camera app data as well + restore the camera app from titanium backup

Just happened very recently the camera was working fine the day before...

Running Siyah 3.3 on Neat rom LPF

3rd party camera apps are working fine only the stock camera is bugged
[Galaxy S II Q&A, Help & Troubleshooting] kalpik:
What happened to the Siyah Dev thread? :s
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
The difference between 3.3 and 3.2.7.2:

799780c2	gokhanmoral	Revert "fs: merges with n7000 update3 sources"	19 hours ago
52dcefad	gokhanmoral	Revert "scsi: merges with n7000 update3 sources"	19 hours ago
21f14d1b	gokhanmoral	Revert "mm: merges with n7000 update3 sources"	6 hours ago
df5217e5	gokhanmoral	Revert "net: merges with n7000 update3 sources"	6 hours ago
dcd73863	gokhanmoral	Revert "usb: merges with i9300 sources"	6 hours ago
9e699132	gokhanmoral	Revert "kernel: merges with n7000 update3 sources"	6 hours ago
6813788 v3.3 config
7c1ef10 Revert "do not remove extweaks profiles when a new version is install…
a839811 net: wireless: bcmdhd: use country code mapping in mach-exynos and fa…

Hence, the changes included all of 3.2.7.2 except the N7000 fs,scsi, mm, net, usb and kernel (if compared to 3.2.7.1, then the modem was also reverted). Also extweaks profiles are removed when installing a newer version. Also the country mapping is defaulted to JP if country code is not found.

It's not "as close to stock as possible". It's "not including N7000 source updates". Please check the facts before you post. Misleading users (and insulting them about it) is really bad.

See above.
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
It's fine here. It's a ROM problem (NEAT ROM?).
[Galaxy S II Q&A, Help & Troubleshooting] duykhang524:
I just tried to roll back to gb and the problem's not there. Let me try another samsung rom to see if its Neat rom. Never had that issue before though

Edit: I fixed the problem by using the system panel app and closing all apps now runs fine :D soooo happy
[Galaxy S II Q&A, Help & Troubleshooting] willybarca:
in 3.2.8.2 i got the best wifi range, it connects very fast too, does 3.3 have different driver? what ever driver there is in 3.2.8.2 is really doing good
[Galaxy S II Q&A, Help & Troubleshooting] bundi22:
anyone know how to get superuser permissions to work on secondary rom: NEAT LPG. works fine on primary. i have tried resetting extweaks and also removing and auto installing root?
[Galaxy S II Q&A, Help & Troubleshooting] TheRplima:
What happened with the DEV thread?
[Galaxy S II Q&A, Help & Troubleshooting] vertrag:
Thanks pikachu now is very clear.. Hehe... *cheers
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
I did link it to github. And then you went and say something misleading. It's not confusing at all. The post below just confirmed it. :/

If you have to say something at all, please confirm your facts. It's not the first time I've caught this.
[Galaxy S II Q&A, Help & Troubleshooting] vuvuxela:
after 3.2.8.2, facing FC and bootloop, follow your way and problem solved!

now i have up to 3.3, no problem so far :)

Thank you Kalpik

Thank you gokhan for your great work!
[Galaxy S II Q&A, Help & Troubleshooting] bala_gamer:
what happened to the original development thread?:eek:
[Galaxy S II Q&A, Help & Troubleshooting] drahad110:
I tried to install from zip and then installation got hang at middle. I restarted it and then it stuck on samsung logo. Not going in recovery mood. :confused:
[Galaxy S II Q&A, Help & Troubleshooting] Crescendo Xenomorph:
Apparently closed by GM... Since he's no longer developing this kernel in favor of S3. He WILL make this kernel more stable but no longer new feature/experimental feature.

The God of S2 left us already, but the miracle he bought to us will remain and make our S2 stay perfect.

Thanks Gokhan for your great awesome work. You're the best.
[Galaxy S II Q&A, Help & Troubleshooting] bala_gamer:
but why delete the thread instead of locking it?
[Galaxy S II Q&A, Help & Troubleshooting] LNJ:
So people can't complain if the kernel is buggy!
[Galaxy S II Q&A, Help & Troubleshooting] Ankit Tulsian:
That could be even done by locking the thread.
[Galaxy S II Q&A, Help & Troubleshooting] LNJ:
Then the evidence still remains!
[Galaxy S II Q&A, Help & Troubleshooting] droidphile:
GM did not delete the thread, neither did he ask any mod to do so.
[Galaxy S II Q&A, Help & Troubleshooting] bala_gamer:
hope it comes back in a locked state atleast :( it has hell loads of data and can be mined whenever we need.
[Galaxy S II Q&A, Help & Troubleshooting] kalpik:
Hope we can get some explanation soon!
[Galaxy S II Q&A, Help & Troubleshooting] willyrabindra:
Thanks GM..you're the best...
[Galaxy S II Q&A, Help & Troubleshooting] gokhanmoral:
hmm.. the thread is gone.. ?

I am sure there is a good reason for that.

possible reasons:

- mods/admins got tired because of the recent reports on irrelevant posts.

- any of them has bricked his device and got angry

- someone has accidentally deleted it.

- one of them was away from the keyboard and the cat deleted it.

the reason is not important.

v3.3.1 will be up in half an hour. only difference will be to merge with linux-3.0.y to update it to 3.0.33
[Galaxy S II Q&A, Help & Troubleshooting] rlorange:
Ooops!
[Galaxy S II Q&A, Help & Troubleshooting] rlorange:
OK just updated the OP a bit to reflect the recent changes in direction.

Will get my Galaxy s3 in August hopefully! :)
[Galaxy S II Q&A, Help & Troubleshooting] Crescendo Xenomorph:
This is the craziest reason... HAHAHAHA.... :D

I love it!

"One of them was away from the keyboard and the cat deleted it."
[Galaxy S II Q&A, Help & Troubleshooting] Tye:P:
v3.3.1 is available for anyone interested

As it seems that the update to the 3.0.33 Linux kernel is the only difference I thought I would provide the kernel changelog as well:

http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.33

There's a slightly easier to read version here:

https://lwn.net/Articles/500221/

Good luck decoding all of that, just thought someone might be interested.

Not all these are applicable to android I guess it's safe to assume.

Is there an android specific changelog?

If anyone knows would they be able to post a link?
[Galaxy S II Q&A, Help & Troubleshooting] jbarol:
Thank you, but I do not use them. Is there anything else that might cause it?
[Galaxy S II Q&A, Help & Troubleshooting] leongwenjun:
is it stop development ?
[Galaxy S II Q&A, Help & Troubleshooting] Crescendo Xenomorph:
Below is the answer from GM... :D :D :D :D
[Galaxy S II Q&A, Help & Troubleshooting] Mimov:
I've just tried it and while flashing it via CWM my screen froze and in a while looked like a TV without a signal :eek: After that i removed the battery and put it again and it started normally. Everything seems ok now but did someone else got this problem also?
[Galaxy S II Q&A, Help & Troubleshooting] pulser_g2:
Lol :)

I spotted it was deleted this morning and restored it. In the middle of a crap clearout, it appears one of the mods deleted posts as well as thread. It's all back now though :)

But... I've not spoken to him, it COULD be his cat that did it... So we will never know :p It's back anyhow.
[Galaxy S II Q&A, Help & Troubleshooting] Bonestack:
I got it once too, nothing to worry about, there has been discussion about it earlier here. It's a software bug as far as I know.
[Galaxy S II Q&A, Help & Troubleshooting] danielsf:
gokhanmoral the gpu in the s3 is very similar to ours but they have these gpu frequencies: 160 266 350 440 (I thought our gpu could only follow that formula that meant it could only go some lower ones and 160, 200, 267,400mhz). Is their anyway to these to get these frequencies to work with our device, as 400mhz is like a tease, it is too high of an overclock (heat gets marginal too high)to be useful, but 350mhz sounds nice :)
[Galaxy S II Q&A, Help & Troubleshooting] Don MC:
Slightly OT (but not by much):

Noticed that on Siyah 3.2.8.x (with stuff taken from n7000), Android OS battery usage was down, while WiFi usage went up. This is how it should be. The thing people refer to as the "Android OS bug" is, as most of us know, in fact an error in reporting battery usage under different categories. Some WiFi functions are put under "Android OS" instead of under "WiFi".

The same applies to Mobile data and other GSM/3G functions.

On my old SGS1, WiFi was always on the top of the list, because I always have my WiFi switched on. Now, I can only assume the n7000 also reports battery usage this (correct) way and thus we can deduce that the "rules" for what functions are included in which category lies within the kernel package.

If people can confirm that Siyah 3.2.8.x (with parts taken from n7000) indeed displays battery usage in this (correct) way, then the case is clear. If not, well, then my investigation resumes...

EDIT: I've now tested 3.2.8.2 and 3.3.1. On 3.2.8.2 Android OS battery consumption percentage is low (and WiFi is high). On 3.3.1 it tops the list (and WiFi is low). There is something in the n7000 kernel parts that's doing something right. It won't increase your battery life, but it will display the different battery consumers correctly.
[Galaxy S II Q&A, Help & Troubleshooting] KennyLegend:
The thread was most likely deleted to hide it for a while as there was a flood of useless and senseless posts one after the other despite being told by crachel not to post non-dev stuff there.

Anyway, back to what matters....

V3.3 is possibly the best release for me since the infamous 3.1 rc6 (the pre-bricking bug issue).

Thanks Gokhan for ur hard work on this. You've made a lot of guys happy on here. The S3 development is gonna be very interesting over the next few weeks with work from some of the best devs on XDA....you, AndreiLux, Chainfire, Supercurio...

I'm excited much.....
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Yes, yes you like to watch and correct everyone here..... I really couldn't care less to be honest. I bet your brain melts if I give an incorrect answer to a technical question. :p

I was right anyways, next time mate... at least try to accept, and understand that others are right... it can't be you all the time.

http://xdaforums.com/showpost.php?p=26980478&postcount=9821

---

Gokhan is back already, haha there is no way he can stay away from s2 kernel compiling. :D

I'm happy with 3.2.8.2 though.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Q&A, Help & Troubleshooting] chris2busy:
trollin? :D
[Galaxy S II Q&A, Help & Troubleshooting] leongwenjun:
:DI think so, 350much more better
[Galaxy S II Q&A, Help & Troubleshooting] gokhanmoral:
if you can use a benchmark tool (such as nenamark) and test 266 350 400 and see a difference, I will add that level to extweaks.

you can use a shell script to set that frequency or maybe adb is easier:

echo 160 266 266 > /sys/class/misc/gpu_clock_control/gpu_control

echo 160 266 350 > /sys/class/misc/gpu_clock_control/gpu_control

echo 160 266 400 > /sys/class/misc/gpu_clock_control/gpu_control

make sure that you increase the voltage of the third step to a level which can handle 400MHz.

I suspect that 350 will give you the same results with 400, but maybe I am wrong.
[Galaxy S II Q&A, Help & Troubleshooting] tolis626:
Unless something in your kernel has changed,you are.350MHz(And everything between 267Mhz and 399MHz) will give you the same performance as 267MHz.Hell,it doesn't even clock to something other than 267MHz.You can check by leaving the 267MHz voltage intact and changing the clock to 350MHz.Sadly,that's the case.Maybe you could port the GPU driver from the S3 and see if it makes a difference? :)
[Galaxy S II Q&A, Help & Troubleshooting] toxicbubbles:
Having issues connecting to leap secure network on the new kernel 3.3.1, anybody else have issues with this? It sees the network but won't connect to it, tried recreating connection settings and still same issue so back on 3.2.6.4 and working fine. Haven't tried on WPA as still in work.
[Galaxy S II Q&A, Help & Troubleshooting] overtime!:
I'm having a 1 sec lockscreen lag again with 3.3.1, 3.2.8.2 works fine for me so i'm gonna keep that one for now.
[Galaxy S II Q&A, Help & Troubleshooting] vastac13:
Gokhan can you look into S3's usb drivers? Out of the box, S3 supports usb-dac. It may be good if you can add that missing driver to I9100 kernel if it's possible. I/We can give you logs etc. If necessary. You can pm/msg me further if you're interested et al
[Galaxy S II Q&A, Help & Troubleshooting] theman22:
I loaded 3.2.8.2 yesterday and ended up having FC in basically all apps. I flashed 3.3 and ended up in a boot loop. I've tried everything I can think of and I can't get Siyah working again.

I've formatted/wiped everything and installed a 4.0.3 rom, a 4.0.4 rom, and various kernels. For some reason I get either boot loops with Siyah, it will reboot into recovery, or the screen goes blank after the Siyah logo comes on. I've even tried Siyah 3.5.2 which some people on the dev thread indicate works for them. That gives me the black screen.

Anyhow, the confusing thing is that my phone will work fine if I load a standard kernel (Kernel I9100XXLPH).

Does anyone have a suggestion of what may be affecting Siyah but not other kernels? I'd like to get back on it if possible. thanks
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Try 3.3. Your usage of 3.2.8.* caused corruption of /data. Only way out of it is to wipe your data or restore a previously backed up nandroid into /data. Hence, wipe data, flash 3.3 and you're good to go.
[Galaxy S II Q&A, Help & Troubleshooting] poczesaniec1:
Gohkanmoral want to leave sgs2 to his wife, this means that his support for as is over? Like exfat and more?

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Q&A, Help & Troubleshooting] LegendZenify:
I think he will still support sgs2, just that updates will be less frequent and there will be no experimental changes.

Which means no beta or rc versions. :(
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
@pikachu01:

do you perhaps have any insight as to what extent the incompatability in 3.2.8.2 is concerning the data partition? (probably due to the n7000 fs merges...)

the only thing I really need to know is : will it be a problem to stay on 3.2.8.2 in the long run?

I did had the problem going back and forth from 3.3 to 3.2.6.4 and back to 3.2.8.2, but I did the 'nandroid-format data-restore data' thingy, and no problem after that...
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
From the changes that were reverted, I can see that encryptfs had some changes that could potentially cause problems.

In N7000's source, the encryptfs filter was removed (I am speculating that this is due to some changes in N7000 ROM that supported the encryption filter, thus the kernel support for it was removed).

The i9100's encryption system in the ROM probably didn't have the said feature and i'm not sure what triggers it, a counted reboot? Like after how a number of boots, the kernel checks for encryptfs, if it doesn't detect it, it locks the /data partition?
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
200mhz gpu treates as 160?

Hi everyone 3.3.1 is working perfectly for me but some discussion about gpu frequencies has led me to do some testing on the GPU with Siyah.

I have been testing the effect of gpu voltage on mean NenaMark2 scores to see if UV reduces performance (-50,-100 etc). However what I found was that both 160 mhz and 200 mhz gets the same score on the benchmark when a 25% improvement could be algebraically expected!

Could someone please do a quick benchmark at 160 and 200 mhz on the gpu to see if this is true?

If anyone wants the test results I will upload them :)

Edit: It appears that this issue was due to me using step1 in extweaks then setting upthreshold to 100%. Apparently this does not work and I get normal results (+25%) by using three identical steps in extweaks. I don't know what causes this strange behaviour!
[Galaxy S II Q&A, Help & Troubleshooting] OGroteKoning:
Don't be silly! We will still have support ... only it will be from his wife now :D

Sent from my Galaxy S2
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Not getting this.
[Galaxy S II Q&A, Help & Troubleshooting] willyrabindra:
Don't be silly! We will still have support ... only it will be from his wife now ￼

Sent from my Galaxy S2

LoL...
[Galaxy S II Q&A, Help & Troubleshooting] xavihernandez:
I know GM already said that he does not know why DSPManager is not working with Siyah ICS kernel, but does anyone else have any clue?? It would be good to get it working.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Give me your detailed gpu settings you tested (FRQs/Voltages/Tresholds) then will check them for you. Have you set 160MHz and 200MHz as Max FRQ for testing?

Edit: Forget it, you already answered yourself.
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
People,

Terribly sorry for putting this question here, because I don't know of it's kernel related.

How can monitor gpu frequencies? It's some information that must be passed by kernel, or it's already possible to get? If it's, someone knows how can I get it?

Thanks very much.
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
Thanks for your offer anyway. In short I found out that if the voltage is high enough to avoid freezing then the benchmark scores will be the same +/- 1 or 2.

Hi right now we can't monitor gpu frequencies but I think I saw some talk about a possible implementation in the future but not for now at least. The only way to know for sure what the gpu frequency is (eg for testing) is to set it manually in extweaks or with scripts. I hope someone does develop a method though!

Hope that helps answer your question :)
[Galaxy S II Q&A, Help & Troubleshooting] quircky:
What is the best Siyah kernel could you suggest for me? I am using the resurrection remix rom (latest). I wanted to do the dual boot however it is giving me an error 2nd rom not found.
[Galaxy S II Q&A, Help & Troubleshooting] carlos67:
Advice anyone, please - lockscreen lag.

Guys, any advice greatfully received.

I am running wanamlite v11.9 with Siyah 3.2.7.2. Only changes I made in extweaks was -50mV CPU undervolt and changing governor to Smartass V2 and scheduler to deadline. Also raised min GPU to 200 mHz from 167 (hopefully to improve scrolling smoothness and reduce lockscreen lag on wake up).

Here is my problem, phone running silky smooth

after

unlocking into homescreen (much smoother than GB was). However, on waking up there is a lag on the lockscreen when swiping to unlock the phone. It lasts about 2 seconds before showing my homescreen. It's annoying because every other aspect of my setup is superb including battery life.

Is the anything I can do/try to get rid of this lockscreen lag? I use Widgetlocker lockscreen by the way and this lag wasn't there on GB Rom with Widgetlocker.

Maybe I need to use a different governor/scheduler or try latest Siyah version 3.3.1? What do you guys recommend to reduce or eliminate the lag. By the way my wifi is working fine. Just this damm lag!!
[Galaxy S II Q&A, Help & Troubleshooting] egps2:
It may be your lock screen and not necessarily any settings you are using. What may help is to try increasing your minimum cpu freq to 200 (from 100 if you had that). Also, just for the sake of testing try cfq scheduler.

You might also want to uninstall your lock screen and reinstall it from scratch to make sure there are no conflicts as this sounds like an application issue and not a performance issue :)

Edit: You may also benefit from installing the latest 3.3 Siyah (is very stable for me) and wiping cache and dalvik just to ensure there isn't some random bug causing this issue. Obviously these are just general suggestions trying to help as it's hard to pin point the issue without more information. Have other users of widgetlocker reported this issue? I don't know if they have a discussion board.

I hope you sort it out!
[Galaxy S II Q&A, Help & Troubleshooting] carlos67:
Some good suggestions there - thanks. Already CPU is 200Mhz minimum as I believe 100 mHz creates as many problems as it solves. Will try what you suggested.
[Galaxy S II Q&A, Help & Troubleshooting] Holgott:
Is it healthy for the phone to set 18 CPU steps? Can it damage anything? Are u using this Feature?