yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Princeomi:
Barely flashed the last version and a new update. Thanks, prior to installing your kernel, under battery stats, the display consumed about 50% of the battery, after installing your app, the display consumes about 60-70%, which means that other processes are consuming less battery.

Thanks

Using setcpu for now as voltage control does not has that many profiles. I really need the in call profile as before using setcpu, my phone used to get hot while talking. After putting the cpu @ 800 while on call, it does not heat up.
[Galaxy S II Original Android Development] KixMe:
so far so good, but im facing one problem.

when i put a cpu manage script in init.d, it doesnt run when i reboot the phone.

is there something im missing? running cm7 at the moment

i named it S95CPU
[Galaxy S II Original Android Development] gokhanmoral:
EDIT: I had to delete v2.6.10 because of a minor mistake I made (left in the source)

I'll reupload soon.
[Galaxy S II Original Android Development] pikachu01:
Did you save it as a Unix file (Edit using Notepad++)? Did you put rwx-rwx-rwx permissions on it?
[Galaxy S II Original Android Development] b2rdetor:
its a CPUoverheting!!! you CPU overheat >85C and CPUfreq became 800mhz - because you had a lags

put that inda you init.d script - it will increase CPUoverheatfreq (0 - 1200, 1-1000, 2-800mhz)

echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target;

now you can set high freqs (1400/1600) and when yourCPU overheats over 85C CPUdown to 1200 (not 800) and you will have a good performance.

or you can downgrade to 2.6.4 (havent CPUoverheating regulation)

also 400mhz GPU goes to oveheating.

but imho OC meaningless because CPUoverhetinglimits exist.

example: you can set maxCPU\GPU to 1600\400 but you freqs really most of time wiil be 1200\400 (with smooth target = 0) and your performance will be the same as 1200\400 ))) or little bit higher.

if you smooth target = 2 (default) you wil gave a bad performance if you try 1400\1600 because in real you CPU will jumps between 1600\800.

also when you OC you drammaticaly loss batery life

and that you get? 20% performance ))) but you batery may drain up to 2X faster compare with UVdefaults
[Galaxy S II Original Android Development] KixMe:
i put permissions now. do i also need to save it as .sh extension or without ?
[Galaxy S II Original Android Development] pikachu01:
Without. What editor are you using? I suggest using VIM or Notepad++. If you save, you need to save it as a Unix file, or else you'll have an extra space at the end.
[Galaxy S II Original Android Development] gal peleg:
Love the 2.6.9 but sinse I've installed it my vibrant notifications r gone I'm sms , in coming calls vibrat don't work.. in seting it's on always..
[Galaxy S II Original Android Development] singingshiver:
Hi, Bluetooth was off....but I had been using sixaxis app and uninstalled it as couldn't get it to work. I'm guessing it left something running in the background after uninstall. Restarted phone and all seems OK now
[Galaxy S II Original Android Development] Evollution:
im still with 2.4.2 XD
[Galaxy S II Original Android Development] niubia:
Send for me to cukenpis@gmail.com

Thanks
[Galaxy S II Original Android Development] gokhanmoral:
isn't it a little old ? :)

keep it if you like but I would be glad to receive a feedback about 2.6.9 vs 2.4.2 :)
[Galaxy S II Original Android Development] :
early feedback Gokhan...using conservative and bfq to test and as per discussions earlier it feels the same as you did mention. i will provide further proof later on in the day or tomorrow regarding battery life but what i will test is youtube play see if that lags in high quality videos, will test music and few more stuff.

comparing it with the other governor that is similar if not the same freaking thing i will say you so far you are right. but like i said i will provide more feedback later on in the day..but so far when starting up laggy but it settles when the phone boots up..when going into a bit of deep sleep kinda takes few seconds to get out of a bit of lag but after that it is fine. not bad governor but still prefer my favorite one over the conservative
[Galaxy S II Original Android Development] AndreiLux:
Actually the thresholds I choose were not random, especially the down-scaling ones; GPU performance and use is vastly more linear than CPU therefore you can map it directly to the frequency: 133 is 50% of 266, so with a little breathing room of 5% => 45%, 40 is 30% of 133 so => 25%.

If you want to use 160 (I don't think 167 works, still the whole frequency multiplier deal), then the down thresholds should be 40/166 = 24% => something like 15-20%. Scaling down under 30% could cause it to immediately ramp up again, so it's too aggressive.

And for the second state: 160/266 = 60% => ~50%. On that one you're scaling down not aggressive enough.

I made a neat ASCII graph to explain it better...

85% 30% 80% 30%

040: |########++

160: |------------####################++++++++

266: |--------------------##############################################

85% 15% 85% 50%

040: |########++

160: |------############################++++++

266: |---------------------------------#################################

90% 25% 90% 40%

040: |#########+

133: |--------######################++++

266: |---------------------------#######################################

- : load under threshold

# : load between thresholds

+ : load over threshold​

... I made the bars to scale to the frequencies and so they are representative. I hope they make sense to you.

Use 85% 15% 85% 50% if you want to use those frequencies, as the other one has a load gap for one, and overlaps too much on the other frequencies.
[Galaxy S II Original Android Development] droidphile:
Good work Andrei...

And yeah like you said, 167 doesn't work, VC (and the file) shows 100 as the second step if you use some thing like 100 167 267.

So previously 300 might have been reset to 267 or something.
[Galaxy S II Original Android Development] TheFaixy:
lionheart not available in governers list after flashing this with 2.6.10
[Galaxy S II Original Android Development] pikachu01:
As mentioned many a times in the thread, Lionheart is just a fancy name for conservative governor that has a low sample rate :)
[Galaxy S II Original Android Development] TheFaixy:
so should use conservative then?
[Galaxy S II Original Android Development] Entropy512:
Thanks. That's odd - as far as I can tell it is 0xf in the base I9100 source tree. However there's clear evidence now that it's possible for userland to override this setting with an ioctl - now I know where to start looking after reading your patches.

Interesting results so far:

On AT&T UCKK6, lots of users complain of severe drain on networks with lots of ARP traffic. (This happens to be common for AT&T customers, since their UVerse residential broadband service uses a craptacular 2Wire router that seems to ALWAYS be spamming ARP requests for no good reason.) - Seems to be one of the many wifi battery regressions people report with that build. I need to reproduce this in a controlled manner.

On an XXKI3 base, running the following command:

arping -b <ip address of my file server>

Sends the phone into repeated-wakeup hell. Drained almost 75% in only 6-7 hours. Android OS shot up to 55% and this is on a kernel with the IRQ time accounting patch applied (which hides most AOS usage during suspend/resume)... Of interest is that my Galaxy Player (with an older BCM4329) experienced no noticeable drain, same for my Tab 10.1 (which does have a BCM4330).

Next up: UCKH7 testing. Probably not for a day or two, out all night after work tonight.
[Galaxy S II Original Android Development] CamoGeko:
Ondemand = battery savings

Conservative = performance

Sounds weird doesn't it. :p :)
[Galaxy S II Original Android Development] bgx:
For me Android OS Bug has gone ... Very nice deep sleep but I'm still at 1.7.8 beta0 ;-)

Will post a screenshot later!
[Galaxy S II Original Android Development] jdmcivic:
hi. may i know what this superdaemon 3.0 you're talking about? link?
[Galaxy S II Original Android Development] GDT:
I used the undervolt script in init.d folder from first post. Can someone tell me which files are in init.d folder by default? I want to exclude I've got some zombie file from o/c daemon.

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

from here: http://goo-inside.me/superuser/
[Galaxy S II Original Android Development] jdmcivic:
lol. thats superuser.

brw, init.d scripts are dependant on your rom. has got nothing to do with kernels. the scripts are inputted by ur rom maker. diff roms have different scripts included.

just fyi, o/c daemon works for this kernel.
[Galaxy S II Original Android Development] GDT:
right... my typo ;). I'm a bit tired.
[Galaxy S II Original Android Development] AndreiLux:
By going from beta1 to beta4 the phone wouldn't want to go to deep sleep. I fixed it by wiping the dalvik cache.
[Galaxy S II Original Android Development] gtizon:
So the safest to use is 1.7.7 so far? Right?
[Galaxy S II Original Android Development] hausmanis:
that one works perfect for me!
[Galaxy S II Original Android Development] bragon2010:
I don't have a /system/etc/init.d folder so when i reboot i miss the configuration of SetCPU and the UV.

Any ideas?

PS: Sorry for my english.
[Galaxy S II Original Android Development] theory_87:
Just create the directory yourselves or use setcpu

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] bragon2010:
I use SetCPU. It's installed and i tick "set on boot" but the folder isn't here!
[Galaxy S II Original Android Development] theory_87:
Setcpu don't create any folder. Inti-d folder is only needed if you are running script. But for the easier way, you use setcpu for of or uv.

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] bragon2010:
Ok but i tick set on boot and setcpu don't remember the governor and UV settings. I deleted manually the SU file in system/bin (all the procedure) and reboot but it's still the same :S

i'm on v1.7.8beta4
[Galaxy S II Original Android Development] gokhanmoral:
don't launch setcpu as soon as the system starts.

give it some time to run at the startup.

it doesn't run as soon as your system starts.

if you wait enough you will receive a notification that setcpu is given superuser permissions. if you launch setcpu after receiving that notification you will see that the settings are remembered.
[Galaxy S II Original Android Development] Galaxy_Fan:
@gokhanmoral:

Strange behavior in 1.7.8b4 :

Some apps had connection problems, but not all.

Came from b2. Flashed back to b2 and all is ok.

Anyone else has this issue?
[Galaxy S II Original Android Development] bragon2010:
Well i wait 5 minutes and i didn't see the toast notification and when i opened setcpu the governor was ondemand (default). Then, i open superuser app and i didn't see setcpu in the list but i can change de governor and UV in setcpu. Whats wrong??? :confused:
[Galaxy S II Original Android Development] gokhanmoral:
try to clear cache and dalvik cache.

if it doesnt help clear superuser application data.
[Galaxy S II Original Android Development] bragon2010:
I cleared cache + dalvik and app data (of superuser app). Then reboot. Five minutes later i opened setcpu and ask me for root access. I set up governor and UV and tick set on boot. Reboot again and wait 5 minutes but its the same :confused:

I also try reinstalling setcpu.
[Galaxy S II Original Android Development] manom18x:
In order to get automatic calibration I must have my phone on or off?
[Galaxy S II Original Android Development] gokhanmoral:
on. and charge until 100% + 15 mins.

by the way, I have added this link to the second post: http://xdaforums.com/showthread.php?t=1242323

there is a good explanation about cpu governors and i/o schedulers.
[Galaxy S II Original Android Development] Igor 3:
I read that there was some problem with 2.6.10 and that it would be reuploaded very quickly with the fix? Is it ok to flash it now? Love it that conservative is default now, its always been the smoothest gov. for me.
[Galaxy S II Original Android Development] :
Interested to find out what your v6 power is;)

yes mate it is fine to download.:)
[Galaxy S II Original Android Development] gmavro:
Flash Kernel 2.6.10

Kernel Flash Failed

No zImage found

?????
[Galaxy S II Original Android Development] gokhanmoral:
you can use conservative.

lionheart is just the same as conservative governor with different parameters and v2.6.10 has already very close set of parameters (not exactly the same to preserve more battery).

lionheart is not a highly tweaked governor. there are still hundreds who believe that bull****. that is why I set the conservative governor as default in the latest version.
[Galaxy S II Original Android Development] :
go into recovery. then install zip and then flash away. that is if you are using the zip file of the kernel. if you are using tar then flash through odin

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

Gokhan i do not know if you saw my earlier feedback but making comparisons it is still the same thing as previously stated by yourself above.:)
[Galaxy S II Original Android Development] barrist:
tried siyah again , got a random reboot on 2.6.10 after turning bluetooth off

ah well, guess its still not quite there.
[Galaxy S II Original Android Development] CamoGeko:
I think your whole setup is not quite there. I haven't had a random reboot on Siyah since the early beta versions.

Go complain to your mummy about your phone randomly rebooting, at least she might give you a hug.
[Galaxy S II Original Android Development] KcDaRookie:
Making your mind up this fast without searching for the cause of the reboot clearly shows that the problem is in front of the phone and has nothing to do with the kernel.
[Galaxy S II Original Android Development] legendasboy:
well gonna try 2.6.10 but i must say 2.6.9 been perfect for my phone.
[Galaxy S II Original Android Development] droidphile:
Yeah it is very very bad.

About 3 million hits on the thread shows how many people want to get random reboot or freeze or some other not-so-good-stuffs.

Without providing details like your rom, logcat, last_kmsg posts like this is actually funny.

And one more thing when anyone whines about "random-reboot". Reboot to bootanimation is caused by rom/apps. Reboot to bootlogo is mostly caused by kernel.
[Galaxy S II Original Android Development] gokhanmoral:
if you can give more details about your rom and send me a log I can try to help you.

if not, just go and use your previous kernel who is made by a great(!) developer who cries like a filthy dog when he faces with critics and tries to sell you a freshman app in 3 euros.

oh man! I missed being rude and it feels good! :)
[Galaxy S II Original Android Development] flash608:
Can anybody post stock values of CPU and GPU, i haven`t backuped them :(
[Galaxy S II Original Android Development] gokhanmoral:
there are a lot of values but basic stock values are:

200MHz - 1200MHz - ondemand for CPU

160MHz-267MHz for GPU

voltages are determined dynamically depending on your cpu and they are not the same for everyone.
[Galaxy S II Original Android Development] msgfromside3:
One thing interesting/weird that I am seeing with 10 - when my phone is being charged it is stuck at 500mhz. Before it was at 200. I am pretty much using default setting with noop and no oc/uv/scripts. Weird thing is it was stuck at 200 a day before with the same version. Not bothering me but just fyi if anyone sees the same and gok is interested.
[Galaxy S II Original Android Development] xavihernandez:
Hi peeps!

No one here using BLN built-in feature from CM7? It does not work for me. But it works with BLN Control.

I woulf like to use BLN feature from CM7 and BL always off as I know where are my sensitive button ^^.

It worked before (I can't precise which version of Siyah).

Thanks in advance for infos.
[Galaxy S II Original Android Development] pepe2909:
I tried the latest version of the knzo but i noticed that the brightness is weaker than a kernel stock or Siyah kernel :(
[Galaxy S II Original Android Development] Entropy512:
Yes, doesn't it! Too bad none of us can match Hacre... Flaming is an art for him, and he's got the development skills to back it up. :)
[Galaxy S II Original Android Development] Harsha Raj:
Flashed 2.6.9 via cwm and the phone stuck at the Galaxy SII I9100 screen. Basically its not booting up. I cant go to CWM mode now with 3 button comibation. I can use the jig for download mode. What to do now?
[Galaxy S II Original Android Development] estanenmi:
cry lol....

take off battery and try again cwm... if not work try jig... clear dalvik cache and data cache.. always before change any kernel

if not work too cry more...

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] hallydamaster:
Download a .tar version of the kernel, and flash it through Odin! Or find a stock kernel of some sort, and try with that. Try re-flash your ROM. Else you might have to start over with a nandroid or scratch!
[Galaxy S II Original Android Development] Harsha Raj:
Well I have the backup of data so thats not an issue. Let me try the .tar kernal first. Thank you.
[Galaxy S II Original Android Development] Honusnap:
Expected for 2.6.11

For 2.6.11 :

- GPU : freq set is (40,167,267) .. really so low (40 ?), good.. :), i suppose that this will be the frequency when not using 3D applications..?

How the GPU works ..? I mean the any applications do not need 3D... does this mean that the GPU will stay at the lowest frequency when using 2D functions ? (cf 40Mhz).

I remember it was like that on old Nvidia video cards, a low frequency for 2D than a bigger one for 3D work.
[Galaxy S II Original Android Development] xavihernandez:
Happened to me when I tried to flash from ROM Manager app. I had to flash thru Odin CF-Root. As Siyah available in TAR format you may success flashing it thru Odin (without flashing CF-Root first).
[Galaxy S II Original Android Development] Harsha Raj:
Thank you.

I flashed the CWM itself through link as below and have my phone up and running.

http://xdaforums.com/showpost.php?p=21805204&postcount=9748
[Galaxy S II Original Android Development] xavihernandez:
NP. I'm glad you have solved it.
[Galaxy S II Original Android Development] Harsha Raj:
:) And flashed 2.6.9 with out any issues now. Better to keep the CWM.tar handy as you cant avoid the issue which I had. Looks like it happens once in a while.
[Galaxy S II Original Android Development] gokhanmoral:
but I must admit that the guy is also very good at defending his pitiful position with non-scientific and pathetic arguments. he still makes a list of the patches which means just nothing because instead of following that path, which is artificially made complex anyway, one can only

1) get the conservative governor from upstream linux kernel

2) disable two lines (just as arighi disabled in ondemand) and this part is not even necessary

3) lastly, lower the sampling rate either by hardcoding or using netarchy's method.

to get that governor...

I do miss Hacre as well in these situations.

anyway.. we got better things to do than arguing people who behave like a morons.

at least I am sure that any recognized (or unrecognized) developer with dignity would agree that your posts in that thread are right and true.
[Galaxy S II Original Android Development] remorema:
hey gokhan.

can we expect a fix for mice and keyboard anytime soon for this peace of art kernel?

edit: also. is zeemote working without mice & keyboard support?

edit 2: using 2.6.10 with lulz and battery is pretty decent

Tapatalked from "The ICS Killer"
[Galaxy S II Original Android Development] xavihernandez:
@gokhan

Sorry to point you but if I don't name someone I don't think my post will be read or at least answered (maybe no one use my configuration).

Does the BLN built-in feature from CM7 should work with Siyah? And if yes, should it work when disabling BL (feature of CM7)?

Thanks in advance.
[Galaxy S II Original Android Development] gokhanmoral:
strangely, my HID keyboard works with 2.6.10. and the issue with my apple magicmouse may be something else.

do you mean bluetooth mice and keyboards? or USB?
[Galaxy S II Original Android Development] gokhanmoral:
normally it should work as it works in CM7 kernel, but if I missed a change in that I should check it.

if it doesn't work as expected you can replace liblights with the one in /res/misc and use bln control app until I have time to install cm7 and check it.
[Galaxy S II Original Android Development] confusedmuse:
No Voodoo Louder support since v.2.6.7?

Hello,

i own the App Voodoo Louder, but when flashing Siyah 2.6.9 or 2.6.10 the Voodoo driver says that the Kernle is not supported. When i flash back to 2.6.7 it works again. I also have used the newest Samsung Kernel cleaning script (v1.7) before flashing.

Do someone else have this problem?

I´m using CkeckROM Revo v4.
[Galaxy S II Original Android Development] gokhanmoral:
try to update the louder app.

new app doesn't require module to be loaded and it supports v2.6.9 and v2.6.10 instead of the kernels support voodoo louder :)
[Galaxy S II Original Android Development] remorema:
bluetooth mighty mouse here. only kernel its seems to connect is cf and tegrak build31

Tapatalked from "The ICS Killer"
[Galaxy S II Original Android Development] droidphile:
It works perfectly here.

Since 2.6.8 or something, the mc1n2_voodoo.ko module was removed from Siyah. That may be the reason. (But how! Supercurio confirmed to gokhan there's no need to auto-load the module since the app does it in it's own space).

You can try this:

Flash 2.6.7 or whatever version that has "mc1n2_voodoo.ko" under /lib/modules.

Copy it to some place safe: your internal sdcard.

Flash 2.6.10.

In terminal emulator/adb

su

insmod /mnt/sdcard/mc1n2_voodoo.ko

Now run the app.

EDIT: Saw Gokhan's post. You didn't update the app? :eek:
[Galaxy S II Original Android Development] cmd512:
Thanks for the new kernel, gokhan. Trying out bfq scheduler as per your feedback on its effectiveness against skipping music.
[Galaxy S II Original Android Development] seaweeduk:
works absolutely perfectly on 2.6.9 and CM7 maybe you are using an out of date version of Voodoo or something it definitely works fine for me.
[Galaxy S II Original Android Development] droidphile:
Bfq can assign higher budgets for music playing task over a 'period' of time. And since the scheduler produce less jitter, it is supposed to support skip-free music play and stutter free video streaming.
[Galaxy S II Original Android Development] Harsha Raj:
Hey USB flash drive is working for me through OTG cable. But mouse is not getting detected. I think one of your previous version (don't remember the version number) had made the mouse detectable, but not in 2.6.9.
[Galaxy S II Original Android Development] cmd512:
Makes sense, thanks for the explanation droidphile! :)
[Galaxy S II Original Android Development] confusedmuse:
Well, the Voodoo Louder app is not available in german market, so i downloaded it somewhere else. The payment is in-app anyway. For the same reason i can´t update via market...

But i bought it about 10 days ago, it can´t be that outdated already!?

Thanks. I´ll try that.
[Galaxy S II Original Android Development] xavihernandez:
Thanks for answer. Well I didn't replace anything and it is working already with BLN Control so no worries. If someone else can give a feedback then you may have not to reinstall CM7 to check. I may have done something wrong.
[Galaxy S II Original Android Development] MistahBungle:
Yep. He's done around two updates in that time if I recall correctly.
[Galaxy S II Original Android Development] gokhanmoral:
you can use marketenabler and download from the market.

since it is free the market will just let you download the app.