yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gokhanmoral:
I will compile it when I receive some positive feedback.
[Galaxy S II Original Android Development] eybee1970:
positive feedback :)
[Galaxy S II Original Android Development] grisha1:
Is the changelog for 1.7.1 still valid? arighi patch? USB charging (doesn't seem to be written to sys/devices/virtual/misc/charge_current/charge_current)

Thank you for the great kernel!!!
[Galaxy S II Original Android Development] brenopapito:
i flash this kernel (1.7.2), for now, all seems ok !
[Galaxy S II Original Android Development] hyperx:
running it with stock rom since a week and it runs really fine and smooth :)

thx to the dev
[Galaxy S II Original Android Development] chadouming:
forever f5 <3 :D
[Galaxy S II Original Android Development] MPKO:
Latest beta working nicely :-) Great work!
[Galaxy S II Original Android Development] rodries:
No need to take off the battery, only press power button for about 10 secs

I had similar issues, now with stock values and not using 100mhz all is working fine.

Try different governors
[Galaxy S II Original Android Development] tolis626:
HOLY ****!!!!!!

Please tell me you're joking... :p :p
[Galaxy S II Original Android Development] tristecire:
features list updated on http://www.gokhanmoral.com/

CWMmanager 3.0, and another one.

So, nothing new to download and flash, but it's alive and evolves ;)
[Galaxy S II Original Android Development] hallydamaster:
I know it shouldn't be about benchmark scores, but I really wanted to share my results!

Running CM7 Nightly #100, no overclocking 50 mV undervolting on all steps.

So thank you Gokhan for this great kernel!

EDIT: forgot to mention the great battery life with this kernel. lots of screen on time, and still 44% battery after 16 hours use!
[Galaxy S II Original Android Development] ace55:
hi is it safe to flash this kernal on a 2.3.3 stock rom

thanks
[Galaxy S II Original Android Development] vnvman:
Hi gokhan, any plan about implementing the gralloc opensource drivers for the gpu? I tried them in the latest cm7 kang and even tho there's still something to be ironed out games seemed to be smoother and more responsive than ever.

Regards.
[Galaxy S II Original Android Development] crypticc:
Gokanmoral. CWM 3 APK says that recovery that comes with your kernel isn't cwm 5, so disables features..did you want me to report this to chainfire, or do you have this covered?

P.s. b4 is so smooth it's almost pre cognitive
[Galaxy S II Original Android Development] alcurtis93:
Yes I would upgrade to a newer firmware if i were you though :)
[Galaxy S II Original Android Development] cmd512:
Agreed, 2.3.5 is so much smoother than 2.3.3, there is no reason why anyone should still be on 2.3.3.
[Galaxy S II Original Android Development] JB-007:
Hi, just install b4, everything seems to work fine except browser lagging.
[Galaxy S II Original Android Development] cmd512:
No browser lag here on Intratech's KJ3. What FW are you using?
[Galaxy S II Original Android Development] fasst:
I think your are misunderstanding the message that appear i CWM-3.

CWM disables the posibility to flash a ROM-package, or a ROM-package + CF-root at the same same.

Chainfire clearly states in his release notes that this is only possible with a flashed CF-root kernel and not with other kernels.

But a good idea would be if Chainfire opened up for other kernels. If that is in his interrest, or if it is possible, is for me unknown.
[Galaxy S II Original Android Development] JB-007:
I'm using revolution 2.7.1 from leomar75

No problem with 2.1.1
[Galaxy S II Original Android Development] crypticc:
Appreciated
[Galaxy S II Original Android Development] xavihernandez:
You can set notifications by LED in CyanogenMod settings menu. Even BLN working on Samsung devices.
[Galaxy S II Original Android Development] Acesi7:
I'm having some issues with Siyah Kernel 2.2 Beta 4, and Galnet MIUI 1.11.4. It seems the phone doesn't go into Deep Sleep very often. Staying at 100mhz most of the time and it kills my battery. Anyone else experiencing similar problems? Or know a fix?

Thanks guys.
[Galaxy S II Original Android Development] Radikaal:
Going towards the best battery cycle ever with 2.1.1 slightly undervolted, if this keeps up im going to get over 6h screentime 2d+. This with data on always when screen is on and sometimes when its not even if i mostly disable it when screen is off because i sync stuff manually anyway. And almost all time in XDA app when screen is on. And a couple of hours on WIFI. However playing no games this test cycle to compare with speedmod k2-13 batterylife.

And those who experience any browser lag, try changing i/o scheduler to sio, fixed it for me and everything is very smooth now.
[Galaxy S II Original Android Development] cmd512:
Good point, mine defaulted to cfq, which was really slow... so just threw a line into one of my init.d scripts to set to sio during bootup. :)
[Galaxy S II Original Android Development] jetpackjeff:
You can also set BLN timeout, which is very important to me. I't won't be too hard for Gok to immplement these features into a beta release that allow for the phone options list to be available.
[Galaxy S II Original Android Development] yakyllan:
In order to improve the battery life, in KI3 rom (stock) + Siyah 2.1.1..

My main setCPU page is: 100-1200mhz

Which one of the profiles is the best for 100-1200mhz? lulzactive, ondemand, ondemandx, smartassV2... [....]

I don't want the performance to be decreased ( No lag ). But, as I said, I want my battery to last as long as posible.

Any recomendations?

Thank you
[Galaxy S II Original Android Development] Radikaal:
Everyone wants that, but running 100MHz and other governor then Ondemand you are going to get micro lags from time to time. Its very little, and some people maybe are used to having it so they dont notice it but it will be there.

Id say Ondemand since its changed so much lately, it doesnt ramp up like it used to do and you spend most of the time in 200-500MHz anyway doing all stuff except playing heavy games. This because its the most lagfree governor i would say (other then obvious Performance governor).

So just test until you find what works best for you, im running 200MHz with ondemand since i value performance most but still im getting great battery life.
[Galaxy S II Original Android Development] timberwolf60:
I used lolzactive 100 -1000mHz. My battery last 40% longer. lolzactive more smooth than ondemand.
[Galaxy S II Original Android Development] twosix:
I also notice browser lag when viewing facebook mobile using smartassV2. Changed to lulzactive and it is better, still lag though. Using sio all these time.
[Galaxy S II Original Android Development] Molitro:
I agree... ondemand is the way to go. I was using ondemandx, which gave me a great idle battery life, but tried ondemand again on b4 and is just as smooth as speedmod (that is, all the smoothy it can be), and, I'll see tomorrow with my usual test overnight, but I think it has pretty much the same battery life as ondemadx, since while in deep sleep it actually is pretty much the same.
[Galaxy S II Original Android Development] ermacwins:
Im on official miui 1.11.4 is this kernel suitable? After a flash any settings I need to change?
[Galaxy S II Original Android Development] olifee:
@gokhanmoral:

I think this is missing from some changelog ;-).

- CONFIG_NETFILTER_XT_MATCH_OWNER activated to enable the use of orbot / tor

However, in case I want to use transparent proxying of orbot, the iptables-binary of orbot segfaults after complaining the ip_tables-module is missing.

It also segfaults if I just run

/data/data/org.torproject.android/app_bin/iptables --list

However, as

/data/data/com.googlecode.droidwall.free/app_bin/iptables_armv5 --list

works fine (also complaining about ip_tables module missing, but you compiled it into the kernel, which I very much prefer), I am not sure whether the problem is really kernel-related or whether orbot is just broken ;-).

Copying over the iptables_armv5 of droidwall over the iptables-binary orbot brought in solved the problem for me, orbot is working fine now even with transparent proxying.

EDIT: In case you also think it is not kernel related (maybe they compiled against a different libc and it is ROM-related, after all), I can report this to the orbot-bugtracker.
[Galaxy S II Original Android Development] V1TRU:
CLOSE ENOUGH

:D I'm on Miui + 2.2 b3
[Galaxy S II Original Android Development] Radikaal:
you gotten those kinds of results on other ROMS? never been close to those results, especially not the score on CPU Integer and IO with any kernel/ROM at 1200MHz. Just curious!

---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------

Try changing to ondemand and put 80000 sampling rate in setcpu. Still lag?

---------- Post added at 03:30 AM ---------- Previous post was at 03:26 AM ----------

40% compared to what? If this was true for me i would get 8hours 30min screentime which i think is impossible with this device.

I also disagree with it being more smooth:)
[Galaxy S II Original Android Development] V1TRU:
@Radikaal

With Checkrom Rev 2.0 + sijah 2.1.1 the best score i have obtained is 6170 about.

New miui and new sijah make the difference i presume
[Galaxy S II Original Android Development] yoursong:
confirmed working.
[Galaxy S II Original Android Development] runedrune:
@Gokhanmoral

Have you switched over to MIUI yet? :)
[Galaxy S II Original Android Development] chanw4:
Am I the only one getting random system hang (which require me to reboot the device) after turning it to screen off for a long time (happen 3 times, once connected to a wall charger, 1 when connected to usb charger and 1 time just putting it in my pocket) (that is after flashing 2.2 b4 )
[Galaxy S II Original Android Development] cmd512:
Been using beta4 all day, no hangs. And, my lowest frequency is 25MHz @ 800mV.
[Galaxy S II Original Android Development] chanw4:
Using CM7 nightly 108 with no additional script and no UV/UC/OV/OC

Only thing I did is to set the governor to SmartassV2 and click set on boot from the Cyanogenmod setting
[Galaxy S II Original Android Development] jetpackjeff:
gok: can you immplement the device settings availability in newest cm7 builds? It's the only feature keeping me away from your kernel right now. I hate having the touchkey backlights always on and the device settings gives me the option to disable them completely.
[Galaxy S II Original Android Development] adam1741:
All of a sudden my wifi has started to act up. It keeps disconnecting and reconnecting. I'm running ki3 villian rom 3.0 with siyah 2.2 b4. just noticed it tonight. Not sure how long it's been doing it. Any ideas? THanks, Adam.
[Galaxy S II Original Android Development] jlevy73:
25mhz you must be using some of that special Nissan GTR silicon :p

B4 using stock KJ3 has been running smooth all day. Lulzactive seems to be the most responsive IMO.

---------- Post added at 07:49 AM ---------- Previous post was at 07:48 AM ----------

Try going into CWM and 'fix permissions'...might help.
[Galaxy S II Original Android Development] cmd512:
Haha, I'm using one of the excellent init.d scripts from here where it throttles to 25~500MHz/conservative governor when phone is in deep sleep, getting excellent battery life. Agreed on lulzactive being the smoothest.
[Galaxy S II Original Android Development] s2d4:
umm,

1.deep sleep is a completely different state/step..

2.http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html. no need for screenoff.. it's smarter than most of us...
[Galaxy S II Original Android Development] :
Well in theory ondemand should be more conservative than lulzactive or smartassv2, they should be more aggressive governors while staying at lower frequencies when idle.

With Siyah the truth is that ondemand is smoothest governor (excluding performance and some weird setup) with 200-1200, but when down to 100 there are microlags as someone noted. Lulz and smart don't have that lag.

IMOP the most efficient governor would be screen on 500-1200 / screen off 100-200, and that should be lagfree, but I stopped using it as it acted up on me.

This is all my non-scientific opinion and do flame me if you or anyone wants (love to entropy512 :p ).
[Galaxy S II Original Android Development] terenceleechan:
at 100mhz i have lags with lulz and smartass, even with ondemandx, especially in graphics/games. with ondemand everything is much smoother
[Galaxy S II Original Android Development] frankcilo:
For me Conservative governor is the best for Galaxy S2, and thanks to the power of the Cpu x2, you do not see slowdowns and still save a lot of battery!
[Galaxy S II Original Android Development] terenceleechan:
i shall test conservative :)
[Galaxy S II Original Android Development] badtzo:
my best is smartass2 o_o conservative I got lags and on demand that's true about it is the smoothest governor but it always is on 1ghz ~1.2ghz So i prefer smartassv2 it works perfect for me between 500mhz ~1.2ghz (most of time it use lower volting). also on screen off it waste less battery (200mhz~500mhz).
[Galaxy S II Original Android Development] bandit79:
Hm another discussion about this settings ;)

I'm using atm cfq as i/o and ondemandX with 100-1200. There're no lags and the performance is also ok. Only the benchmarks are not soo fantastic.

For example with ondemandX in AnTuTu 5760 points, with lulzactive 5825, with conservative 6010.

So i can't decide which settings i should use. So i'm searching for the best combination between performance without lags and battery saving. Which is it?
[Galaxy S II Original Android Development] :
Siyah OOTB (out of the box) :p.
[Galaxy S II Original Android Development] bandit79:
U mean without any control apps like Voltage Control, SetCPU or something like that? Only the 2.2beta and nothing else?
[Galaxy S II Original Android Development] :
Exactly.. Get 6 hours screen on time :)
[Galaxy S II Original Android Development] GuestK00150:
hey gokhanmoral!

thanks for your hard and really good work. only big thing I'm missing (and it's keeping me away from using this) is that it breaks the new backlightnotification implemented in cm7.

are you planing to fix / integrate the functionality? would love it! thanks
[Galaxy S II Original Android Development] crypticc:
Please and thank you? Tsk. The. youth of today.
[Galaxy S II Original Android Development] kwerdenker:
Guys, could you please keep *all* discussion concerning batterylife and what the optimal settings for you are to the Q&A thread? I just had to read through 3 pages full of that stuff and if gokhan has to do the same, he might skip something important. This thread should be used for development related stuff only.

I know all of us just want to help out and make our little contribution to this great kernel but this should be done in an orderly fashion. We want gokhan spending the free time he is sacrificing for us as effeciently as possible at fixing bugs and compiling and not reading ;).
[Galaxy S II Original Android Development] :
Uhhm okey.. If governors and improving battery life is not about development.......
[Galaxy S II Original Android Development] alcurtis93:
Just found this www.thinkwiki.org/wiki/How_to_reduce_power_consumption about Linux systems but applies to our phones ttoo. Read the section about CPU and then click the explanation link by the man from Intel. Some misconceptions going on in this thread if he is right :)
[Galaxy S II Original Android Development] spaxx24:
"it's better power wise as well; it's a bit complex to explain, but

it's better to execute the code you need to execute at full speed, and

then really quickly go idle, than it is to execute at a much lower speed.

Maybe a simple example (I plucked these numbers out of the air, they

don't represent any real cpu that exists) will help:

Say you have a cpu that consumes 40 Watts at full speed, and 30 Watts

at half speed, and 4 Watts when idle.

You have something to do, lets say mp3 decoding of 1 second of audio,

and that takes a full second at half speed, and one second at full speed.

At full speed decode + idle, that is half a second at 40 watts (20

Joules) and half a second at 4 Watts (2 Joules); total is 22 Joules.

At half speed decode, that is a full second at 30 Watts, so 30 Joules.

So, what ondemand does would cost 22 Joules, while a "hit the exact

frequency" governer would cost you 30 Joules....."

Interesting
[Galaxy S II Original Android Development] kendragon:
where can I found 2.2?
[Galaxy S II Original Android Development] sebsasko:
http://www.gokhanmoral.com/
[Galaxy S II Original Android Development] gokhanmoral:
yes, and it is working great :)

there are some problems which will be fixed in beta6 or 7 (usb related mostly)
[Galaxy S II Original Android Development] karlesg:
Well yes in theory this is true. But there is a catch here :)

This is true if the bolded sentence is true.

So do we really know what's going on with the total consumption of our device in let's say 1200 MHz or 800 MHz or 500 ΜHz under load? There is another law that says that the integrated circuits our device is using, in half frequency they will consume half the power. So what is actually going on is a little bit more complicated than the above example.

I don't know if there are any official datasheets that actually tell us the total power consumption of our device in certain frequencies under specific conditions of load. If someone knows any more info that would be really useful and we would have something solid to talk about.
[Galaxy S II Original Android Development] energie:
im also using MIUI with your kernel and its great both battery and performances.

Little OT: Gok will you move to the Galaxy Nexus? :p
[Galaxy S II Original Android Development] fasst:
gokhanmoral,

You wrote for the upocomning beta:

■added cwmmanager3 (thanks to chainfire)

Does this means that CWM3 has full functionality with your kernel or is CWM3 like now, dependent of CF-root kernels for full functionality?
[Galaxy S II Original Android Development] kwerdenker:
We may have different opions as to what "development" means. If I have to decide, if I post something here or in the q&a thread, I ask myself this simple question "can gokhan do something about it?". If the answer is yes, it's going here and if not it's q&a material. Saving batterylife by changing settings the kernel offers you is not something development related. If, for instance, something changed in a new version of the kernel and you suddenly, without doing anything else, get 2 hours instead of 2 days, that would be development related :)

Maybe someone of the more batteryconsious users could write up a guide or something about the effects on batterylife the different settings have so we could sticky it in the Q&A?

What he said. The link talks about a very specific setting in which this would work, but that doesn't have to be the case every time. This discussion about "race to idle" is going on for ever and there will probably be always people who say it works and others who say it won't :). The datasheet for exynos chip would be really nice though but I couldn't find it anywhere.
[Galaxy S II Original Android Development] kendragon:
does mhl tv out works with kernel 2.2?
[Galaxy S II Original Android Development] AndreiLux:
Values from Samsung are 577/408/249/148/55 mAh for respectively 1200/1000/800/500/200 MHz

​

Theoretical power is used using the C*V²*f rule of thumb CMOS transistor power formula.

It's funny because the 1200MHz/1000MHz states are basically straight out of the formula. If the values from Samsung are anything representative of real-world metrics then something very weird is going on with the 800MHz state.

It also shows that efficiency gains are, again, except for the whacky 800MHz value which disrupts the whole table, are pretty near to what theoretical values would be.

I don't know what to do of it. The values are crazy accurate for some states and completely off the scale for 800MHz. Take it with a pinch of salt. If you ignore the 800MHz state values from Samsung then the scaling and linearity to the theoretical formula is correct within a 5% margin. Make your own conclusions. I personally would just prefer to follow the formula.

The efficiency coefficients are what are most important here, you want the lowest ones (yea I know I should have inverted those values to rightfully call them coefficients... brainfart... anyway).

The problem is that we have no value for deep sleep power usage, but I imagine that it's something so ****ing low that the infliction point where the race-to-idle conditions apply are wayyyy below 100MHz.

Basically we shouldn't even use anything under 200 or 500MHz when the screen is off, because

1) getting the job done faster decreases the "work" part of the awake time;

2) when we are using <200MHz then the load can be too high for the CPU to enter the deep idle state, again something for which we don't have any power usage values and have no idea how much it uses. If the Nexus S comparision is any sign (Completely different processor) then it's around 50% less power.

3) Most of us use the same voltage for 100 as for 200MHz, so in terms of power efficiency, it's irrelevant. The only reason to use it then would be during screen-on times, because we're not racing to sleep.

It's all a load of shenanigans and estimates without having engineering data from Samsung, but at least it's something to guide you.
[Galaxy S II Original Android Development] Molitro:
Doesn't anyone have problems recording video?

I don't recall a time when I could record 1080 or 720 fluidly.
[Galaxy S II Original Android Development] the^one123:
lulzactive

@gokhanmoral

Can you please try to tweak the lulzactive governer for a better wakeup after sleep. This governer is IMOP the smoothest and very batteryfriendly. The only issue i think is the wakeup lag or wakeup response @ incoming call.

I run this governer 5 days and it's great. 150 -1200 lulzactive with 150 mhz @ 850mv and have in 10h deepsleep only 1% battery drain. I'm using Golauncher and the lags are minimal. Thats what we all want.

thx theone
[Galaxy S II Original Android Development] karlesg:
Thanks man! Extremely useful post! :)

I totally agree with all this theoretical approach if the values from Samsung are true.

But can you please explain me what the **** is going on at 800 MHz??? This makes no sense :confused: Could it be a typo? :p Does this have anything to do with cpu going to 800 MHz before deep sleep? 800 Mhz consumption just doesn't add up to the rest of the values and the equation... :(
[Galaxy S II Original Android Development] runedrune:
Yay. That's great. :)
[Galaxy S II Original Android Development] _cummoo:
Gok is already workin on it.

And yes it's true, since i've running my SGS2 uv and stable at 1656Mhz, i had to switch from "ondemand" to "lulzactive" governor to prevent microlags. So my experience is that "lulzactive" is the optimal and smoothest choice if you uv and oc your phone to the max !
[Galaxy S II Original Android Development] d3l1:
Back to 2.0 kernel because 2.1 and the supposedly fixed 2.1.1 gave me a lot of lags through the whole phone, not just the homescreen but the apps, too. I tried different governers, different voltages. Nothing beats the smoothness of 2.0 on my device.

Any ideas on why that could be?

Are you still using o/c daemon controller or is there a newer/better app if I don't want to script all the details, just change governers, maybe scheduler?
[Galaxy S II Original Android Development] chris331022:
2.2beta3 works great for me. Looking forward to the 2.2 final version.
[Galaxy S II Original Android Development] CA3iR0:
Not only fluidly but also without that stupid zoom always on @ 720p (makes things more pixelated and it's not practical)