yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] rhai:
Hi Guys! I need help.

I am searching the forums and google for a fix and I am trying to debug my script. but I see that my script does not run properly. I would like to seek your opinions on what I'm doing wrong.

Currently here is my script.

#!/system/bin/sh
#CPU Frequencies
AWAKE_MIN="100000"
AWAKE_MAX="1200000"
AWAKE_GOV="lulzactive"
SLEEP_MIN="100000"
SLEEP_MAX="500000"
SLEEP_GOV="conservative"

#CPU Frequency
FREQ_STEP_1="1600"
FREQ_STEP_2="1400"
FREQ_STEP_3="1200"
FREQ_STEP_4="1000"
FREQ_STEP_5="800"
FREQ_STEP_6="500"
FREQ_STEP_7="200"
FREQ_STEP_8="100"

#Setting CPU Frequencies
echo $FREQ_STEP_1" "$FREQ_STEP_2" "$FREQ_STEP_3" "$FREQ_STEP_4" "$FREQ_STEP_5" "$FREQ_STEP_6" "$FREQ_STEP_7" "$FREQ_STEP_8 > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo $AWAKE_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $AWAKE_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#Setting Governor
echo $AWAKE_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#Starting Profile
while [ 1 -eq 1 ] ; do
AWAKE=$(cat /sys/power/wait_for_fb_wake)
if [ "$AWAKE" = "awake" ]; then
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "1" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
echo $AWAKE_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $AWAKE_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo $AWAKE_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
fi
SLEEPING=$(cat /sys/power/wait_for_fb_sleep)
if [ "$SLEEPING" = "sleeping" ]; then
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "0" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
echo $SLEEP_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $SLEEP_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo $SLEEP_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
fi
done

I am constantly checking the value of this in ADB

/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

but it seemds that it does not change. it always stays on ondemand.

Here are my scripts on init.d

C:\Users\rhai>adb shell
~ # su
su
# ls -l /system/etc/init.d
ls -l /system/etc/init.d
-rwxrwxrwx 1 root root 1410 Aug 1 2008 S70zipalign
-rwxrwxrwx 1 root root 1965 Jan 8 05:02 S95CpuManage
-rwxrwxrwx 1 root root 1354 Nov 2 23:58 S96CPUV
-rwxrwxrwx 1 root root 1601 Nov 1 19:10 S97GPUV
-rwxrwxrwx 1 root root 782 Aug 1 2008 S97ramscript
-rwxrwxrwx 1 root root 3098 Aug 1 2008 S98tweaks
-rwxrwxrwx 1 root root 5132 Aug 1 2008 loopysmoothnesstweak
#

I am executing the other scripts successfully but not my script above. The filename of the script that i'm having issues is S95CpuManage

hoping for an answer. thanks much!
[Galaxy S II Original Android Development] shawnaye:
hey guys, is there like a nice list of scripts to try? (excluding those in OP)

i'm still not exactly sure how to enable the scripts just by placing them in the init.d folder, i downloaded script manager and executed the scripts placed with Superuser and Boot.
[Galaxy S II Original Android Development] tolis626:
Try putting "sleep 30" like I did in the script you posted(with red lettering).Maybe it solves the problem.Some apps/other stuff change your governor on boot."Sleep 30" will delay the script's execution for 30 seconds.That way,it executes after media scanning completes.Should work.

If you don't know what each script does,don't use them.You might want to read droidphile's sticky thread in general section.It's a really worth read.If you understand what every parameter is,then start messing with those.Else,you are challenging your luck and will,most probably,face problems.
[Galaxy S II Original Android Development] ziroxs:
S96CPU UV. Please post the content of the script here. I assume that there are used some variables from your script as well.
[Galaxy S II Original Android Development] incubus_fr:
Nothing...
[Galaxy S II Original Android Development] ercxar:
...else matters with having this awesome kernel?:p
[Galaxy S II Original Android Development] jaher:
Oh by the way darky rom tool mot there on market anymore.

Ps. If i use set cpu with this kernel would it be ok
[Galaxy S II Original Android Development] veyka:
Set CPU works, but voltage control is recommended, and free, see market.
[Galaxy S II Original Android Development] incubus_fr:
You got it ;-)
[Galaxy S II Original Android Development] poochewer:
I couldnt agree more! It works well,and quite snappy too.

I use cognition rom and launcher7, using sio/ondemandx with 100-1400MHz

stock voltages.
[Galaxy S II Original Android Development] sahidmiah:
I think 2.6.5
[Galaxy S II Original Android Development] gokhanmoral:
v2.6.6 is up. ( http://www.gokhanmoral.com/ )

I will also upload it to the first post.

all previous versions are deleted.
[Galaxy S II Original Android Development] jaher:
Voltage control ?
[Galaxy S II Original Android Development] veyka:
https://market.android.com/details?...xLDEsImNvbS5kYXJla3hhbi52b2x0YWdlY29udHJvbCJd
[Galaxy S II Original Android Development] lpsi2000:
Exactly, I said it many times. With all of these options I don't see how any other kernel could be better for my needs.
[Galaxy S II Original Android Development] DocRambone:
Bug report: no boot with v2.6.6 and CM7.2
[Galaxy S II Original Android Development] Vaedryn:
CM7 and 2.6.6 boot fine here, no problem for me.

Feels very smooth. Thank you again Gokhan.

Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
I did not change anything related with cm7. if you flashed CWM version that happens sometimes.

if so, I recommend you to flash CM7 again and then flash tar.
[Galaxy S II Original Android Development] DocRambone:
I tried both, tar and by cwm, still no boot. Previous versions ok tho
[Galaxy S II Original Android Development] cmangalos:
2.6.5 is awesome with regards to battery and performance. Yesterday by 7pm i got 88% of battery starting from 100% at 8am, with 4hours of music using beats head set couple of sms, data connection and ow i forgot to turn off wifi. But, now 2.6.6 is out im wondering if i apply it. Maybe later. Still enjoying 2.6.5
[Galaxy S II Original Android Development] fleau77:
Same for me: No Boot with tar, rom --VK-- 3.2 KL1. Previously i was with Siyah 2.6.5 wich worked fine.
[Galaxy S II Original Android Development] cooldfuzion:
WOW this new version is incredible smooth, and responsive! Thanks mate
[Galaxy S II Original Android Development] antt00:
2.6.6 boots fine with turkbey Rom. Did you guys download the correct version? I9100 international.
[Galaxy S II Original Android Development] biopc:
Hi. Ive been following your kernel for a time and i appreciate your work. Just installed 2.6.6 on miui but with most of governors frequencies stay hanging on my max (1200mhz). I did a properly clean install but problem remains. I hope it can be fixed since 2.6.5 was running here like no other.
[Galaxy S II Original Android Development] :
booted up the 2.6.6 and works like a charm..only problem is regarding voltage control and cpu clock frequencies going back to stock..im overclocking and when i save on boot and reboot after the phone loads up the frequencies revert..using no frills and everything is working fine...but how can i undervolt though?
[Galaxy S II Original Android Development] lpsi2000:
+1 on that feeling. I am still trying to find a reason to leave 2.6.5 and update to 2.6.6.
[Galaxy S II Original Android Development] fleau77:
Yes I9100 international as usual
[Galaxy S II Original Android Development] Vaedryn:
For all who have boot problems, take a look you have download the right version.

Use kernel clear script.

I am on CM7 , all works fine, lulzactive is very very smooth , all in all 2.6.6 is fine.

Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] :
any of you lovely gents have any problems with voltage control if you are overclocking or underclocking?
[Galaxy S II Original Android Development] gokhanmoral:
do you save as boot settings in voltage control app? I've just overclocked my phone and saved it as boot settings and it did not revert back to stock after reboot.

if you check the frequency just after you reboot you may see that it reverts back to stock.

but if you check it after a minute you'll see that it will be set back to your saved frequency.

I modified init.d script execution part a little so that the upper freq level is re-applied after 30 seconds to override the overriden settings :)
[Galaxy S II Original Android Development] :
Hey Gokhan yes my friend i tried all that and i wait for the phone to load up before i go into Voltage Control....The thing is not that it is rom related i think its the build or whatever you call it..KL1 i have this problem with voltage control..But when i was using 2.6.3 on KK5 and when i reverted yesterday back to KK5 just to test 2.6.4 and 5 worked fine
[Galaxy S II Original Android Development] gokhanmoral:
I see.. then I should play the permission card maybe...

that only happens in samsung rom's and some process sets the freq back to stock.

I will modify the init.d script execution a little more and change the permission of the file after re-applying the frequency. but this will be in the next version.
[Galaxy S II Original Android Development] :
Thank you much appreciated....Stupid question..Can i use setcpu to alter voltages like to undervolt and use no frills to overclock? or will one clash with the other? thanks again for your replies:)
[Galaxy S II Original Android Development] ka2uki:
2.6.6 is breezing fast .use voltage control and lulzactive app.up to 1.6ghz ..runing games super smooth..thanks again @gok!
[Galaxy S II Original Android Development] :
What rom are you using my friend?
[Galaxy S II Original Android Development] lutanica:
Bro.. I'm on CM7.2 KANG as well and there is no booting problem. You have to remember that you have got to wipe cache and dalvik once before and once after you flash the kernel.

And always do the flash twice...
[Galaxy S II Original Android Development] gokhanmoral:
you can use setcpu, voltage control and nofrills all at the same time.

voltage control settings will be applied first.

then setcpu or nofrills (I am not sure which one will be the first)

you can set everything with voltage control app and then overclock (only frequency) with setcpu.
[Galaxy S II Original Android Development] ka2uki:
using stock samsung ZSKI3(HK) 2.3.5 rom.my phone region haven't update to the 2.3.6,maybe will be jumping into ICS 4.0 in Feb？:D..
[Galaxy S II Original Android Development] :
Thank you for clarifying that for me...you are the Boss after all:) Many thanks...Just wished i could of used just Voltage Control as that is the best in my eyes...But i shall use No -Frills for now and see how the battery goes with out undervolting....It is running soo smooth do not want to touch anything else and mess it up..Thank you Gokhan for your replies much appreciated.:)
[Galaxy S II Original Android Development] V1TRU:
2.6.6 revitalized my s2. Much faster than all previous versions. Miui 1.12.31
[Galaxy S II Original Android Development] stevehkim:
oh man oh man, 2.6.6 is freakin amazing boss!!! Thank you gokhan! I feel another donation coming for you boss hog!!
[Galaxy S II Original Android Development] ajvulcan:
Lulzactive seems in siyah v2.6.6 that is stock in one frequency and doesn't change to others even changing the governor parameters.

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] VFO:
I just checked CPU spy and I am utilizing all frequencies and not sticking on only one. Maybe you had a bad install. I would try r flashing and see if that helps.

I am using lulzactive with VR and it seems to be a work of art so far. Amazing work gokhan!
[Galaxy S II Original Android Development] chiggah:
what should lulzactive frequency be in 2.6.6 ?

mine is SIO lulzactive minimum 200 mhz and max 1200 mhz
[Galaxy S II Original Android Development] ajvulcan:
I'll try to wipe everything and do a clean flash. For now I'm using a tweaked conservative governor and runs well. Thanks!

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] chrisjcks:
hi,

I know nothing of governors other than stock on-demand.

I see alot of people using lulzactive, is this considered the fastest & smoothest amongst our xda comminity?
[Galaxy S II Original Android Development] droidphile:
Lulzactive is a 'wild' governor. Many people love it because it's like a tiger. Tame it properly and you'll love it. With wrong tweaks, you will hate it.

More info here.
[Galaxy S II Original Android Development] chrisjcks:
Hey thx for that, however...

As I'm new to this kernel, I certainly don't want to mess with scripts, so is lulzactive smoother & faster than default on demand? :)

- I'd prefer smoothness & speed over battery as the SGS2 battery is fine for my daily usage as i charge overnight.
[Galaxy S II Original Android Development] d8389:
I hate lulzactive because it takes very long time to switch screen on on incoming call.
[Galaxy S II Original Android Development] hutame:
thanks for all... hope continue...
[Galaxy S II Original Android Development] Simba501:
There's a sticky explaining all of them in general I believe....there's also a link in my signature.

Sent from my Galaxy SII
[Galaxy S II Original Android Development] stevehkim:
2.6.6 is blazingly fast and smooth. but deep sleep isnt as frequent and as long. were the deepsleep parameters changed gokhan? hows everyone elses deep sleep? does thunderbolt play nice with 2.6.6? currently ondemandx and no scripts.

tweaked - by me

kernel - siyah the og

rom- me you eeee.
[Galaxy S II Original Android Development] zer:
On default lulzactive (2.6.6)without scripts its really an beast. Poweramp on background with a bit download from market en editing script resulted 45min on 1200mhz constantly. For me to hot/beasty. As they mentioned, just play with the govenor parameters. I prefure ondemandx with script and adjust it till i have smooth playback on 720p videos.
[Galaxy S II Original Android Development] cmd512:
Lulzactive is not throttling down on 2.6.6 at 75% inc_cpu_load like 2.6.5 and earlier. Could this be a new bug?
[Galaxy S II Original Android Development] stevehkim:
hmm lulzactive won't drop lower than 500mhz either.
[Galaxy S II Original Android Development] cmd512:
Mine sticks to 1400MHz 99% of the time whereas previously, it would throttle down to 200MHz every second or so.

Gokhan, please advise what "changes/tweaks" you made to lulz? This completely changes the behavior.
[Galaxy S II Original Android Development] lpsi2000:
LOL, if that is the only reason you don't like Lulzactive then the solution is easy. Simply set a profile for when your screen is off to use another governor then you will be all set. I believe the issue you mentioned is only occurring when the display is off. I have done the same when I am using that governor.
[Galaxy S II Original Android Development] cmd512:
Also, have you guys noticed 2.6.6 is about 2 MB smaller than previous siyah kernels? Something seems off here...

EDIT: Ok, 2.6.6 is definitely broken with lulzactive. Several times I brought the phone out of idle, it was stuck at 500MHz. Never seen that with previous siyah revs...
[Galaxy S II Original Android Development] runedrune:
From the changelog:

XZ compression (this is not a feature but an explanation for smaller kernel size. I am sorry that I had to give up LZO because it gives me >8MB kernel image which exceeds the available kernel partition size)

No issues with lulzactive here :p
[Galaxy S II Original Android Development] greatmagician:
Hello ... I have problem with the network after I update the kernel in v 2.6.5 & 2.6.6 the network go to the flight mode and back .... ???
[Galaxy S II Original Android Development] greatmagician:
Is the problem with my script :

#!/system/bin/sh

echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1400 1275 1175 1075 975 900 850 825" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo lulzactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 10000 > /sys/devices/system/cpu/cpufreq/lulzactive/up_sample_time
echo 40000 > /sys/devices/system/cpu/cpufreq/lulzactive/down_sample_time
echo 80 > /sys/devices/system/cpu/cpufreq/lulzactive/inc_cpu_load
echo 5 > /sys/devices/system/cpu/cpufreq/lulzactive/pump_up_step
echo 1 > /sys/devices/system/cpu/cpufreq/lulzactive/pump_down_step
echo 6 > /sys/devices/system/cpu/cpufreq/lulzactive/screen_off_min_step

echo "160 267 300" > /sys/class/misc/gpu_clock_control/gpu_control
echo "60% 30% 90% 70%" > /sys/class/misc/gpu_clock_control/gpu_control
echo "950000 1000000 1150000" > /sys/class/misc/gpu_voltage_control/gpu_control

echo "0 0 0 0 1 2 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static
echo enabled > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

echo 3 > /sys/module/cpuidle/parameters/enable_mask

echo 50 > /sys/devices/virtual/sec/sec_touchscreen/tsp_threshold

echo sio > /sys/block/mmcblk0/queue/scheduler

echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step

echo 4 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel

echo 35 > /sys/class/misc/brightness_curve/min_bl
echo 1 > /sys/class/misc/brightness_curve/min_gamma
echo 24 > /sys/class/misc/brightness_curve/max_gamma

echo 30 > /sys/module/pm_hotplug/parameters/loadl
echo 80 > /sys/module/pm_hotplug/parameters/loadh
echo 40 > /sys/module/pm_hotplug/parameters/loadl_scroff
echo 90 > /sys/module/pm_hotplug/parameters/loadh_scroff
echo 499999 > /sys/module/pm_hotplug/parameters/freq_cpu1on
echo 200 > /sys/module/pm_hotplug/parameters/rate
echo 400 > /sys/module/pm_hotplug/parameters/rate_cpuon
echo 800 > /sys/module/pm_hotplug/parameters/rate_scroff

echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
[Galaxy S II Original Android Development] cmd512:
Way to be descriptive. Anyway, flashed back to 2.6.5 and phone is throttling properly back to 200mhz on lulzactive as expected. Regardless of whether or not you think your phone is "having no issues," 2.6.6 breaks lulzactive down stepping behavior.

(I only use lulz, so I immediately noticed this.)
[Galaxy S II Original Android Development] stevehkim:
+1 flashed back to 2.6.4 and after 10 mins deep sleep is already at 85% where as 2.6.6 would be at 30%-40% tops. Ondemandx and lulzactive tried with both tbolt scripts and siyah stock. Although Performance on 2.6.6 is a MONSTER!
[Galaxy S II Original Android Development] Jibreil:
TIP: Thunderbolt 2.3.6 working perfect on 2.6.6. Make sure you manually mount /data, /system in CWM before flashing Thunderbolt.
[Galaxy S II Original Android Development] zzz777:
2.6.4 is not vailable

can u upload it please ?

thanks
[Galaxy S II Original Android Development] antt00:
All previous versions had been removed due to a bug that was just discovered.
[Galaxy S II Original Android Development] stevehkim:
How's deep sleep with your setup? Which governer?
[Galaxy S II Original Android Development] Gowind:
hey buddy, flashing via CWM app wont do the trick...?
[Galaxy S II Original Android Development] mchu6am4:
Using latest MIUI ROM and siya 2.6.4 kernel but have noticed my phone crashes/freezes alot, probably a few times a day...especially using when market, for example whilst installing/updating an app, if i try to do something else at the same time such as try to search/browse the market for another app etc it just freezes! :-(

Any ideas...UK unlocked phone on Vodafone network.?
[Galaxy S II Original Android Development] stevehkim:
it's not a kernel issue. it's miui. There's a issue with the new market and miui not working together.
[Galaxy S II Original Android Development] cmangalos:
Im wondering if you guys have working wifi on 2.6.6 going back to 2.6.5 i got wifi issues on 2.6.6
[Galaxy S II Original Android Development] vastac13:
no problem here...
[Galaxy S II Original Android Development] mchu6am4:
Thanks
[Galaxy S II Original Android Development] cmangalos:
I guess the issue is on my router. I am connected to my wifi however i cannot browse. Tried deleting dalvik then upon reboot i can browse for 10 seconds then afterwhich i cannot browse again. I reverted back to 2.6.5 since im an addict playing mc3 online
[Galaxy S II Original Android Development] stevehkim:
not only you. I can connect to wifi on 2.6.6 as well but can't surf. or go on tapatalk.
[Galaxy S II Original Android Development] sc00by666:
Syiah have a new GPU Mali400 drivers(Nov. 2011)?
[Galaxy S II Original Android Development] Naytmer-fr:
No problem with wifi and surfing over the web for me on the 2.6.6, everything is working for now.
[Galaxy S II Original Android Development] iamsmallpang:
hi gokhanmoral,

you set default i/o scheduler is SIO

but VC setting default is cfq lulzactive after flashed v2.6.6

---------- Post added at 05:40 PM ---------- Previous post was at 05:15 PM ----------

how to solve VC setting did not save after a each reboot?

overclock kernel app FC
[Galaxy S II Original Android Development] N6666661:
everything works fine with 2.6.6 and CyanogenMod 7 #117.

Performances are back compared to 2.6.5.

I didnt had enough time to test the battery life.
[Galaxy S II Original Android Development] nk7:
Not sure if happening to anyone else but still with Batista and have been using Siyah for a while. Since update from 2.6.2 (I've tried all updates since this version up to 2.6.6) - whenever I open the messaging application (go launcher btw) and close the app using the back button. The task for messaging app is still open in task manager. Didn't happen with 2.6.2. Anyone else.

Don't really mind as I play around with new roms soon - but thought I might mention it.
[Galaxy S II Original Android Development] ephraim:
the best kernel ever! This removed the youtube stutter problem! Thanks!
[Galaxy S II Original Android Development] gokhanmoral:
for my case, lulzactive works very aggressively but it also scales down fast enough. I think I will revert back some changes and publish 2.6.6i. it is more like the interactive governor with some lagfree behavior (doesn't scale down very fast) and also it has sleep profile as in interactivex. I was trying to make it scale up faster and scale down a little bit slower but this one is a bit more aggressive than I have planned. but strangely, it doesn't suck the battery very fast. and (maybe preventing interactive governor threads startup when the phone boots up) I have very low idle consumption.

for wifi problems, I tried to mix&match the drivers and tried lots of different things but none of them makes everybody happy. in 2.6.6, I used the same drivers as in hardcore's kernel and that is from galaxy note I think. I never had any problems with any wifi driver and that is why I cannot help you guys having wifi problems for now. I will try to use the latest broadcom drivers in the next version.
[Galaxy S II Original Android Development] cmd512:
Thanks gokhan, makes perfect sense why I'm seeing this new behavior with lulzactive. You are right, I haven't tested long term battery consumption, but given mine wouldn't throttle down at all from max frequency, I assumed it couldn't be good.

Also, like you, never had issues with WIFI here with any siyah release. Given I was having all sorts of connection issues (regardless of what kernel I used) before upgrading my router, I'm betting most of these issues are router compatibility related.
[Galaxy S II Original Android Development] Vaedryn:
2.6.6 Cyanogen 7 Lulzactive , the best version from all you have bring to us.

Great work

Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] cmd512:
Interesting to note gokhan: Based on your feedback, I up'd the pump up threshold from my default 65% to 85% for lulzactive. Result: v2.6.6 is now throttling down much better.