yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] KcDaRookie:
Of course the scores are getting lower on battery balanced settings but if you compare scores from first siyah kernels til 2.2 they will slowly increase, after that they more or less stagnated and now they are even slowly decreasing, although performance and battery life (at least for me) are still increasing and I love it that way, so all the guys that just want to show off with their benchmarkscores are going to other kernels and spamming their threads while we can just enjoy the greatest experience ever since sgsII hit the markets...

Although I must admit that 2.4.2 was a bit of a outlier for me because it was the only version that started to drain more battery life but 2.6 is just kicking ass!

So I'm gone for today, wishing you a merry christmas and plenty of fun with siyah kernel =)
[Galaxy S II Original Android Development] zoie:
merry christmas everyone
[Galaxy S II Original Android Development] sahidmiah:
Sorry mate I am pretty new at writing comments. But regarding that issue I have not OC or UV and still the problem still there. U should watch that movie and see for ur self
[Galaxy S II Original Android Development] b2rdetor:
found a 800mhz bug

I set min CPU to 1600 and Max cpu to 1600

and run antutu

freq scales down to 800 with every governors except performance wtf!!!

after I put my phone into a cold place (I am from Russia and now - winter and its not a problem) for a few min.

set min to 100 and max to 1600 and antutu gave me 7300! while cputesting cpu freq was 1600!

so it isn't kernel, rom, app bug!

its a hardware issue. seems like overheating protection.

but my phone isn't really hot. may be its a bug, may be its a hardware bug of my phone.

so, gokhan can you confirm overheat protection of s2 which scales down cpu freq to 800 when high temperature is appears

and may be excist some remedy to increase cpuoverheatingprotectiontemperature? or turn off that protection?

if your phone isn't overheat you can put it to hot place and after test antutu or other high loading app.
[Galaxy S II Original Android Development] zzz777:
in \sbin\siyah\modules.sh i don't have that lines :eek:

can i flash siyah battery or should i do something before ? :o
[Galaxy S II Original Android Development] gokhanmoral:
yes, there is cpu throttling part when the temperature is high.

if (cur_temp >= set_thr_temp) { /* 85 */
tmu_info->ctz->data.tmu_flag = TMU_STATUS_THROTTLED;
s5pv310_cpufreq_upper_limit(DVFS_LOCK_ID_TMU, CPU_L4);
cpufreq_limited_thr = 1;
if (tmu_tripped_cb(TMU_STATUS_THROTTLED) < 0)
pr_err("Error inform to battery driver !\n");
else
pr_info("normal->throttle:\
set cpufreq upper limit.\n");
}

and the level is 800MHz.

about 2 months ago, I was trying to break antutu record and I could do it by running the test in a refrigerator.

in the original kernel, the level is 2 but we have 2 more steps (1400&1600).

I don't want to remove that limitation because the possibility of causing damage will make some people uncomfortable .
[Galaxy S II Original Android Development] Vaedryn:
Gokhan and all other , wish you a Merry Christmas.

:)

SGS II Cyanogen Tapatalk
[Galaxy S II Original Android Development] stevehkim:
i would much rather have that implemented. this explains the inconsistent benchmarks. those of you that want high benches let your phone cool down prior to a benchmark. and pls dont run a benchmark right after flashing the kernel and as soon as the phone reboots. give it 10-15 mins of cooldown and to rebuild its cache. thx gokhan and merry christmas.

ps im still out of town gokhan. donation will come soon.

supercharged sgs2 i777 galnet rom/siyah kernel = beast
[Galaxy S II Original Android Development] lpsi2000:
Interesting, I will try that at some point. I went back to 2.5 Turkbey pre-released version because that one was very good to me. I will jump back to 2.6.1 after Christmas.
[Galaxy S II Original Android Development] Hertz33:
What is this unhealthy obssesion with benchmarks wich gives you abssolutely nothing. I mean it all becomes a **** whipping contest to see who's got the bigger one.

All I want is a stable device with decent battery time wich bring me to another topic of battery obssesion. Are we all live in some post appocalyptic wasteland where power and chargers are scarse? Is it really so hard to plug your phone in at 9pm? Just enjoy your great device and plug it in when needed.

Sorry about my rant.

Great Kernel Gok, been a fan for a while now.
[Galaxy S II Original Android Development] stevehkim:
My settings for all of siyah kernels since 2.3. Running magnificent.

Just use my settings as a base.

governer-ondemandx

100-1400 min/max frequencies.

(mhz - volts)

1400 - 1325 mv

1200 - 1200 mv

1000 - 1100 mv

800 - 1000 mv

500 - 925 mv

200 - 875 mv

100 - 850 mv

I have 1 screen off profile in setcpu and its max/min is 200-100 mhz.

I have been switching from sio/bfq in voltage control for i/o scheduler and get me the best results as far as smoothness and response. Also I have oc'd the gpu.

max - 400 mhz - 1150 mv

gpu min 133 mhz - 950 mv

Adjust to your liking. You may uv more if your phone can handle it. I'm currently running siyah 2.6.1 default.

---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------

+10000000000000000000000000000000000 :d
[Galaxy S II Original Android Development] xsycox:
That might be more interesting and important than stupid benchmarks: http://xdaforums.com/showpost.php?p=20640751&postcount=14421
[Galaxy S II Original Android Development] AJ.Rockwell:
It's all the matter of how clean your system is, concerning battery consumption overnight etc. I uninstalled all of the aps (even system ones) I don't use, UV'd GPU & CPU and set min frequency to 100. After a hearty dose of sleep (about 6-7 hours) battery went down just 1%... With performance profile applied... I'm supper hapy

Oh and MERRY XMAS EVERYONE!!!1
[Galaxy S II Original Android Development] eybee1970:
No........
[Galaxy S II Original Android Development] ebliss:
I thought 200 to 1200 was stable. But no. after using the device for awhile, the device hang. I had to press on the power button for a long time to reboot. After rebooting, it reboots again. And after it boots up, it reboots again. Didn't set anything with Setcpu and nothing in init.d dir.
[Galaxy S II Original Android Development] gokhanmoral:
I really have no idea why you have those reboots...
[Galaxy S II Original Android Development] angel of other:
Hi all

had 3 reboots in the past 72h since I started with this Kernel

1 - post installing Macify from the market

2 - post pushing rainbow unicorn attack apt via awsome drop over wifi

3 - during using the default MMS app to send a txt last night

I'm running stock settting with no modifications to the voltage, no under/over clocking, no change to the schedulers or governors

I started out with 1.7.0 followed by 1.7.4 & then 1.7.7

any ideas anyone :(
[Galaxy S II Original Android Development] ebliss:
Well, if you can make a debug version, maybe it might help?
[Galaxy S II Original Android Development] gokhanmoral:
yes, I will do it.

but I'm in the middle of a big merge.

I'll release a debug version of v1.7.8
[Galaxy S II Original Android Development] holyshit1:
Now i am running clock 200/267, voltage 500000/500000 and it is stable. And in gpu_control file everything is as I have set. Is that safe?
[Galaxy S II Original Android Development] :
I find it funny how we all use phones in different ways and how phones are different. My phone loves this kernel and almost everything I do works. Only freeze I had was rc1 or rc2 which was damaged anyway.

Huh well, more debugging for you :).
[Galaxy S II Original Android Development] mantzaros:
guys how can i get back the stock charging values?
[Galaxy S II Original Android Development] lpsi2000:
I have none of the issues you mentioned. The only problem I have right now is my security app (smart app protector) is not working well. I have enable the logs and I don't think it is working right yet.

As per my signature, I have it overclocked to 1.6ghz and undervolted accordingly and very stable for me. After 9 hours of moderate use with all kind of widgets, email, social network stuff running, I still had 70% left. According TiBu, I have over 400+ application installed on my phone.

Yes, I don't use all these apps often, but they are there when I need them. The same goes to our PCs, we don't use all the apps constantly, but we have them installed there too. This is smartphone so I believe in keep it loaded with things I need and want.:D
[Galaxy S II Original Android Development] Sp33d_:
Noobquestion ;) :

Is there a possibility to see if kwerdenker's UV script in the init.d folder work?

Maybe in the log?

/edit

When I execute the script manually it gives me an error:

sh UV
Kwerdenkers kernel adaptive UV init-script acitve. Cheking kernel for UV support...
UV: line 18: syntax error: unexpected word (expecting "in")
[Galaxy S II Original Android Development] AndreiLux:
Did you copy it correctly? Line 18 is correct (Switch/in syntax).
[Galaxy S II Original Android Development] wanam:
Why reverting back su?
[Galaxy S II Original Android Development] kwerdenker:
Yes, there is a very easy way: put this script on your phone and run it via adb shell or terminal emulator. It will print out some informations including the current UV table so you can see if the values were accepted.
[Galaxy S II Original Android Development] kapa75:
hi :)

does this kernel have the new features from new ki3's kernel (better battery life and better sound quality? )

btw, you're doing a great job!!! !

thanks.
[Galaxy S II Original Android Development] Sp33d_:
When I open the file with vi I see this strange "^M"

I tried to execute the dump.sh file and it shows me the orignal voltages.
[Galaxy S II Original Android Development] AndreiLux:
It has better battery life but it doesn't have the new sound drivers. Samsung will have to release the next source code update for those.

Those ^M's shouldn't be there. You copied/downloaded the script wrong. It won't work at all like that.
[Galaxy S II Original Android Development] kapa75:
ok, thanks mate :)

do you think that samsung will release the next source code soon? ^^
[Galaxy S II Original Android Development] kwerdenker:
The ^M is just the ASCII representation of the carriagereturn (a.k.a enter), so that normal.

Could you please check your file permissions in the init.d-folder via

cd /etc/init.d/
ls -l

There should be rwxrwxrwx in front of my script. If not, enter

su
chmod 777 *

while still in the init-folder and the check again with ls -l
[Galaxy S II Original Android Development] Sp33d_:
Done
[Galaxy S II Original Android Development] randomhkkid:
Merry Christmas guys!

Just tested 2.6.1 with the new basemark 2.0 taiji

58.10fps!!!!!!
[Galaxy S II Original Android Development] wurzelsepp3:
Can you tell me your settings? I only got 46 fps with gpu @400Mhz.

BTW. a good App to check CPU frequency while benchmarking (or doing other stuff) is CoolTool
[Galaxy S II Original Android Development] KennyLegend:
Id agree with this normally... But....

Im running a slim Rom at the moment with very little apps or system apps and i had the SOD and heavy drain overnight on 2.6.1. Its weird...

I've since removed boot settings and scripts and reflashed 2.6.1 with performance script.

All i can say is WOW!!!

With The performance script .. 2.6.1 is awesome.
[Galaxy S II Original Android Development] mathsmart:
I tried since yesterday the auto brightness but its seem to constantly switch to darkness light ! do you guys have tested it ?

I'm on 2.6.1 with batt script :)
[Galaxy S II Original Android Development] poochewer:
I agree its magnificent!

---------- Post added at 11:14 PM ---------- Previous post was at 11:08 PM ----------

You are so right!! why dont we just go for super performance and simply plug the bloody thing into a charger!
[Galaxy S II Original Android Development] xavihernandez:
Well BLN control is not needed. Use specific menu "settings > device settings" (under CyanogenMod menu). There is a notification by led option to enable.
[Galaxy S II Original Android Development] CamoGeko:
On 2.6.1 now with the old battery performance script zip (didin't like the low brightness levels in the new one). Also I have adjusted voltages slightly and will be testing it for a day or so.

I think mycfg v3 is coming. :D

Thanks gokhan, merry christmas to you and everyone else here at XDA.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] Dark_Lord0122:
send me your V3 config as soon as you finish them ;P as i think i am stuck with V1 xD
[Galaxy S II Original Android Development] gokhanmoral:
I've just found this link (it is exactly the same error that I was getting while playing, i.e. "we're late by blahblah us") and I think the problem with youtube HD content does not only happens with our roms/kernels but it also happens on other devices. it may be youtube app related. I tried dailymotion and watched several HD content without any problem.

and I want to remind you once again that those three "siyah-*" scripts (battery, defaults and performance) are just examples. modifying them is very simple. you may not like the low brightness settings but also prefer battery optimized settings, then just copy&paste brightness_curve settings from performance to battery script. droidphile has a great post about the details of those settings.

merry christmas to all.
[Galaxy S II Original Android Development] KennyLegend:
Merry Xmas to all from Paddy land !!!
[Galaxy S II Original Android Development] Entropy512:
1) Periodic processes can set a timer so that the CPU wakes up at some time in the future. So the process isn't actually running, it just says "I need to wake up 2 minutes from now" and sets a timer that wakes the CPU then. The CPU has a few TINY portions that remain on in deep sleep - they're independent enough that I think they're even on a different regulator. Incoming phone call or incoming wifi packet, and other similar events will raise a GPIO interrupt which wakes the CPU. (The radio has its own low-power CPU and is always running unless in airplane mode.)

4) Deep-sleep power drain is from the peripherals that remain on, independently of the CPU:

Wifi chipset (if wifi sleep policy is "never") - this is VERY low with the BCM4330. The older BCM4329 was much higher, which is why it used to be recommended to turn off wifi when not needing it

The whole radio subsystem has its own CPU that handles all radio management. In fact, the "modem" binary is just a firmware image for this CPU.

DRAM needs to remain powered on and refreshed - the DRAM refresh circuitry is one of the few parts of the CPU that remains powered.

A few other low-drain devices (like the aforementioned timers) keep running.

Think of deep sleep on our phone being similar to what happens when you put a laptop into Suspend to RAM mode. In fact, the mechanisms are almost EXACTLY the same - 90% of the Linux code paths are the same.

Search for the Exynos public TRM for more details - Searching XDA for "S2 hack pack" or something like that should have it.
[Galaxy S II Original Android Development] brack11:
Here is my battery life with this "simple and clean" rom and syiah 2.6

This is my record so far, and I'm already working half an hour more surfing forums.

Sent from my GT-I9100
[Galaxy S II Original Android Development] CamoGeko:
Will do mate, I think I sent you v2 before. ;)

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] Prankey:
Gokhanmoral - both your 2.6.x kernels have reintroduced the wifi tethering bug which was almost fixed (except for "n" mode unavailability) in 2.5.x versions.

Did we do any changes to the wifi drivers yet again or accidentally switched back to older drivers on these new kernels?

More info: http://xdaforums.com/showthread.php?p=20660099#post20660099
[Galaxy S II Original Android Development] xcarecrow:
hi gokhanmoral, there is a kernel named Phenomenal 2.0. This kernel is a speedmod kernel with undervolting. There are listed the undervolted values in some version and for example the extreme version that is the most undervolted has this values:

cpu arm voltages: 1200mhz = 1150mv (stock = 1250mv)

1000mhz = 1050mv (stock = 1150mv)

800mhz = 950mv (stock = 1050mv)

500mhz = 875mv (stock = 975mv)

200mhz = 850mv (stock = 975mv)

cpu internal voltages: 1200mhz = 1000mv (stock = 1100mv)

1000mhz = 1000mv (stock = 1100mv)

800mhz = 1000mv (stock = 1100mv)

500mhz = 900mv (stock = 1000mv)

200mhz = 900mv (stock = 1000mv)

bus voltages: 400mhz = 1000mv (stock = 1100mv)

266mhz = 900mv (stock = 1000mv)

133mhz = 900mv (stock = 1000mv)

gpu voltages: 266mhz = 900mv (stock = 1000mv)

160mhz = 850mv (stock = 950mv)

my question is, what are the cpu internal voltages? are more values that can be undervolted? because with voltage control we can modify cpu arm voltages and GPU voltages right? anyway yo edit these values?

looking these values is that are bus voltages and internal voltages that we can't edit with voltage control, maybe we can edit these through script?

thanks in advance.
[Galaxy S II Original Android Development] Rafael1000:
Hello mate,

Could you send me your new config when it's ready please?

Thank you !
[Galaxy S II Original Android Development] b2rdetor:
so that it means that my CPU temperature is over 85C??? 0-0!

i can explane that - my GPU was 400\1200 ))))) may be GPU cause overheating CPU, setting back GPU to 266\950 and some testing GTA3 gives me a good performance (better than GPU400), because my CPU isnt limited 800mhz.

may be GPU has overheat protection too???

also may be you can make a script adjustble for CPU overheat protection?? (like on\off, or turning up and down that temperature???) or a special HARDCORE version of your kernel?? ))).

IMHO disabling that protection is safety for phone, because it has another EXTREME protection! when a critical temperature are reached the phone automatically switched power off.

HOW we can see the real CPUtemp??? may be some utilities or engeneering menu???

and some more!

BATERY FREAKS its for you:

tested conservative and ondemand and found that ondemand MUCH MORE battery friendly than conservative - why? - i was answered that question some my post ago
[Galaxy S II Original Android Development] CamoGeko:
I will when I've finished testing and tweaking it. :)

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise.
[Galaxy S II Original Android Development] b2rdetor:
offtopic

sorry guys, i know that is a offtopic, but during last 800mhz searchig i made a fix permission via CWM and now all works fine, but some apps isnt work (evernote, betterbatterystats, polaris office, may be some else...) trying to uninstal them and reinstall, but market says me that that apps are incompatible with my device...

have you any idea haw i can fix it??? so many apps are installed and i reaaly hard to make a full wipe (because bad inet connection).
[Galaxy S II Original Android Development] MPKO:
Put your screen resolution back to def...
[Galaxy S II Original Android Development] RotesMeerJogger:
some questions from a siyah kernel newbe. how can i modify all this settings like frequencies, voltages, smartassv2 and so on? is there a gui like setcpu? is setcpu needed for change siyah settings? or do i change all parameters in a file? thanks for feedback.
[Galaxy S II Original Android Development] z2k:
Voltage Control should do everything you want. It's free from the market.
[Galaxy S II Original Android Development] gokhanmoral:
do you have 2000mA battery or 1600mA?
[Galaxy S II Original Android Development] gokhanmoral:
I forgot to add that. although I do not recommend you to change it I will try to add an interface to the next version.

we have cpu freq/voltage and they are editable (8 steps)

we have gpu freq/voltage pairs and they are also editable (2 steps)

we also have bus freq/voltage pairs and there are 3 voltages to set.
[Galaxy S II Original Android Development] b2rdetor:
i asked same question early (2000or1600)

but even its 2000, same onscreentime are possible with reader with black background and white text
[Galaxy S II Original Android Development] alcurtis93:
Merry Christmas peeps
[Galaxy S II Original Android Development] RotesMeerJogger:
thanks a lot. i give you a thanks vote when i'm next time be online with my pc :-)
[Galaxy S II Original Android Development] xcarecrow:
thanks for the answer, i hope you can make editable all values if we can get a little more battery life.
[Galaxy S II Original Android Development] jonamafun:
Do you have 3G enabled?
[Galaxy S II Original Android Development] tolis626:
Well,I have no intention of lowering internal voltage,because I value my data and it puts them at risk.BUT,do you think that there is any chance that upping internal voltages for some high frequencies will make it more stable?I never really understood if it's directly related to the CPU.

On the other hand,bus undervolting along with your promised bus overcloking would make a nice addition to the kernel me thinks. ;)
[Galaxy S II Original Android Development] droidphile:
Afaik, internal voltage should 'sync' with bus frequency voltages as well.

Did ya notice that stock internal voltages form a set of {1100, 1000} and the stock bus voltages for bus frequencies are also from the same set.

I think decreasing internal voltage will not have much effect on battery life as compared to decreasing the core/arm voltage (even undervolting core voltage has no "huge" effect on battery life huh) but will have effect on the stability.

Because of the connection with bus, and since bus has major effects on gpu, i think decreasing internal voltage will make the device unstable.

Long back, when i was on stock kernel, with tegrak module and tegrak oc app, i had tried undervolting internal voltage and ended up in a device that refused to boot. This voltage is very sensitive.

Decreasing internal voltage may also cause increased voltage droop, ie loss in output voltage when on load. Decreasing bus voltages should cause instabilities too.
[Galaxy S II Original Android Development] tolis626:
Well,I like these answers. :D

I too had messed with internal voltages when I was using CF-Root with Tegrak's app,but I had seen no difference whatsoever,so I left these voltages some 50μV lower than stock and never bothered again.

Now,if they indeed sync with bus voltages,that's another story and we shouldn't mess too much with it I believe.If Gokhan makes internal voltage user-adjustable,I'll only test whether it improves OCing stability.I don't actually care that much about battery life as long as it's decent,and with Siyah it's more than decent,especially after 2.3.

Also,considering the needs for high bus speeds,the GPU should be affected far more than the CPU by lowering internal/bus voltage,as GPUs normally need far more bandwidth than CPU(they process much more data at full load).Or at least I think it's like that.
[Galaxy S II Original Android Development] droidphile:
Yes, gpu will be more affected when bus speed/voltages are changed, since gpu always demands high memory throughput. Remember some of us had hd video lag in one version while using static bus freq scaling. (The issue was bus freq locking to 133 during 1080p playbacks regardless of user-set values and Gokhan solved it immediately).

With internal volt/bus freq volt undervolting support, we're gonna get one more feature to play with ignorance and complain to Gokhan huh :)
[Galaxy S II Original Android Development] tolis626:
I agree with the last line...Maybe he should make it really hard to change or something,so that noobs and idiots won't be able to mess with it. ;)