yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] MistahBungle:
Wow ! What more could a tweaker possibly want ? ;) Well worth the wait & thanks for your work with this new release/the new app Gokhan. Fantastic :)
[Galaxy S II Original Android Development] gokhanmoral:
actually I was talking about opening the source and making something that other's can use.

anyway. I don't want to start any argument about this, therefore I will be very careful about what I write.

I do not think that anything closed source (about a kernel and in this context) is a contribution. that is why I do not count (EDIT: app seems to be open-source, sorry.) the recovery and those were not the differences and different approaches that I was talking about.
[Galaxy S II Original Android Development] rodries:
Hi gokhan

I've downloaded you sources but when I compiled and flash the kernel I get a hang (no bootloop) I have to reflash your original kernel using odin to fix it.

I've added a little line in build_sh

mkdir -p $INITRAMFS_TMP/lib/modules/

after

rm -rf $INITRAMFS_TMP/.hg

to get lib/modules copied

I've tested it with & without this line

Can you check it?

I mean hg clone in another directory and try to run ./build_sh from clean

I'm using international config (the default in build_sh)

Thanks for your great kernel
[Galaxy S II Original Android Development] gokhanmoral:
I tried that a few days ago and it worked.

make sure that you are using codesourcery 2009q3-68 compiler.

I had the same hanging problem with newer ones using the current compiler options.

you may need to use -mno-unaligned-access with newer ones.

but since the newer compilers won't give you better performance use the older one.
[Galaxy S II Original Android Development] :
ah my bad. and no you are not starting any arguments here GM as i am pretty sure Simone has no objections with opening the source as making something that the others can use. i am pretty sure his app will not be closed source anyway and that his configurator app would be able to work with all kernels in general and he just as you is a supporter of open source and for devs to work together and share opinions on how to make each others work better and beneficial for the user.:)

and the differences and different approaches that i was talking about was in regards the kernels itself and not the application. from my own comparison the battery life i use to get with 2.6.9 is pretty similar to what i am getting now on 1.4 NEAK and the previous version. hence why i said are pretty similar in style. the current application he is using is merely all the stuff in recovery to be able to do it while the phone is on and not having to go into all the process of going into recovery. and also if i am not mistaken he is working for all in one app something like phoenix but better and use as a cpu app ala VC...apologies if i have got it wrong just going by what i have read and what i have spoken to simone from it.:) Like i said both of you have great kernels and both of the ideas you both are working on are nothing but good for us users and you two are just great
[Galaxy S II Original Android Development] coloxim:
Wow...thanks

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
you'll get almost the same battery life with any recent kernel on the board.

maybe some tweaks can change it a little but nobody will be able to notice the 1-2% difference.

I haven't talked to him lately but if he is working on something like VC, it is good.

but I am against anything close&paid to configure some easy settings (as in phoenix app). of course anybody can do that, there is nothing to prevent it but I find it wrong to make profit from someone else's open work. if your work is only 1% of the whole, you should not be the only party to get the profit. as an example: selling an app to set some thresholds which is implemented by someone else (netarchy in our case)

I just saw that neak config app is open source and edited my post. so, forget about that part.
[Galaxy S II Original Android Development] :
no problem mate like i said you both are working on great stuff so it can only be good for us the users. thank you again GM...i can stay and talk to you for hours mate...you have alot of wisdom and have a lot of time for you.:)
[Galaxy S II Original Android Development] Entropy512:
Great news... Argh, I just remembered I STILL haven't answered your PM regarding the whole config interface stuff!

The one thing is - I hope the configurator app is separate from Voltage Control. For various reasons (screen-off profiles, and in my opinion doing a better job of identifying when the kernel interfaces change - not as much of a problem on GS2 where we all use netarchy's voltage code but on Infuse and GS1 it's a problem because some use netarchy's OC/UV code and some use existz's code - init.d scripts generated by VC for existz's code will instacrash netarchy-style kernels), I prefer SetCPU for clock/voltage control.
[Galaxy S II Original Android Development] gokhanmoral:
I didn't want to ping you for that but I am still waiting for you opinion about the BLN problem I had :) as in starwars: you are my only hope :)

xan is also thinking about making it another app, or maybe he will make two different versions. VC has now different method to set boot time parameters, just like setcpu it can set parameters without using init script.

but seperate app may be better to provide support for /system/uci.sh and /data/uci.sh interfaces and users may share their scripts. also rom developers can implement some config interfaces and maybe zipalign etc...

there is already profile support built into the uci.sh for those who need it.

you can delete, rename or select (which also creates new profiles) profiles and have different settings.

having VC app implementing profile support will be good but it is not a must.

I am still waiting for xan's decision on this.

I would prefer both if he has time.
[Galaxy S II Original Android Development] :
Gokhanmoral thanks for your hard work on this awesome kernel! Keep it up mate!
[Galaxy S II Original Android Development] sianzb0i:
Am i right to say, if i want to run in single core or full dual core mode then i can still use tergrak's app and manually override your integrate scripts? or is there another way of doing it?
[Galaxy S II Original Android Development] Entropy512:
Nice... As to BLN... That has admittedly always been low on my priorities list. I remember when a developer more competent than I am (LinuxBozo) tried to implement wakelock-less BLN on the Infuse... Let's just say it soured us on BLN for a long time.

I still keep debating ripping out BLN altogether but too many people would whine. (It causes wacky touchkey backlight behavior sometimes on firmwares that have liblights but don't use the BLN control app - multiple people have given me dmesgs indicating that liblights killed the backlights.)
[Galaxy S II Original Android Development] dark4light:
what you think the best version for battery of siyah
[Galaxy S II Original Android Development] kwerdenker:
I looked through it and quite honestly, from my end of things everything looks a-ok. The only thing I noticed is that your script is owned by system and group sdcard_r. I don't know if this is a problem but you could try a

chown root:root 96undervolt

and see if this changes anything.
[Galaxy S II Original Android Development] gokhanmoral:
v1.6reTOUCHed and v1.7.8rc2 is up.
[Galaxy S II Original Android Development] diddsen:
why v1.6 now too??

iam confused now
[Galaxy S II Original Android Development] gokhanmoral:
also, please do not report any instabilities if you are using undervolting.

I have changed some UV logic and I think it is more appropriate to have those changes. They will make your device either more stable or unstable, I don't know...

if you are unstable with your current UV values, just increase them.
[Galaxy S II Original Android Development] bgx:
Little bit late, but with tapatalk upload to XDA now works. Here result of 1.7.8 beta0

Yes and android os bug has gone for me... ;-)
[Galaxy S II Original Android Development] gokhanmoral:
I know this is unusual :)

but some people asked me to get speedmod v27 sources, add the current modifications and release.

and since it is based on i9100-update2 sources I did not give it a new version number but instead I named it v1.6..

try it, maybe it will work better...

some people believe speedmod-v27 is the best. so, this is the modified version of the best.

lets see if it is a placebo effect or not...
[Galaxy S II Original Android Development] ngoonee:
Is logcat disabled for this kernel?
[Galaxy S II Original Android Development] gokhanmoral:
yes, it is

just as speedmod v27
[Galaxy S II Original Android Development] ngoonee:
Thank you, I was wondering why my logcat was empty.
[Galaxy S II Original Android Development] syahrulzaman:
gokhan,

is 1.6 compatible with Touch X-POWER+ 2.0 SP1 ?
[Galaxy S II Original Android Development] syahrulzaman:
thanks....
[Galaxy S II Original Android Development] ebliss:
Hi,

is smartassv2 supposed to behave this way?
[Galaxy S II Original Android Development] cbeckstein:
hmmm... still do not understand:

you write:

SiyahKernel v1.6reTOUCHed

all the features of v1.7 series but based on update2 sources

some stability patches

BUT

speedmod up to version T27 was not based on update2 sources and although hardcore in version T28 switched to update2 he reverted to update1 in T32 (probably still T40 is update1 based)

I therefore wonder which speedmod version 1.6reTOUCHed is based on: T27 (but this is update1 and you write your 1.6 is based on update2), T32 (update2) or T40 (the latest speedmod)
[Galaxy S II Original Android Development] gokhanmoral:
actually no. I am currently testing it. I think I will make it scale slower in rc3
[Galaxy S II Original Android Development] bgx:
+1 for that! ;)
[Galaxy S II Original Android Development] gokhanmoral:
as I said before it is based on speedmod T27 patches.

I got T27 patches and applied it to update2 source.

speedmod was using update1 sources until v40 because it was believed that update2 was preventing deep sleep.

in v40 some drivers are merged back to update1 sources from update2.

I don't think we have any deep sleep issue in update2 sources.

you will never know if you don't try.

I do not say that this is the same as speedmod nor I do not say that it is as stable.

I just say that I did not make any radical changes in the source code.

so... this is not speedmod kernel. and v1.6 is based on update2 sources.
[Galaxy S II Original Android Development] vandanh15:
send gokhanmoral

SiyahKernel v1.6reTOUCHed and SiyahKernel v1.7.8rc2

Which to choose?
[Galaxy S II Original Android Development] inferno17x:
Hi Gokhan,

I am on version1.7.8rc1. I observed that the Suspend and Events/0 under the BetterBatteryStats are always running red under the Process list.

Is that suppose to be this way or can it be deactivated?
[Galaxy S II Original Android Development] gtizon:
Hi Gokhan, what is better for Leomar Rev 2.7.1? I know youve been doin some tests using that rom earlier. Thanks!
[Galaxy S II Original Android Development] Vaedryn:
2.6.7 / 2.6.9
[Galaxy S II Original Android Development] nitronos:
hello

can u tell me wtf is happening with my phone? i use Checkrevo hd v6 with syiah 2.6.9 and after a few days my phone is heating and battery drain very very fast. I used my phone like every other day. I uploaded some screens to see anything that might be a problem.

Thanks
[Galaxy S II Original Android Development] MistahBungle:
2.6.9 *very* closely followed by 2.6.7
[Galaxy S II Original Android Development] veyka:
Use OS monitor to see what is running your CPU, I had the same issue, but it was the DRM service keeping pegging the CPU at 100%.
[Galaxy S II Original Android Development] s2dh:
Will you post your voltage control settings when you post this new version, or pm me screenshots.

Would be good to see how your config compares to magicConfig v0.31's

(unless you use the same settings...)

Yours looks super fast...
[Galaxy S II Original Android Development] ernest101:
sry for the late reply mate, I used to have Kies and the correct USB drivers (as they did work months back) all the sudden my computer can't detect my phone (I still have Kies and the same driver then, uninstalled it to reinstall them), I reinstalled the driver, and tried to reinstal Kies (it gave me the blue screen of death, hence unable to install it anymore). I wiped my phone and the problem persists. Please do advice

p.s. should i be posting in another sub forum? i no longer think this has to do with Siyah kernel anymore as i tested with CW7 116 nightly stock kernel it still didn't work
[Galaxy S II Original Android Development] simone201:
Hey gokhan! :D:D

Good to see the new configurator working fine, seems really good and ultra customizable, i hope i can include it also in my app :) :)

Great work as always, both you and xan!
[Galaxy S II Original Android Development] don1bong:
Have you changed the port where you plug your phone in? Plug it in main USB port at the back of your PC

Swyped from white Siberiantiger coated checkROM enabled brick
[Galaxy S II Original Android Development] ernest101:
yep I have tried all the ports, I use a laptop if that's relevant
[Galaxy S II Original Android Development] geomax45:
If you are having problems with the driver in Kies, try loading the specific phone driver from the Samsung website. I had problems with Kies at one point and got the driver from Samsung.
[Galaxy S II Original Android Development] gokhanmoral:
your app? ;)

thanks. I hope you can :)
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
It's not just my router though. I see it sometimes at school where I drop Wifi. I'm not sure what industrial grade routers they use, but obviously I feel like my SGS2 is just bad with wifi overall. I say this because my Nexus S and iPod Touch have no problem maintaining a wifi connection as I walk around my building at school.

I'm not usually one to ***** about wifi because I feel like 90% of the time its the user, but with my device only having remembered 3 wifi hotspots (work, school, home), I feel its weird that it struggles sometimes to connect.

And yes my wifi sleep policy is never.
[Galaxy S II Original Android Development] rodries:
Thks, I've tested it with 2009q3-68 compiler and works like a charm
[Galaxy S II Original Android Development] ny-hardcore:
I compiled from latest source too but could not get it to boot on miui.

Could start adb and get a shell but no GUI on phone. using the iniramfs from .12 I got it to boot.

adjusted the build.sh because of missing /lib/modules in /tmp/initramfs/

Still testing but seems to run well. nothing to say about battery time.

Must add that i changed the keyboard driver so that touch key back light times out after three seconds.

I guess there is no risk in running latest sources (1 march)?

Used 2009q3-68 compiler.
[Galaxy S II Original Android Development] Vaedryn:
last GB version, a area will be end, nice time from version 1 to version 2.6.13 . Hope the ICS time would be so nice too:) Thank you for all GM.

SGS II Cyanogen Mod
[Galaxy S II Original Android Development] sachs:
2.6.9 was the best....agree 100%.
[Galaxy S II Original Android Development] xuxuzao:
gokhan, why deadline?

is this your new favorite?
[Galaxy S II Original Android Development] mundixx:
Hey, can you share how you did this? Would you be able to share your keyboard driver as well? I am using MIUI 2.2.24 and I miss the option to have the backlights automatically turn off.
[Galaxy S II Original Android Development] stevehkim:
2.6.7 FTMW!

MIUI/SIYAH Pimp Juice

Fast and Furious @ 1.5ghz
[Galaxy S II Original Android Development] geomax45:
+ 1:

2. 6.7!
[Galaxy S II Original Android Development] ny-hardcore:
I used this file for reference

https://raw.github.com/myfluxi/xxKe...ers/input/keyboard/cypress/cypress-touchkey.c

All credits go to fluxi

Binary here: http://db.tt/Tf2QRBsi
[Galaxy S II Original Android Development] zikarus:
Changelog (updated):

fixed decoding issues because of the new cpuidle driver (thanks to Entropy512)

set default I/O scheduler to BFQ-v3r2 (you will be able to change the default I/O scheduler using the config app)

conservative governor is tweaked to have better performance (you will be able to set the default cpu governor using the config app)

reverted lots of code back to v2.6.9 (based on the user experience, it is the best version until now)

completed universal config interface implementation (the app will be posted when it is finished. the implementation at the kernel side is ready)

you may need to flash this in CWM recovery if you mess with the default config (especially when trying too much undervolting. although most of the settings are safe, changing gpu voltage and freq settings may cause lockups or bootloops): siyah-resetdefaultprofile.zip. this script will reset default profile and your device will boot with default settings.

this will be the last GB kernel release of SiyahKernel. If there is a bug in config interface I may update it (even without changing the version) but the kernel files will no longer be updated.

And released....
[Galaxy S II Original Android Development] gokhanmoral:
I have released v2.6.13.

xan is still working on the app. he decided to make an open-source lib for the parsing part and a closed-source implementation.

I hope he will complete it soon.

I tested almost everything in the config interface but if there are still bugs I may update the latest version.

but I won't add anything new to this branch.

I will work on ICS kernels and since there is no source available for now I will try to modify the stock kernel and add a config interface (only for the available options)
[Galaxy S II Original Android Development] gokhanmoral:
and for those who wants to modify some boot-time defaults using a text editor, you may mess with /data/.siyah/default.profile :)

that file has all the configurable options and the changes will be applied after the next reboot.

now.. I am waiting for the bug reports :)
[Galaxy S II Original Android Development] :
Thanks for the latest release mate.:) Downloaded and testing now.:) Many thanks again
[Galaxy S II Original Android Development] gokhanmoral:
about the default i/o scheduler: it is bfq but that doesn't mean it is my favorite or best.

once the config app is ready (it is almost, but needs some tiny fixes) you will be able to change it.

you will also be able to change the default governor which will let you use lulzactive app and apply your favorite lulzactive settings using that app on boot.

and the last last-minute change is that you will be able to disable android logger. although I do believe that it is useful and not a battery hog you will have an option to disable it to feel better maybe :)
[Galaxy S II Original Android Development] :
Nice one mate i am looking forward to testing this with lulz app but seems i hit a wall here now when trying to install the kernel through recovery. First time it gave me random reboot as soon as i installed it. When ahead again and tried through recovery and this time wiped everything. what i mean wiped voltage settings, cache and dalvik and now i just get a black screen and notification lights at the bottom are lit up..Going to try the Tar version now to see if that works..

EDIT1:Flashed through Odin and everything works fine now..Nice one mate will report back with results...

EDIT2: Same problems persists. I can not use the lulzactive app as it reverts everything back to stock after i put my settings in it..Works fine on NEAK.:(
[Galaxy S II Original Android Development] antt00:
Flash 2.6.13 through CWM without problem.

There is no /data/.siyah/default.profile. Do we need Xan's app for this?

Currently using scripts to echo my settings.
[Galaxy S II Original Android Development] gokhanmoral:
hmm, I just checked and you are right.

you need to reboot twice to get that file because I missed the case when there is no /data/.siyah directory and it is created in efsbackup script which is executed far later than default.profile creation.

I will not fix that little mistake for now. just reboot again and you will have the file.
[Galaxy S II Original Android Development] gokhanmoral:
edit /data/.siyah/default.profile and change ondemand to lulzactive.

then you will have lulzactive as default after you reboot your device.
[Galaxy S II Original Android Development] ole12:
Why not use voltage control to change governor?
[Galaxy S II Original Android Development] gokhanmoral:
lulzactive app needs the lulzactive governor to be selected before it is run and it runs before voltage control app applies and sets the governor to lulzactive.

therefore, he has to apply it either by using scripts or change that value to have lulzactive governor as default on boot.

voltage control app's settings are applied after a delay.
[Galaxy S II Original Android Development] antt00:
Yup fix with a reboot. So far everything is working, wifi, bluetooth, deepsleep... so no bug apart from that tiny one. Great job. :D
[Galaxy S II Original Android Development] :
works. Many thanks mate. I did had on Voltage control Lulzactive to run on boot. Not sure why it never worked with the app. But anyway all is good now and i will report with my findings
[Galaxy S II Original Android Development] gokhanmoral:
you can execute "/res/uci.sh generic /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor lulzactive" instead of editing that file.

I know.. it is hard. that is why we will have an app to do it for you :)

the command above will both set the governor to lulzactive and make it persistent after a reboot.

changing /data/.siyah/default.profile will need a reboot to apply the settings

and the available settings can be seen in /res/customconfig/customconfig.xml (for developers only)
[Galaxy S II Original Android Development] Dennys_Santos:
gokhanmoral.

Is there any chance you leave the boot this kernel as fast as in version 2.6.7 +?

Thanks Dude.
[Galaxy S II Original Android Development] antt00:
In default.profile, there are no settings for governor specific settings (eg. up_threshhold etc.). Will it be available in xan's app or are scripts still needed?
[Galaxy S II Original Android Development] :
Thanks GM...You are right. App works alot better for me. Less scripts on my phone the better as i would not know what each ones does and which one i need to get rid off. Hence why i love apps to do the work for me. Anyway thank you for your time..Flashed it through odin and worked like a charm..Last question why do you think it is best to flash through odin instead through recovery?
[Galaxy S II Original Android Development] gokhanmoral:
does it boot noticeably slower?

I didn't notice a big change. it may be caused by newly added parse-xml-and-apply-settings part.

I may try to optimize that a little but it will be in the next kernel which will be for ICS.
[Galaxy S II Original Android Development] gokhanmoral:
the governor and i/o scheduler options are there to change the defaults selected at the very early stage of boot.

you will still need another app (setcpu, or lulzactive app) to change the thresholds.

I didn't add them to UI because the interface is not that complex. I would have to add all governor settings and that will make the interface very crowded and complex.

the interface will support mostly kernel specific options.

and some very advanced options will not be available for now (such as modifying frequency table)
[Galaxy S II Original Android Development] Shamms:
Hi Gokhan

Very sad to hear that this is the last release by you. If so is the case then pls let us know which other kernel matches close to Siyah? I like using your kernel and have been doing so since I have started rooting.

Rgds,

Shammi