Database Info

Overclocking / Underclocking

either with setcpu or voltage control...would someone care to just explain how to use these apps.
I understand the governers, and I understand the min / max.
So If I bump that max up to 1400 or even 1600 and leave the minimum down...what exactly does that do?
If paired with on demand does it mean it will use as much processor as it needs to perform a task all the way up to the max of what I have it set to?
also, the thing that seems to confuse me mostly are the individual sliders you can adjust per frequency.
I know this is broad question, but I was just hoping someone wouldnt mind explaining this to me as best as possible...or at least dumb it down for me.
I have googled and searched, and really havent found clear answers to me personally to understand it.
thanks

I personally use voltage control extreme.
In regards to the individual sliders you speak of, I believe that those control how many volts the phone uses at each particular frequency. You don't want to turn the voltages down too low/high though because you can freeze your phone and have other problems.
I use the "conservative" governor and seem to get the best battery life with it.
By overclocking to 1400 or 1600 it allows for your phone to run applications, videos, etc. smoother, by using the remaining cpu capabilities of the phone's hardware. The drawbacks of overclocking are that it sucks the battery very quickly, it can cause the cpu to overheat, and can also decrease the life of the processor.
Hope that helps some!

So what is a safe top end? To run on a daily basis.
Sent from my SAMSUNG-SGH-I997 using XDA App

Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App

Perpetrator said:
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App[/QUO
But doesn't overclocking cause the phone to heat up? I suppose it also depends on what temperature the phone is rated to safely run at too though doesn't it? Cause with increased temperatures I am pretty sure the processor's life could be impacted. But that is probably only if you overclock for a extended period of time.
I would suggest staying at 1.2 for daily use, but if you are doing something that requires a little more cpu you can just bump it up until you don't need it anymore.
Just my 2 cents worth.
Click to expand...
Click to collapse

I know that some ppl OC to 1.6 with ondemand gov and use that as a stable setting... others report problems, FCs, ... think it depends on individual phone.
Some stay at 1.4 to be cautious...
The UV section is where I hear a lot of dissenting opinion. Some say -100 across the board gives best battery/stability... others say voltage should be high toward 1600 and UV more as you approach lower frequencies... personally I find that a graduated setup is best but I am not an expert.
Just sayin' what I've read here.

[Q] overclocking droid charge

How can I go about overclocking my droid charge? I am running TWEAKSTOCK 1.0 rom and was wondering how to overclock my charge?

I haven't seen any over clockable kernels so until then I don't think you can.

Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App

Chitala383 said:
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
With the same kernel?

Well, if you actually searched, this would be clearly stated in many threads.
For GB overclocking, use Tegrak for now, until we can get an actual OC kernel up and running. I think Tegrak will work on the stock kernel as long as you're rooted, as it uses a module to modify the CPU frequency.
Sent from my SCH-I510 using xda premium

Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App

xdadevnube said:
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?

BattsNotIncld said:
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
Click to expand...
Click to collapse
Take what I say with a grain of sand, I'm expressing my views without much scientific validation.
Keep in mind that overclocking is like icing on the cake. There are far more beneficial things like changing the scheduler to noop or deadline. Fugu tweaks and V-6 are highly recommended to improve responsiveness and improve your launcher resiliency. That said, I feel overclocking has its place and helps in many cases. I've noticed, in general, various tasks and some web-browsing will benefit from the increased clock speed. Some things don't ramp up the CPU very much and you won't notice much difference in that case.
I monitor my CPU usage with CPUNotify as well as OS Monitor.
I monitor the CPU temps with TempMonitor (it allows for a notifcation icon that shows the CPU temp.)
I use StabilityTest to check for overclock settings stability. The cool thing about Tegrak is that when you apply overclock settings on boot (paid version only) and you choose settings that crash the phone, the settings don't apply until most of the phone is already booted up, so you aren't stuck in an infinite boot loop of crashing fun. You should be able to simply change up the settings after they apply since the phone will be mostly idle by the time Tegrak settings are applied.
As for settings...
I use the Interactive X governor. I prefer this governor for its simplicity and ability to ramp up to high CPU clock speeds quickly. I enable the governor by typeing "su" and "ix enable" in Terminal Emulator when on Imoseyon's 4.0 kernel.
I change the "scaling min" to 200Mhz to avoid instability when CPU usage ramps down quickly.
Currently at CPU Level 0 I am at 1265mv Core Voltage, 1100mV (unchanged) Internal Voltage, and 1200 Mhz Frequency.
I don't actually change other CPU Levels.
Lately I've been just keeping at eye on temps so I haven't achieved my desired clock speed of a relatively low-voltage 1.4Ghz to 1.5Ghz.
Overclocking is very dependent on the particular sample you get. Some of us have "Golden Chips" and some of us have duds.
Your CPU should be totally safe at temps around 130 degrees F, although I suspect that it could even take higher sustained temps well above that if it needed. I don't actually know, this is speculation.
I like to keep my temps low in general, I rarely crack 100F with my current settings (weather is cool here.)
Overclocking computers is one of my hobbies, and its fun to dive into the phone side of things. I haven't been able to find a whole lot of information regarding overclocking the Hummingbird processor. People have overclocked to 1.6Ghz. Stability tests are essential to improve the reliability of your overclock. Die hards will run the tests for 24 hours to weeks in the computer realm. At least with computers its better understood how the stability test actually works. I run 24 hours of Orthos blend mode (Prime95) on each core.
With phones, its hard to say if it will truly be stable.
I test for an hour on the phone with StabilityTest and call it good. Hopefully in the future more information will come to light regarding how to properly overclock.
Remember, the other side of the coin is underclocking and undervolting. If you drop your voltage, you should see a nice increaes in battery life. If you drop your clocks, then you can drop your voltage even more. If you get your phone dialed in to where there isn't much background apps sucking juice- a phone that is UV/UC'ed should have excellent battery life.

Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium

kvswim said:
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.

xdadevnube said:
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
Click to expand...
Click to collapse
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium

kvswim said:
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.

xdadevnube said:
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
Click to expand...
Click to collapse
Probably because no one has taken the time to write one. Not exactly in high demand. I knew of one "guide" but the site has been down for quite some time.
Of course there are noobs guides but nothing quite in depth. I suppose people don't write them because there are obvious limits set by the kernel dev, and anything beyond that requires someone who obviously knows what they're doing, which defeats they purpose of a guide.
Sent from my GT-P1000 using xda premium

CPU Freq: How do you keep yours?

This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk

that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.

ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to

so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.

AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.

yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.

Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.

On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.

pros and cons OC/UV

about time for me to change roms again. i know there are many with this option, but have never chose to pursue that option due to lack of understanding benefits. always seemed to get satisfactory battery life out of phone, but could it be better? i have noticed different speeds on my phone with different roms but is this something that can speed up and keep the smooooth in my phone?
just thought i would get some feedback of the advantages and disadvantages of overclocking and undervolting.
will it harm my infuse?
what are good settings?
what exactly would the OC or UV each do?
if i run a search on this, i know i am going to get the phone book and just figured i would get a more specific answer directly as opposed to piecing little bits together and still not being confident in what my interpretation would be.
everyone in the infuse community always seems to have the answers and dont steer the dullards such as myself in the wrong direction.
you guys are the MAN, and well, you women.....your the woman i reckon

captemo said:
will it harm my infuse?
Click to expand...
Click to collapse
No, so significant damage can be done with overclocking. Alhought if you set your ghz too high your phone might become unresponsive, overheat and/or auto reboot your device. This is normal if your on GB and some ICS roms. Don't see it much on JB becuase the some kernels dont support it. Just be sure to play with your settings and MAKE SURE SET ON BOOT IS DISABLED or else your phone will be stuck in a bootloop when overclocked beyond stable settings.
captemo said:
what are good settings?
Click to expand...
Click to collapse
I usually stick with 1400 ghz because 1600 ghz[max] drains battery too quickly for not much of performance boost and 1600 is considered unstable on most GB and ICS roms. As for CPU governor Id stick with ONDEMAND.
captemo said:
what exactly would the OC or UV each do?
Click to expand...
Click to collapse
OC is over clocking your processor to a higher ghz for better perofmance and under volting is drawing less energy

Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2

Garen21 said:
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1420742

I used to under volt a lot to get better battery life. But it seemed to make a couple apps hang now and then.
I am now on Scotts PA JellyBean ROM. Battery life is very good for me stock with this. So I have left under volt to stock settings.
Normally I'll run on smartassV2 governer. With NOOP i/o. And 100mhz - 1400mhz.. just for a little extra boost.
When I know I'll be playing a game or multitasking, I'll boost it to 1600mhz.
Overall stock settings run amazing, both battery life and performance, on Scott's PA JB and CM10.
After doing some reading, I believe I can get better results from using the above settings. It all depends on what your personal goal is.
The biggest concern you should have when overclocking is mentioned above. Boot loop, just make sure you test it for a while with set on boot un checked.
Undervolting you can go to low and also boot loop, so same applies here... leave set on boot un checked. All phones are different on what settings they run best at. Just gotta play around and see what works for you.
A good rule of thumb for under voting... go down 25mv at a time and test it out... keep going down 25mv until you get a problem or boot loop and then go back.. then you'll know your max.
You can safely under volt more on the lower frequencies than you can the higher ones. Personally I never undervolted more than 100mv across the board. And when I did, I usually kept it around -50mv.
Sent from my SGH-I997 using xda app-developers app

not for infuse but a good reference for ocuv. explains what they do
http://forum.xda-developers.com/showthread.php?t=1827635
Sent from my GT-I9300 using xda premium

This is the best guide I've found covering kernel and system tuning - CPU parameters, governors, schedulers, init.d, loadable modules, etc. It's for the SGS2 (i9000) and some of the governors/schedulers are not available on the Infuse, but much of this is applicable to our phone:
http://forum.xda-developers.com/showthread.php?t=1369817
As for OC/UV, as long as you stay away from the "Performance" governor (this runs the phone at max freq all the time), and undervolting below -75 to -100 you generally will be safe. As phones are different, it is important to test in gradual steps to ensure your phone will be reliable. Use a good CPU manager, like SetCPU, Antutu, or Voltage Control. Make sure you enable the "revert to stock" feature so that you can boot recovery and turn off any bad OC/UV. As noted above, do not check the enable on boot setting until you are certain you have a good config.
The decision to OC should take into account how you use the phone. If your phone is asleep more than 80% of the time on average, you can probably run an OC config and still have overall good battery life (i.e. lasting an entire day with nightly recharges). If you use your phone for music playback or something else that prevents it from sleeping, OC may not be for you. If you run CPU intensive games, it is better to disable UV settings while OCed.
Use CPU Spy to keep an eye on your time at each freq state (and sleep). Use the default battery stats and graph to monitor which apps are consuming the most battery. Use apps like Better Battery Stats, Android Assistant and Watchdog for more detailed monitoring of what is keeping the phone awake and which apps/processes are top cpu resource consumers. With this information you can identify problem apps and decide whether you should remove them from your phone.
From the "unintended functionality" side of the house, there are certain tweaks that will cause your phone to run at max freq ... mucking around with phone properties in build.prop can lead to runaway rild process problems (usually shows up as unusually high "Dialer" in the standard battery stats list and a phone that is warm or hot to the touch). Some of the tweak scripts in adrenaline and tbolt can cause similar problems. There is a known bug in the infuse network drivers that shows up as much higher than normal Android OS battery usage. This can usually be corrected (short term fix) by toggling Flight/Airplane mode off/on. Running the stock UCLB3 GB kernel also seems to minimize this issue (assuming you are running a GB ROM), but flash with caution as you will need to disable voodoo lagfix first. (You will also lose CWM recovery, OC/UV capability, and be on the slower stock file system setup).

I have done a fair amount of experimenting including lots of time on conservative governor with Fmax=1600 and never had any problem that I attributed to OC'ing.
In contrast I did find a limit on UVing. I just updated my thread with my experience on uv here:
http://forum.xda-developers.com/showthread.php?p=32552571#post32552571
The bottom line is that for MY phone, the following works fine:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Some other links with others' experience suggestions about UV'ing for Infuse:
Hozw low is your undervolt?
http://forum.xda-developers.com/showthread.php?t=1693689&highlight=kernel
[Q] Recommended SetCPU settings?
http://forum.xda-developers.com/showthread.php?t=1292836&highlight=setcpu
You’ll note the last thread has comments from Entropy’s settings.
Also Zen and qkster gave advice in the first thread (my thread).
All three guys very well respected and worth listening to.
Entropy mentioned you can uv the higher frequencies more than the lower (different than what was posted earlier in this thread). I don’t know for sure but I’d lean toward Entropy’s advice on that matter.
I think all in all somewhere between 50 and 100 is the max you can expect to undervolt.
What can be achieved varies with phone as stated by many.
You are welcome to experiment with slowly decreasing. That's what I did.
But in the benefit of hindsight, the process of slowly decreasing is tedious. And going beyond the limit was a little scarey for me. Could've been worse if the phone crapped out at a critical time during "experimenting". Like almost everything related to battery life, the results (how much benefit) seem y subjective (difficult to measure quantitatively). Most people say they don’t notice a dramatic difference with UV. If you want to get the low hanging fruit without a lot effort, you might just try 50 down. That's what I'd do if I had to do it all over again.
By the way, setcpu can be set up to provide a failsafe escape route even if you go overboard. There is a zip file that will toggle the setcpu settings off when launched from CWM. You just have to put the zip file on your sd card before you start tweaking. See "safe mode" in the setcpu documentation.

started to wonder at first whether i would get any responses after 218 views and nothing, but i knew the community would come through as they always do. all the regulars as usual regulars ( Zen, Quickster and others) are always eager to help. i think you have all provided me with the valuable info i requested.
thank you much party people

Overclocking, kernel and governors

Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.

OC 806 can damage your phone for ever manage carefully this
Sent from my LG-P500 using Tapatalk

And what are the safest levels? And best governors? Im actually using smartass min 480 max 729

Overclocking will not "damage your phone for ever." Some of the P500s are stable at higher clock speeds than others, which is typical of mobile CPUs (even the two cores of my Sensation's CPU are stable at different maximum clock speeds). IIRC, my Optimus T was only stable up to 729 MHz. If you try to overclock higher than your phone is capable of, then it will freeze or reboot. There really isn't a "safest" level; any clock speed that your phone is stable at is going to be perfectly safe. Run a stability test or benchmark app from the Play store to check stability. IIRC, another easy way to test stability on the P500 is to open a camera app. The camera tends to crash the phone when the CPU is clocked too high. If you manage to crash the phone by doing any of that, then I recommend dropping down to a lower clock speed. Otherwise, the phone is fine and you can test a higher clock speed. FWIW, I'm pretty sure that most P500s are stable up to 729 MHz, but many of them are not stable higher than that.
I personally like to use Interactive governor. I think I used Interactive with min 480 and max 729 on my Optimus T. Governors Explained

chalo99 said:
Hi, I have some questions with kernels, overcloak and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
1. I use smartass as governor (well on the jenkins build). It has a balanced battery and performance I think.
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
3. Well overclocking on android depends on the ability of the kernel to handle overclocking situations. Some kernel can handle overclocking very well that the noticable errors are up to a minimum level. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
5. Before, we use to have different kernel developers and different rom developers. as the the passed by and newer devices are being developed, some migrated to newer devices and abandoned the development for our beloved phone. Now I think only 1 developer is still developing (original development not just cuztomizing and stuffs it with design) androidmeda (check "jenkins armv6") and the kernel included in the rom is sufficient enough to handle overclocking (used it and set the freq to 320 - 710 at smartass). I also use sweetnsour's kernel before but i think he too abandoned the development)
5. k

engr_exxi said:
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
Click to expand...
Click to collapse
That isn't true. Processor manufacturing is inexact, so some processors end up with higher clock speed capability than others. As the maker of a device, you have to set the clock speed low enough that ALL of the processors in ALL of the devices function properly. Setting the clock speed conservatively means that most or all of the devices are actually capable of functioning at a higher clock speed, which in most cases -- and certainly in the case of the P500 -- is completely safe. And it is extremely naive of you to believe that every processor or computer you buy is running at the "best and safest" speed as tested by the manufacturer. CPUs are often significantly underclocked simply to allow manufacturers to differentiate pricing. The same thing is done with finished products, including smartphones. For example, my HTC Sensation has a Qualcomm MSM8260 clocked (originally) at 1200 MHz. The HTC Sensation XE has the exact same processor clocked at 1500 MHz.
3. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
Click to expand...
Click to collapse
Again, it is nonsense to say that overclocking this phone "is not really safe." You won't find one example anywhere of a person who has damaged this phone by overclocking it. These things don't get hot enough at any clock speed to damage the hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
Click to expand...
Click to collapse
4.a. Heat is probably the only legitimate concern with overclocking a smartphone, and that's exactly why there is no risk with the P500 -- it doesn't get anywhere near hot enough, at any clock speed, to cause any damage.
4.b. This shouldn't be a problem. If your phone is not setting clock speed on boot, then a crash/reboot will send your phone back to the original clock speed. Even if you make a mistake and change a clock speed that is being set on boot (which I actually did by accident just yesterday), you can boot directly into recovery and restore a backup.
4.c. Who cares? As I said before, if your system is unstable as a result of overclocking, then you should lower the clock speed. That isn't a problem.
4.d. *sigh*
But to each his own. If you don't want to go "yolo" with your antiquated $50 smartphone, then by all means, keep it at 600 MHz. Nevertheless, there is absolutely no way that you would damage it by overclocking, regardless of what you may believe.

Well, its overclocking and not overcloaking.
Small error, but make changes in the OP

rhar**** said:
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
Click to expand...
Click to collapse
I wrote it bad in the title, but in the middle of the post it was OK. Thanks anyway, ****ing spanish that you read it like you write it, or viceversa.

chalo99 said:
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
The phone won't work above 729MHz. And the only risk i can thinknof is depleting battery life faster.

Im actually using interactive min 480 max 806.
That permit no lag and normal reactivity.
Obviously there is a battery drain than normal.
I've also use a seeder application.