Database Develop

To OC or not OC, that is the question

hi folks, thinking about leaving oc on permenantly (1200 mhz) I an aware of the dangers, but thought about getting some facts, my question is, how long have people been running art 1200 mhz without any issues, how many weeks or months?
Sent using TCP/IP

1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.

dhiru1602 said:
1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.
Click to expand...
Click to collapse
my phone spends approx 20% of its time at Max freq, thats 1/5 th of its time. I think there would be more potential damage than a computer cpu as these have much better cooling (fans), I just want to know how long people have run at say 1200 without any issues.
Sent using TCP/IP

Longest time: two weeks ... whitout problems ...

I'm been overclocking my SGS for over 6 months now, no issues at all.
"Standard" voltage values seems to work fine on my device (1350mV at 1200MHz, 1400mV at 1300MHz) but I've tried to undervolt a bit more than once and had no issues as well.
Bye

There are absolutely no dangers in OC/UV. The worst thing to happen is a freeze or reboot once in a while if u go too high. I've been having 1.5mhz w/ some UV for like 2 months and nothing happened so no worries.

Been doing that for about a month now. No problem.
Knowledge is Power. Guard it well.

there are no risks if you overclock your device,but of course depends on how you do it. first of all i would not go past 1300mV which is the physical limit of our beloved hummingbird..of course you can do that,but past 1300mV you are going to shorten the life of your CPU. if you change phone every year then,there's no problem
then if you want to overclock keeping safe voltage values just get Tegrak Overclock,don't activate the "CPU MAX frequency" option,go in optimization tab instead and push up the max frequency by little steps keeping the voltage at the default value of 1275. test it a bit till you reach the most stable one. for example my CPU it's totally rocksolid 'till 1132MHz at 1275mV,no more. but there are CPUs which can archieve better results. then if you want to optimize and save battery consumption you can play a bit with UV on the other frequencies,cheers

[Q] OC/UV settings for battery life

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

[Q] Undervolted

I've undervolted my device and right now I have
100mhz - 825 mah
200mhz - 825 mah
500mhz - 800 mah
for some reason the 500mhz setting is stable and if I undervolt 100mhz/200mhz even more, I crash.
If I set my minimum processor power to 500mhz would I consume less batter than if I were to use 100mhz/200mhz?

Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels

Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.

Maskell said:
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Click to expand...
Click to collapse
It's been my minimum even before posting this thread. I just started to wonder.
I've been on it for 10 hours now. I have 45% battery life left. Probably due to my 1700mhz being @ 1350mah right now.
I can assure you, it's VERY stable. It's so SMOOTH. Smoother than just having rocketrom and all that stuff. NO LAGS, NO SHUTDOWNS. ALL STABLE.
I can see better battery life, and CPU Spy says it used up 47% 1700mhz and 40% 500mhz. I think it's giving me better battery life.
It's evenly splitted up probably because I was using lulzactive governor.
but then again I didn't log my previous battery life without undervolting.
Some more insight would be nice.
SweCrow81 said:
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Click to expand...
Click to collapse
There are alot of risks. Minor chance that you will cause hardware damage to your phone but I'm saying VERY minor. Just don't be stupid with voltages, like just suddenly overdropping the voltages. Your processor might die.
It's scary as hell, it crashes alot while testing and all that ****.
Feels good when you get it stable though.
TL;DR
Very slight chance to damage your hardware; only if you're very daring.
It should increase your battery life by atleast 20% if you reach the peak of your processors limit.

Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help

clairenix said:
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
Click to expand...
Click to collapse
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest

kaos_king said:
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
Click to expand...
Click to collapse
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?

clairenix said:
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
Click to expand...
Click to collapse
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.

I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.

kaos_king said:
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
Click to expand...
Click to collapse
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
liutszho said:
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
Click to expand...
Click to collapse
It's basically the same with SetCPU aside from its voltages.
I do not know if it should be used with SetCPU with the note because from what I've researched. It's only a common practice with SGSII.

Tried setting 100 and 200 mhz to 825. Crashed my phone twice in one day using it, gonna revert back to 875

clairenix said:
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
Click to expand...
Click to collapse
Many thanks!
I will just experiment then, i didnt want to do that and then cause hw damage. I'll let you know how my processor gets on

OC and Battery questions

hello,
im just wondering first of all whats the best speed to OC without permanent damage. I have done over 900 Mhz but I will get maybe 1 or 2 reboots a day so I went down to 864Mhz and its been smooth no problems. but what do you think is best to use.
also taking the first question to mind, what governor and i/o settings should I use to give the best balance between battery life and performance? I have tried smartassv2 and the battery like suffers.
Please give me your opinion for what is the best combination for my phone

Well first of all you can't have both performance and battery life.
If you are after performance go for 883 ( I think. I don't exactly remember the freq so forgive me for that) or what you suggested yourself (864) and set the governor to interactive and min frequency to 245. Personally I would set the governor to performance and Max frequency to 864 min 245 though it may sound crazy but that's my settings, phone doesn't get as hot as it used to battery life has kinda increased actually well if you think about it you will see that your phone will complete a given task in a shorter time and therefore ...
If you are after battery life then don't think about over clocking. In fact you might wanna under clock to certain level.
Sent from my GT-S5830 using xda premium

Overclocking the Nexus 4 - Benchmark of application load time = BIG difference

A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.

please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings

so overclocking makes things faster.. really? who would have thunk. and you just found this out?

my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.

zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.

So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?

well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?

sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **

gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **

If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.

No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.

zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100

is there any kernel that can overclock with 4.3?

Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:

simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?

Check the Development sections.
This thread makes my head hurt.