yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] hawkerpaul:
yes i did actually.

if you want gokhan's settings as a base then tweak further, then this is fine.

all i am saying is if you want to use Gokhan's settings as-is, then they can be potentially altered by any boot settings you may have defined in voltage control and setcpu.
[Galaxy S II Original Android Development] sid9922:
I think ther is a problem with CPUspy..even in other kernel, when i set my scaling to 100-1000mhz after reboot when i open cpuspy, ther is a reading for 1200mhz..what i did is after i reboot, i clear the timer in cpuspy..the next time i open it, there is no more reading for 1200mhz..
[Galaxy S II Original Android Development] jim-bo:
No, there isn't a problem in the app, it is telling you what is happening.

When your phone reboots, there is a period of time while it is running, booting, before your settings are applied, either by init script, or by an app that runs at startup.

Before this point, unsurprisingly, the kernel (ANY kernel) runs with a set of default values, the ones compiled in at boot time.

This means that if the default is 200-1200, then it will use all those frequencies as it sees fit, until your script or app runs to set the max frequency to 1000.

That means that when you reboot, your phone will almost certainly spend a little time at 1200, even if you want to set 1000 as the max.
[Galaxy S II Original Android Development] sid9922:
I see..thanks for the explanation mate..
[Galaxy S II Original Android Development] iron@ss:
Thank you.

I believe that the kernel's default settings take precedence for a second or two during boot-up before the SetCPU/Voltage Control configuration kicks in. This results in the, otherwise, unused settings being displayed.
[Galaxy S II Original Android Development] hussainmushahid:
with this kernel button backlights are a bit buggy in MIUI, sometime they run when you turn the screen on, sometimes they don't.The also don't auto time out when the screen is on, they keep running till I switch it off.
[Galaxy S II Original Android Development] droidphile:
(Only for those who are confused about the defaults/performance/battery zips; of-course the names are self-explanatory,but behind the scenes: )

note: If you already have init.d script(s), note that those might override Gokhan's script or vice versa partially if there are tweaks applied to same values. (Example: Gokhan's script set governor to ondemand, your script set governor to lulzactive; after booting don't wonder why is the governor lulzactive)

1) Defaults:

Sets reasonable thresholds for hot plugging for screen-on and screen-off states. Hotplug sampling intervals make sure second core kicks-in latency is satisfactory during screen-on and second-core is checked for 'kick-out' at the right time.

Reasonably aggressive ondemand governor scales cpu between 200-1200 (the original samsung stock which we forgot)

Device enters deep sleep @800 mhz with 400 mhz bus speed.

GPU is clocked @ samsung stock 160 to 267 with 60 and 30 up/low thresholds, which are less than samsung defaults, and hence aggressive.

Bfq scheduler, dynamic bus frequency scaling, sched_mc & AFTR enabled.

Smooth scaling parameters tuned to cause ondemand jump to intermediate frequencies first before jumping to a higher frequency.

2) Performance:

Aggressive thresholds for hot plugging for screen-on state. Second core stays ON longer as compared to defaults zip.

Aggressive conservative governor scales cpu between 200-1400 mhz.

Device enters deep sleep @1000 mhz with 400 mhz bus speed.

GPU is clocked @ samsung stock 160 to 267 with aggressive thresholds.

Bfq scheduler, static bus frequency scaling, sched_mc & AFTR enabled.

Smooth scaling parameters set to cause conservative jump up at will.

3) Battery:

Hot plug threshold set to keep second-core kick-in minimal. During screen-off state, second core will not kick in.

Gentle ondemandx governor which is a little lazy to scale up, scales cpu between 100 and 1000 mhz

Device enters deep sleep @800 mhz with 400 mhz bus speed.

GPU UC @100 to 267 with not-so-aggressive thresholds.

Sio scheduler, static bus frequency scaling, sched_mc & AFTR enabled.

Smooth scaling parameters tweaked to prevent ondemandx jumping cpu towards higher frequencies without visiting intermediate frequencies.
[Galaxy S II Original Android Development] Evollution:
Great Battery life with 2.4.2 topo+ when lisening music:

12h+ of music

+ 20min 3g (facebook and surfing on net)

=
[Galaxy S II Original Android Development] WebReaper21:
These settings should work if you set 100MHz to 101MHz (otherwise the settings will be ignored). I ran these myself for a few days but I found 25 Mhz to almost never be used as even playing some music needs about 75 Mhz with my device, so don't get your hopes up too high ;)
[Galaxy S II Original Android Development] tolis626:
@Droidphile

First of all,thank you for your thorough and amazing explanations man.Stuff I didn't know of before are very clear now(mostly thanks to your sticky thread in General section).

I'd just like to ask your opinion or something.Is there any point in using IDLE+LPA(enable_mask 2) against AFTR+LPA(enable_mask 3) for those who prefer performance over battery life?I mean,it should only affect screen-off consumption before deep sleep,right?
[Galaxy S II Original Android Development] jim-bo:
Not entirely placebo. If someone had kicked their USB charge rate up to 950 from 450, then it would have gone up from 400 to 650, which is a significant increase.

Also, remember that an awful lot of chargers wrongly identify themselves as being USB ports rather than either misc devices or AC chargers, including many car and even some mains chargers, so some people will have seen big improvements between the two settings, just.... not quite what was expected and portrayed.

Bottom line is.... if you want it to charge as fast as it can, set all three charge rates to 650 (or higher) and you'll get your wish.

If you want it to definitely not overload a USB port on your PC, set USB to 450, and the rest to 650.

but values above that are meaningless, and values between 450 and 600 round down.
[Galaxy S II Original Android Development] kalpik:
THIS! http://i.imgur.com/NDJDA.png
[Galaxy S II Original Android Development] droidphile:
Imho, aftr+lpa mode is used to make 'real-powersavings' a reality. Using normal idle with lpa might not cause serious performance improvements, but i think gps & bluetooth have a better chance of not getting interrupted when idle+lpa is used (in screen-off state).

Screen-off activities such as music play will not be affected regardless of Idle or Aftr is used, but the Deep Idle mode (lpa) is better off with Aftr, than Idle.

Off topic, what're all these absurdly weird tags for this thread at the bottom of the page!!
[Galaxy S II Original Android Development] jlieu:
help, I can't find the download for V2.6 kernel..
[Galaxy S II Original Android Development] Phone_Guru:
XDA developer Airbus360 is trying to port ICS to the SGS2 but he is having trouble compiling the linux kernel. Can you help him gokhanmoral? He is using the source at https://github.com/yjwong/android_kernel_samsung_galaxys2 and is running into errors. You can see his progress at https://twitter.com/ICS_for_SGS2. At the moment he is getting the "arm-eabi-gcc command not found" error.
[Galaxy S II Original Android Development] tolis626:
Yeah,the tags are very idiotic.Especially one about someone losing their virginity and making their wife horny and stuff.I honestly would like to know who came up with these.They aren't very...creative(Can't put it more nicely).

Anyway,that's what I thought on AFTR too.I don't care about GPS and bluetooth as I rarely use those.I'm gonna test it and report back in case of weird behaviour. :)
[Galaxy S II Original Android Development] Bushido76:
My best guess: The makefile in the root directory contains the wrong toolchain-path (CROSS_COMPILE).
[Galaxy S II Original Android Development] Phone_Guru:
Thanks, I'll pass it on. If it doesn't work are you able to compile it from the source?
[Galaxy S II Original Android Development] maranello69:
whre's the link? :D can't wait no longer, i needz to flash something right now
[Galaxy S II Original Android Development] Bushido76:
You and your friend can PM me. Then we will find a solution. ;)
[Galaxy S II Original Android Development] xavihernandez:
I have a question: if we decide to flash a battery/performance script, do we have to disable/uninstall SetCPU or other apps like?

Thanks for any answer that can help.
[Galaxy S II Original Android Development] budi5555:
@gokhan: hi mate.. is siyah2.6 already fix external sd problem?
[Galaxy S II Original Android Development] sansunggalaxys2:
I have random reboots with v2.6 on sensation rom 2 please fix this in the new version.

Selametle...
[Galaxy S II Original Android Development] stylez:
I've cleaned idiotic ones.

_________________________________

Running Insanity II 56, Siyah v2.6 with battery script and all i can say is OMG smooth even at them low setting and battery lasted longer than usual...
[Galaxy S II Original Android Development] Entropy512:
Reports like this are useless without debugging information.

Were you overclocking or undervolting? Don't report stability problems if you are.

Pull /proc/last_kmsg (I believe gokhan has working ramconsole... if he doesn't he's nuts!) and post it after a crash. Without debugging info, nothing will get fixed.
[Galaxy S II Original Android Development] Entropy512:
No, these do nothing. The values go into the MAX8997 charging driver, which is COMPLETELY AND TOTALLY IGNORED.

The MAX8922 is controlled by a completely independent code path.
[Galaxy S II Original Android Development] Entropy512:
Need a dmesg.

And probably Gokhan needs to implement basic currentwidget support if he hasn't.

https://github.com/Entropy512/linux_kernel_sgh-i777/commit/a1a44c90a91e01c0f98bba21688759278646f79a

I wonder if there are some hardware variants that have the 8922 and some don't. It's pretty clear when the 8922 is taking over charging in dmesg if you grab a dmesg after a few plug/unplug cycles.
[Galaxy S II Original Android Development] stevehkim:
I don't understand posts like this one. AMAZING...if it gives you problems use a different kernel man or go back to the kernel you were using.
[Galaxy S II Original Android Development] Steven6489:
Anyone willing to share their undervolt value for 2.5.2?

Stock mV in 2.5.2 seems very high..
[Galaxy S II Original Android Development] stevehkim:
ive got mine at -75 all the way down. dont know if your phone can handle it. try-25 each step first then work your way down. its a tedious process.

supercharged sgs2 i777 galnet rom/siyah kernel = beast
[Galaxy S II Original Android Development] sansunggalaxys2:
I was using siyah kernel before and i had no problems with the same rom but when i flashed v2.6 i got random reboots with the same settings. That is why i posted that.
[Galaxy S II Original Android Development] Bushido76:
1200 MHz -> 1225 mV

1000 MHz -> 1100 mV

800 MHz -> 1000 mV

500 MHz -> 950 mV

200 MHz -> 875 mV

100 MHz -> 850 mV

This config runs stable on my phone. But no phone is like another... ;)
[Galaxy S II Original Android Development] Neo.:
How should I keep decreasing the values? Do I have to decrement 25v from every frequency or a specific one? How do I know if it's crashing on specific clock speed?
[Galaxy S II Original Android Development] Thenetstriker:
I wan't to build the kernel myself, but on https://bitbucket.org/gokhanmoral/siyahkernel/overview there is no build.sh file included and the old kernelsources links do not work anymore. Can someone send me the build.sh?
[Galaxy S II Original Android Development] Bushido76:
Most safe way is to fix frequencies (min=max) one by another using setcpu/voltage control and check stability with benchmarks or watching videos etc. When a frequency is stable then I add 25 mV to be completely sure... :D

Make sure you don't set "test frequencies" as boot setting... :D

---------- Post added at 06:18 PM ---------- Previous post was at 06:13 PM ----------

The build.sh alone won't help you. You will need the complete package (voodoo-drivers, initramfs-files etc.) to build the kernel. But you can PM me your email and I will send you my last build.sh.
[Galaxy S II Original Android Development] gokhanmoral:
unfortunately I am incredibly busy in the following weeks and I have only 30 mins to compile and release v2.6

I have added some more brightness modifications.

I will compile and upload it very soon.

and then I will be unavailable until I finish my current project.

I can only check the messages on my phone. so, don't expect long answers and fixes soon :)

EDIT: I could not check the scripts. maybe siyah-defaults.zip do not have the correct default values. if you have any problem with them, just remove /system/etc/init.d/01siyah and reboot. kernel default values are not that bad anyway.
[Galaxy S II Original Android Development] KennyLegend:
Running 2.6 here with a little undervolting and its the fastest my phone has been in a while.

Seems fairly stable so far and no problems with deep sleep either.

Battery seems good enough too considering its performance.

Thanks GK ! ;)
[Galaxy S II Original Android Development] gokhanmoral:
redownload the new one and flash battery script :)

you can now configure the brightness level further.

I have added a lower brightness step (thanks to hardcore) and also added min_gamma parameter to brightness_curve misc device dir. if you find it too low, just set min_gamma to 1 and you will have nearly stock brightness levels.

and another change is the hotplug frequency level.

in battery optimized version, we have second core disabled for 100, 200 and 500MHz.

so, you won't be able to activate the second core by repeatedly touching the screen which makes the cpu to jump to 500MHz.

in defaults and performance scripts, it is 200 and 100 respectively.
[Galaxy S II Original Android Development] manyakurt:
new version (20) nearly 4 second slower then first one (16).
[Galaxy S II Original Android Development] douglatins:
Should i update from 2.5? i am getting exceptional batt life, 2 days
[Galaxy S II Original Android Development] 03188lee:
First of all thx gokhan bro for such a wonderful kernel~

My question is how to review the uv script? noobie here~ Coz i'm now goin to flash beta3~ what shud I do in detail after that to uv script?
[Galaxy S II Original Android Development] gokhanmoral:
edit /system/etc/init.d/s98undervolt script

there should be some values like "echo 1375 1275 1175 1075 975 875 850"

there are 7 numbers in that script because we used to have 7 frequency steps (1600, 1400, 1200, 1000, 800, 500, 200) but we now have 100MHz step.

just add 825 at the end of that script.

make it like "echo 1375 1275 1175 1075 975 875 850 825 blah blah..."
[Galaxy S II Original Android Development] mehmetenis:
Thanks Gökhan;

I'm so proud.

I'm trying beta3.But as soon as posible you make stable versiyon.

You said " no, I don't use dolphin browser. I use the stock browser and opera mobile or mini sometimes.

your device will get warm if it uses too much cpu"

I'm using normal not hard.(phone call,internet,music vs...)

I think dolphin web browser make warm.

You thing my device has issisue.

Finally thanks very much.

Im trying beta3.Turn back to feedback.

Regard
[Galaxy S II Original Android Development] gokhanmoral:
I use 825mV@100MHz. I didn't dare to try 800 because I am still implementing new features and want to be at the safe side. :)

---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------

I don't think there is anything wrong with your device. I remember some feedbacks about dolphin browser using too much resources, especially on pages with lots of adobe flash content.

just use stock browser and you'll be fine.

there used to be lag in stock browser but rom developers have already solved it. the stock browser is hardware accelerated and it works quite good.
[Galaxy S II Original Android Development] eybee1970:
that was good idea from you - I tried 800 for both 100 mhz and 200 mhz --> freeze :D
[Galaxy S II Original Android Development] colli666:
Can anyone upload the beta3 to a mirror like megaupload, pls? I'm not able to download, because the virus scanner in my office blocks the path.
[Galaxy S II Original Android Development] eybee1970:
...here you go: http://www.multiupload.com/5P8M83NOKJ
[Galaxy S II Original Android Development] Tomasch10:
No longer beta?!

greetz Tomasch
[Galaxy S II Original Android Development] gokhanmoral:
I am testing the first release candidate but I haven't uploaded it yet.

there is no noticable difference between rc1 and beta3. beta3 is stable enough.

I stopped experimenting new settings/features for now.
[Galaxy S II Original Android Development] 03188lee:
Thx for the tutorial~ Guess I'll be waiting for rc1 to release first~ Keep up the good work bro Gokhan~:D
[Galaxy S II Original Android Development] uronfire:
I didn't experience any lag with beta 1. Using beta 3 now will report soon on that.
[Galaxy S II Original Android Development] kwerdenker:
I'm having lock-ups or random reboots with beta3 when device is in screen-off. I'm currently running a kmsg log and will see if I can provide you with some pointers.
[Galaxy S II Original Android Development] gokhanmoral:
That will be quite useful thank you.

Maybe I should increase 100mhz voltage value to 950mv. Can you please use setcpu to set min freq to 200Mhz and see if you still have lockups?
[Galaxy S II Original Android Development] zhite:
I'm using batista final rom 3.7.7...

I will test it and report...

## EDIT ##

No Luck at all... i found it freeze 2 time in 10 min... roll back to RAGEmod T27

Hope you can fix this problem.
[Galaxy S II Original Android Development] unun281292:
No issue was found, feeling great using this kernel, pls have close follow on this post
[Galaxy S II Original Android Development] tudort:
Is there a version 1.5 FINAL ?
[Galaxy S II Original Android Development] thanksgiving60:
honestly, 100MHz is too low no matter what voltage you use
[Galaxy S II Original Android Development] gokhanmoral:
No it is not. The cpu can run on that freq w/o any problems and in the worst case I will set the voltage to the same as 200mhz.

If your rom has any overclocking or undervolting scripts that may be the reason of the lockups.

Tomorrow I will release the final version. I think I will set the voltage of 100mhz to 975 which is stock min and leave undervolting to users. Although the voltage levels are the same with 200mhz it will consume less, believe me on this :P
[Galaxy S II Original Android Development] galinha:
what is 100-1200MHz SmartassV2 UV ?
[Galaxy S II Original Android Development] gokhanmoral:
smartassV2 is the default cpu governor of this kernel, unlike ondemand on most of other kernels.

UV is undervolt. I have undervolted at all frequency values.

100-1200 is the min and maximum frequency step values which are also default for the latest beta.
[Galaxy S II Original Android Development] tonysac:
Now you are the most popular kernel dev...and you deserve it...congrats from a .....greek person...bravo!

Sent from Galaxy!
[Galaxy S II Original Android Development] zaphod777:
Do you have a latest version for the SC-02C? I am running 1.7.2 and have been waiting for the latest stable one.
[Galaxy S II Original Android Development] :
Look at how nice it to see it (in attachment), now give me my BFS kernel, pretty please :D .. I sent you PM.
[Galaxy S II Original Android Development] Heimiko:
Read my last post; I don't think CM7's kernel is doing placebo ... SetCPU re-reads the voltage as actually being 600mV, after it has been set, so I was just wondering if this kernel could possibly also set it as low?
[Galaxy S II Original Android Development] chadouming:
Dont want the CFS boosted one instead ?
[Galaxy S II Original Android Development] :
No, I want BFS, I really like BFS as a concept and from Nexus S days and morfique kernels. Miss him over here, but great that we have gokhanmoral now :D
[Galaxy S II Original Android Development] gokhanmoral:
I will :) in v1.8... :)

first I want to make sure that there are no instabilities with the current version.

1.8 branch will be very instable, you are warned...
[Galaxy S II Original Android Development] gokhanmoral:
I will check this in cm7 source code.
[Galaxy S II Original Android Development] :
can't wait.. my phone is so boring when everything is working fine :p
[Galaxy S II Original Android Development] ebliss:
Hi,

I think you might have missed this post among all the noises. No UV/UC. VR2.5. 100 to 1600.

I hope you can make a debug version. I will log for you.
[Galaxy S II Original Android Development] gokhanmoral:
do you have the same problem with 200-1200MHz?
[Galaxy S II Original Android Development] Heimiko:
I have further evidence to support my theory; 500MHz on CM7's kernel runs 100% stable at 800mV, but if I set it lower, my device will crash (not right away, but it will) this indicates that the CM7 kernel definitely supports lower voltages than 800mV.
[Galaxy S II Original Android Development] gokhanmoral:
can you run this kernel stably at 500MHz with 800mV?
[Galaxy S II Original Android Development] ebliss:
Stupid me. I kept saying that there is no UC. in fact, 100 to 1600 is already uc and oc already. Anyway, I am running stock voltage now, and using StabilityTest app to test stability of the freq. 200 to 1200 seems stable.

Now, I am testing 100 to 500.
[Galaxy S II Original Android Development] cedric123:
I had a couple of thinks i like you to add:o:o 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.
[Galaxy S II Original Android Development] Heimiko:
yep, any kernel runs 100% stable at 500MHz/800mV on my device.

one happy camper :)

so if I could go lower on those 100 and 200 MHz settings, that would be awesome....
[Galaxy S II Original Android Development] gokhanmoral:
ok, I'm convinced :) you are so lucky that samsung sent you a next gen sgs2 accidentally :)
[Galaxy S II Original Android Development] Heimiko:
indeed!! just post a message if you figured out at some point how to UV lower (if possible at all with the samsung based kernel).

just pitty even SetCPU doesn't support lower voltages than 600mV, cause I suspect i might even be able to go lower at 200MHz.
[Galaxy S II Original Android Development] cedric123:
how to know wich gen you got?

my sgs2 is a bit diffrent than my friends outer case has lichter color and mine is newer,
[Galaxy S II Original Android Development] AndreiLux:
Just something that dawned me that one count optimize and improve. For me I have the system process "tvout resume wo" which always takes up 2-3 minutes of CPU time (BetterBatteryStats) which relates roughly to 2% battery more or less. I'm not sure but considering the process name I guess it's the TV out functionality which does whatever it does. Since they're many people who don't use it (who even has the adapter??) it's something that might be smart to disable or able to switch off to improve battery life. Just something that one might want to look into in the future and maybe add onto the todo-list.

Open up the phone and the memory chip on top of the processor and read the processor manufacturing date :D It may truly and is usual that newer devices get better chips because manufacturing processes get better over time. So he either got a "diamond-quality" chip out of sheer luck or things do indeed improve at Samsung's semiconductor plant.
[Galaxy S II Original Android Development] poochewer:
2.6 with performance script RUNNING WONDERFULLY

I have to report that 2.6 with performance script for me is running superbly. I am extremely happy with it. Its been on my phone now for about 24hrs. It sleeps nicely and when it needs to perform, it really flies. It is also extremely smooth!

Many thanks Gokh as usual.