yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Dark_Lord0122:
i use 100Mhz with 800mV sio+lulzactive and its working perfectly no deepsleep issues:)
[Galaxy S II Original Android Development] lrbpereira:
I had the same prob as you and it isn´t a kernel related prob.

You have to config your sms/mms app (if it is gosms pro) to not wakeup the screen when a sms/mms gets in. If not, as the screen goes on, the BLN is deactivated by default and the lights go off...

Did you understand me?

GO SMS PRO - CONFIG - NOTIFICATIONS CONFIG - uncheck IN SCREEN

PM me if you have any issue doing this right...
[Galaxy S II Original Android Development] xuxuzao:
had sod with

200mhz - 850

500mhz- 900

800mhz - 975

1000mhz - 1075

increased all values with 25 and its working fine now!
[Galaxy S II Original Android Development] mengsuan:
No problem with the linaro complied version. I always give slack space to my undervolting, like stable voltage+50mV or +25mV for lower frequencies. Could never go wrong even if there's some cosmic radiation flooding over earth :p

The 100MHz gpu settings is cool. I could save an additional 50mV. Lets see how the battery life goes later.

So far all stability test looks good. However bluetooth hid is still not working
[Galaxy S II Original Android Development] Bushido76:
Am I the only one experiencing this problem? ;)

Could anyone try to download the tar-file?

Thank you,

Bushido
[Galaxy S II Original Android Development] el_tute:
I have the same problem, the tar's link is broken.
[Galaxy S II Original Android Development] ChilliBo:
same here. cant download the 2.5 tar file...
[Galaxy S II Original Android Development] Siberian Tiger:
+1 here :D
[Galaxy S II Original Android Development] GDT:
Can't dl the tar version too. File not found.

I raised up my voltages for 500MHz and 800Mhz by a 25 step.

I'll post my results.
[Galaxy S II Original Android Development] el_tute:
I have to increse between 25 and 50mv

100 + 25

200+ 25

500 + 50

800 + 25

1000+ 25

1200 + 50

1400 + 25

So for now Im on these values and I didn't ave sod.

1400 @ 1250mv/400mhz

1200 @ 1225mv/400mhz

1000 @ 1100mv/266mhz

800 @ 1025mv/266mhz

500 @ 950mv/133mhz

200 @ 900mv/133mhz

100 @ 900mv/133mhz
[Galaxy S II Original Android Development] Gowind:
what is the minimum screen off time to experience SOD. i don't have it. ondemandx with 100-1200mhz and 100mhz@825mv :D
[Galaxy S II Original Android Development] Dark_Lord0122:
i haven't experienced SOD either . Lulzactive 100-1200Mhz 100@800Mv
[Galaxy S II Original Android Development] mbwatson:
Cannot get Bluetooth mouse to connect.
[Galaxy S II Original Android Development] Dennys_Santos:
I wrote the following script in the file S101ScalingGovernor, but when you restart the SGS2 no change to the governor ondemandx

#!/system/bin/sh

echo "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

chown root.shell /etc/init.d/S101ScalingGovernor

chmod 750 /etc/init.d/S101ScalingGovernor

Via the terminal below works perfect

echo "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

What should I do?
[Galaxy S II Original Android Development] LukeOII:
so whats the defference between tar and zip version?
[Galaxy S II Original Android Development] cmd512:
Awesome, trying out ondemandx. Seems nice and smooth so far!
[Galaxy S II Original Android Development] dica:
Two different methods of flash. zip by cwm and tar by odin
[Galaxy S II Original Android Development] LukeOII:
no read carefully,there is same difference
[Galaxy S II Original Android Development] bclark:
http://xdaforums.com/showthread.php?p=20261919
[Galaxy S II Original Android Development] hooozy:
Why don't I get such battery life like you even I'm on 2.4.3??Tried everything :-( :-( :'( :'(
[Galaxy S II Original Android Development] Dennys_Santos:
What the script needed to set ondemandx ?

I wrote the following script in the file S101ScalingGovernor, but when you restart the SGS2 no change to the governor ondemandx

#!/system/bin/sh

echo "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

chown root.shell /etc/init.d/S101ScalingGovernor

chmod 750 /etc/init.d/S101ScalingGovernor

Via the terminal works perfect

echo "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
[Galaxy S II Original Android Development] tomeks:
So far so good. Not a noticeable difference between 2.5 default and 2.4.2 default kernel setting (tomorrow battery life test ;-)) in everyday overall speed.

No SOD after three hours of usage.

Default kernel configuration (zip version) with only enabled 100mhz ( echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq)

in short. great kernel! thank you.
[Galaxy S II Original Android Development] gh.rohit:
i was using it with uc...send me pm ;-)
[Galaxy S II Original Android Development] nightranger73:
If you have a S99 script it will be executed after your script so it will override any other setting... in ASCII 101 is lower than 99

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] sierrafox:
i can confirm that 2.5 linaro and codesourcery compiled kernels both cause sleep of death if i don't raise voltages (which worked fine in 2.4.2). on a happier note, 2.4.2 and 2.5 appear to have solved HD video playback stuttering (from internal and external SD)

:)
[Galaxy S II Original Android Development] tomeks:
it seems devices dependant. I do not change any voltage values and no SOD even with 100mhz with linaro compiled kernel. at least till now :-)
[Galaxy S II Original Android Development] KennyLegend:
Anybody having issues connecting to BT car kit on GT2.5 ?
[Galaxy S II Original Android Development] kremator:
+1 with problem on deep sleep with settings from 2.4.2 on 2.5GT - phone just blacks out
[Galaxy S II Original Android Development] douglatins:
Should i always update to newer versions? Because i sometimes see people saying bad things about updates
[Galaxy S II Original Android Development] gokhanmoral:
then it is because of the changed code in frequency scaling part or you have very low voltage for 500MHz, maybe

anyway.. this happens...

I've never had a single crash with v2.5 with stock voltages for about a week.
[Galaxy S II Original Android Development] Molitro:
Same here. I've been using the same (fairly light) UV since the very first time I used Siyah, and I've never had a SOD.
[Galaxy S II Original Android Development] ReiKo90:
Yeah, I supose you should have two separate download servers - one for major, and other for silent updates.

btw. great job on 2.5
[Galaxy S II Original Android Development] Alukard1:
Hi!

Installed 2.5 GT update and...that's sooo good lol :D

All is very smooth, fast and even android market is faster :D

Thanks again Gokhan for you great work...kardesh ;)
[Galaxy S II Original Android Development] sierrafox:
definitely, i'll try upping the voltages, esp for 500MHz, thanks for the tip!
[Galaxy S II Original Android Development] poochewer:
It does not hurt to try the new ones for a while. If its no good you can always flash back to the version that you prefer.
[Galaxy S II Original Android Development] ReiKo90:
When I put CPU Govenor to ondemandx to Voltage Control lite what I/O Scheduler should I use?

Thanks!
[Galaxy S II Original Android Development] mbwatson:
Thanks for lowering the screen sensitivity. It solved all the issues of using a SGP glas screen protector.
[Galaxy S II Original Android Development] brack11:
As already been mentioned, I also have kinda sod but a little different, i have phone shut down after I finish call, also had sod. Removed undervolting which I successfully used since 2.1.1, and now everything is working. Well, I'm ok with no uv as long as battery life is good.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Miguel-:
I upped only the step 6 voltage and everything has been fine for several hours.. Sod every time before that..
[Galaxy S II Original Android Development] Astegal:
Same question

Envoyé depuis mon GT-I9100 utilisant Tapatalk
[Galaxy S II Original Android Development] Rockin_Zombie:
+1 this is the only problem I am facing. Raising 500mhz voltage now.
[Galaxy S II Original Android Development] BoneMo:
.

I've never had a single crash with v2.5 with voltages in my signature..great work,,great kernel
[Galaxy S II Original Android Development] tolis626:
Hey Gokhan,I won't bother saying the good stuff about 2.5,you know it. :p

Anyway,after many many SODs,I settled for 950μV for 500Mhz and everything else is kept the same.Seems stable until now...

Only problem I have faced is that,although general operation is fast and smooth,GoLauncher lags.And it's bad,because it was SMOOTH in 2.4.2.Then I realised that ondemand and ondemandx don't actually use more than 1400Mhz and there is something funny in the scaling.Not that 1400Mhz isn't smooth enough,but it like sticks to 800-1000Mhz when I set my maximum frequency to 1624MHz.Could you check it out?It kinda ruins the experience for me.I'm using conservative for now but bleh,it's not ondemand. ;)
[Galaxy S II Original Android Development] tendan:
@gokhanmoral

I flashed the kernel just when u posted it in your website and few hours later all is working perfect: no lag, no freeze device and no problems with deep sleep. I'm using 'linaro version' on default (no oc, uc, uv..)
[Galaxy S II Original Android Development] lpsi2000:
I can concur with this statement, stock voltage no SOD but I did get one this morning when I was not using stock voltage. I was trying to figure out which one to raised, but I think you just give me the clue:)
[Galaxy S II Original Android Development] gokhanmoral:
I had to make a choice between device getting warm or preserve battery.

I am planning to release v2.5p version that scales to the max frequency more easily. if you do not have a constant load ondemand (or any other governor) will not scale up to the highest freq but it will first set the freq to 800 then 1000 and finally 1200.

if you set the sampling rate low (you can set it to 10000 for ondemand in my kernel if I am not wrong) you will have less lag. so, if you want to reach 1200mhz in the same duration that you reach with v2.4.2, use 40000 instead of 120000 as the sampling rate.

I think I will use arighi's method in v2.5p but the battery life will be less I think and people will complain about 1000MHz not being used.
[Galaxy S II Original Android Development] poochewer:
I have had a few random freezes, where the phone just froze .I was in the middle of sending an SMS most times I could not do anything except hold the power button to shutdown. BTW I am using the >TAR version.
[Galaxy S II Original Android Development] Dennys_Santos:
Thanks Bro!

But it worked!

I changed the name of the script to 01ScalingGovernor and even then after I restart SGS2 access via terminal and run the command below to see if there was a shift to ondemandx but continues as ondemand

script: 01ScalingGovernor

#!/system/bin/sh

echo "ondemandx" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

I do not know what to do to use the ondemandx

Someone could send me some script that really works?

thanks...
[Galaxy S II Original Android Development] rauschkugl:
Just try lulz. Everything is fine for me. No lags on golauncher.

Sent from my GT-I9100
[Galaxy S II Original Android Development] ReiKo90:
Can someone please tell us newbies what I/O to use with ondemandx governor?

Thanks!
[Galaxy S II Original Android Development] Ogy77:
I flash 2.5 GT version and when I connect first time on USB and disconect phone reboot,anybody with this?But next few time ok,no reboot.
[Galaxy S II Original Android Development] CamoGeko:
Sio, VR or deadline. It's your choice, do some tests.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise. :D
[Galaxy S II Original Android Development] tolis626:
I vote for performance! :D

Anyway,that's not what I was saying.It's like it's bugged,not slow to reach max frequency.I already tried playing with all sorts of tweaks for ondemand but nothing.Perfect example of the problem occuring is setting both min and max frequency to 1624MHz(1600 for everyone else ;) ).It bugs out and sticks to 800MHz.

I guess it's time to give it a shot...Thanks man! :)
[Galaxy S II Original Android Development] Prankey:
No such issue with me. And the best part is my most critical bug is FINALLY resolved to an extent after several months of 2.3.4 (update 1 and above) kernel code where I lost internet access through wifi tether. More info:

http://xdaforums.com/showthread.php?p=20272819#post20272819
[Galaxy S II Original Android Development] blaex:
Vr and lulzactive stuck at max freq. (1.4ghz). Gpu clock, wasnt changed after reboot with 2.5 using voltage ctrl. Ondemandx scales properly up and down.

Cache + dalvik cleard before and after flash.
[Galaxy S II Original Android Development] gokhanmoral:
Right I can easily reproduce that. I never tried lulzactive with 1400. I will check the code and try to find the reason.
[Galaxy S II Original Android Development] nightranger73:
You missed the point. Are you sure there's no other script executed after 01ScalingGovernor overriding your settings?

Maybe s99voltagecontrol? as 101 (as it was named before) is lower than 99 in char table and is executed right after s10 and not after s99.

Have you double checked your script for extra trailing spaces at the end of the line that could lead to a syntax error?

If it works on terminal emulator it should work on init.d too.

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] spd2230:
I can't seem to get 2.5 to boot on my ATT GSII. I have downloaded the CWM package two separate times and ran a cleaning script before install, but the phone refuses to boot. It just sits on the CM7 boot screen. Doesn't act bootlooped, just doesn't boot. If I boot back to recovery 2.4.2 installs without issue.
[Galaxy S II Original Android Development] kragebein:
Hi, installed this kernel ontop of MIUI based rom. The ROM i have does not have a option to turn on/off the LED lights on the touchkeys -- When the screen is on, the touchkeys are on.

I want them to be -always- off.. How can I fix this?
[Galaxy S II Original Android Development] jangomango:
This sucks more juice than a bulimic ho....

Sent from my GT-I9100 bulimic ho
[Galaxy S II Original Android Development] Dennys_Santos:
These script are in /etc/init.d

ls -lha /etc/init.d/
drwxr-xr-x 2 root root 4.0K Dec 13 22:07 .
drwxr-xr-x 13 root root 4.0K Dec 9 15:14 ..
-rwxr-x--- 1 root shell 27 Aug 1 2008 01sysctl
-rwxr-x--- 1 root shell 105 Aug 1 2008 05modules
-rwxr-x--- 1 root shell 771 Aug 1 2008 06defaulttheme
-rwxr-x--- 1 root shell 273 Aug 1 2008 07internalsd
-rwxr-x--- 1 root shell 611 Dec 13 22:06 10ChargeCurrent
-rwxr-x--- 1 root shell 91 Dec 13 22:05 11ScalingGovernor

I checked each of the script and makes no change in voltage or governor.

I changed the name of the script again to try to get it to run last, then looked like this: 11ScalingGovernor

I edited the script 11ScalingGovernor[/ B] and saved in UNIX format and encoding UTF-8 and this was precisely the problem, ie, the file was not in the correct format.

Thank you for your help and attention...
[Galaxy S II Original Android Development] blaex:
It look likes the voltage ctrl boot settings do not apply properly. Tried setcpu ... Works with 2.5 ... But i cannot find the boot setting file ... How applies setcpu the boot settings, cannot find anything in etc/init.d...
[Galaxy S II Original Android Development] hkfriends:
it seems GT-2.5 hanged my stock (rooted) KI3 firmware
[Galaxy S II Original Android Development] miahegypt:
my ntfs HD still not working using OTG . is there some thing i have to do to make it work
[Galaxy S II Original Android Development] gokhanmoral:
I have reuploaded v2.5 files for those who use 1400 and 1600mhz

and this change also includes mc1n2_voodoo module (thanks to supercurio) as an apology for the bug and the silent update :)
[Galaxy S II Original Android Development] gokhanmoral:
I don't think sgs2 can drive an hdd because of current limitations?. it works with usb flash though.
[Galaxy S II Original Android Development] miahegypt:
i'v just tried my 16G Flash drive and it's not working olso
[Galaxy S II Original Android Development] antt00:
Redownloading to check on the voodoo module. Is it still linaro toolchain?
[Galaxy S II Original Android Development] miahegypt:
could u test NTFS

it's not working at all , i still got the same msg , blank or unsuported format

i cant even mount ntfs.ko
[Galaxy S II Original Android Development] xinfinityoO:
m using the following boot script

#!/system/bin/sh

echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1425 1325 1175 1050 975 900 850 825" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 35 > /sys/module/pm_hotplug/parameters/loadl
echo 75 > /sys/module/pm_hotplug/parameters/loadh
echo 35 > /sys/module/pm_hotplug/parameters/loadl_scroff
echo 100 > /sys/module/pm_hotplug/parameters/loadh_scroff

echo 1 > /sys/devices/system/cpu/sched_mc_power_savings

echo "160 267" > /sys/class/misc/gpu_clock_control/gpu_control
echo "900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control

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

echo "800 800 500" > /sys/devices/virtual/misc/charge_current/charge_current

echo disabled > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

it worked fine with 2.4.2 but with 2.5 my phone restarts randomly..

any suggestions..

thanks
[Galaxy S II Original Android Development] Entropy512:
These are a result of gokhan putting back in the code that tries to enter sleep at 500 MHz.

The device's hardware (or the bootloader, according to one guy from Samsung, see http://permalink.gmane.org/gmane.linux.kernel.cpufreq/7439 ) wants to resume from sleep at 800.

So your voltage for 500 MHz must support 800 MHz operation.

This could even cause SoDs with stock voltages on any device that happens to not allow 800 MHz stable operation at the voltage setting for 500 MHz (because the regulators will be set for 500 MHz but the device will hit 800 for some amount of time)
[Galaxy S II Original Android Development] AndreiLux:
500MHz still needs a lot of voltage now for it to properly sleep, linaro is guaranteed SOD at <950mV, codesourcery kinda works at 925mV but still needs 950 to be completely stable. Just an observation, not a complaint.
[Galaxy S II Original Android Development] CamoGeko:
This is why I'm sticking to 2.4.2-topo for now. I like how stable my low voltages are at the moment.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise. :D
[Galaxy S II Original Android Development] goose2600:
Wowowowow! It run so fast, even using launcher pro 3d drawer: it works smooth and with no lag (conservative governor).

Gokhan, thank you again!
[Galaxy S II Original Android Development] gokhanmoral:
can you try the attached file and see if it helps with SOD with old voltage values?

EDIT: uploaded to the first post
[Galaxy S II Original Android Development] Aleq:
I used to be running 500 MHz at 825mV (while 200 required 850mV) - strange. But it was stable. Now I see thanks to Entropy's explanation, that 500 MHz needs the same voltage as 800 MHz (otherwise I'm also unable to wake the device from sleep). That's much higher (950mV - 975mV) for me so can you explain what is the advantage of getting to sleep at 500 MHz? Does it save me more than what I would get from 825mV 500 MHz?

And perhaps one more question if anyone would know - if I would be running old kernel with 200 MHz 850mv, 500 MHz 825mV (yes, this was really stable for me, while 825mV for 200 MHz was not), would I save power if I would limit CPU to do not use 200 MHz, but start at 500 MHz?

Thanks!
[Galaxy S II Original Android Development] cmd512:
Thanks gokhan! Also noticed conservative *rarely* went to 1400 based on "time state" with the old 2.5, is this normal?
[Galaxy S II Original Android Development] DreddJudge:
Just tried this after the old 2.5 gave me a SOD using my old UV values and lazy governor and have not had a SOD yet.
[Galaxy S II Original Android Development] CamoGeko:
Any chance for a CWM zip please mate?

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise. :D
[Galaxy S II Original Android Development] AndreiLux:
Works with my previous voltages. Did you revert back to 800MHz?
[Galaxy S II Original Android Development] gokhanmoral:
no, I just set the voltage levels to 800MHz voltages just after disabling frequency scaling before sleep.

so, you will have 500MHz sleep with 800MHz's voltage value. not bad I guess.
[Galaxy S II Original Android Development] troyjamz:
Hi

How would one go about using the Voodoo Module, what are the effects?
[Galaxy S II Original Android Development] gokhanmoral:
can you post the voltage levels of 500 and 800MHz if you have SOD with v2.5?

and, what do you set your voltage level of 500MHz in order not to get SOD? do you set it to previous 800MHz voltage level or less?
[Galaxy S II Original Android Development] bclark:
The new version is causing no issues but older versions of 2.5 would cause SOD.

500 - 900

800 - 1000

I reverted to 2.4.2 before finding stable values BC I needed my phone today and only had a little bit of time to play
[Galaxy S II Original Android Development] lpsi2000:
My old 2.5 works well as far cpu scaling with ondemand and conservative.
[Galaxy S II Original Android Development] CamoGeko:
I had SOD with 500Mhz at 950mV and 800Mhz at 1000mV.

Communicated from a Galaxy far far away via an XDA premium neurotransmitter while DJ'ing on The Enterprise. :D
[Galaxy S II Original Android Development] lpsi2000:
I have no SOD yet with the old version with 500 @900mV and 800 @975mv.
[Galaxy S II Original Android Development] terenceleechan:
gokhanmoral,

will this kernel be ICS compatible if the leaked firmware comes out in the next few days/weeks? will auto-root it also?
[Galaxy S II Original Android Development] AndreiLux:
That's good fix I guess.

Can we further decouple the sleep voltage from the voltage table? For example just not take 800MHz voltage but a completely separate value just for sleeping. It would allow to decrease normal-use 800MHz voltage since I think it would run stable on lower values; without compromising the sleep functionality. It would also be worth testing if you could go even lower in the sleep frequency with that method.

Old values: 500:900mV / 800:975mV

New values: 500:950mV / 800:975mV

I didn't touch the other frequencies.
[Galaxy S II Original Android Development] ka2uki:
it seem that my phone alway wake up when the screen off.can't get a deep sleep all the time,..i am using ondemangx...
[Galaxy S II Original Android Development] gokhanmoral:
since deep sleep power consumption is very low I don't think using stock 800MHz voltage would hurt too much. undervolting will help more when the device is in use.

I am now using 6th level (index 5) which is 500MHz as default. I will try to use lower frequencies.

also, I think this modification will let you lower your 800MHz voltage even further because the voltage will be set to stock until the device wakes up and then the frequency scaling will be reenabled + undervolted values will be effective again.
[Galaxy S II Original Android Development] cmd512:
Definitely working here, but I can see it rarely ever goes to 1.4GHz on conservative. Ah well, maybe that's a good thing. :)
[Galaxy S II Original Android Development] AndreiLux:
My point was, 800MHz itself is stable at for example 925mV, but needs more due to sleep not to SoD.

Ohhhh! Good to know. Basically that means we're sleeping all at 1075mV (or whatever default is) now regardless?

PS. How about a linaro build with the latest changes? I'm curious to test out the differences.