yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] alcurtis93:
Has anyone noticed pikachus settings for lulzactive on idle with voltage control open likes to jump up and down between 200 and 1200mhz
[Galaxy S II Original Android Development] brack11:
Read a few posts above, I always had lulzactive governor set on boot. It's just app cannot save it's settings. By the way, it doesn't ask for root rights.

Sent from my GT-I9100
[Galaxy S II Original Android Development] omniwolf:
nope. using lulzactive and pika's settings and mine pretty much sits on 200MHz. it does jump up to 1200 and 1000 and 800 and 500 ever few seconds for maybe 20 seconds after opening the antutu cpu master app (it's what i'm using to look at what freq i'm at), but after that it's solid 200MHz. the cpu master app has ads too.
[Galaxy S II Original Android Development] KcDaRookie:
@brack11: but you know that you have to press menu button and choose "save as boot settings"?
[Galaxy S II Original Android Development] omniwolf:
not true. lulzactive saves it's settings fine for me (without requiring root), it's just that SetCPU doesn't do a proper job (or something?) of setting the governor at boot up. If you use Anutu CPU Master (even the free one, the pay one allows for profiles which we don't need) or Voltage Control it appears to work fine.

Gok: might be something worth putting on the first or second post.. unless you can find out why this happens :)
[Galaxy S II Original Android Development] ka2uki:
I have find the problem what's crash the touch wiz and get the FC. it's the GPU MAX clock. xan' voltage control app max GPU only can set to 400MHz.but 2.6.2 max GPU clock is 300MHz?，so if you set max GPU clock by voltage control to 400MHz not 300MHz.will crash the touch wiz when you edited the app to move.max to 267MHz is ok.will not cause the problem.hope can fix it..
[Galaxy S II Original Android Development] cooldfuzion:
In the lulzactive app doesnt have that option!
[Galaxy S II Original Android Development] :
it does...the first thing at the top it states to save on boot:D
[Galaxy S II Original Android Development] TecQuality:
me too!! i've the same troubles.

(KK5 w/2.6.2)
[Galaxy S II Original Android Development] cooldfuzion:
yes it as but doesnt works, when i reboot the settings are lots.
[Galaxy S II Original Android Development] TecQuality:
exactly, however i use nofrills and voltage control (extreme) and i settled correctly the lulzactive w/sio scheduler, but the lulz.apk doesn't works properly ....
[Galaxy S II Original Android Development] :
buddy it does work. i just done the settings from Pikachu then ticked the set on boot option. also done my setting on VC and again saved on boot. i even flashed the battery script from Gokhanmoral site....reboot...you have to leave it for a few minutes after reboot to check if your settings have been saved...do not know what else to say really:o

---------- Post added at 11:42 AM ---------- Previous post was at 11:40 AM ----------

why are you using nofrills when Voltage Control does the same thing? just curious that is all. and yes in voltage control you have to set governor as lulzactive first before downloading the lulz.apk...i can only go by what my settings are and i can say it works my friend
[Galaxy S II Original Android Development] gokhanmoral:
I can do that but it will report the time spent in the internal state and I don't know how to re-read the gpu frequency from the gpu itself.

the original threshold values are "85% 65% 100% 98%" which means that the third step will never be used or maybe it will be used rarely on very high load because utilization is UInt32 and it may be bigger than 255. I tried original values and they are also fine for my usage.
[Galaxy S II Original Android Development] brack11:
You talking about voltage control, right? I'm using setcpu at the moment, but will try to return to voltage control.

Voltage Control does.

Sent from my GT-I9100
[Galaxy S II Original Android Development] brack11:
I also used that combo, because my governor settings were reset on every second reboot.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
use voltage control. i have not used Setcpu in ages...and on every reboot it works for me my friend....have you got any other scripts in place?
[Galaxy S II Original Android Development] cheewaca:
2 minor bugs. Volatage control apply gpu voltage but does not save them on boot all other settings are applied without problems and lulzactive app does not save settings on boot.
[Galaxy S II Original Android Development] :
i must be the only lucky one it works for then...do you guys go straight into the lulzactive app after the phone reboots to see if the settings have been saved?:confused:
[Galaxy S II Original Android Development] brack11:
OK, will try that, I used to have that combo forever, voltage control got two or three updates since.

About lulzactive app issue, it is solved upon removal of setcpu.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
That would make two of us, all the settings are getting saved as applied both on vc as well as lulz app
[Galaxy S II Original Android Development] cheewaca:
I apply them and save on boot but on reboot all settings are default settings. I tried it many times with the same result.
[Galaxy S II Original Android Development] rodries:
As I've said in my previous post

http://xdaforums.com/showpost.php?p=20770016&postcount=14830

If you try to set a lulzactive param the script freezes, so you can't use scripts to set lulzactive params. You have to remove lulz params from script and use lulz apk from market and set on boot.

Maybe gokhan can fix it in next version.
[Galaxy S II Original Android Development] :
when i first used VC i use to go straight into the app after reboot to see if my settings were saved. it never did because for some reason it needs few minutes for all the configurations to be set up by Superuser i think or whatever i do not know. Anyway someone told me once wait for the phone to reboot properly let all the scans to go through (media scanner and sdcard) then go into VC and see if the settings have been saved. and funnily enough it has...That is why i am asking you guys...Do you go straight into the app after reboot or do you wait? Same goes for the lulz.apk
[Galaxy S II Original Android Development] koolshubh:
Which is the most stable version of Siyah Kernal???
[Galaxy S II Original Android Development] Mutalisk:
That's right, but it's possible to set another bootscript setting the lulzactive params, that way it worked for me (only that way!) ;)
[Galaxy S II Original Android Development] rodries:
No, the script will freeze in first param, tested using adb shell
[Galaxy S II Original Android Development] gokhanmoral:
I fixed that freeze already and I will fix couple of things more before I publish v2.6.3

I will also change battery script and make lulzactive as it's default + provide an example of setting lulzactive params.
[Galaxy S II Original Android Development] ivangs1:
I have flashed "“siyah-battery.zip“ from SiyahKernel v2.6_S99 but it looks like not all parameters are applied - especial about GPU thresholds.

Any idea how to fix this?

Using adb shell?

Thank you @gokhanmoral :)
[Galaxy S II Original Android Development] Mutalisk:
I set the params in my 01Siyah - had to restore a nandroid, didn't boot. But as an independent bootscript it works for me ;)

The shell might freeze, you are right ;)

You are awesome! Thanks alot! :)
[Galaxy S II Original Android Development] gokhanmoral:
01siyah is the first script that is executed.

if the values are not applied then there is another script which overwrites the values.

check all scripts in /system/etc/init.d and remove the ones you don't want.

c:\> adb shell
~ # ls /system/etc/init.d
01siyah
~ #

if you see anything other than 01siyah then use "cat /system/etc/init.d/blablah.sh" to see its contents

then remove it by using "rm /system/etc/init.d/blahblah.sh" where blahblah is the name of the script
[Galaxy S II Original Android Development] ivangs1:
Thank you again.:)
[Galaxy S II Original Android Development] runedrune:
The latest. V2.6.2.
[Galaxy S II Original Android Development] Heimiko:
i've been searching this looooog thread to no avail:

would this kernel enable MHL on a AOSP rom? (ie cyanogenmod)

I'm thinking "no"... but.... asking anyways....

*hides and ducks in preparation of any flames*

thanks!
[Galaxy S II Original Android Development] mavixda:
+1 same here
[Galaxy S II Original Android Development] fracmo2000:
I cant seem to find the script which you flash in cwm before flashing a few kernel (Something like it wipes stuff being held by the previous kernel). I was to do this as well as the built in controls in cwm.

Any ideas? Something like Samsung wipe script.

Thanks
[Galaxy S II Original Android Development] runedrune:
Nope. :p
[Galaxy S II Original Android Development] Heimiko:
thought so, thanks
[Galaxy S II Original Android Development] runedrune:
www.xdaforums.com/showthread.php?t=1363738
[Galaxy S II Original Android Development] brack11:
Where can I download 2.6.3?

Sent from my GT-I9100
[Galaxy S II Original Android Development] gh.rohit:
Its not released yet
[Galaxy S II Original Android Development] hirokoboi:
Anyone facing the same thing as me?

While making a voice call, the gps icon will be flashing on the notification screen and once the voice call ends, the gps icon goes away?

Noticed this after flashing to 2.6.2.
[Galaxy S II Original Android Development] gokhanmoral:
it is related with your rom or the apps installed.

if something accesses the gps and gps is enabled that icon flashes.

it seems that you have an app which tries to find your location each time you make a voice call. maybe latitude?
[Galaxy S II Original Android Development] gokhanmoral:
I think I will switch internal & external sd locations to be able to access internal sdcard from clockworkmod recovery (as in old versions)

so, be prepared. if you cannot find your files in "internal sd" then use the other menu item.
[Galaxy S II Original Android Development] mavixda:
People with "save settings" Problem

1 - if you use "set cpu". delete this

2 - Install "Voltage Control" app from market

3 - Install "lulzactive "app from market

4 - go first to "Voltage Control" to hit the menu button (see screen shot) choose "save as boot settings"

4- And then go to "lulzactive" app and tap set on boot (see screenshot)

5 - Now you can reboot your sgs2

then see that all the setting is saved. :)

This explanation helped me
[Galaxy S II Original Android Development] cooldfuzion:
Worked like a charm :) thanks mate!
[Galaxy S II Original Android Development] mavixda:
you are welcome :)
[Galaxy S II Original Android Development] brack11:
I gave up for now, returned to 2.6, had very good battery with that, 7+ hours of screen time, but with 2.6.2 I only get freezes every now and then, even with default settings of lulzactive.

Sent from my GT-I9100
[Galaxy S II Original Android Development] pikachu01:
Are you OCing/UVing?
[Galaxy S II Original Android Development] gh.rohit:
I did uc,uv....but no freeze problem.

Also i am usimg your thunderbolt 2.2.0 script.
[Galaxy S II Original Android Development] hirokoboi:
Found the culprit that caused the problem. Thanks for the fast and kind response. :)
[Galaxy S II Original Android Development] pikachu01:
Yeah, the problem is OCing/UVing when the phone can't support it. Using the ThunderBolt!'s aggressive CFS setting will hasten the effect of hangs/reboots if you are OCing/UVing too aggressively.
[Galaxy S II Original Android Development] gh.rohit:
Man !! I am saying, i am NOT facing freeze problem wd uc,uv. :-p
[Galaxy S II Original Android Development] pikachu01:
I was referring to the other guy :P
[Galaxy S II Original Android Development] gh.rohit:
Lol,i got that..... :-D
[Galaxy S II Original Android Development] desean:
thanks for your suggestion. i did this after your suggestion.

1) removed those "chmod 444 xxx" and added "sleep 20" = did not work

2) change it to "sleep 40" instead thinking i might need a longer delay = did not work

3) change my governer to smartassV2, and comment out the lulz settings = the other setting sticks now

for some unknown reason, the lulz settings can only be set via the app and not the script. using script will cause issues for me :(

reverting back to smartassV2 for now. anyway, smartass is very responsive for me and i have been a fan of it since my HTC Hero days. was trying lulz as i read alot of good stuff about it.

anyway, saw gok posting about releasing 2.6.3 that contains fix relating to lulz. perhaps this might be related. might try again later.
[Galaxy S II Original Android Development] aegeuss:
I want a clean phone :))

Guys, I hope someone helps me.

Now that I have installed nearly all Siyah kernels and applied scripts, and am now using lulzactive kernel with it's own tweak utility. I have realised that the phone started to act weird :)

In my system/etc/init.f folder I have s91voltctrl, 01siyah, 02modules, 05module, 90ram tweaks, 98mounts, 99complete and s95zipalign files.

What I want is now to have the ability to get rid of all modifications I have applied via voltage control and scripts etc. and to use a pure siyah kernel from scratch with only default values.

So what would you recommend me?

Regards.
[Galaxy S II Original Android Development] xuxuzao:
i was using ondemandx + vr on 2.6.1

now iam using pikachu's settings + vr on 2.6.2

bouth configs are is very smooth and fast..

but 2.6.1 was more battery friendly
[Galaxy S II Original Android Development] xavihernandez:
@pikachu01

First thank for your answer.

I'm using default battery friendly governor: ondemandx. I/O scheduler is sio.

I haven't tried another player I'm glad with stock cm7 player, but those freezes.

How to rescan mp3 files? I used to do it with powerAmp but my trial has expired.

Thanks for help peeps.
[Galaxy S II Original Android Development] droidphile:
@desean, yeah i spoke too soon! Lulzactive tweaks seem to stick only with lulz app on 2.6.2.

Bug with script-set-lulz-tweaks will hopefully be fixed in 2.6.3.

If Gokhan wasn't this committed, our GS2 experience would never be this good. No way..
[Galaxy S II Original Android Development] Vaedryn:
7+ hours screen on ? Sorry ,never.

SGS II Tapatalk
[Galaxy S II Original Android Development] sgsgs:
On 2.6.2 and managed to get pikachu settings to work on boot.

After trying various combinations with VC, setcpu and lulzactive app, my findings is that VC + lulzactive app combination works perfectly.

Problem with setcpu + lulzactive app is you can't really control which app runs first after boot. If lulzactive app runs before setcpu app sets the governor, the settings won't take effect.

VC sets the governor in init.d script which probably runs before lulzactive app setting kicks in.

Just remember to activate "Save as boot settings" in VC and enable "Set on boot" in lulzactive app after configuring your settings.

Btw, echoing lulzactive settings in siyah script doesn't work in 2.6.2 and gokhan already fixed it in the yet-to-release 2.6.3
[Galaxy S II Original Android Development] ka2uki:
i must say~ New mali drivers from Galaxy Tab Plus really cause the problem with i9100 when use touch wiz lunch~hope can go back the drivers the same to 2.6.1..in 2.6.2 the max GPU clock only can set to 267mhz..if you set higher than it ,like 300 or 400.. will cause the touch wiz problem--(the problem is edit the apps in "applications" ,like move one app to next side page..the touch wiz must be freeze and got FC!! you can do only reboot your phone~)
[Galaxy S II Original Android Development] grey77:
Its achievable with black backgrounds; e.g. I use such custom .CSS for Opera Mobile.

We have AMOLED in SGS2, that means that white/light text on black background consumes like 3+ times less power compared to traditional black text on white/light background approach.
[Galaxy S II Original Android Development] brack11:
I do uv very heavy actually, but it works smooth and stable on 2.6. Well, I guess that is the reason.

Sent from my GT-I9100
[Galaxy S II Original Android Development] cmd512:
That's because 10000 up sample time is way too fast. Set it to 20000+ and you won't see it jump as much.

Personally, I'm not a fan of pikachu's settings precisely because the phone is constantly jumping out of 200MHz min. I prefer a 75% with 2 pump up step and up sample time of 20000 and down sample time of 40000.

Just my own preferences I guess.
[Galaxy S II Original Android Development] brack11:
Don't believe me? OK have to repost my screens. And I still worked about 15-20m after taking screens. There was about 5hours of WiFi browsing in that time.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Lownita:
What impact on scrolling lags would the performance script have when using lulzactive? I tweaked it with lulzactive app and I could nearly get rid of them. But now I am struggling to flash the performance script, since I think that 99.9% of scrolling lag issues are governor/scheduler related.
[Galaxy S II Original Android Development] plop974:
Soo good

Siyah is soo popular.

Happy #15000 post !

Happy new year !

Thanks for the Kernel

Lost 20% in 1 day not using the phone.

So far soooo good in my opinion. :) :cool:
[Galaxy S II Original Android Development] brack11:
Do you mean in browser? I didn't tweak anything there, I used black android theme but that's all. Regular dolphin browser. But I achieved this result only after three days without flashing. I also never calibrated battery and never discharged till shutdown.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
i have been saying the same thing over and over the last day or so. Lulzactive app and Voltage Control works perfectly. Using Pikachu's settings for lulzactive.apk and using my own settings for voltages frequencies on VC. Save both on boot and reboot. What is so hard with that. Wait for a few minutes for the phone to settle and that is it. If you are trying though to use scripts instead the lulzactive app then that is different...

But as far as i know im getting good battery life and performance with the two and could not be happier...Regarding bus frequencies that is a whole different level for me i just leave them stock as i would not have a clue what to do.

But lulzactive app and voltage control great combo and i think i found a new fave governor
[Galaxy S II Original Android Development] pikachu01:
Yeah, your problem is associated with heavy UVing and/or Ocing

Yup. The aggressive CFS settings increases the likelihood of instability. These instability would show itself again when your device gets hotter even without the CFS settings. Try playing a RMVB file using MX Player/ Rock Player using software decoding. I can guarantee that you can't exceed 10 minutes of playtime without hanging (even with v2.6).
[Galaxy S II Original Android Development] grey77:
heh. I used to 200000 sampling rate with 50...1000 ondemand on my daily usage and cant see any perceivable loss in smoothness.

---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------

sorry, u quoted wrong. not mine.
[Galaxy S II Original Android Development] brack11:
Ok, must admit I never tried this, only tried 3d games, and it was stable. Sims3, roc, asphalt 5, are favorites of my kids, not talking about talking tom, santa, and others.

Sent from my GT-I9100
[Galaxy S II Original Android Development] pikachu01:
Yeah, games are stable for me as well with aggressive UV. The problem is that, games can only take you so far. RMVB decoding takes a big chunk of your system resources (even in the PC).

Also, to solve all the issues regarding scripts and tunes, here's ThunderBolt!:

News

Updated ThunderBolt! to v2.3.0 with some minor fixes to sdcard arrangement, governor tweaks as well as support for SGSII tunables. Screenstate_scaling is given a major addition of governor tuning for lulzactive and smartassV2. Also added i9100 restore pack. These CWM zips are using the latest updater_binary that is compatible with CWM5.5. All the other older CWM zips aren't updated to that updater_binary yet. If you need the updater_binary, I've uploaded it. Just replace it in META_INF/com/google/android.

Changelog:

12/30/2011 (2.3.0, screenstate_scaling 1.4.0)

- Updated 2.3.0 with minor editiing of sdcard tweak arrangement, smartassV2 and lulzactive governor tweaking, and SGSII tunables (hotplugging, bus frequencies etc).

- Added i9100 restore pack

- Used newest updater_binary. All the older CWM zips are not using the newer binary. Just update it with the file I've uploaded in the 2nd post.

Not necessary to install lulzactive app. Only need Voltage Control to set the governor/frequency of choice and let ThunderBolt! manage it.

The screenstate_scaling particularly will boost battery life as lulzactive/smartassV2 is tweaked so that they are less battery draining while screen is off.
[Galaxy S II Original Android Development] :
Pika im currently using your settings with lulzactive app. Are the new scripts going to be included in the new kernel by Gokhan? And if i was to flash the new script now does that mess anything with my current settings? Thanks bro in advance
[Galaxy S II Original Android Development] pikachu01:
I'm not sure. It will override Gokhan's scripts (older ThunderBolt!).
[Galaxy S II Original Android Development] ka2uki:
@ gok，back to 2.6.1 use voltage control app set the min GPU clock to 267MHz 950mv max GPU clock to 400MHz 1100mv. touch wiz luncher problem was gone.so I can consider the reason is the new mali drivers in 2.6.2，and when play gameloft MC3，the same voltage control setting.2.6.2 feel lag.and 2.6.1is smooth.so i think back to the 2.6.1GPU mali drivers is the best choose.maybe the new sourse is not mean the best.

来自我的GT-I9100 使用XDA高级版 发送
[Galaxy S II Original Android Development] stevehkim:
pika can u pm me on how exactly i need to update your scripts? also im using v6 supercharger scripts. will they bump heads?

miui+siyah = beast
[Galaxy S II Original Android Development] jlevy73:
No problems on MC3 and 2.6.2, using Lulz governor @ 1400/200
[Galaxy S II Original Android Development] kobi63:
Can someone help me? HOW DO I GET RID OF THE ****ING GTALK_CONN partial wakeclock??? GTALK is frozen and uninstalled so why am I still seeing it??
[Galaxy S II Original Android Development] :
why dont you just unistall it using Titanium backup and then reboot your phone. that should get rid of it completely...simple as that and your GTalk will be gone...and another thing...Manners do help and cost nothing...so next time you post something be nice or get ready to be either ignored or just flamed at due to the stupidity of the way you wrote your post
[Galaxy S II Original Android Development] gabx:
Kernel 3

Did you start to build a Kernel 3 ? I am very eager to test it with ICS !!!

Btw, is there any way to test if ICS boot with your Kernel? On some other devices, you can $ fastboot boot zImage, but impossible with SGS2. Shall I try to flash it via Odin, and see what happens? I think it will not work.
[Galaxy S II Original Android Development] chadouming:
1st He cant make a kernel without the sources. Or it will miss some feature.

2nd It wont work on ICS. I knew it but i still tried it and it didnt work.
[Galaxy S II Original Android Development] Hertz33:
The One Kernel to Rule them All

Is it just me or is those *.*.2 versions work the best?

I mean the 2.4.2, 2.5.2 and now 2.6.2 rock stable and batt friendly.

Other ones not so much. Anyways more then happy to test any version that comes out. This is the best kernel for me bar none.

I've tried the rest and allways come back to the BEST.

Keep it up Gokhan and Happy New Year.
[Galaxy S II Original Android Development] AndreiLux:
I do not have any such issues and the new drivers work just fine, I think your lags are governor or other settings related.

That's interesting, more info?