Database Users

Show your SetCPU Profile for the Legend

Hey everyone,
i think it would be interesting if we collect some SetCPU Profiles.
The App you can find here:
SetCPU for Root Users [2.1.0]
Maybe someone has found allready a good Profile for saving battery but having enough CPU-Power for a smothy work on the Legend?
I have used this Profile for a while, but i think through the overclocking there´s to much battery waste and no really noticable better performance with the apps i use.
Temp > 40° Priority 100
122min | 245max
Screen Off Priority 70
122min | 245max
Battery < 20% Priority 60
122min | 480max
Battery < 50% Priority 50
122min | 600max
Battery <101% Priority 40
122min | 806max
Some interesting Posts about SetCPU:
[TUT] SetCPU and Advanced Settings
Greetz picz

245/787, interactive
That is all

122/768 ondemand....
Is interactive better than ondemand? I mean from fast response/battery life POV...

Main
787 max, 245 min, interactive
Battery 40%
600 max, 245 min, interactive
Screen Off
400 max, 245 min, Ondemand
Screen Off and Battery 40% both at priority 50

Dr.Romca said:
Is interactive better than ondemand? I mean from fast response/battery life POV...
Click to expand...
Click to collapse
I read this in an other board:
From what i've read, "Interactive" is a bit more aggressive at ramping up CPU speed based on load, and is slower to drop off to "idle" speeds once the demand has passed.
"Ondemand" is a bit more conservative in the way it reacts; and will drop back to "idle" speed more quickly.
"Interactive" makes the device significantly snappier, at the cost of battery life. "Ondemand" will last a bit longer batterywise, however; the device will seem a bit sluggish at times.
Click to expand...
Click to collapse

I can't go below 245 how r u guys managing it ?
Swyped from my legend using XDA app

Maybe your kernel doesnt support this? Which ROM do u use?
Sent from my HTC Legend using Tapatalk

picz said:
Maybe your kernel doesnt support this? Which ROM do u use?
Sent from my HTC Legend using Tapatalk
Click to expand...
Click to collapse
cm 6.1
kernel 2.6.29.6

245/787mhz
Can anyone tell me the differences between ondemand, performance, interactive etc.? I can't seems to find the comparison between these in google, xda etc.
Please help me! I'm sure there's people out there who wants the answer as well

picz said:
Some interesting Posts about SetCPU:
[TUT] SetCPU and Advanced Settings
Click to expand...
Click to collapse
You can find it in this Threat.

Can anyone tell me the differences between ondemand, performance, interactive etc.? I can't seems to find the comparison between these in google, xda etc.
Please help me! I'm sure there's people out there who wants the answer as well

[REF] Best Governor And I/O Scheduler Studies + Battery Saving Tips

Ok it's been so long and for the love of God! I still see a lot of users posting about how horrible their battery lives are. So, here are a couple of guides that I found. I'm copy pasting them here because (1) I find them very informative and (2) I can agree with the information provided from my experience. And hopefully you find it helpful too.
Please follow the original thread and thank bedalus for all his time and effort!
Governor And I/O Scheduler Studies
Direct Copy Paste---I TAKE NO CREDIT---Original Thread Here:http://forum.xda-developers.com/showthread.php?t=1470247
bedalus said:
Spreadsheets for CPU Governors and I/O Schedulers
GOVERNOR RESULTS
I/O SCHEDULERS
Summary of the Results
This is a summary of the six most commonly used governors, listed in order of performance.
Best Performing
#1 - Performance
--- : Use Noop or Deadline
--- : Uses a lot more battery
#2 - SmartassV2
--- : Use Noop or SIO
--- : Uses a little more battery
#3 - LulzactiveV2
--- : Use Deadline or Noop
--- : Uses a lot more battery
#4 - Lazy
--- : Use Deadline or CFQ
--- : Helps save battery as long as SOMF is not enabled
#5 - Ondemand
--- : Use Noop or Deadline
--- : Helps save battery
#6 - Conservative
--- : Use CFQ or Noop
--- : Helps save battery
Check my summary in this thread for more info about how to save battery.
Thanks to all the developers.
Caveats
The most important thing to remember is that the testing hardware is a nexus s. Although I believe they are essentially the same device, there may be differences in how the galaxy s hardware affects performance. Do some experimenting yourself, and if it feels right, go with it!
Click to expand...
Click to collapse
--------------------------------------
Battery Saving Tips
Direct Copy Paste --- I TAKE NO CREDIT --- Original Thread Here: http://forum.xda-developers.com/showthread.php?p=22126792#post22126792
bedalus said:
Spreadsheet of the Battery Drain Data
BATTERY DRAIN BENCHMARKS
VIDEO of how it's done! (Do NOT try it yourself!)
NEW: Lab study done by nathanson666 see here and featured on the XDA's portal and twitter here.
Summary of Results
#1 - With screen on, if the processor is Idle, 100MHz saves the most power.
#2 - Regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%. (Click here for explanation.)
For the instability introduced by UV, it seems a 2% increase in battery life isn't really worth it! REMEMBER rebooting uses so much power, a single one would more than undo any savings made by UV.
#3 - The most power saving governor is Ondemand. If you need a high performance governor, use smartassV2, which offers some battery savings.
#4 - This is one point that everyone ought to know, but I'm including because many people seem to believe in myths: if the screen is off, and the CPU is not active, neither deep idle nor UV will have any impact on battery life.
#5 - The matr1x kernel by mathkid95 mainly saves power through UV of the INT voltages. You may need to raise these if you have freezes/reboots with your phone (in addition to raising the ARM voltages). I found that a maximum of 1 mA can be saved through INT UV, regardless of whether the CPU becomes idle (or with screen off in deep idle), so this is a constant saving. However, it is a very small saving, and doesn't apply if the phone is asleep. Remember, reboots cost more juice than UV can ever save.
#6 - If you have an amoled display, black saves a great deal of power. After that, red. If you have a black and red theme, this is saving you power!
#7 - If you are determined to UV, I found that my phone would become unstable with UV settings that were fine when the battery was fully charged. So check what UV your phone can handle when your battery is nearly empty. Again I say: Because of the high likelyhood and massive battery drain that comes with a reboot, I highly recommend you DO NOT USE EXCESSIVE UV. Also remember, even with extreme UV, you will not increase battery life more than 2%
#8 - I found that with bluetooth or GPS preventing the TOP=OFF state, there was no additional power saving from Deep Idle, i.e. the TOP=ON state does not save power.
#9 - Kernels with the 65 fps hack will cause the screen to drain about 10% more power compared to the usual 56 fps.
#10 - Conservative does not save power! For further details and exceptions, refer to my new thread: here.
#11 - This is just general advice: if you are having very poor battery life, have you tried turning auto brightness off? And if you've got no reception, you might as well be in airplane mode, because searching for reception also eats battery.
#12 - If your phone can't handle OC (or UV for that matter) it's because components in general are built to cost, which means factoring in tolerances, and every chip is made as cheaply as possible within the specified tolerances. Outside of those tolerances, whether your chip can cope or not is unfortunately down to the whether you got lucky with the individual device that dropped off the manufacturing line.
ARM document on A8 fault tolerance: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344k/Babhjhag.html
In fact I measured how UV in particular can cause errors, and saw in action the A8 using MORE power to correct the errors. From my spreadsheet:
At 100Mhz
mV 1500 4.92mA
mV 950 2.83mA (default mV)
mV 800 2.58mA (UV saves some power)
mV 750 2.96mA (Extreme UV uses MORE power)
Same test but with Deep Idle enabled:
mV 1500 1.91mA
mV 950 1.49mA
mV 800 1.29mA
mV 750 1.49mA (Same result again but with DI enabled)
Referenced from my spreadsheet starting row 41.
Recommended reading: http://everything2.com/title/wafer+yield
Stock voltages for reference:
ARM
1000MHz @1250mV
800 MHz @1200
400 MHz @1050
200 MHz @950
100 MHz @950
INT
1000MHz @1100
800 MHz @1100
400 MHz @1100
200 MHz @1100
100 MHz @1000
Summary of Power States by tchaari (thanks!)
After research, and some explanation from Steve Garon, it is clear that Deep Idle & CPU Idle are two completely different things:
1) Three main CPU states are implemented in the standard android kernel: NORMAL, IDLE and SLEEP
2) Ezekeel added an intermediate 4th state: Deep IDLE. This saves more power but only when the processor has a background task to run while screen is off. Bedalus proved here that it really saves a considerable amount of power in particular cases (e.g. music playing when screen is off). A minority of users are reporting some slight instabilities with it, but they may in fact be caused by things other than deep idle.
3) The CPU IDLE backport is a replacement of the standard android kernel drivers used to put the CPU in idle/sleep states by the new ARM methods integrated in the linux 3.2 kernel. This backport is theoretically supposed to improve battery life (with just the basic 3 CPU states). It is 100% stable but no power saving has been shown either in bedalus' amp meter measurements, or Harbb's overnight drain tests.
Where did the other benchmarks go?
All ICS ROM Benchmarks: this thread
Kernel Features and Benchmarks: this thread
CPU Governors and I/O Schedulers: this thread
Power Saving Governors: this thread
Thanks to all the developers, and a big shout out to: Harbb for his dedicated testing; tchaari for his motivation, great ideas and inspiration; jcolinzheng for the idea to test Deep Idle at fixed frequencies (genius); aLNG for links to interesting and useful articles; Steve Garon for demystifying esoteric kernel technicalities and his excellent kernel itself; everybody else who helped; and of course Ezekeel for making Deep Idle work, and for a stimulating debate!
Click to expand...
Click to collapse

here's a screen shot of my battery life in standby.
set up:
Governor and Scheduler: Ondemand/Noop
CPU Frequency: 200-1000
No OC/UV
No Didle

xtone said:
here's a screen shot of my battery life in standby.
set up:
Governor and Scheduler: Ondemand/Noop
CPU Frequency: 200-1000
No OC/UV
No Didle
Click to expand...
Click to collapse
OMG
Can you please share What kernel are you using and what are your settings buddy ??

amritpal2489 said:
OMG
Can you please share What kernel are you using and what are your settings buddy ??
Click to expand...
Click to collapse
I think you're getting your hopes up. Something tells me the radio isn't in use the whole time, extended battery might come into play, or a total of an hour's worth of screen on time. The vibrant has battery drain problems with normal use with aosp ROMs, nothing is gonna change that.
Sent from my Nexus S using xda app-developers app

xtone said:
here's a screen shot of my battery life in standby.
set up:
Governor and Scheduler: Ondemand/Noop
CPU Frequency: 200-1000
No OC/UV
No Didle
Click to expand...
Click to collapse
Dude! My phone on for 1d18h says 13% battery and i don't even use wireless or bluetooth.

amritpal2489 said:
OMG
Can you please share What kernel are you using and what are your settings buddy ??
Click to expand...
Click to collapse
He has not been using his phone see his screen drained only 5% battery. all phones will gives similar results if you just keep phone on table.

unable to scale to 1400 mhz on LPY

Note on stock non rooted LPY,in CPU Spy 1400 mhz is always listed as unused states even after heavy usage and reboots,any solutions or this is an ICS bug?

Do you have power saving option enabled? That limits the CPU to 1200 MHz
I have just tried on mine with CPU Spy. I had unused 1400 MHz speed until I just disabled power savings and it shows 6 seconds of use at that frequency now.
deadundead said:
Note on stock non rooted LPY,in CPU Spy 1400 mhz is always listed as unused states even after heavy usage and reboots,any solutions or this is an ICS bug?
Click to expand...
Click to collapse

hi
personally i corrected the problem with rom-manager pro (rooted)

Le [email protected] said:
hi
personally i corrected the problem with rom-manager pro (rooted)
Click to expand...
Click to collapse
How does that help with a stock unrooted firmware?

Le [email protected] said:
hi
personally i corrected the problem with rom-manager pro (rooted)
Click to expand...
Click to collapse
Could you please explain how to use this? have kingdroid v2 with speedmod kernel... CPU spy shows only 6ms of 1400 mhz usage on 70 hours phone uptime!!
Before if I play Asphalt or temple run, the 1400 mhz would be used, but now this is not the case...

Try to disable power savings mode and check.
Sent from my GT-N7000 using xda premium

No, my phone is not in power saver mode... Never put it on...
Sent from my GT-N7000 using XDA

UV Settings Discussion

kartalgurhan said:
Care to share how you uv'ed GPU?
Br
Click to expand...
Click to collapse
-100mv for all freq, like the next phenomenal extreme
then: echo "800000 825000 900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control
CPU undervolt:
200-725
300-725
400-775
500-800
600-825
700-850
800-875
900-900
1000-950
1100-975
1200-1025
1300-1075
1400-1125
are the most extreme voltages possible, nobody has been able to go under
i have studied these voltages with fenomeno83

giajp said:
-100mv for all freq, like the next phenomenal extreme
then: echo "800000 825000 900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control
CPU undervolt:
200-725
300-725
400-775
500-800
600-825
700-850
800-875
900-900
1000-950
1100-975
1200-1025
1300-1075
1400-1125
are the most extreme voltages possible, nobody has been able to go under
i have studied these voltages with fenomeno83
Click to expand...
Click to collapse
Tried your undervolt and it gives random restarts. Sometimes its okay but other times it just locks up within a few minutes. Just wondering if you have revised those voltages yet to become more stable?
Thanks

xqwiza said:
Tried your undervolt and it gives random restarts. Sometimes its okay but other times it just locks up within a few minutes. Just wondering if you have revised those voltages yet to become more stable?
Thanks
Click to expand...
Click to collapse
these settings vary from one device to another. Those, for example, perfectly worked for me but locked up my friend's device constantly (same ROM, same config).
you need to try and find the best config for your own device.
hth
regards

xqwiza said:
Tried your undervolt and it gives random restarts. Sometimes its okay but other times it just locks up within a few minutes. Just wondering if you have revised those voltages yet to become more stable?
Thanks
Click to expand...
Click to collapse
those are extreme voltages for s3, you device not support them, up all of 25mv, if still unstable, up 50

I'm looking to find out how far UVs can be taken on the S3. Please vote in my poll:
http://forum.xda-developers.com/showthread.php?t=1738572

Darkstriker said:
I'm looking to find out how far UVs can be taken on the S3. Please vote in my poll:
http://forum.xda-developers.com/showthread.php?t=1738572
Click to expand...
Click to collapse
Useless, lowest voltage are mine, stop.
Sent from my iPhone Fu**er S3 using Tapatalk 2
ROM: CheckROM EvoHD V2
KERNEL: Ninphetamine v1.1.1
MODEM: NELE4

Hacre said:
If you don't understand the principles involved in under/over volting/clocking, which you clearly don't, then don't do it. Do you understand that you're messing around with potentially dangerous settings on a very expensive device?
Click to expand...
Click to collapse
Just testing other other people's UVs as I've been doing some of my own. Seeing if extreme UV was true and stable but it wasn't for my device (was confirmed working for 3 people by the looks of it).
I've managed to get mine running on these voltages with 200-1200mhz not fully stable yet but usable. Still working on it for full stabilty.
200 - 695
300 - 695
400 - 707
500 - 783
600 - 807
700 - 840
800 - 855
900 - 890
1000 - 927
1100 - 985
1200 - 1000
Sent from my GT-I9300 using xda premium

xqwiza said:
Just testing other other people's UVs as I've been doing some of my own. Seeing if extreme UV was true and stable but it wasn't for my device (was confirmed working for 3 people by the looks of it).
I've managed to get mine running on these voltages with 200-1200mhz not fully stable yet but usable. Still working on it for full stabilty.
200 - 695
300 - 695
400 - 707
500 - 783
600 - 807
700 - 840
800 - 855
900 - 890
1000 - 927
1100 - 985
1200 - 1000
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
absolutely impossible that your are stable, the totally stable:
-100mv for all freq, like the next phenomenal extreme
then: echo "800000 825000 900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control
CPU undervolt:
200-725
300-725
400-775
500-800
600-825
700-850
800-875
900-900
1000-950
1100-975
1200-1025
1300-1075
1400-1125
i have studied these voltages with fenomeno83, the creator of phenomenal
Sent from my iPhone Fu**er S3 using Tapatalk 2
ROM: CheckROM EvoHD V2
KERNEL: Ninphetamine v1.1.1
MODEM: NELE4

Hacre said:
If you don't understand the principles involved in under/over volting/clocking, which you clearly don't, then don't do it. Do you understand that you're messing around with potentially dangerous settings on a very expensive device?
Click to expand...
Click to collapse
I have to agree. And I've messed around with voltages often enough to know that it simply isn't worth the hassle of trying to find the right voltages to suit ur device as u gain next to nothing in terms of battery life and heat reduction.
"Mine is bigger than yours " springs to mind
Sent from my GT-I9300 using xda premium

giajp said:
-100mv for all freq, like the next phenomenal extreme
then: echo "800000 825000 900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control
CPU undervolt:
200-725
300-725
400-775
500-800
600-825
700-850
800-875
900-900
1000-950
1100-975
1200-1025
1300-1075
1400-1125
are the most extreme voltages possible, nobody has been able to go under
i have studied these voltages with fenomeno83
Click to expand...
Click to collapse
Holy ****! That's an epic undervolt. I'm amazed at how much UV the higher over clocked frequencies can handle.
Sent from my GT-I9300 using xda premium

[TWEAK][Siyah Kernel 4.1.1+][Extweaks] Get up to 7 hours of screen usage

WARNING: Use this settings at your own risk. I am not responsible for what will happen to your phone.
So, Siyah Kernel 4.1.4 has been released, and since 4.1.1 and its new features I have struggled for obtaining maximum battery life without loosing smoothness.
I tested these settings on 5 phones (Galaxy S2 GT-I9100): mine and my friends' ones, and we all got the same (more or less) results: it's awesome!
Screen usage can get up to 7 hours. I did these tests with mobile data on for all phone usage, and not in deep sleep. When I was at home I switched to Wi-fi.
My ROM is AOKP M6 (ICS 4.0.4), other tests were made on Resurrection remix JB, stock XWLPF (ics), CM9 stable (screen usage: about 6 hours, no more), and AOKP JB (latest).
Extweaks settings:
CPU:
GENTLE FAIR SLEEPERS: ON
CPU HOTPLUG: (default)
CFS TWEAKS: Linux kernel defaults
CPU IDLE MODE: AFTR+LPA
SMOOTH SCALING LEVEL: 800 mHz
MAX CPU LOCK: Dual core mode
CPU UNDERVOLTING: - 50mV (if you get freezes, set -25mV)
CPU STEP COUNT: 16 (all available)
GOVERNOR: pegasusq
MAX FREQ: 1200 MHz
MIN FREQ: 200 MHz
GPU:
MALI TOUCH BOOST LEVEL: Step 2/Step 3
GPU STEP 1: 44 MHz
GPU STEP 2: 66 MHz
GPU STEP 3: 100 MHz
GPU STEP 4: 200 MHz
GPU VOLTAGE LEVEL 1, 2 AND 3: 800 mV
GPU VOLTAGE LEVEL 4: 950 mV
THRESHOLDS: default values
AUDIO:
HEADPHONE AMPLIFIER: 0 (set this value as you want and as you ears can stand it, it doesn't affect battery life unless you listen to music)
SCREEN:
TOUCHMOVE SENSITIVITY: 3 pixel
ALL OTHER SETTINGS: default values
mDNIe negative toggle: off
BLN:
BLN: off
NOTIFICATION TIMEOUT: never timeout
BLN EFFECT: set what you want, cause BLN is disabled
LED TIMEOUT: use ROM defaults
LED FADEOUT: on
LEDS ON WITH TOUCH: off
LED VOLTAGE LEVEL: 2700 mV (2750/2800 mV if led lights are dim)
MISC:
ANDROID LOGGER: off
DEFAULT I/O SCHEDULER: cfq/noop
ALL OTHER SETTINGS: default values
I think they are not too aggressive values, but if you get freezes, I recommend you reset your extweaks settings via CWM recovery and then use less aggressive ones.
In the attached screenshots, battery stats analysis starts from 91% since I had to restart my phone, and when it was at 10% I plugged the USB cable in to transfer a .zip file in my SD card, but I don't think that this 15-second charge affected my test (I'm sure it didn't!).
Phone usage was high today, I used Tapatalk, created a new UCCW skin, did some long phone calls, Facebook, messaging, e-mail checking, and other stuff I don't remember since the battery stats don't even report them (lol).
Notice that this is an extreme test. 7 hours of screen usage is not a myth, reality instead, but you cannot get them with the so called 'everyday usage'.
Screenshots of test made on my usual phone usage will come soon
THANKS:
gokhanmoral : the men who created THE kernel, the Siyah kernel.
geko95gek : author of MagicConfig. He found out the perfect balance between GPU frequencies and voltages.

I think you forgot the most important part : the extended battery

Extended battery? so what we can get on normal? 4h?

minidou-77 said:
I think you forgot the most important part : the extended battery
Click to expand...
Click to collapse
I have a 1650 mAh battery... never had extended 2000 mAh

I don't think these settings are good for performance... I have used even higher settings and there was lagg in some cases. But that was all on my phone

This seems largely similar to my MagicConfig thread.
Sent from my HTC One X

7 hrs screen time with 1200mhz max frequency and stock battery.. how much more if it's set on 800mhz.. 8-9 hours probably on stock batt?
you could have atleast included what you were doing in those 7 hours screen time like browsing, texting, facebook, etc, also the brightness of the screen, battery chart..

gb.yolo said:
I have a 1650 mAh battery... never had extended 2000 mAh
Click to expand...
Click to collapse
I saw u're using XXKH3 modem as it's also my favourite... can u please share with me XXKH3 RIL ? It was what I've been looking for & nobody could provide it w/ links or a drop box.. thanks..
Sent from my GT-I9100 using xda app-developers app

I only have 3 steps on my gpu?
Sent from my GT-I9100 using xda app-developers app
Just updated my siyah. Goin to try this config

Adam Hui said:
I saw u're using XXKH3 modem as it's also my favourite... can u please share with me XXKH3 RIL ? It was what I've been looking for & nobody could provide it w/ links or a drop box.. thanks..
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
My modem's XXKH3, and i downloaded it here: http://www.ziddu.com/download/19200730/Modem-XXKH3-CWM-DragoN3252.zip.html
hope this helps
cheers!

saywhatt said:
My modem's XXKH3, and i downloaded it here: http://www.ziddu.com/download/19200730/Modem-XXKH3-CWM-DragoN3252.zip.html
hope this helps
cheers!
Click to expand...
Click to collapse
Thanks for reply mate..
I already have XXKH3 modem, I mean I need XXKH3 RIL (radio interface layer) to match modem with as it was the only method to avoid RIL crashes & RILJ wakelocks which prevents phone go to deepsleep.. do u have it sweet?
Sent from my GT-I9100 using xda app-developers app

Dark Emotion said:
I don't think these settings are good for performance... I have used even higher settings and there was lagg in some cases. But that was all on my phone
Click to expand...
Click to collapse
As you said, it was all on your phone. This is why with someone's settings nobody get exactly the same results: I get lags, you don't get lags, but he sometimes gets lags and sometimes not
geko95gek said:
This seems largely similar to my MagicConfig thread.
Click to expand...
Click to collapse
MagicConfig was my starting point for GPU voltage levels, how cannot I admit? I always used those frequency steps (first post) but I've never found the right voltages to avoid lags, especially when turning screen on. And I forgot to thank you. I say sorry mate
Tricks25 said:
7 hrs screen time with 1200mhz max frequency and stock battery.. how much more if it's set on 800mhz.. 8-9 hours probably on stock batt?
you could have atleast included what you were doing in those 7 hours screen time like browsing, texting, facebook, etc, also the brightness of the screen, battery chart..
Click to expand...
Click to collapse
In the first post:
Phone usage was medium-high today, I used Tapatalk, created a new UCCW skin, did some long phone calls, Facebook, messaging, e-mail checking.
Click to expand...
Click to collapse
@Adam Hui sorry if I can't help you, but I don't have a RIL matching the XXKH3 modem. I have XXLPW, and since it is all going well with it (deep sleep is ok, wakelocks are ok [more or less]) I didn't much care about it

Try GetRIL
Adam Hui said:
Thanks for reply mate..
I already have XXKH3 modem, I mean I need XXKH3 RIL (radio interface layer) to match modem with as it was the only method to avoid RIL crashes & RILJ wakelocks which prevents phone go to deepsleep.. do u have it sweet?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Try the GetRIL app, it should be able to find the RIL for you.
But if I understand correctly, KH3 is a Modem from the GB firmwares, and you're running and ICS Firmware, the RIL is part of the Firmware and I don't think you can install a GB RIL on ICS... but try the app.

Need to test this. The magic config thread was slightly outdated and with new Siyah v4+ releases, it never got updated.
Sent from my GT-I9100 using Tapatalk 2

rakeshishere said:
Need to test this. The magic config thread was slightly outdated and with new Siyah v4+ releases, it never got updated.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It will once I get some testing results.
As I have mentioned before I do not possess an s2 anymore so it makes the process of updates slower. Doesn't hurt to be a bit patient right?
Sent from my HTC One X

geko95gek said:
It will once I get some testing results.
As I have mentioned before I do not possess an s2 anymore so it makes the process of updates slower. Doesn't hurt to be a bit patient right?
Sent from my HTC One X
Click to expand...
Click to collapse
No offense mate. I'm aware that you no longer own S2 and moved to HOX. I just gave my opinion about magic config thread and it wasn't towards you.
Sent from my GT-I9100 using Tapatalk 2

Great ! I'll try it.

Looks great, must try....................:good:

Thanks gb.yolo
I configured my phone with your settings and it's running nice.
I can't really feel a difference in "smoothness" and it's the first time I change GPU frequencies and UV... but I still can't really tell a difference... what should I expect from changing GPU params, other than battery life?

buddy i cant find Siyah Kernel 4.1.1+ do you have any dwonlad that.