yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] CamoGeko:
Thanks for the advice mate, I was thinking about it but I'm not a fan of having lots of different profiles.

I'd rather just have one governor that does everything. :)

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] BlackRainX:
About 6200 with 1200MHz and ondemand Governor.. only UV.. no OC
[Galaxy S II Original Android Development] yahyoh:
my bench mark result

wow:eek: faster than galaxy note lol :D

no oc only uv
[Galaxy S II Original Android Development] veyka:
To be honest, I don't actually see the point in a screen off profile, aka a cap on screen off cpu speed.

If the phone is doing something CPU intensive, to the point it needs more than 500mhz or w.e when the screen is off, why should we cap it? Maybe setting a governor that scales down more aggressively and wont scale up and quickly might be helpful, but what if keeping the cpu capped at 500mhz means it takes X more time for it to finish what its doing so it can go to sleep?

IMO/YMMV
[Galaxy S II Original Android Development] Rampler:
Ok, I changed the gouverner from Lulzaktive to ondemand with 2.6.7 .

Performance and drain is much more better....

Thanks

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
exactly. capping the max freq won't help much if you do not have any problem with your setup. if you have an app sucking the battery then it will suck less if you cap the max freq. however, it is not a solution. in that case you have to find out the problem and solve it.

there are some cases in which it is useful though. if you are listening to music or doing something else which keeps the device awake but doesn't need much cpu power then you may want to keep the frequency at lower levels to have longer battery life.
[Galaxy S II Original Android Development] blaex:
6061 in antutu (latest version) with 2.6.7 (sio/ondemand + uc of -50mw except 500mhz + gpu oc/uv in low state 133/900mw)

great work, battery drain seems to be less while the device is online.
[Galaxy S II Original Android Development] Gowind:
I had USB storage damage issue twice with 2.6.6i. went through a lot of trouble to recover the data.. :D but 2.6.7 is just fine.... no issues so far... :)

by the way i tried to find out setting profiles in voltage control but failed miserably... is it only available in VC extreme...?
[Galaxy S II Original Android Development] CamoGeko:
The only issue I'm having is WiFi being frozen on one bar after every reboot. Have to turn it off and back on again.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] N6666661:
It's painfull to have (like I did) spent days tweaking Lulzacive with more than 7300 under Antutu, great battery life ( near 2 days with medium use + benchs tests) to see with 6.5.7 scores like 5100...

Even with very agressive scales, Luzactive is now useless showing scores nearly the same as Conservative...

The best I was able to do was with a script in the init.d folder : 5340....

Also with 6.5.7 you can change from noop, SIO, bfq, you get extremly fluctuant results on the internal SD writes : from 3Mb/s to 35Mb/s...:eek:

That said, I hope that Lulzactive is not dead...
[Galaxy S II Original Android Development] CamoGeko:
So which scheduler gave you best results?

Communicated using a Galaxy S2 droid from far far away via an XDA premium quality neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] ziTney:
Wow, loving your font, which one is it?^^

2.6.7 working perfectly here, in fact, never had problems with this kernel :D

I'm on the Hyperdroid 5.2.21 ROM

SGS2 | Hyperdroid v5.2.21 | Siyah v2.6.7
[Galaxy S II Original Android Development] N6666661:
None!!! They all can go from 3Mb to 30-40 mb/s!

I have tested with Chainfire CF-Bench Pro v1.1 and Lulzactive gave me : .... I prefere not to say...
[Galaxy S II Original Android Development] CamoGeko:
Hmm... thanks. Sounds like finding the perfect combo of governor and scheduler is still the key. This method has worked for me since the old days of Desire HD when the right combo meant I was getting way over 3 usage out of the tiny stock battery.

Communicated using a Galaxy S2 droid from far far away via an XDA premium quality neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] gokhanmoral:
if you want to score higher just run the benchmark in a fridge.

I am not kidding. put your phone into deep freeze and close it, wait a min, then open the freezer run the benchmark and leave your phone in it until the benchmark is complete.

and that is exactly why I don't overclock. also that is the reason I don't care about benchmark results.

overclocking is just an option.

"not all chips are equal".

that is why I sometimes reply people "are you kidding? :) "

if your device crash @1600MHz or 25MHz with or without under/overvolting it should not be reported here.
[Galaxy S II Original Android Development] stevehkim:
im using MIUI and the font is from RD's dark orange theme.
[Galaxy S II Original Android Development] cmd512:
Yes sir, I like it, please keep ignoring the benchmarking crowd. :) Those of us that actually use our phones prefer real world performance and usability improvements.
[Galaxy S II Original Android Development] IvkovicD:
Hi, thank you for the test. How about vice versa (to SGS2)?

Dejan
[Galaxy S II Original Android Development] fusionjack:
So far so good with 2.6.7 ondemand sio, I feel that 2.6.7 is running smoother and faster than latest version that I used 2.6.4. Or is it only placebo effect? :D. Anyway, well done Gokhan!

As I was playing a game with 2.6.4 ondemandx sio, the game only used 500 Mhz, but now with 2.6.7 ondemand sio is using 800 Mhz. Can I tweak something in ondemand so that the game will use 500 MHz like in 2.6.4? Thanks.
[Galaxy S II Original Android Development] N6666661:
It's an honor that you did directly answer one of my post Gokhanmoral.

No joke here, no kidding.

But I allready know, everything reagarding CPU/GPU overclocking theory.

I work in Computer Graphic 3D and real time 3D for 17 years now.

I have ALLWAYS overclocked my workstations to a very high level while keeping them cool with watercooling systems (some of them was under 0°C) even if for some combos were dual socket mobos!

Quadran is QRAAAAAAPPPP:D

But sorry Antutu and at second intention CF-Bench they both give accurate results and so its not normal that for example you see Lulzacive 2.5.6i gives you 7300 when 2.5.7 gives you 5100 (wich is exactly the same as 2.5.5).

There is definitly something wrong with Lulzactive AND something NEW and wrong with the IO writes on the SD reagarless of the scheduler.

But I may be wrong.
[Galaxy S II Original Android Development] stevehkim:
+1 to antutu and cf being pretty accurate. As far as database i/o for 2.6.7 it's pretty spot on for me. whether it's sio, bfq, noop, deadline. It's definately lulzactive. Don't really care for lulzactive here, ondemand and conservative is the best imho.
[Galaxy S II Original Android Development] chrisjcks:
I'm new to siyah,

Thunderbolt script integrated...

May I ask what this means?

Thanks.
[Galaxy S II Original Android Development] veyka:
Some of the thunderbolt! tweaks are built in, aka the kernel default values for some settings are the same as thunderbolt!

Thunderbolt! is a tweak package by pikachu.
[Galaxy S II Original Android Development] chrisjcks:
Cool, so do I still need to look into thunderbolt tweaks, or is all the good stuff now integrated into the kernel?
[Galaxy S II Original Android Development] stevehkim:
siyah defaults are very very good. tbolt is the icing on the cake. up to you if you want to try them or not. Every phone is different so try it out and see how they work for you.
[Galaxy S II Original Android Development] ata1918:
Emeğine sağlık yaa gökhan abi :D

Amazing kernel, feels like the old SGS 1 with speedmod and ext4 :))
[Galaxy S II Original Android Development] spoiltz:
Do i need to flash battery.zip file, which was once posted for better battery life, or now its already integrated???

Can anyone please provide me the links to the file, or PM me.

What does disabling fast dormancy do??
[Galaxy S II Original Android Development] tbong777:
Agreed, But there will always be those who want the "numbers" and make getting them a "hobby" Just like those who don't use their devices for three days then post screen shots of "300 hours" battery life on a device where batteries are small, cheap easily replaced and up and running full strength in less than a minute.

Its smart phone. USE it as such. When real world performance suffers in a meaningful way I reboot and all is well......and Charge every night. :D
[Galaxy S II Original Android Development] ercxar:
lovely night for boot loops!:p

It seems that 2.6.7 is not very friendly with aggressive UV
[Galaxy S II Original Android Development] N6666661:
It is a commonplace to emphasize those kind of things, and a waste of time for everybody here.
[Galaxy S II Original Android Development] veyka:
Phone works fine without the full thunderbolt! script, but if you want to try it, you can, its easy to install and remove, so knock yourself out.

There's links to it in quite a few peoples sig, and pikachu has posted in this thread quite a bit.
[Galaxy S II Original Android Development] olifee:
Did you try to put it in the fridge?

The phone (as it is not meant for constant load) has a by far smaller heatsink and so the CPU can become hot pretty fast. As with the desktop machines, when temperature becomes too high, the frequency is throttled. That mechanism was disabled in one of the older releases and has been activated again (which is good for safety, lifetime and real life usage, but bad for benchmarks).

So you can either open your phone and add some water cooling (just kidding) or try the fridge ;). I guess your benchmark results will jump high again, comparable to the old ones, and that's what you want, right?

To measure raw performance, selecting "performance" as governor in the fridge would be best.

Did you get the fluctuant results in I/O performance with Antutu? I guess it creates a file for benchmarking each time and then writes to it / reads it back.

If you have a high level of fragmentation on your sdcard, this might explain varying results. Although fragmentation should not *really* hurt with flash memory concerniing the I/O itself, I guess it might increase CPU load. Please correct me if I am wrong here.

To check, I have just done a simple test with my (pretty full and fragmented) internal sdcard, always writing to the same file, and could not notice any such problem:

dd if=/dev/zero of=/mnt/sdcard/bla.img bs=512 count=200k
104857600 bytes (105 MB) copied, 15.2529 s, 6.9 MB/s
104857600 bytes (105 MB) copied, 14.1835 s, 7.4 MB/s
104857600 bytes (105 MB) copied, 19.9847 s, 5.2 MB/s
104857600 bytes (105 MB) copied, 12.0517 s, 8.7 MB/s (I turned screen on)

As caching is still active with dd, a small variation like that is tolerable.

External SD (class 10, apparently caching fools it or the card is just better than it should :P ):

104857600 bytes (105 MB) copied, 5.41983 s, 19.3 MB/s
104857600 bytes (105 MB) copied, 5.45218 s, 19.2 MB/s

So in short, I can't reproduce your I/O-problem ;).
[Galaxy S II Original Android Development] crypticc:
2.6.7 much better. Lags and random power offs gone from my otherwise stock Kl1. thank you
[Galaxy S II Original Android Development] thunderteaser:
Just flashed 2.6.7 over 2.6.6i. lulzactive is not as smooth as it was back in 2.6.6i, but smartassV2 is still fine.

P.S.: I haven't run any benchmarks, I'm talking about how I "feel" smoothness.
[Galaxy S II Original Android Development] N6666661:
I will or must? hit the magic "thanks" button... just because of the time you spent reading my post from its begining to its and.

So thanks you!

Next...putting your GS2 in a fridge is a very very very bad idea!

When you will exctrat it from the fridge, then the phone will be outside but also INSIDE completly covered with water due to a quasi perfectect condensation cycle.

Then the phone will probably die or if its not instantly maybe in the next 2 days...

Then maybe you would be interested into Peltier modules, cold plates, 24 carats thermal compound (an Arctic Silver like but not for noobs), dielectric greasses or sprays, etc...
[Galaxy S II Original Android Development] chadouming:
I was a benchmark freak for a long time. Still a flash junky, but let my bech addiction die. I did this trick often to get higher score. This or put it in front of cold air, outside ( -24 °C currently here ), on cold water bottle. Name it, I tried it :D. Leave my phone in the fridge never hurt it, well never had any problem since i have it.

P.S. Cant wait that kernel source for ICS are out to see siyah kernel on ICS :D.
[Galaxy S II Original Android Development] cmd512:
Exactly. I use my phone HEAVILY all day for mostly productivity/work related stuff. So, it is absolutely essential that I charge overnight. Not sure what these other folks are doing, maybe benchmarking 24 hours? :)

On another note, given all the interest in ondemand now, been playing with it all afternoon. Threw in some pretty aggressive settings to try to get it to scale up fast like lulz (even with the smooth scaling parameters), and the battery life seems to be much better. Will be trying this out for a few days to test. :)
[Galaxy S II Original Android Development] Dennys_Santos:
After applying the kernel version 2.3.7; the screenshot (keys: Menu + Vol.Down) stopped working properly in ROM MIUI 2.1.13

Someone who stands by SGS2 and MIUI could confirm?

Thanks
[Galaxy S II Original Android Development] MrPhilo:
This would be alot better kernel if it didnt use MtpApplication as the usb ..
[Galaxy S II Original Android Development] chadouming:
Flashing ASAP too see this :D
[Galaxy S II Original Android Development] lpsi2000:
CFroot does this job and does well. I vote for the removal because it is causing more issues then it is solving:D

---------- Post added at 07:24 PM ---------- Previous post was at 07:21 PM ----------

CF-root is your friend, removing root will be a good thing.
[Galaxy S II Original Android Development] chadouming:
You made it, my phone is not lagging at all :D (Except the 2-3 sec after waking up, but thats normal )
[Galaxy S II Original Android Development] superleeds27:
Ive also got this problem. When i restart my phone, it puts me back to ondemand and default voltages.

I updated superuser in the market. Syill happening though. Any ideas?
[Galaxy S II Original Android Development] sasho36:
+1

Still having freezes while using Gscript...
[Galaxy S II Original Android Development] jsompis:
+1

Testing 1.7.8beta3 with smartass 100-1200@mhz, Didn't found any problem yet.
[Galaxy S II Original Android Development] inferno17x:
Hi Gokhan,

I have installed version 1.7.8 beta0-3 , when I use SetCPU to create a screen off profile 200mhz MAX and 100mhz MIN. When I do a screen off and waited for some time my phone is not able to wake up. But this does not happen on version 1.7.7.
[Galaxy S II Original Android Development] ebliss:
beta3 still freeze on me despite clearing the superuser and files. It freezes after booting at "Media scanner running... (usb storage)"
[Galaxy S II Original Android Development] jlevy73:
Have you updated superuser to the latest version?
[Galaxy S II Original Android Development] Dreyuser:
dmesg: klogctl: Function not implemented

Hi gokhanmoral,

I'm new in Android so I'm sorry if my question is stupid.

I've just installed kernel 1.7.7 (had 1.7 before). However still have a problem. Some apps returning an error "dmesg: klogctl: Function not implemented". I saw a note about "disabling Android logger by default" and run script (provided) to enable it. I was told that this message means that no logger is implemented in a used kernel. What is right, and what is wrong, and what should I do?

Thanks a lot!

[Samsung I9100XXKI3, Gingerbread 2.3.5, kernel Siyah 1.7.7]
[Galaxy S II Original Android Development] lpsi2000:
The above quote in green is how it used to be with SGS I but I believe Chainfire saw some issues when we started rooting either Atrix or SGS II where it was causing all kind of challenges and changed his rooting method to use xbin. So I am not sure that is a good idea unless something has changed recently. As you will see if you install cf-root after rooting and su is located in /system/bin, it will cleaned it up and a new version installed in /system/xbin
[Galaxy S II Original Android Development] mobix:
Been using 1.7.7 for past 2 days, great work mate. Only problem I faced, that also only once, was WiFi didn't started and have reboot the device. Everything said and done, an amazing effort bro.
[Galaxy S II Original Android Development] geoalexus:
DON'T REMOVE THE ROOT !!! please...
[Galaxy S II Original Android Development] chadouming:
You know that by removing the root script from the kernel it wont magically unroot your device ? It will only not install Superuser and required root file if you dont have it. So you can flash CF ROOT then this kernel and you will still have root. Also, the only reason to lost root would be by clearing manualy the files or by changing roms and i suppose that you dont change rom often.
[Galaxy S II Original Android Development] gtizon:
Will the nex s tweaks work with thia kernel? Also i have the super user bug which doesnt give su permission on boot. Tried reinstalling su v3 bu issue still present. Can i revert to the old version and just flash it thru cwm?
[Galaxy S II Original Android Development] cescof:
Yes but here we change roms often...
[Galaxy S II Original Android Development] superleeds27:
Having mixed thoughts upto now about this kernel.

Seems really good, progress is been made every day, just seems that my battery is worse off with it though, and im not sure why!

Facebook seems to have a lot of wakelocks, yet ive turned off all updates to do with it, so it doesn't refresh every set amount of hours.
[Galaxy S II Original Android Development] tonysac:
I'm with ondemand 200-1400 with uv and I'm using also 100-500 for sleep profile..(1.7.8 beta3)..everything goes well except that I noticed when phone is charging randomly open screen by itself for 1,2 seconds and then close again..I tried also with no sleep profiles but the same..any clues? This happens only once after I close phone..

Sent from Galaxy!
[Galaxy S II Original Android Development] jlevy73:
I noticed the same thing Tony. I might try the stock cf kernel to see if I can duplicate it.
[Galaxy S II Original Android Development] myfluxi:
No process should ever need more than 500-800 Mhz during suspend. Hell, even games like GTA cruise at 800 Mhz max. So capping it at 500 might help a tiny bit.

Music does not send spikes, CPU will never exceed 100 Mhz.
[Galaxy S II Original Android Development] stevehkim:
miui has a screenshot toggle from the status bar pulldown. either way it cant be kernel related. didnt 2.1.13 just come out? i think its the rom boss.

tweaked - by me

kernel - siyah the og

rom- me you eeee.
[Galaxy S II Original Android Development] Igor 3:
I clean flashed Turkbey rom 30.0 that comes default with 2.6.7 but my haptic feedback is not working anymore, does anyone have this problem?

my wifi is not working either.
[Galaxy S II Original Android Development] cmd512:
Works both ways no problem on v2.6.7.

Not sure about spikes, but PowerAMP would skip if lulzactive's screen_off_freq was set to 200MHz or below. Setting it to 500MHz got rid of the skips. Of course, could be because PowerAMP is doing a whole lot more processing of the audio given all the EQ settings, but just throwing that out there.
[Galaxy S II Original Android Development] N6666661:
:D

Ok but in your country, don't you have 2 doors that make a hermetic "region" between the -24°C and 20°C?
[Galaxy S II Original Android Development] myfluxi:
lulzactive is a joke. WTF is everyone so excited about this useless piece of crap. Maybe because many "enthusiasts" love to download useless apps for problems that should not even exist in the first place.
[Galaxy S II Original Android Development] veyka:
Most of the decoding should be done by the DSP, must be the poweramp EQ stuff tapping the CPU.
[Galaxy S II Original Android Development] cmd512:
I like making far reaching one liner claims as well. Maybe you should take that up with the developer?

Agreed. No worries though, 500MHz is good to go. :)
[Galaxy S II Original Android Development] chadouming:
Nope, leaving in igloo, so I dont even have a real door.
[Galaxy S II Original Android Development] Vaedryn:
CM7 2.6.7 Ondemand , very fine. Works like a charme.

Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] cmd512:
Yup! I have my sampling_rate at 50000... and sampling_down_factor at 20! :D

The device will wait a full second at max speed before allowed to throttling down.
[Galaxy S II Original Android Development] olifee:
Thanks ;).

I know about the condensation, I personally never put it in the fridge because I am okay with smoothness without a software tool to measure it.

However, if the environment is not too wet and you only use the fridge-trick for a few minutes, it should not fail (at least not from doing this once ;) ).

Best solution is just living at the north pole :P.

<offtopic>

My desktop i7 is also running with some liquid-metal thermal compound, still air-cooled @ 4.2 GHz. I will only try 'real' OC in case I find a way to make this machine busy for several hours :P. All the simulations I wrote up to know finished 'too fast'.

Same with the mobile: As long as it can run rtorrent, pyload and some 3D game at the same time without any OC, I will rather try to UV a bit to conserve power, it's just 'too fast' for a phone.

</offtopic>
[Galaxy S II Original Android Development] :
@gokhan

hi have you tried charging your phone when its switched off?, the soft lights lit up instantaneously and take you to recovery menu. Curious?
[Galaxy S II Original Android Development] sayatsugu:
Just flashed 2.6.7 this morning, everything seems ok.

Only thing I noticed is that the overall responsiveness is down. Tested with sio with demand/lulz/smartassv2. No scripts, no oc and uv settings which I have used for the last couple of revisions which is stable for my phone.

Tho I must say TW hasn't crashed yet unlike in 2.6.6i, which I think shouldn't be a kernel problem.
[Galaxy S II Original Android Development] s2d4:
VC is not about screen off profiles at all..

It is actually usage profiles, that are toggleable..

When you are playing games - use one profile - higher cpu/gpu clock

when are just reading on xda app - use one profile - lower cpu/gpu clock

when you need absolute battery and only phone use, turn all smartphone features (sync/gps/location/wifi etc) off - minimum cpu clockrate allowable so calls won't be affected.

so you switch to it when you know you are going to need it.

And go to something else when you don't.
[Galaxy S II Original Android Development] stevehkim:
2.6.7 must be spot on as i havent seen 20+ pages after the release. u da man GK!

MIUI rommed, SIYAH kernel synthetics, V6 supercharged, struck by a bolt of THUNDER!

I777 SGS2
[Galaxy S II Original Android Development] poochewer:
Lulzactive used to work really really well a few versions back. But lately it seems to cause probs, especially with video playback.
[Galaxy S II Original Android Development] stevehkim:
damn homie pooch why you so angry at lulz? i personally dont like it either so i just stay my ass away from lulz and stick with conserve and ondemand.

MIUI rommed, SIYAH kernel synthetics, V6 supercharged, struck by a bolt of THUNDER!

I777 SGS2