yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] omniwolf:
yes, but VC only has room for 2 frequencies to UV (until the next release). not sure if it will only UV on those two you set, or if it fails altogether because the kernel expects 3... test it out and let us know.

[edit] actually i think the VC script will probably stop mine from working because it concurrently sets the frequencies to be used as well as the voltage. i'll have a test and see [/edit]

[edit2] ok, VC will overwrite my script's settings. Flash this one to make it execute after VC's scripts. VC doesn't understand Siyah at the moment.

ps if you use the VC startup service, i have no idea what will happen. just use the init.d script method in VC to be safe for the moment.[/edit2]

"my" script doesn't do any UV, just sets the usable frequencies and when they get used.
[Galaxy S II Original Android Development] :
Well, thanks for that but how do i do that?

1. What file extension?

2. Permissions to 755???

All I got is: Read, write, execute for Owner, group and others. Set uid, set gid and sticky...

Thanks for your help.
[Galaxy S II Original Android Development] omniwolf:
use my script:

link is in the post above yours
[Galaxy S II Original Android Development] OrangePL:
Hey,

Noticed from the previous posts quite a number of you are not using the 100 Mhz CPU frequency. Any reason for that?

Had a couple of incidents when the screen "died" on me (phone seemed to be working but the screen and buttons were dark/unresponsive), so I'm trying to track what's that related to.

I'm using 100Mhz with 850mV
[Galaxy S II Original Android Development] MistahBungle:
A lot of people report having problems with music skipping & so on with 100mhz & screen off. Personally speaking, that was a problem for me in earlier builds of Siyah (say before 2.4 or so), but since then I've been using 100-1000 ondemand/sio & haven't had any problems whatsoever with music skipping while the screen is off at all.
[Galaxy S II Original Android Development] omniwolf:
this is why i use min of 200MHz:

Entropy512 post #1

Entropy post #2 (bottom of this post)
[Galaxy S II Original Android Development] :
http://www.android-hilfe.de/samsung...80670-info-akkuverbraucher-des-galaxy-s2.html

Can be read here (for those of you that are able to understand german)

For all others, I'll quickly sum it up: This guy measured every comsumption with some device for measuring currents and all that kind of stuff, I have no idea what it is exactly. Really scientific though. His result: 100mhz is ****. It takes more juice than 200mhz and that is a fact!
[Galaxy S II Original Android Development] Vaedryn:
Yes, i can notify the same results, 200 bring me a little bit better battery than 100 , scary but fact.

SGS II Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] dikai_yang:
I believe it's because most tasks require 200MHz to do. So in idle, the phone needs to keep jumping between 100 and 200MHz, which drains battery somewhat compared to staying at a set frequency and do nothing.
[Galaxy S II Original Android Development] MistahBungle:
Just flashed 2.6.11. Love the new recovery. Everything is structured really nicely. And the Siyah logo is a nice touch :) Will post my thoughts after a day or two of different kinds of use (heavy use/idle/etc).

Thanks as always GM ;)
[Galaxy S II Original Android Development] jermitano:
is it more preferable to just flash the script and not touch vc settings or can i flash the script and manually set vc sets after boots...i dont set mine on boot (i just memorize and set it when i do)...which one is advisable?:o
[Galaxy S II Original Android Development] ole12:
lol i think the new cwm steels battery from me.

After i flashed to 2.6.11 everything went fine.

I rebooted to cwm to check out the new cwm.

After i rebooted to normal system, i lost 20% battery. From 44%. Its been 2hours and i dont get i back lol.
[Galaxy S II Original Android Development] Hannibal226:
OK thanks will try later.

Which mode? Ondemand,smartass or conservative...?

EDIT: Tested ondemand on 200 to 1000 and 800... Both brought crashes :-(

Sent from my Galaxy S2 - I9100 with SensatioN Rom!
[Galaxy S II Original Android Development] omniwolf:
if you touch GPU settings in VC after boot, it will try and set it's 2 step GPU settings, which doesn't apply to our 3 step GPU Siyah kernel.

best bet IMO:

1) remove boot settings in VC

2) flash "my" script

3) use your phone as usual

4) wait for VC to be updated.

if you really want a different governor than ondemand, or different CPU frequencies, or a different IO scheduler.. then set it in VC and flash my script, but make sure your boot settings in VC are "init.d scripts", and NOT "startup service".
[Galaxy S II Original Android Development] XSCounter:
Hey guys. Got a question. What is the difference between the ZIP in the OP -

su-2.3.6.3-efgh-signed.zip (290KB)

and

Siyah-v2.6.11-CWM.zip (7312KB)

from www.gokhanmoral.com

I guess the one I need is from www.gokhanmoral.com

Then is there something wrong with the link in the OP?

Cheers
[Galaxy S II Original Android Development] :
@omniwolf

do you gpu script and thunderbolt interfere with each other in any way or is ist safe to flash both?
[Galaxy S II Original Android Development] Igor 3:
Guys, Im using Turkbey rom that comes with Siyah kernel. When I look in init.d folder there are a lot of scripts that come with rom. Should I delete those scripts or let them live?
[Galaxy S II Original Android Development] ercxar:
New CWM Recovery is perfect! But it would be better to make it use via touch without hitting volume keys thousand times to navigate through folders.
[Galaxy S II Original Android Development] pikachu01:
Were you using your battery actively after that? That explains the spike and then the downtrend. :/
[Galaxy S II Original Android Development] legendasboy:
This kernel doesn't seem so battery friendly compared to 2.6.7 and 2.6.9

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] ercxar:
I just found you can navigate folders via touch menu button! Cool:D
[Galaxy S II Original Android Development] ole12:
Nopp.

Just after the boot up, i just saw my battery dropped from 40% to 20%.

It has happend before, like when u flash roms, but the battery stabileze after few minutes.

But battery keeps draining from 20%, havent gone upwards.
[Galaxy S II Original Android Development] pikachu01:
Are you using 2.6.11?
[Galaxy S II Original Android Development] omniwolf:
it does actually, but akin to VC, it uses the wrong settings :(

#gpu clock, threshold and voltage
#echo "160 267 300" > /sys/class/misc/gpu_clock_control/gpu_control;
#echo "70% 40% 80% 60%" > /sys/class/misc/gpu_clock_control/gpu_control;

but as there are no cheeky sleep in the thunderbolt scripts, if you flash "my" scripts on top of thunderbolt, all will be well

*ahhhhhhHHHHHHHHHHh*

(that's the sound of angel singing that all will be well)
[Galaxy S II Original Android Development] pikachu01:
Yes, but were you actively using it after that? Try a few charges/discharges. It'll return back to normal :)
[Galaxy S II Original Android Development] jermitano:
thanks mate...btw i dont set any settings on boot...can i change governor/schedules and voltages after boot (after flashing the script)? apologies as i am a little confused on what to really actually do...
[Galaxy S II Original Android Development] NoOneCanHelpMe:
On 2.6.11 for 2 days now, I rly like the new recovery :)) but I think I have kernel wakelock or the "applockLite" is waking up too many times 5300 what do you think?

================

Kernel Wakelocks

================

"svnet" (): 1 h 9 m 17 s (4157 s) Cnt:(c/wc/ec)3870/0/3871 11.3%

"alarm_rtc" (): 38 m (2280 s) Cnt:(c/wc/ec)3650/0/146 4.3%

"sec-battery-monitor" (): 30 m 9 s (1809 s) Cnt:(c/wc/ec)3655/3634/0 4.9%

"radio-interface" (): 7 m 41 s (461 s) Cnt:(c/wc/ec)496/0/0 1.3%

"alarm" (): 3 m 53 s (233 s) Cnt:(c/wc/ec)4515/0/0 0.6%

"svnet-dormancy" (): 3 m 53 s (233 s) Cnt:(c/wc/ec)180/0/180 0.4%

"deleted_wake_locks" (): 3 m 33 s (213 s) Cnt:(c/wc/ec)14391/0/597 0.4%

"PowerManagerService" (): 3 m 23 s (203 s) Cnt:(c/wc/ec)5120/0/0 0.6%

========

Alarms

=========

com.morrison.applocklite (): Wakeups: 5322

com.google.android.gsf (): Wakeups: 73

com.google.android.apps.maps (): Wakeups: 34

android (): Wakeups: 32

com.google.android.location (): Wakeups: 3

========
[Galaxy S II Original Android Development] Simba501:
Yeah, that's a lot. I'm not familiar with the app, but your solution lies in changing something within that app, or removing it.
[Galaxy S II Original Android Development] omniwolf:
after boot do what you want, just do not try and change GPU settings via VC.

if you have a perfect setup that you want to achieve PM me with it and i'll try and give you the steps to achieve it.

*aaaaaHHHHHHH PERFECT SETTTUUUPPPPP*

(IMO perfect setup is just don't touch anything, and flash AndreiLux's settings (with my ZIP))
[Galaxy S II Original Android Development] jermitano:
ahahaha...well im just taking your advise now hehehe...touch nothing after flashing script is done...thanks a lot...

btw...some buddies of mine using 2.6.11 are reporting having problems with batt drain higher than 2.6.9 when using wifi...
[Galaxy S II Original Android Development] OrangePL:
Alright, which is better - AndreiLux's settings or geko's (regarding GPU) from his thread: http://xdaforums.com/showthread.php?t=1466017?

Or maybe merged?
[Galaxy S II Original Android Development] omniwolf:
geko's uses the 2 step GPU. so.. it's not optimised at the moment.

I don't know if i'm just retarded, but i couldn't find any download link on his thread.. so i'm not sure if my script will overwrite his or his mine. sorry.

at the moment you want mine to overwrite his.
[Galaxy S II Original Android Development] CamoGeko:
Let me make this clear, I do not use any kernel scripts whatsoever. So I don't see it interfering really, potentially if you set my VC values first (make sure you leave GPU values stock) then flash omniwolf's script I think it would be a good pairing.
[Galaxy S II Original Android Development] ole12:
Does the kernel interfere with the battery?

Because i've been fully discharging/charging a couble of times now.

Using it actively?

Well, no not actively.
[Galaxy S II Original Android Development] OrangePL:
Was clear, it's in the first paragraph of your thread in massive font ;-)

Yeah, I was just wondering what's the best compromise for performance and battery life. Stock GPU voltages would theoretically mean more drain - and by using that flashable script the frequencies of the GPU are toned down a bit - which in turn could affect performance (high in particular worries me).
[Galaxy S II Original Android Development] CamoGeko:
Obviously now there is some trying and testing to be done. Otherwise its hard to say if and what combinations will work best together.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] legendasboy:
I flashed it yesterday but I should revert because my phone doesn't behaves so good with the new kernel

Had some wakelocks and my phone doesn't go to sleep like he did in 2.6.9, and my battery drains before my eyes especially when using wifi actively, like when I'm on taptalk it drains like crazy.

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] mad_max911:
Why cpu frequency keeps dropping under constant load? This happens under all governors, and ondemand seems less infected than others... ? I am not sure if this is strictly kernel related... For example i run stability test, cpu under constant load and frequency varies from 800-1400, shouldnt it be constant 1400 if i use "ondemand"?
[Galaxy S II Original Android Development] pikachu01:
Try a few battery cycles first?

You meant performance? Ondemand is what it's just it is. Ondemand performance when it needs it?
[Galaxy S II Original Android Development] Entropy512:
Fully discharging/recharging is not needed to recalibrate our fuel gauge... Just time.

You need to keep in mind - State of charge estimation is just that, and ESTIMATE. It's clear that high load after a reset (e.g. the exact load pattern of a reboot) will confuse the fuel gauge chip, and the fuel gauge seems to become more inaccurate at lower SoC levels.

Nothing the kernel can do about this - all it does is read a number from the fuel gauge hardware.

Yup. Idle states complicate a lot of the old rules of thumb.

Or figure out what's causing the wifi chip to fire interrupts.

Best to run Shark for Root to get a packet capture of traffic while the drain is happening. Head over to the I777 forums and read my "known battery drainers" reference thread in the General section, nearly all of that can apply to the I9100 - skip straight to the Shark for Root instructions.

I think GM put in the calculations to divide - I really questioned whether to put the calculations in the kernel or not. Putting them in could "break" some things, although on I9100/I777, the more I think of it - reading this was never in there in the first place so there's no backwards compatibility to break.
[Galaxy S II Original Android Development] legendasboy:
I think the phone not going to sleep like he used to has nothing to do with running a few cicles.

Had a partial wakelock called backup for 1 hour running and I really don't know what this is. And I was having problems with gmail sync since I flashed don't know why.

The good thing I discovered I was auto signing in on talk and disabled it

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] el_tute:
Hi people, I don't know anything abt scripts for cwm (neither for android, but its the same, jajaja), can anyone create a .zip file for CWM recovery that move all files in etc/init.d directory to some folder in internal SD ??

Maybe could be a good way to avoid boot loops when a script is "messing" with the new kernel.

Thanks and sorry my rusty english!!

---------- Post added at 03:03 PM ---------- Previous post was at 02:54 PM ----------

mmhhh, actually, according to cpu spy, I am on

1400mhz = 4:35

1200mhz = 3:04

1000mhz = 1:54

800mhz = 14:44

500mhz = 2:02:25

200mhz = 10:25

100mhz = 4:45:37

deepsleep = 10:05:45

so, my phone stays much more in 100 than in 200 so...it dont jump much between 100 and 200.

the phone was in charger abt 6 hours, so I presume that 500mhz and 100mhz are charging times (500 charging and 100 with the battery full but connected to charger)

I didn't test the consumption with min freq 100 vs min freq 200.
[Galaxy S II Original Android Development] stevehkim:
Gok the new att tar fixes cwm issues. just tested.
[Galaxy S II Original Android Development] mad_max911:
No, performance locks CPU clock to max... I am talking about other governors... If there is 100% CPU load, why clock varies and not beeing at max all the time.. For example, i use time lapse app and during rendering CPU load is at max and clock is not at max all the time. It varies from 800-1400 MHZ... If i use "ondemans" and there is 100% DEMAND, clock should be 1400 MHZ all the time... Ofcourse that on performance governor CPU clock will be at max even not under load, but who even use performance governor on daily basis.
[Galaxy S II Original Android Development] goldencore:
I just had a SOD with 2.6.11 and the same UV/OC settings I am using for ages. Also only SmartassV2 gives me a UI without lags. Ondemand is laggy as hell. I'm using GoLauncherEX.

Sent from my GT-I9100
[Galaxy S II Original Android Development] a1adin:
I agree, for mine: 2.6.6i and 2.6.7 drain the battery less than 2.6.11.

And also, they have far better deep sleep %.
[Galaxy S II Original Android Development] legendasboy:
At least I'm not alone, going to revert to my previous kernel, and wait for another release.

Sent from my Galaxy SII using Taptalk
[Galaxy S II Original Android Development] SupraN0va:
Use the tar file
[Galaxy S II Original Android Development] kwerdenker:
Sadly had another lock-up while charging and screen-off and forgot to run the kmsg log. Since I'll be on the road the next few days I'm reverting back to RAGEmod because I need my phone as stable as possible. As soon as I get the chance I will flash this kernel again and try do get another log for the problem.
[Galaxy S II Original Android Development] manyakurt:
hafız bunu miui'ye çakabilir miyiz ? Good job btw...
[Galaxy S II Original Android Development] dandroid13:
Working great here, no lock-ups. :)
[Galaxy S II Original Android Development] antt00:
I tried ondemandX last night with setcpu setting from 200mhz to 1200mhz with beta 3. Have disable ocdaemon and restart. No profile set in setcpu and my device did not sleep. It went from 100% to 19% battery. Can you check on this? I never had this problem using 1.3 with ondemand during screen on and conservative during screen off with ocdaemon.
[Galaxy S II Original Android Development] gokhanmoral:
Hmm I also had a lockup with ondemandx. I will check it. I had no problems with smartass and ondemand though.
[Galaxy S II Original Android Development] gokhanmoral:
No, this kernel could not be used on miui.
[Galaxy S II Original Android Development] antt00:
I think my case was also a lockup. My batt widget got no records everything was blank. But when it lockup it seem to drain the batt. No problem with ondemand.
[Galaxy S II Original Android Development] dandroid13:
Is this kernel on base 2.6.35-11?
[Galaxy S II Original Android Development] gokhanmoral:
No, not yet.

Still at 2.6.35.7 with some pathches from upstream.
[Galaxy S II Original Android Development] dandroid13:
Interesting. A guy from an italian forum made a custom ROM and his kernel runs 2.6.35-13 :eek:

Check it: http://www.androidiani.com/forum/modding-samsung-galaxy-s2/57919-rom-thunderbolt-base-2-3-4-a.html
[Galaxy S II Original Android Development] gokhanmoral:
Those minor versions include changes for other platforms as well such as x86, not only arm and other features. We are on arm and samsung has already acquired some necessary patches from new versions while keeping the version number the same. So that 2.6.35.13 doesnt mean much. Latest is 2.6.35.14 anyway.

It is a nice thing to have all the patches but it is not necessary for us now. I will stay close to samsung sources for now.
[Galaxy S II Original Android Development] dandroid13:
Oh, ok got it. Thanks mate. ;)
[Galaxy S II Original Android Development] :
That's Angelom who makes the thunderbolt kernel. Its on Batista's rom, if my memory serves me right.
[Galaxy S II Original Android Development] Zanr Zij:
Me too for the first time! Flash it again and work fine for me :)

Sent from my GT-I9100
[Galaxy S II Original Android Development] eybee1970:
hi gokhanmoral,

hi all,

I am quite sure, that smartassv2 does not stay on 100 mhz in deep sleep, but jumps up to higher frequencies rapidly!

So I set a profile on SetCPU for 'screen off' with 100 mhz up tp 200 mhz, governor 'ondemand' --> this will assure the frequency will stay on 100 mhz most of the time in deep sleep
[Galaxy S II Original Android Development] gokhanmoral:
you are right. it doesn't stay at 100MHz. all the time.

100MHz is the desired suspend freq. which means that the governor will scale down to that freq very rapidly and steps up slowly (by staying for some time on every frequency before stepping up again) and if there is still a demand it can scale upto the max freq.

we are aiming to save battery by keeping the freq low but if there is something which uses the cpu, keeping it at 200mhz won't help. you have to find out the reason why the cpu is being used and fix it.

then why not we use this behaviour while screen is on?

because it causes lag in the UI.
[Galaxy S II Original Android Development] eybee1970:
i just set ondemand for screen off - when phone is awake smartass is my preferred governor. I do not have any procesesse or wakelocks, so I presume that smartass is rating up to much in deep sleep, regardless of any running processes ;)
[Galaxy S II Original Android Development] gokhanmoral:
hmm, you may be right again :)

maybe I should revert all the responsiveness tweaks in smartassV2. after all it is aimed for battery saving.

of course there is nothing wrong using screen-off setcpu profiles. if you have deep sleep it would not be problem anyway...
[Galaxy S II Original Android Development] gokhanmoral:
I have uploaded v1.5rc3 and I guess that will be the last release candidate.

I have made ondemand governor default @200-1200MHz (stock). having stock settings as default and others as optional will make everyone happy I think.

I also disabled some kernel debugging features. I hope those won't cause app protectors not to work again. android logger is still enabled by default.

I still use smartassV2 without any screen profiles and if I don't use any undervolting I have no problem at all.

other than SLQB (which is also used in lots of other kernels w/o any problems) all settings and voltages are default when you install this kernel.

please make sure you disable undervolting scripts or settings before you report any problems.

EDIT: I forgot to tell you that I am still working on ondemandx governor. if I cannot fix it I will remove it before I relase the kernel. so please don't use it for now.
[Galaxy S II Original Android Development] chadouming:
There should be no problem.
[Galaxy S II Original Android Development] lpsi2000:
I change ROM often for testing but I always have backup

Exactly

LOL
[Galaxy S II Original Android Development] paranoid2007:
Just had a spontaneous reboot using market with beta 4. I'm on OndemandX no UV.
[Galaxy S II Original Android Development] jsompis:
Tried , but still no deep sleep.:(
[Galaxy S II Original Android Development] lpsi2000:
1.7.8 Beta4

It seems as beta 4 drains battery much more than 1.7.4. I was running for few hours and it seems to drain more than 1.7.4. I am using the same setcpu values for both versions oc to 1.6ghz

I just switched back to 1.7.4 to see...
[Galaxy S II Original Android Development] jmblazquezh:
Hello.

I have 1.7.7 kernel installed. I had superuser.apk 3.0 from kernel version 1.7.6 but I´ve installed criskelo rom v22 and I lost version 3.0 of superuser.apk. Now I have version 2.3.6.1 of superuser.apk. How I can retrive version 3.0 of superuser.apk?

Regars
[Galaxy S II Original Android Development] lupu87:
For automatic battery calibration must I connect to a charger when it is discharged, or indifferent? Thanks.

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] chadouming:
Do you really need SU 3.0 ? 2.3.6.1 does the job and has less trouble.

Only need let it plugged to a charger until it's 100% + 15 mins and you will be alright
[Galaxy S II Original Android Development] inferno17x:
I have installed version 1.7.8beta4 the Android OS is running at 60% sometimes 55%.

Is this normal?
[Galaxy S II Original Android Development] AndreiLux:
Reflashed beta4 and it wouldn't go to sleep again. Did the same wipe of cache & dalvik and it fixed it. Seems to be something reproducable.

Edit: Ooookeeeey. I rebooted the phone and now it doesn't want to sleep again.

beta4 gets my official stamp of disapproval. Get back to work on that one gokhan :D

Things I've been able to reproduce: beta1 doesn't have the typical Android OS bug behaviour, events/0 and suspend are not tied together. Also, it doesn't trigger at all or very seldom. beta4 on the other hand shows the typical huge drain and suspend and events/0 hog the CPU directly after flashing the kernel. The thing is, I only managed to get beta4 to sleep twice and after that it doesn't want to sleep again.
[Galaxy S II Original Android Development] xgeneralex:
+1
[Galaxy S II Original Android Development] BuHaneenHHHH:
does this kernel work on GB 2.3.3? or is it just for 2.3.4 and 2.3.5?

i do not know if this question is answered or not

but i just want to know because i want to try it and since the offical arabic roms are still at 2.3.3

thank you
[Galaxy S II Original Android Development] jsompis:
Yes, i agree with you.

I still facing no deep sleep issue on beta4, now i back to 1.7.7 and got deep sleep again.