Related
My problem basically is that setting conservative governor (recommended for SGS) i can't get over 1000mhz. With performance i get 12800mhz, which is my goal and it's stable but it won't change so it kills my batery.
The other options won't work, ondemand is unstable (locks my phone), powersave keeps 100mhz and userspace won't change the rate.
So how can i be able to get 12800mhz in conservative governor in SGS?
Thanks and sorry for my bad english, i speak spanish actually
Any one please?
Sent from my GT-I9000B using XDA App
You need a OC kernel ... speedmod as a basic kernel just has the cpu stepping changed ... but does not enable OC
you might try this kernel
http://forum.xda-developers.com/showthread.php?t=965103
broken64 said:
So how can i be able to get 12800mhz in conservative governor in SGS?
Click to expand...
Click to collapse
If you are able to really get the 12800Mhz share it pls with screenies. I am not sure that even desktop records are that high. But good luck on that
Here you have. I'm getting 12800mhz in a Modded version of SpeedMod that allows you to overclock. Official version does not allow you to oc.
But the problem is that in conservative governor won't go more than 1000mhz.
broken64 said:
Here you have. I'm getting 12800mhz in a Modded version of SpeedMod that allows you to overclock. Official version does not allow you to oc.
But the problem is that in conservative governor won't go more than 1000mhz.
Click to expand...
Click to collapse
Well I am still seeing there 1280 and NOT yours 12800
But ok
oh ok i'm sorry xD added one 0
Anyone knows how to set convervative govertor to max: 1280mhz??
Hey, man.
Use voltage control app and set the maximum clock to 1280.
You should have the i9000b variant, just like me. I'm using this kernel too and overclock my phone easy with setcpu and conservative governor.
The Voltage Control app you can get from market.
Hope this helps.
Just to mention, I wanna could put the vcore higher than 1.3v to achieve 1400 mhz, but the limit is 1.3. That is so sad.
What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.
That really is odd :S I think I'll try it myself.
hi guys,
does anyone have a tried and working UV values for best battery life? I don't want any more performance, so I'm not looking for OC, but perhaps any idea what UV stays stable?
Well, it's easy the higher you OC, the more it will drain your battery. As for UV, I can't tell because the voltages are different for every device, Rom and kernel...
Sent from my LG-Stone from the Prehistory...
Nahh... Just kidding!
CM 7.2 Koboltzz KANG
IronKernel 32MB
Usually undervolting -50mv for each speed will work for most devices, although its not recommended to decrease that much for speeds below 800mhz since it will affect your phone's wake up speed.
And tegra 2 cpu controller only supports minimum of 770mv, going anyway lower than this value will not have any effect.
My advice, try UV -25mv for 500mhz, and the rest above is -50mv. Some o2x can go -100mv, but you need to be lucky to own such device.
Cheers!
Mine is working perfectly on -75.
But when i go to -100, soemtime freezes device, so i use -75 regularly.
trying -50 across the board now, seems to run stable.
brw, how does lower voltage hurt the speed?
I can't really explain clearly since I do not know the technicals, but from what I read in xda, it will affect your speed, meaning 1.2ghz running at undervolted setting will not run the same as at stock voltage. Maybe its an efficiency issue, I do not know.
I thing that i experience, If you undervolt too much the few lowest clock steppings, you sometimes might not able to wake the phone from sleep because there is not enough power to wake it up.
I hope my explanation help you a little, and hopefully someone with more experience can give you a better explanation.
using -25mv ate 1.1ghz and 1ghz, -50mv at 800 Mhz, and -100mhz (750Mhz so its 770mhz because hardware limitations) on all other frequencies!
-50 mv is the limit for the device don't use below -50mv. but it dependes on your device. mine cannot UV it always gives me SOD i think my hardware phone is crap
antec123 said:
-50 mv is the limit for the device don't use below -50mv. but it dependes on your device. mine cannot UV it always gives me SOD i think my hardware phone is crap
Click to expand...
Click to collapse
When did you buy your phone?
I have one of the 10 first phones sold in Sweden and I cannot undervolt mine at all.
Just wondering if there's any correlation between manufacturing time and UVability (yeah I just made that word up).
// Stefan
I run with 1100.. good compromise between speed and battery life i think
What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.
RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.
Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.
overclocking to 1200 mhz will made any difference ?
Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.
I don't know if it works on OOS versions but it does, on the OB12. You need to be rooted to be doing this.
Lower the input boost to 1036 on the big and 556 on the small first. Now, change the governor of the big cluster to conservative and the small to ondemand or conservative , benefit!
To see the improvement in FPS, you need to go to developer options and switch on profile GPU rendering. For those who didn't understand this: lower the graph is, higher the fps. Hit thanks if helped
Where to change these settings?
Any kernel manager would do. I'd recommend kernel aduitor
chinmai560621 said:
Any kernel manager would do. I'd recommend kernel aduitor
Click to expand...
Click to collapse
Just change the option of GPU GOVERNER to simple_on demand one from the above mentioned app. It will work smooth.. works for me..:good:?
ashokspidy said:
Just change the option of GPU GOVERNER to simple_on demand one from the above mentioned app. It will work smooth.. works for me..:good:?
Click to expand...
Click to collapse
I'd recommend to leave it on msm-adreno.
What if I'm on RR 5.8.2 and ElementalX? I have ondemand governor option for little but don't have conservative for big cluster.
karliyo said:
What if I'm on RR 5.8.2 and ElementalX? I have ondemand governor option for little but don't have conservative for big cluster.
Click to expand...
Click to collapse
This is exclusive for OOS. In fact, the interactive is supposed to be better than the rest but it's not the case on OOS which is why I made this thread.
chinmai560621 said:
This is exclusive for OOS. In fact, the interactive is supposed to be better than the rest but it's not the case on OOS which is why I made this thread.
Click to expand...
Click to collapse
Oh alright. Little governor ondemand seems quite fine right now.
By the way, are both governors interactive by default?
karliyo said:
Oh alright. Little governor ondemand seems quite fine right now.
By the way, are both governors interactive by default?
Click to expand...
Click to collapse
Has to be. Unless you use blu_spark kernel. It uses blu_activ.
How do these changes affect the battery life?
chinmai560621 said:
Has to be. Unless you use blu_spark kernel. It uses blu_activ.
Click to expand...
Click to collapse
You mean interactive and not blu_active?
I do recommend you guys taking a look at AKT.. There are alot of peformance oriented and balanced profiles that are already better with smoothness then stock.. Also Franco has some magic with stock settings!
chinmai560621 said:
I don't know if it works on OOS versions but it does, on the OB12. You need to be rooted to be doing this.
Lower the input boost to 1036 on the big and 556 on the small first. Now, change the governor of the big cluster to conservative and the small to ondemand or conservative , benefit!
To see the improvement in FPS, you need to go to developer options and switch on profile GPU rendering. For those who didn't understand this: lower the graph is, higher the fps. Hit thanks if helped
Click to expand...
Click to collapse
Hi friend, shall I change both values of big and small? I mean maximum and minimum?
Same, cant find where to change the input values for those two.
rOck4n said:
Same, cant find where to change the input values for those two.
Click to expand...
Click to collapse
You'll see input boost in the bottom section of CPU in kernel adiutor. Core 1- 1036, core 3 -556 is what you've to do. It'll be 1324 default on both. I'm suggesting that for slightly better battery life
MarcTremonti said:
How do these changes affect the battery life?
Click to expand...
Click to collapse
Lower SOTs are obvious, but to what degree is what matters. As far as I see, it's not that much.
GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .
When I change big cluster to conservative, those cores will always stay above 2 GHz, as shown in Kernel Adiutor.
chinmai560621 said:
GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .
Click to expand...
Click to collapse
The thread is about more performance and you're discussing battery life....of course it will have a lower battery life, the question is are you happy when your quad-core phone stutters....
chinmai560621 said:
You'll see input boost in the bottom section of CPU in kernel adiutor. Core 1- 1036, core 3 -556 is what you've to do. It'll be 1324 default on both. I'm suggesting that for slightly better battery life
Click to expand...
Click to collapse
Got it, thank you. I did notice a slightly battery improvement after two cycles.
Little investigation..
chinmai560621 said:
GUYS, I recommend not to use this anymore. Oneplus has a reason to not release the kernel with conservative on . This is because conservative is not optimized for battery while interactive is. If interactive weren't optimized for battery, it'd be better than conservative for sure. I get only 4 hr sot on conservative but 5.5 on interactive. Though this is not placebo, it has a negative impact on SOT .
Click to expand...
Click to collapse
Good you realised that.. I did a little investigation on your tweak.. Apparently setting governor to conservative locks the frequency of big cluster to max possible, usually above 2 ghz and it will step down slowly ( by slow I mean really slow like 1-2 seconds). Thus causes you to have very less render times on gpu profile as shown in the xda portal post.. I opened up ex kernel manager and observed same freq in higher range.
After some time I just changed governor to interactive and changed minimum freq of big cluster to 2 ghz.. I observed the same render times as situation as time when conservative was set as governor...
So this tweak is nothing but type of placebo since ramping up freq can lead to faster processing
Edit.: Couple of people on xda portal have said the same.. I didn't check it..