I have a question: why I can't overclock my SGS past 1.2 ghz. When I try to set for example 1.3 or 1.4 it freezes and I take out the battery in order to make it work again. Is there something I do wrong, is it a general problem with more SGSs? If somebody can , I really appreciate. Thanks
it is a kernel thing.
the kernel has to support those frequencies.
Sent from my GT-I9000 using XDA Premium App
I tried with tegrak overclocking with voodoo kernel (the application itself doesn't need a kernal that supports those frequencies) and with Supe Optimized Kernel (1.4 ghz) and voltage control and setcpu and is the same result:freezing.
Not every cpu is capable of stable overclocking past a certain threshold. You have probably hit the max speed your cpu can maintain.
I agree with you but then why there are other people with the same phone as me that can overclock them at 1.4 ghz?
With CM7 or miui and either bilboa or zacharius kernel you can overclock to 1300 but I haven't found a kernel that allows 1400 either, I think those that are doing it are hacking the CPU settings themselves.
My phone gets really hot at 1300 running apps like dungeon defender so 1400 might just be a bit too much
Sent from my GT-I9000 using XDA App
I am using Darky's 9.3 ROM but my problem is that i can't even touch 1300 mhz because my phone freezes.
Maybe a dumb question, but, do you overvolt as well as overclock? Maybe the cpu isnt getting enough juice?
Sent from my GT-I9000 using XDA App
Mirasdad said:
Maybe a dumb question, but, do you overvolt as well as overclock? Maybe the cpu isnt getting enough juice?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
+1... not sure if there is much benefit at all to undervolting.. it just seems to make it immediately less stable...
can someone shed some light?
I've seen someone test this on another forum somewhere, and the difference the undervolting makes to the battery length is negligible..
kickassdave said:
+1... not sure if there is much benefit at all to undervolting.. it just seems to make it immediately less stable...
can someone shed some light?
I've seen someone test this on another forum somewhere, and the difference the undervolting makes to the battery length is negligible..
Click to expand...
Click to collapse
The principles of ovetclocking a PC also aplly to phones. Undervolting reduces the power available to the CPU. Undervolt a little and you'll save a little power. Undervolt.too much and the CPU won't get enough power to do basic functions hence freezing.
Every CPU has a limit to which you can over clock. You can overvolt to a point but then then the CPU reaches its limit.
From what I understand (read in another post) the hummingbird processors are not suited to overclocking. Where the arm such as that in the Motorola milestone clock really well. (You can oc a 600mhz milestone to 1ghz before you start seeing instability)
Hope this helped.
Sent from my GT-I9000 using XDA App
I understand the intention of undervolting as i am pretty good with PCs. Got my good old i7 overclocked constantly. But undervolting on the SGS has yet to show me any definitive advantages.
Sent from my GT-I9000 using XDA App
Related
Hi friends,
i´ve a little question about the OC/UV features of some
kernels like damiangto etc.
I know that OC means to overclock the cpu to a higher
mhz rate. But i dont understand what undervolt means?
Can somebody explain that to me?
And i would like to know how the battery drain is.
Thx
its quite simple really, as the name suggets its reduces the voltage applied to the cpu. Less volts = less juice used = longer battery life.
Ok ive understood. But does that mean that when i oc my phone, that i can uv it so the batterylife will be the same as before?
Sent from my GT-I9000 using XDA Premium App
Yes and no. Although everyone seems to be going on about battery benefits from undervolting I've yet to see conclusive proof it makes any difference. There is also quite a lot of trial and error involved in getting the phone stable with some undervolting.
I'd try it without undervolting.. see how stable it is and then try undervolting by 25mA each time on the higher frequencies before testing stability.
There's no guaranteed way of proving stability either, just try running lots of different apps etc and make sure it's not freezing or rebooting.
If I've made any gross errors of judgement feel free anyone to correct me
Sent from my GT-I9000 using XDA App
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Jusrertiner said:
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Click to expand...
Click to collapse
What is your desire to oc?
Sent from my Captivate using XDA Premium
Very risky
Very.
Yes it will shorten the life on your phone no way to know how much though. unless you are into it and read a fair amount about it i would not oc. The benefits just are not that significant
Sent from my GT-I9000 using XDA App
start at 1.2 if your scared
It will not shorten the life to the extent that it will not last the update period
Miui Captivate
Oh well how long do u think it will last. N I want it for the extra speed in games mostly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
If you want some extra speed, still to 1.2 and below and try using Pimp My CPU to drop the voltage -50mV across the board (try messing around with it more to get more drops without charge deaths and etc). By doing this, I am running mine currently at 1.2 ghz with a -100mV voltage drop, which is the same as stock 1.0 ghz voltage level.
It's overvolting that kills a processor, not overclocking. More voltage means more power for the processor to dissipate as heat and some components are not spec'd to take more voltage than stock.
I hope this helps.
I have read that you should be safe up to 1300mv(not mhz). Usually 1200 mhz will run that. After 1300mv, you risk damage. It also can cause charging issues (phone uses more battery than it is charging).
Don't get me wrong, at one point I had my phone up to 1500 mhz, just to check kernel stability. Didn't stay there. Also remember that each phone is different when it comes to this. Some phones tolerate it better than others. That is why entered no definitive guide to it, only recommendations.
You shouldn't be scared to OC. but its your phones processor because everyones is different. My captivate can only get up to. 1.5. Then it freezes up. My inspire 4g can get up to 1.9 without a problem while others can only get to 1.6 or so. So try it out
Sent from my Inspire 4G using XDA Premium App
I overclocked to ,1.3 and my while screen turn purple and green n I had to pull battery. Is that a crash?
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
Hello, Im new in Note, installed yesterday Slim Bean Rom and hydracorenirvana v7 OC kernel and I noticed that Note get warm, like 35-50 C while browsing internet or doing some low requerements stuff. I tried to low CPU to 1ghz but still the same... And while playing it jumps more then 50C, is that normal? I really dont want to burn it
Probably the media scanner is maxing the CPU, normal after installing a new ROM especially if you have a lot of files. Give it some time to settle down.
Sent from my GT-N7000 using xda app-developers app
+1
Dont forget the Hydracore is a maxed out performance kernel, designed for ultimate speed, so it will generate more heat doing basic things unlike the stock kernel.
and not to mention the massive power hungry screen and huge battery inside, its normal so dont worry about it. If it gets to the point where its too hot to touch, just remove the battery for 10mins and allow it to cool down.
Can I OC and UV GPU with hydracore kernel? I have S2 with dorimanx kernel , there is Stweaks app its very usefull when I can choose battery or performance profiles. and its auto OC and UV on that kernel. Can we get something on Note?
there are many apps that can do this, Tegrak, SetCPU etc, but be careful messing with voltages as it can prevent the phone from functioning.
You can use a basic app such as no-frills-CPU to adjust OC and governors.
azzledazzle said:
there are many apps that can do this, Tegrak, SetCPU etc, but be careful messing with voltages as it can prevent the phone from functioning.
You can use a basic app such as no-frills-CPU to adjust OC and governors.
Click to expand...
Click to collapse
Yes, I know setcpu, but I want OC / UV GPU not CPU. On my S2 via STweaks I can OC/UV also GPU.
Ok, now Im on jellybam woth "voldemort" kernel and on battery it looks little less warmer but when I charging and try to play games or browse it gets really hot, like ~55C . Is it normal and not damage my Note? Also I always use 1ghz cpu speed. with 1.4 or 1.6 ghz its little bit warmer
55 is ok. No issues
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
55 is ok. No issues
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
What is highest temp that it could be and its not bad for phone.
My record was 56 C. Do I win something
Abagnale said:
My record was 56 C. Do I win something
Click to expand...
Click to collapse
my record was 59C
scorpio1991 said:
my record was 59C
Click to expand...
Click to collapse
I guess you're the champ here
Abagnale said:
I guess you're the champ here
Click to expand...
Click to collapse
maybe and temp like this was on 1ghz cpu
when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Unfortunately you can't fix it. The overclock ability of the cpu is different in each phone. Some x8 can run on 800+ MHz, some can't reach frequencies over 700MHz. Basically the SoC (the cpu, gpu, dsp and some other device) contains millions of transistors, but the whole chip is only ONE small piece of silicium, the transistors made by litographic and other complex (and expensive) procedures. The overclock ability depends on the material quality (damages in the silicium structure), soldering quality between the core and the casing, etc. So, no existing rules to the overclock, if you lucky you can reach high frequencies, if you unlucky you can't overclock.
Note: under the manufacturing procedure the chips get a selection after testing, the highest quality 7x27 chips marked and sold as 7x27T with default 800MHz.
There is an app in the market called No Frills CPU Control: https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU
It will automatically change your CPU frequencies during boot to save your phone from hard bricking.
Anyway CPU gets overheated by overclocking as more amount of power comes in to it than what is required. So as a long term effect your CPU will die out and also your Battery too. So I would say to use a faster rom and dont overclock the CPU to very high frequencies.
paulebe525 said:
when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Click to expand...
Click to collapse
You are using stock kernel?
Overclocking more than 729 is not possible for stock kernel...
Use "set CPU" application & remember to uncheck "set on boot "option
# I couldnt over more than 729 in stock kernel but now with nAa kernel in can overclock up to 787 mhz
sent using" ultimate - ics - standard"
I Overclocked to 748 MHz on stock kernel....
Without any problem
sent from my W8 using client-server technology
governer also matters, I always use smartassv2
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
mujeeb999 said:
governer also matters, I always use smartassv2
Click to expand...
Click to collapse
I use
ondemand [email protected] [email protected] & using CPU under volt too
not very smooth but I don't care about smoothness
CtrlAltDelIrl said:
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
Click to expand...
Click to collapse
I tried it , it's not that much good:/ plus it have so many bugs with alfs kernel.(brightness bug for example)
I compared it with iXperia 8s rom before, froyopro is better @ one of 3d tests(just 2 fps better)
Other test were like iXpera & minicm7
Remember it's froyo & they are ginger ,they can run newer apps .
My opinion iXperia is our best rom till now
sent using" ultimate - ics - standard"
I use over 800 on CPU with smartassv2 with baa kernel
Sent from my E15i using xda app-developers app
senci00 said:
I use over 800 on CPU with smartassv2 with baa kernel
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
baa kernel , what the....?
Sent from my E15i using xda app-developers app
Mockingbird said:
baa kernel , what the....?
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
He means nAa kernel
Dictionary has changed the word , but wait why nAa is not in dictionary? It's super popular
sent using" ultimate - ics - standard"
CtrlAltDelIrl said:
As someone wise already stated, better using something like FroyoPro which is blazing fast compared to any GB rom instead of overclocking.
I can do more with FroyoPro than anyone running GB, ICS or JB roms.
It's just simple - lighter code takes less cpu cycles therefore it is quicker.
GB, ICS and JB roms really are a waste of time once you've tried FroyoPro.
The other roms are really only good for proof of concept - not for everyday usage.
Click to expand...
Click to collapse
I don't like the UI..otherwise I tried it and it sure was great.
Sent from my E15i using xda app-developers app
..
paulebe525 said:
when i use 729 or above my Cpu stops working and its Reboot automaticaly any way to fix
Click to expand...
Click to collapse
It also depends on the kernel you are using..Alfs is better in this aspect..but too much overclocking is not recommended.
if you are using custom kernel ,under CPU settings, select the frequencies you desire and do NOT select "Set on boot" . Even if your phone gets rebooted due to overclocking the default values will be applied at boot. This way you can avoid problems.
My X8 supports upto 787MHZ on nAa .
Hit thanks if i helped.
Just out of curiosity so upto how much can i overclock my awesome x8??
So far i've been to 729MHZ
Bunny2rock said:
Just out of curiosity so upto how much can i overclock my awesome x8??
So far i've been to 729MHZ
Click to expand...
Click to collapse
It depends on the kernel you are using..some people here overlocked @800Mhz successfully while my X8 got settled only at 787Mhz. Try yourself.
its nAa N is next to B ;-D
At 787hz doesn't restart
Mine work at 787 hz smoothly,,,,it restarts rearly...remember to have an app advanced task killer ...and set its setting to auto kill after screen turns off..Also set it to crazy kill....
Hope it will help you....
If I helped you,,,,don't forget to press thanks button..:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
please read 2nd post by pilu. that's the best explanation. it's a hardware limitation, and it does NOT depend on the kernel.
[cAs]
Partially depends from the kernel too. The cpu clock is not only a simple value: xyz mhz. In the kernel this is a little bit complicated (pll frequencies, dividers, multipliers, voltage level, etc). Different kernels use different frequency tables, the results can be different, this the developer choice who can set different bus speeds (axi, ahb), base pll, voltage to every clock speed. You only see the frequencies in the different kernels, what is same, but the same speed maybe generated with different method.
So, the cpu overclock ability is 90% hardware limitation and 10% other things. Usually if you reach your own max speed with a kernel, the probability of higher speed with another kernel is small, the typical difference is nothing more than +/- 1 multiplier (+/- 19,2 mhz).
Sent from my E15i using xda app-developers app
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.