yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Radikaal:
rc2 is perfect for me on wanam 10.6..found no bugs, tried everything i could think of (wifi+wifi hotspot, USB, BT, videos, camera stuff, games and alot of applications. Not even a freeze.

No lag at all and super smooth scrolling in nova launcher even with full homescreens, and scrolling on webpages. Phone is always cool when doing normal stuff and cpu spy reports most of the time spent at 500MHz and after 3hours of screentime i had 56% of batteryleft and then i had wifi on the entire time. That's with 200-1200MHz.

Also i didnt care to download extweaks for once and just use voltage control instead, changed scheduler to sio and undervolted.

So good i dont see any reason to test 3.0 since im afraid to mess anything up, but want to give a big thanks to you gokhanmoral, your 2.1 kernel on GB gave me perfect smoothness so i used it for months, and now i think i found a kernel that i won't change unless i find out a really annoying bug.

If i had spare money i would donate to both you and wanam, since this is the best combo i had so far on my phone trying hundreds of kernels and lots of roms.
[Galaxy S II Original Android Development] AndreiLux:
I have found that using 100MHz requires more voltage than 200MHz on both frequencies to be able to run stable as opposed to just running 200MHz. I need for example 825mV just for 200MHz where as 100MHz&200MHz both will need 875mV to run stable. And as mentioned, running 200MHz will increase the time the CPU is clock-gated and will reduce leakage as opposed to 100MHz.
[Galaxy S II Original Android Development] Steven6489:
Wifi toggle problem still persist even I flash v3.0 :confused:
[Galaxy S II Original Android Development] Happy_Jack:
You're welcome.

I'm not convinced, but I'm not saying you're wrong. Most of the discussions I have seen are theoretical and extrapolated from a 10 year old IBM paper on the Pentium processor, including assumptions about leakage. :confused:

If you're talking about delaying the time to hit idle from high frequencies I understand, but my phone sits at 100MHz for a lot of the time while I'm reading things on the screen (ebooks, web pages, whatever). Page turning and scrolling doesn't seem to make much difference other than keeping it awake.

The power consumed by a CPU is, in theory, approximately proportional to CPU frequency, and to the square of the CPU voltage:

P=C x V^2 x f

(where P = power, C is capacitance, f is frequency and V is voltage).

http://en.wikipedia.org/wiki/CPU_power_dissipation

So, all else being equal, our CPU uses twice as much power at 200MHz as it does at 100MHz. Of course this is quite a small amount of power either way compared to what your screen is using, which is probably why I haven't noticed any real-life difference in battery life whichever I use. I'd be interested if anyone can point to any experimental data one way or the other.

I know Samsung uses 200MHz as the lowest frequency by default but is that because it's more efficient than 100MHz or is it to avoid the risk of "Sleep of Death" issues? If Samsung always knew best we'd all be on stock firmware. :)
[Galaxy S II Original Android Development] ithehappy:
Hm! +1.

Gotta tap twice ;)
[Galaxy S II Original Android Development] lesp4ul:
Errr mine worked..

Sent from my Nokia 5110 using Pigeon™
[Galaxy S II Original Android Development] olifee:
Indeed, usb mass storage devices are working perfectly, but mice / keyboards and other stuff are detected (they appear in the usb-device tree) but no driver handles them.

Can you provide a link to "Szuptys USB host driver"? Googling for it I only found your post, but maybe I'm just blind ;).

And finally, although I am a bit late on this:

Congratulations gokhan to your new status! You really deserve it :).

And thanks for the wonderful kernel :).

And a small suggestion (don't know if it is really worth the amount of changes needed): Is it possible to add something like "Download extensions" to the ExTweaks interface? I was thinking if NTFS-3G was available as a "downloadable extension" in extweaks, you could go back to a faster compression and tell people to download via extweaks ;).
[Galaxy S II Original Android Development] AndreiLux:
The simple power consumption formula, while it is right, is based simply on the switching power needed on a transistor-level. It does not consider power-saving techniques as clock or power-gating. You have to take into account dynamic leakage and static leakage (short description). The point is that by having the device run on 100MHz it will double the amount of time it spends on doing a computation, and while it will do so at a lower power requirement, the end result is that dynamic leakage as a percentage of the total power consumed during the period of the computation will increase. By enabling lower power states (whichever) we turn off the clock (glock-gating) on the power domain that's being sent into low power and eliminating dynamic leakage, and all that remains is static leakage which we can't do much about unless we power-gate (hotplugging) the thing. Only thing one can do about static leakage is manufacturing process changes, that's why you hear about things like Silicon-on-Insulator (SOI), High-K processes, and recently and soon-to-be FinFET / tri-gate transistors.

There have been measurements made to prove this point showing that 100MHz indeed uses up more power than 200MHz. Not to mention that as I've mentioned, you can run 200MHz at a lower voltage than 100MHz. A multi-billion dollar company like Samsung does actually know best in these regards; the only reason we're not running stock firmware is because we want to make things prettier on our devices and squeeze out performance (in a literal way, and in a battery-life context) in exchange for risking stability.
[Galaxy S II Original Android Development] Happy_Jack:
I think you maybe confusing voltage and power. The simple theory is that CPU power dissipation is proportional to frequency at the same voltage (see my previous post). You may be right that 100MHz doesn't save battery compared to 200MHz but, if that's true, the reasons are far more complicated than the fact the CPU voltage is the same.

Power Misconceptions: http://xdaforums.com/showpost.php?p=22126806&postcount=2
[Galaxy S II Original Android Development] poczesaniec1:
I have a problem with enabling wifi, when I want enable from status bar, it don't won't turn on? but with rc1 it was ok

Wysłane z mojego GT-I9100 za pomocą Tapatalk
[Galaxy S II Original Android Development] Happy_Jack:
Possibly, but that depends what frequencies you phone is running at most of the time. If you spend all your time running benchmarks or 3D games then that will be true. My phone spends > 90% of its time at 100MHz or in deep sleep and only 2% above 800MHz, even though it's not under-clocked.

You choice of CPU governor also has a big impact here. If you are running performance, for example, then under-clocking will make a big difference to battery life, but then why would you use the performance governor and under-clock? A more balanced governor will stop your CPU running high frequencies until it really needs to. Run CPU Spy and see what it tells you. I'd be interested to see that.
[Galaxy S II Original Android Development] darkfra:
Kernel beautiful, congratulations to the developer
[Galaxy S II Original Android Development] kem1337:
i got the same wifi issue under wanam 10.6
[Galaxy S II Original Android Development] Rinoko72:
No problems on Lite'ning v2.6 LP4... ;)

Everything is slike smooth..
[Galaxy S II Original Android Development] korado:
Works like a charm on dynamic 1.1 LP4
[Galaxy S II Original Android Development] KennyLegend:
Mate I'm well aware of what way the frequency scaling/ CPU clocks work. I was just making the point that underclocking can save a lot more juice than undervolting by say...25-50mV per step.

I use the interweb, emails, FB, XDA quite a lot on my phone so my CPU spends a lot of time above 500mHz.

You say ur phone spends 90% of its time at 100mHz....

Do you use ur phone at all??

Why do u even have a smart phone?
[Galaxy S II Original Android Development] KennyLegend:
Its already well known mate. A lot of people have delay in wifi switching on with this kernel for some reason. U might want to read back a few pages on the thread eh?
[Galaxy S II Original Android Development] ithehappy:
Well no offense to anyone here but under clocking doesn't save a LOT of juice. It might save you a good 5-8%, but that's that. Same goes for Undervolting too.
[Galaxy S II Original Android Development] KennyLegend:
It depends on ur phone usage. For me, underclocking to 800mHz gives me about an hour extra screen time. That's approx 25% it saves me !!! I've ran tests several times on GB.

Undervolting on the other hand, saves me nothing worthwhile noticing.
[Galaxy S II Original Android Development] Happy_Jack:
Well thanks for the detailed reply. Unfortunately that link is somewhat lost in translation for me but I agree that there is little, if anything, to be gained from 100MHz.
[Galaxy S II Original Android Development] coloxim:
sorry gm....but the touch is not good,....
[Galaxy S II Original Android Development] frogman:
I am on Omega v9 ROM and I am also experiencing WIFI toggle issue with the latest kernel. Toggled airplane mode first to get it going it took 20 sec to turn on then tryed again and it would not turn on.Rebooted phone with wifi on started straight away.Tryed toggle after deep sleep would not come on even in settings it stayed scanning but stayed grey on the switch. Tryed all the normal wipes reflashed still no luck.
[Galaxy S II Original Android Development] KennyLegend:
Get extweaks from the market and u can adjust it to your own liking. ;)
[Galaxy S II Original Android Development] coloxim:
done.....but the first touch is not good...seems the touch doesn't feel my finger...only the first touch,...I don't know why...
[Galaxy S II Original Android Development] poczesaniec1:
yes but I have seen that was been done, on the page of siyah

Wysłane z mojego GT-I9100 za pomocą Tapatalk
[Galaxy S II Original Android Development] snOwjAwk:
dualboot pleaaase :)))
[Galaxy S II Original Android Development] KennyLegend:
And a lot of people still have the issue... hence why I said read back a bit ;)
[Galaxy S II Original Android Development] sam142000:
Active apps are not showing in the Task Manager!!

Is everybody facing this problem?

And is there any solution to this(even if its temporary from Play Store)??
[Galaxy S II Original Android Development] bala_gamer:
thought i was alone, some quick touches doesnt gets recognized...
[Galaxy S II Original Android Development] Delacor:
+1!!!

Send from my SII ;)
[Galaxy S II Original Android Development] rumirand:
+1
[Galaxy S II Original Android Development] coloxim:
now i'm using netchip kernel and the touch is better...
[Galaxy S II Original Android Development] dee163:
It is a known bug.

It will be fixed when a new kernel is released.
[Galaxy S II Original Android Development] dee163:
Known bug
[Galaxy S II Original Android Development] gendis1979:
+1
[Galaxy S II Original Android Development] nzkller:
same here!! you should use CPU control!!! I like it better!! more stable!!

---------- Post added at 10:48 PM ---------- Previous post was at 10:39 PM ----------

You have to reset it from the CWM Recovery menu!!!!

You are smart you will find it!!!!
[Galaxy S II Original Android Development] zaphod777:
Fyi for NTT docomo users wjchen0 was nice enough to compile a version for us.

http://blogger.wjchen.co.cc/?p=29001
[Galaxy S II Original Android Development] g0tch4:
is this kernel compatible with Hydr0g3n ICS ROM?

thanks
[Galaxy S II Original Android Development] Shm33g:
Yes it is, using it now with latest build. 200-1000mhz with undervolt and battery optimized profile and my phone is flying; GTA III and Dead Space both play flawlessly :D
[Galaxy S II Original Android Development] nzkller:
You are the man!!!!! XD i'm electronic engineer and a master in solid state and telecommunications!! and this guy knows what he is talking about!!!

@AndreiLux can you get me the last post in english!!! I want to read it !!! but i dont want to make a translation with google because I knoe it wont be good!!
[Galaxy S II Original Android Development] goTouch:
CM9 and this kernel is a perfect combination! ;)

Sent from XDA Premium using CM9
[Galaxy S II Original Android Development] MistahBungle:
Will people read the last 20 pages of the thread (and also the first page) before acting like lemmings & posting +1 ?

If you really think the issue you're having isn't already known, you're an idiot. We don't want this thread filling up with mindless crap. This is a dev thread. Take the stupid posts elsewhere.
[Galaxy S II Original Android Development] [deXter]:
NTFS not automounting

Hi gokhan,

I'm running Siyah v3.0 final, and NTFS drives do not auto-mount. When I insert an NTFS flash drive (using an OTG cable), I get a notification message saying that the media is blank or is using an unsupported filesystem. However, I'm able manually mount it using the ntfs-3g binary. Can you please look into this issue? Thanks.
[Galaxy S II Original Android Development] KixMe:
Gokhan: the gentle_fair_sleepers option in extweak is actually useles, because it needs and 'CFS' scheduler to work with. kernel doesnt support this as far as i know.

what are your thoughts about this ?
[Galaxy S II Original Android Development] shanume:
I use voltage control extreme atm. and this on work fine and stable to me.. but I will try to look on this cpu control later :)

edit: I just look into this cpu control and I can see this app has almost same looking as setcpu, but the best is this cpu control support same feature and ICS compatible :D
[Galaxy S II Original Android Development] ithehappy:
Hm! Rapid touches are ignored! Correct.
[Galaxy S II Original Android Development] Harper11:
What governor do u recommend to use? Currently using ondemand but not sure what's best for battery.
[Galaxy S II Original Android Development] Megabit:
I confirm the two issues reported above, switching wifi on status bar and first touch. I'm on stock LPS and the last working version for me is "RC2".
[Galaxy S II Original Android Development] ApriliaM3:
Never mind the app issue... what's up with that font?! :D
[Galaxy S II Original Android Development] Happy_Jack:
SmartassV2 or ondemand, depending on how you use your phone.

http://www.android-hilfe.de/samsung...80670-info-akkuverbraucher-des-galaxy-s2.html
[Galaxy S II Original Android Development] rlorange:
I think you are confusing the core kernel scheduler with the Android user space ones we have control of (SIO, VR etc).

Siyah indeed us compiled with CFS (completely fair scheduler). The only other Linux scheduler used for Android is BFS (Brain **** scheduler).
[Galaxy S II Original Android Development] sam142000:
The font's called Choco cooky!!

Gt bored of other fonts so using this one now!!
[Galaxy S II Original Android Development] xcarecrow:
Any way to make siya kernel compatible with tegrak overclock application?

thanks in advance!
[Galaxy S II Original Android Development] Mr.Greg:
Maybe you gonna ask in tegrak thread to uptade his app to be compatible with ICS kernels? I think lot of people bought his app and he don't want to update it, very sad.
[Galaxy S II Original Android Development] shanume:
tegrak apps support ICS kernel this is siyah kernel this dont support yet
[Galaxy S II Original Android Development] kem1337:
Whats the diff between touch sensitivity values? I dont see any btwn 0-20

wanam v10.6 siyah v3.0
[Galaxy S II Original Android Development] tolis626:
Oh my God!Hacre is that you? :p
[Galaxy S II Original Android Development] cheewaca:
Yes i think that is surely related with 3.0.27 kernel base.
[Galaxy S II Original Android Development] dee163:
Ondemand is fine.
[Galaxy S II Original Android Development] akira888:
Did u guys realize Android OS drain is quite high?

I got around 3.5 hrs screen on time right now. Android OS consumes the same percentage as the screen on time. Normal?:confused:

---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------

Actually can't see any difference among ondemand, smartass, conservative. :D
[Galaxy S II Original Android Development] mikkle:
Yup, same problem here.
[Galaxy S II Original Android Development] pangiotis24:
i think gokhan must revert back to 3.0.15.this problem is probably related to 3.0.27 and i think that the android os high battery consumption has to do with the 3.0.27 linux kernel
[Galaxy S II Original Android Development] ithehappy:
Just noticed the task manager issue. 3 apps are opened, task manager is showing 0!

Swyping from my GT-I9100 via Tt
[Galaxy S II Original Android Development] veyka:
afaik android OS usage reporting has changed in ICS, so comparing it to GB is stupid.

Use your device, see how its battery life is under real world usage, use Betterbatterystats to check for wakelogs.

Androids battery used screen is only even close to valid on stock clocks and stock voltages (As afaik it makes estimates based on power used at clock states etc).

Generally I try and avoid obsessing over battery, and just see if the phone lasts a day or however long I need to use it.
[Galaxy S II Original Android Development] tdamocles:
Gok,

I know this is in the wrong section but will this be released as an ATT i777 version?
[Galaxy S II Original Android Development] Crescendo Xenomorph:
When I navigating menu, the CPU usage maxxed out and make it laggy... Is it normal? Also I occasionally see "android.process.media" maxing out the CPU for about 1 minute or so...
[Galaxy S II Original Android Development] tolis626:
You narrow-minded idiot,mind your language next time you try to play smart.He is 100% right.Sacrificing too much performance and usability for the sake of some minutes longer battery life is worse that stupid.

Our devices don't have the needed hardware to know exactly how much power everything draws,so the Android OS tries to estimate how much battery each process has drawn,mostly judging by the time it has kept the CPU busy.It never was and probably never will be precise.

Next time try to understand facts,try to read something more informative than Playboy and for Christ's sake,don't post here with that kind of attitude.It's not my or Veyka's fault that your iQ doesn't reach room temperature values.
[Galaxy S II Original Android Development] kwerdenker:
If you'd bothered to use your brain for something else than finding curse words, I'm sure you would have understand what veyka was trying to convey:

1. Wakelocks *are* the main source of battery drain in screen-off. Why? Because they keep the cores active instead of sleeping which is a difference between 8mW and 200mW power consumption (if I remember the numbers correctly).

2. The information for the battery usage screen in android is based on values that are supplied by the manufacturer of the device. They basically say "if the devices runs on frequency x the power consumption equals y". So if you change voltages/frequencies from stock, these values might not be accurate anymore and thus the information displayed by the usage screen is also inaccurate. That's at least as how I remember it. If that has changed or is simply wrong, I'd be happy if someone could correct me.

P.S.: Happy Easter to everybody :)
[Galaxy S II Original Android Development] paryav:
I have running Omega 9.

my wifi problem was gone when I set in build.prop wifi supplicant scan interval to 0.

with it I am turn on fast dormancy
[Galaxy S II Original Android Development] BrandoHD:
Thank you guys for taking the time to set him right, I was about to reply, but then I didn't, I don't have the energy to reply to these types anymore, where is Hacre???
[Galaxy S II Original Android Development] copponex:
What, I barely get 3 hours of screen time before my battery has run low :(
[Galaxy S II Original Android Development] Orka82:
Works! Make sure that root works also make sure that you have allowed ExTweaks in Superuser.
[Galaxy S II Original Android Development] MistahBungle:
Don't worry about it too much, you'll be banned within the hour. You clearly have no idea whatsoever about anything.
[Galaxy S II Original Android Development] aceofclubs:
Disrespectful prick.

----------------------

GTI9100 KK5
[Galaxy S II Original Android Development] rlorange:
your on fire man! Donation coming your way next pay day. Smooth scaling... hmm something to learn for me. Luzactive doesn't seem to want to hit 1400. Is smooth scaling meant for ondemand only?
[Galaxy S II Original Android Development] rlorange:
I'm using lpq based rom but on GB bootloaders... any reason I should update?
[Galaxy S II Original Android Development] tvhak:
damm. just can't get my phone to get startup. just black screen.

tried it with westricp rom and just now official rom
[Galaxy S II Original Android Development] troffers:
You and me both mate. It's frickin annoying :mad:
[Galaxy S II Original Android Development] euri007:
system hangs

Try beta 3 with omega 5.1. All seem to be stable until I change via setcpu frequencies. Try to put max 800 mhz and system hangs.

Governor is on demand
[Galaxy S II Original Android Development] johnsin:
Great benchmark at 1600mhz, 5375 with Antutu and html5test with chrome got 343 points.
[Galaxy S II Original Android Development] BadWolfy:
Yeah, System hang when I open setCPU and then it's impossible to go past the PIN screen without flashing another kernel
[Galaxy S II Original Android Development] BoneMo:
which 0320 build ??? last is 0319...

PS: exist---found at http://codeworkx.de/download/cyanogenmod/galaxys2/
[Galaxy S II Original Android Development] tvhak:
what rom you are using?

thanks
[Galaxy S II Original Android Development] tolis626:
Don't ever test your IQ,please. :)

Back to topic.Gokhan,it seems that overclocking doesn't stick.I tried only on CM9 from 19/3 and everything worked quite good,but:

-No matter if I overclocked,both CPU and GPU,performance would be the same(I don't even think it scaled higher)

-Using SetCPU,when I set max CPU speed to lower than 1200Mhz,the phone hangs and I have to reboot.

I don't know if it's something wrong on my part or kernel related,as I didn't have enough time to properly test.In case you can't find anything wrong,I'll look into it further. :)

Congratulations whatsoever man. :)
[Galaxy S II Original Android Development] gabx:
Sorry, was 1 build ahead !!

U right.
[Galaxy S II Original Android Development] rlorange:
Yeah I'm experiencing the same thing. OC seems to revert to 1200 after a short period
[Galaxy S II Original Android Development] BoneMo:
Nevermind,but i hope that the 0320 will be released tonight.. :)...next repaired things :D
[Galaxy S II Original Android Development] metinrecepi:
I want to upgrade my SGS2 to ICS.

What ROM do you recommend to use this kernel with?

I want to use it with original samsung rom but I don't know which one to download, I'm from Macedonia but I couldn't find open Europe rom in sammobile.

I'm expecting quick responses from you.
[Galaxy S II Original Android Development] Bene2k11:
Works like a charm for me. Latest CM9 Nightly, newest SetCPU version, Siyah beta3.
[Galaxy S II Original Android Development] chudm:
anyone having problems connecting the cellphone in mtp mode?
[Galaxy S II Original Android Development] rlorange:
I'm using darky HD LPQ base and FAOP ics theme/mod.
[Galaxy S II Original Android Development] johnsin:
I am using CM9 19th.
[Galaxy S II Original Android Development] stormtroopercs:
One problem with newest beta 3.. when you turn screen back on it resets brightness...
[Galaxy S II Original Android Development] II_DiE_4:
i think its already answered... Get ExTweaks and set smooth scalling to 0..

If not some1 correct me
[Galaxy S II Original Android Development] Binaryian:
I was wondering if maybe Gokhanmoral has lowered the touch sensitivity in 3.0 from rc4? For me I believe there is a big difference. Anyone else experience this?

I for one loves a very touch sensitive screen. :)

Edit: Is there a way to change the touch sensitivity yourself?