yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Entropy512:
Yeah, I was very disappointed to find the MAX8922 in control.

I had a customized "step charging" algorithm in my Infuse kernels that worked very well - It would keep the battery at around 90% when the screen was on max brightness during Navigation. (I set it to automatically reduce charge current as battery voltage increased - the idea was to have high charge current when battery was low, but not to wear the battery too much by reducing charge current before the battery itself did as the voltage rose above 4.0 volts.)
[Galaxy S II Original Android Development] veeruchinnu143:
I don't know anything abt volatge & other stuff. Installing every new kernel release & I'm satisfied. But this time they released 3(defaults,performance,battery) more zip files along with this v2.6. What to do guys..? Shud I flash those zip files also...? Help me...? I'm on MIUI 1.12.16...
[Galaxy S II Original Android Development] PedroMRP:
Only flash one file according to what do you want... if you want battery to last longer flash siyah-battery.zip, if you want performance flash siyah-performance.zip, the default one is for returning to the default values.
[Galaxy S II Original Android Development] extract1:
I concur 2.5.2b gives much better battery life. It would be great if Gokhan would release a version that is based on 2.5.2b with the new 2.6 configurable tweaks and faster boot times added to it. Then we will truly have the "One Kernel to rule them all".
[Galaxy S II Original Android Development] Ogy77:
Hey guys I have few question,I used this kernel version 2.6 and rom is CM7 nigthly,everything its ok,but I must ask,does overclock risk and can damaged phone,I never use and changed voltage its thst need or not,can anybody answer me on my questions?Cheers and I press button THANKS:p:p:p
[Galaxy S II Original Android Development] stevehkim:
you either didn't clear something out in vc or got a bad flash. the other files in init.d that don't say siyah01 leave them alone. even though you use the cleaning script i suggest to clear dalvik and cache in cwm manually + cleaning script before and after the flash. I know it's overkill but I always do it. Try re-flashing.

---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
[Galaxy S II Original Android Development] droidphile:
Added all Siyah user configurable parameters with examples into 3rd post. When i started the thread, i didn't realize there's a sea of information to cover :)
[Galaxy S II Original Android Development] mathsmart:
is it just me or when somebody call me its take 1 sec to get out of deep sleep and let me push the respond button ? i have siyah 2.6 with battery mod

I just flashed the default script to see if something is wrong cause since this morning I don't really use the phone and my battery seem to drain very fast ! and I can see its in deep sleep in cpu spy

EDIT: its seem to be better after default script back on ! lets see if the battery gonna drain faster in sleep mode ! :(
[Galaxy S II Original Android Development] Bushido76:
Hey tajkun,

there is always a risk playing with parameters like frequencies or voltages. But in the last years I never experienced a "real" problem with one of my phones.

It's your decision... And remember - everything is on your responsibility... ;)

Bushido
[Galaxy S II Original Android Development] bala_gamer:
Hi gokhanmoral... supercurio has released "LOUDER" sound volume for galaxy s2.. He has also said that those tweaks can be added to any custom kernels, so how about adding those audio tweaks to our much beloved siyah kernel ??

https://github.com/project-voodoo/mc1n2_voodoo
[Galaxy S II Original Android Development] Ogy77:
Thank you one more time,but can I do overclock,its risk,I dont like voltage never do that?
[Galaxy S II Original Android Development] Thenetstriker:
I've looked at the source files of the SiyahKernel and found the Xbox 360 Gamepad driver: https://bitbucket.org/gokhanmoral/siyahkernel3/src/02f570cb5357/drivers/input/joystick/xpad.c

I tried to attach my Xbox 360 Wireless receiver, but the gamepads are not reconized. Is this driver really supported or is this a bug?
[Galaxy S II Original Android Development] drziddo:
@gokhanmoral You should check this out.

Please implement it.

Thanks.
[Galaxy S II Original Android Development] Bushido76:
It's a slight risk - but it stays a risk. ;)

If you want to extend battery life you will get back to stock frequencies soon... ;)

Bushido
[Galaxy S II Original Android Development] radicalgel:
Sounds interesting. What exactly does this mod do?

CheckROM v4
[Galaxy S II Original Android Development] gokhanmoral:
we already have it but I think it is updated. I will update it when I have time to recompile the kernel.
[Galaxy S II Original Android Development] xsycox:
2.6 is nice.
[Galaxy S II Original Android Development] SilverMist1:
i have a question, if i flash only 2.6 without additional scripts, will i get default parameters. i am very happy with 2.5.1 and i want to upgrade to 2.6. is it sufficient to flash only the kernel to get performance and battery life of 2.5.1?
[Galaxy S II Original Android Development] CruiseMod:
Back to great 2.4.2 version/

2.6 has a slower response in screen sliding .. :/
[Galaxy S II Original Android Development] Rampler:
Can anybody explain what exactly is deep sleep? I thought it is the time which the handy resides at the lowest frequency, but the times between the lowest frequency and deep sleep are different. I checked it with voltage control

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] MaheshSolanki:
2.6 seems to have fault. Gmail emails will not synchronize so reverted back to 2.5.2 Has anyone experianced this problem?
[Galaxy S II Original Android Development] spelaben:
Same here, I was getting a much better battery life with 2.5.2b. Yesterday I faced a sleep of death on 2.6 and I just ignored it instead of rebooting like I usually do.

About 30 minutes later I felt that the phone got extremely hot in my pocket and after rebooting I checked the temperature with the spare parts utility of WajkIUI and found out that the temperature was 38°C...

TL;DR Reverting back to 2.5.2b because it's more stable and gives better battery life.
[Galaxy S II Original Android Development] droidphile:
Deep sleep is like a man (or a woman :) ) sleeping

1) CPU is mostly powered off

2) Screen is dark (of-course)

3) CPU is not clocked anymore (probably the most important aspect of deep sleep. Hence governor does not have any role during deep sleep)

4) Device will wait for an external input/interrupt to wake.

5) Some essential background processes will be running during deep sleep, like power management service and alarm service. They hold some wakelocks too, to prevent service-stop.

6) Many other services are suspend during deep sleep and resumed when device wakes up.
[Galaxy S II Original Android Development] Rampler:
Perfect explanation, thanks again
[Galaxy S II Original Android Development] cwc3:
What are you folks using?

Governor:

Clock:

Voltages:

2.5.2b Came with undervolting, and was pulled because some people could not use.
[Galaxy S II Original Android Development] spelaben:
I used vr + ondemandx and I didn't change any clock or voltage settings. Like I said, never ran into problems with 2.5.2b but with 2.6.
[Galaxy S II Original Android Development] xavihernandez:
I don't know If it's kernel related but does someone have issue connecting wifi? It stays as "connecting..." then it disconnects. I have to connect a public hotspots then log to my personal wifi to success.
[Galaxy S II Original Android Development] seaweeduk:
How long have you been experiencing the issue? Do you have the same issues on the 2.5.2 kernel? A patch was applied in 2.6 which fixed my wifi...
[Galaxy S II Original Android Development] lpsi2000:
Okay, so what are you using:p
[Galaxy S II Original Android Development] cwc3:
You could try to undervolt your phone to 2.5.2b's voltages. Might make up for the battery life difference.

As for the crash, I got one last night too. Will see if it happens again.
[Galaxy S II Original Android Development] xuxuzao:
iam using ondemandx and vr too

and i've undervolted more than 2.5.2b and still battery drains faster! =(
[Galaxy S II Original Android Development] sasho36:
I've noticed that 2.3.5 is much more sensitive to GPU undervolt. Before was stable with 247mHz@800mV, now anything below 950mV for 247mV causes freezes in certain apps (like quadrant - 3D test).

Also I've noticed that the occasional reboots not only occur when mounting an ntfs drive but also when executing some sh scripts (even sometimes when restoring default voltage values with Gscript), don't know the reason...

That apart, is rock stable!
[Galaxy S II Original Android Development] cedric123:
[Running 500Mhz at 800Mvolts no reboot :P now doing stress test for 5 mins no reboot:P
[Galaxy S II Original Android Development] SupraN0va:
1.8 ......

Don't tweak too much, will make netchip jealous ;-) .
[Galaxy S II Original Android Development] incubus_fr:
Mine is 100% stable at 500MHz/825mV
[Galaxy S II Original Android Development] Heimiko:
so I'm def not the only one with a good proc ;)
[Galaxy S II Original Android Development] cedric123:
having 1200@1150mv 1000-1100mv 800@950Mv 500@825Mv 200@800Mv 100@800MV im not allowed to go lower than 800 for some reason:confused::confused:

---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------

someone else wants to post settings? i want to try lower:P just dont know the risks
[Galaxy S II Original Android Development] incubus_fr:
1200MHz@1125mV - 1000MHz@1025mV - 800MHz@950mV - 500MHz@825mV - 200MHz@800mV
[Galaxy S II Original Android Development] dannyboyp:
Rofl.... :)
[Galaxy S II Original Android Development] Heimiko:
i'm having about the same values, just 25mV lower on every setting.

and 100/200MHz are stable at 600mV, maybe lower. (but can only be tested on CM7's official kernel at the moment, as this and every other normal kernel doesn't support going that low)
[Galaxy S II Original Android Development] dannyboyp:
1600mhz@1425mV-

1400MHZ@1250mV-

1200MHz@1150mV - 1000MHz@1050mV - 800MHz@950mV - 500MHz@825mV -

200MHz@800mV

100MHz@800mV

Super stable!!
[Galaxy S II Original Android Development] cedric123:
I had a couple of thinks i like you to add so if i can:

- MDNIE screen sharpness tuning (improves text readability)

- MDNIE color tuning (reduces over-saturation of color)

- Compiled with optimizations using Linaro GCC 4.5 toolchain thanks for you work i would be very happy if you could add these.

- undervolting till 600Mv

-base on the newest sources(I dont know wich one meaby you alredy have but still its important.

If you add these you got a perfect kernel
[Galaxy S II Original Android Development] SimpleNick:
finally running 100MHz@800mV stable (3 hours from first flash).

before this phone would crash immediately after 100MHz is applied.

KI3 deodexed stock, SiyahKernel v1.7.7:
[Galaxy S II Original Android Development] evolutionvii:
Somebody can tell me what this mean and how to config??

GPU clock and voltage control interface (thanks to netarchy).

Really i know what it is but i dont know how to config it.

Thanks!!!

However this is my config for setcpu

200mhz@800mV

500 @ 825

800 @ 950

1000 @ 1025

1200 @ 1175

1400 @ 1275

1600 @ 1425
[Galaxy S II Original Android Development] cedric123:
whats the best gouvernor for CPU?
[Galaxy S II Original Android Development] kartalgurhan:
Gokhan,

You'll definitely get me fired as i am sitting and F5'ing all day long! :D

The gpu uc/uv example script you provided says:

Voltage info:

500000 min 1200000 max

950000. 1000000 defAult

i set gpu as 100/160 for cpu freq and 600000/650000 for voltage.

i get a system dump and i see that the values are inserted as instructed and these values show up in gpu_control file.

However, maybe i'm wrong but somewhere in this thread i remember somthing like you said the min voltage that can be used is 800000... is that so? Or can i really go as low as 500000?

many thanks
[Galaxy S II Original Android Development] alucine:
version 1.7.8 are in changelog

But 1.7.8 link where is ?
[Galaxy S II Original Android Development] yoplaboum:
I think not again available
[Galaxy S II Original Android Development] chilavert_gr:
can you tell us your voltages?
[Galaxy S II Original Android Development] rodries:
I'm having problems in recovery mode

when I try to start adb in root mode I get:

adbd cannot run as root in production builds
[Galaxy S II Original Android Development] h20pt:
Silly question.. Will this kernel work on CM? :)

Didn't find any "cyanogen" or "CM" words using search :/

Thank you

Can't really understand if it means it will work on CM or not..
[Galaxy S II Original Android Development] olifee:
I hope you are still following the thread, just read your post.

A while ago (http://xdaforums.com/showthread.php?t=1263838&page=288 , yes, really on page 288 :P ) I faced a similar problem and fixed it by removing some App2SD. It seems the increased I/O activity on boot paired with the media-scan caused some locking up and a (partial) reboot. Some processes (SSH) survived that, so it was no complete rebooting, but as you noticed, a soft (or 'warm') reboot.

It does not happen at every boot and depends on the governor, scheduler, cpu speed after boot, init-script delay etc.

Maybe this is the reason why Samsung reverts the cpu speed to 1200 MHz after boot, who knows ;).

drigz08 has found the app "Rescan Media" (free on market) which can disable media scanning on boot, this fixed the problem for him (and for me, too). So you can either remove some App2SD (put them back to internal storage) or disable media scanning on boot (the app allows you to rescan media manually in case you need it).

Does that solve your problem?
[Galaxy S II Original Android Development] cwc3:
Have you folks tried applying any of the .zips? Such as the performance one (my fav).

New CWM flashable zip files: “siyah-battery.zip“, “siyah-performance.zip” and “siyah-defaults.zip“.

The speed stepping might work better.
[Galaxy S II Original Android Development] poochewer:
2.4.2 was definately a great version, but to me this new one seems to be slightly more stable in an "allround" way (if you get my layman's drift)
[Galaxy S II Original Android Development] rauschkugl:
How long are you running the kernel? You should give him some days before judging about battery. Using default values here and battery is not worse than on any previous versions.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Heroeagle:
gokhanmoral Cwm app dissapeard after flashing v 2.6

I tried to install cf-root but nothing back .... what can i dooo ???
[Galaxy S II Original Android Development] ggogolewski:
On my phone CWM is dissapeard too!
[Galaxy S II Original Android Development] xavihernandez:
Yeah in previous versions i had this issue. I think since 2.5.
[Galaxy S II Original Android Development] stylez:
I've shared a file with you through Box. To access this file, please visit the following link: https://www.box.net/shared/uytdog8egsghioe5eh5m

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] tolis626:
Good question. :p

Well,I still try to decide between 1536MHz/1375μV and 1576MHz/1400μV.If nothing suits me stability-wise,or doesn't prove to really make the phone heat up less and drain the battery less while using the phone intensively,I'll go back to my previous 1624MHz/1425μV and be done with it.I'll either fry my device or enjoy it more than anyone. :p
[Galaxy S II Original Android Development] cwc3:
Appears to be fine on mine. AT&T.

As for people having issues with 2.6, play with it a little longer. It would be more helpful we could tell him why your battery life is not as good. Are you using your phone exactly how you were the day before? Wipe your cache and let it rebuild again.

So far, everything is fine for me. No more drain than any other version. If anything, it is better.

Though this thread is 90% people saying "I like version X more than Y because it is faster and has better battery-life".
[Galaxy S II Original Android Development] lutanica:
Hi mate,

A little noob question... How do you set it to 1536MHz? Isn't the freq-steps fixed? Which app do you use?
[Galaxy S II Original Android Development] Heroeagle:
Thanx Mate If you were bit earlier I wouldn,t have to Make a clean rom installation :D
[Galaxy S II Original Android Development] tolis626:
Read man,read. :mad:

Anyway,the values aren't fixed.You can change them,albeit withing some predefined limits(not lower than 25MHz and not higher than 1696MHz).The command is:

echo "step1 step2 step3 step4 step5 step6 step7 step8" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table

The steps above are the frequencies you want to use for each step.

Notes:​

i)You can't set a frequency higher than the next one normally is(e.g even if you set 1640MHz instead of 1600MHz,you cannot set 1608MHz instead of 1400MHz)

ii)Values you use must be multiples of 8.

iii)Needed voltages can vary for very small frequency steps.

iv)Once you find the frequencies that suit you,copy the command to an init.d script if you want them to persist after a reboot.​

Hope I helped. :)
[Galaxy S II Original Android Development] Heroeagle:
Gokhan 2.6 HAS ALOT OF PROBLEM WITH CWM not only the app But also in the recovery After installing 2.6 I couldn,t flash any .zip files From the recovery
[Galaxy S II Original Android Development] moore808:
That's weird because I just flashed a new rom and modem after flashing it. Might be user error.
[Galaxy S II Original Android Development] lutanica:
Thanks mate... You know.. all the info here is scattered around. It's very difficult to find the proper info.

The last question: Can't I just edit the freq_table file instead of adding a script?
[Galaxy S II Original Android Development] Bushido76:
When you just edit the frequency table directly your changes will be gone after the next boot.

---------- Post added at 11:56 PM ---------- Previous post was at 11:49 PM ----------

Hey guys,

I know it's hard to be completely objective in judging over battery drain. There are too many parameters which have to kept constant to do a fair comparison. But like some others in this forum I have (after some charge/discharge cycles) the same feeling about the battery life of 2.5.2b and 2.6 (battery config/static bus frequencies). And I'm pretty sure it's not just because of the "placebo" in the name. :D That's why I had a look at the changelog and found the following differences:

1) CONFIG_RCU_FAST_NO_HZ is disabled in version 2.6. The most documentations recommend to enable this parameter in systems which have to be energy efficient. In my builts I never experienced any negative side effects with this option. But I'm interested in other opinions.

2) Memory allocation: I'm not sure, but in 2.5.2b it was SLUB. In 2.5.2 it's SLAB and concerning the latest defconfig it should be SLUB again. So this shouldn't be the reason. ;)

3) Android-Logger: In 2.5.2b the android logger was included as a module - in 2.6. it's build directly in the kernel. I know that it is a philosophical question, but I think, that every log/trace/stat needs additional cpu cycles, i/o-time and battery power. So I'm personally an "advocate" of disabling as much logging as possible.

4) Toolchains: When I remember correctly 2.5.2b was build with the codesourcery toolchains. 2.5.2 was considered as "too stable" ;), so there was a switch to the Linaro toolchains. So it could be, that linaro was the cross compiler for 2.6 too.

Maybe we can use this comparison as a basis for Siyah 2.6.1... :)

Bushido
[Galaxy S II Original Android Development] KennyLegend:
Anybody here with bad battery issues and cwm issues and blaming v2.6 is talking crap .

It is certainly no worse than 2.5.x and it hasn't caused any cwm issues for me.

I would think Something has not flashed properly in your case. Try flashing again...only this time remove boot settings, wipe cache etc etc

For those missing cwm app....is it present in /system/app ?

If so, click on it and install.

Did this help?

Whether its better or not on battery remains to be seen in the next few days.
[Galaxy S II Original Android Development] xuxuzao:
ive used the battery.zip and saw no difference.

is it possible that applying the performance zip, battery drains slower?

and for the ones saying that this is bull****, r u using my phone?

gokhans kernel is awsome!

i am addicted to it and cant wait for every new version

but last version, on my phone, had better battery life!

how can u say battery is not drainig faster?

iam using and i know that it is draining faster on MY phone! :D
[Galaxy S II Original Android Development] gokhanmoral:
I think you are only wrong about the toolchain.

I haven't decided about the logging yet.the other things are already reverted in the announced 2.6.1

There are some other unannounced changes between those two but I don't thing any of them is related with battery drain.
[Galaxy S II Original Android Development] Piretia:
You can get the lights? is that since the 2.4.2 never worked
[Galaxy S II Original Android Development] KennyLegend:
Yes but its obviously an incompatibility issue with your phone/settings etc and not the fault of the kernel itself.
[Galaxy S II Original Android Development] Bushido76:
Hey gokhan,

the toolchain was just an assumption. ;) I experienced several strage problems with linaro, so I'm glad that you are back at codesourcery again. :)

Did you every realize performance advantages of the compiler flag -O3 over -O2?

Bushido
[Galaxy S II Original Android Development] gokhanmoral:
I have not noticed any performance or battery advantage of -O3 and that is why I used -Os in (I think) last 3 releases.

I will not change it in this release.
[Galaxy S II Original Android Development] alcurtis93:
@Gokhanmoral Will you be implementing supercurios new sound improvements posted on his github?
[Galaxy S II Original Android Development] alcurtis93:
Here is the tweet where he announced it..... That's the kernel driver that LOUDER for #GalaxySII #GalaxyNote uses: https://t.co/g9DNyMSQ feel free to integrate in in your custom kernel. -- supercurio (@supercurio)
[Galaxy S II Original Android Development] gokhanmoral:
we have that module for a long time but I've just updated and enabled the auto-loading of that module. it's already in my changelog (mc1n2_voodoo)

EDIT: v2.6.1 is up.
[Galaxy S II Original Android Development] CekMTL:
Thx man!

That is a good gift, as in a few hours I'm catching a plane, and my layover will be in ataturk airport :)

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] lutanica:
Thanks brother for your hard work!

By the way still no CWMManager in 2.6.1!!
[Galaxy S II Original Android Development] PedroMRP:
Just flashed v2.6.1... my first impression is that you done it again.

Now I will test it and try to find something wrong but I know that will be difficult :P
[Galaxy S II Original Android Development] whazi:
Atm on 2.6+ batt.. For 2.6.1 u flash it then battery script on it?
[Galaxy S II Original Android Development] poochewer:
I dont want to seem picky but 2.6.1 seems to be a little bit less smooth than 2.6

Apart from that all looks good so far
[Galaxy S II Original Android Development] PedroMRP:
I don't notice any change in smoothness but different devices different experiences
[Galaxy S II Original Android Development] shahulvm:
can someone give more info on what causes SOD problem. Not that i have SOD, but would like to understand the details of the issue....
[Galaxy S II Original Android Development] hwwr:
Thank you so much for putting in the effort for the kernel.

hello guys, i am rather confus wif the battery zip. only the recent release tat it was available.

may i noe wad it does?

thank you.
[Galaxy S II Original Android Development] desiromeo719:
anyone hear a difference from the voodoo sound module?
[Galaxy S II Original Android Development] lpsi2000:
Let me know how it goes. I am currently sticking with my 1624@1350mV because it seems to be pretty stable for my daily use.