What are the noticeable downsides of over clocking nexus 7 to 1.7 ghz? I know I'll lose battery life, but what else.
Thanks
Sent from my Nexus 7 using Tapatalk HD
Get's so hot very fast when you are playing 3d accelerated games that it has to shut down and reboot.
You can introduce instability. Random reboots, freezes, lag, and complete hardware failure are all possibilities.
Sent from my Nexus 7 using Tapatalk HD
cpu recommended clock is 1.2 1.3 1.4 or max 1.5 per core, if you want performance, remove apps you dont use, use greenify and overclock gpu, overclocking gpu a bit may help you
In the old days "software can't damage hardware".
But the new days are here, where software controls things like: CPU/GPU voltage regulators, clock rates, usb charging currents, # of online cores, bad block mappings, etc.
Imagine that your processor "makes a mistake" in the middle of controlling any of those things - for instance, changing a voltage regulator setting.
Imagine that your processor gets locked in a tight loop as a result of some error and the kernel code that is supposed to service the emergency thermal throttle can not happen - even though the CPU(s) are still running - possibly overclocked at full bore with all cores online.
That's why najaboy said what he did - literally anything can happen - from minor problems such as the device seizing up and becoming unresponsive, all the way up to and including destruction of critical hardware components.
Now, random errors generally will cause the processor to fault (invalid instructions, for instance), and the most common result of this this will be a kernel panic, a tablet freeze, etc. This is the most probable outcome, statistically speaking. But that is no guarantee that a rare event won't happen to you.
But - as he said - anything is possible. And as you reduce the processor voltages ("under-volting") or increase clock frequencies ("over-clocking") the probability of logic errors increases. Remember that computers are built to be strictly deterministic - what happens when they depart from deterministic behavior is completely undefined.
good luck
bftb0 said:
In the old days "software can't damage hardware".
But the new days are here, where software controls things like: CPU/GPU voltage regulators, clock rates, usb charging currents, # of online cores, bad block mappings, etc.
Imagine that your processor "makes a mistake" in the middle of controlling any of those things - for instance, changing a voltage regulator setting.
Imagine that your processor gets locked in a tight loop as a result of some error and the kernel code that is supposed to service the emergency thermal throttle can not happen - even though the CPU(s) are still running - possibly overclocked at full bore with all cores online.
That's why najaboy said what he did - literally anything can happen - from minor problems such as the device seizing up and becoming unresponsive, all the way up to and including destruction of critical hardware components.
Now, random errors generally will cause the processor to fault (invalid instructions, for instance), and the most common result of this this will be a kernel panic, a tablet freeze, etc. This is the most probable outcome, statistically speaking. But that is no guarantee that a rare event won't happen to you.
But - as he said - anything is possible. And as you reduce the processor voltages ("under-volting") or increase clock frequencies ("over-clocking") the probability of logic errors increases. Remember that computers are built to be strictly deterministic - what happens when they depart from deterministic behavior is completely undefined.
good luck
Click to expand...
Click to collapse
So even if I lower my overclock to 1.5 it could still screw up my system, right?
Sent from my Nexus 7 using Tapatalk HD
nicetaco said:
So even if I lower my overclock to 1.5 it could still screw up my system, right?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Just don't run it that high all the time. Besides it's quick enough on 1.3.
Sent from my Nexus 4 using Tapatalk 2
Hi,
My LG P500 (Rocking 512MB!) has a custom recovery since february, now. Since then I've been switching ROMs a lot, the first being CM11 which I switched really quickly to CM7, rock stable and fast, still one of the best ROMs I've tested. Also tried CM12 (KitKat), AOKP, VoidForever and Oxygen.
Using Oxygen at the moment, being the lightest and fatest, really stable.
Naturally I've been playing around with CPU frequencies since february too which was really useful in the long run. Underclocking and underclocking, while I did not kept the LG overclocked 100% of the time.
I did more benchmarks and stuff on Oxygen, testing out more overclock frequencies stability - people complaining of fried CPUs are rare to my knowledge (Well, didn't read much), and anyway, I can now find the LG P500 for 30-50$ used. My LG starts rebooting from 787 MHz, so I generally can use 729-768 MHz for a few time. I always depend on which factors, how much times does it actually takes before the device reboot due to unstability/unstable overclock, which I would like to know why, the hardware logic behind the reboot.
729 MHz has been really stable since a long time - I don't know if it's just me, but I feel like the CPU might be weakening after all this time, if it's possible at all? Not sure. But it does happend that it randomly reboot on 729 MHz still, pretty rare. Doesn't matter thought, if the CPU happens to die, I'll just buy another cheap one I guess.
But what is the actual cause of these reboots, overclocking sure push the CPU more than it should, so in theory it shorten battery life, and CPU lifespan too, also produce more heat. Which makes senses that when the phone get too hot, it reboot due to a thermal protection, same thing goes for computers.
Still sometimes, battery isn't that hot anyway, 32 degrees? 30? I've never exceeded 40 (Which is really rare, while charging - at this point I stop using the phone for a while) Apparently, LG P500 does not support showing the CPU temperature, tried, no succeed.
So is the CPU going too hot in that case? I'm aware I couldn't do anything to, hm, make overclock more stable, impossible besides lowering the frequency, but I'm just curious, would just like to know the logic, why does the phone choose to reboot? Just simply crashing? Hm, may I ask, what causes this crash? Entirely hardware related, right? I've tested overclocking with different kernels, while Android 4.0 had a worse tolerance to higher overclock, doesn't matter which kernel, my device can never get above 768 MHz without an instant crash. Why is the crash instant ?
Would like to know the logic behind overclocking affecting stability, please. Is that explainable? Exclusively hardware crashing? Or hm, does the software report any kind of alert at some moment, I don't know?
(On a side-note, never managed to overclock my PC CPU, Intel Core i3-2350M Sandy Bridge, apparently locked. Not ready to do this (Not the same price value obviously!), just wanted to see if that was possible on my laptop and so, how. Never figured that out, well, doesn't matter)
Thanks
To the extent that flickering and low charging is related to Sony thermanager, here is the permanent fix for AOSP/CM based roms. While the idea of thermal manager is good and we should credit Sony for doing it, the implementation kind of s*cks. For example, the manager kicks in when CPU/GPU temperature rises to 44 degrees. Also, several triggers are set between 54-56 degrees. This is plain wrong, because 44, 50 and 55-56 are all perfect numbers for an active device and at these temperatures, thermal manager should not be active. I have adjusted trigger numbers so that there will be no mitigation until at least 60 and surprise surprise, all screen flickering is gone away....
Attached is thermanager.xml which should be put in /system/etc/ with 644 permissions. Reboot is required. UNZIP FIRST. Also, backup your current file just in case.
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
sgspluss said:
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
Click to expand...
Click to collapse
Any touch issues related to thermanager kicking in early could be resolved. But lollipop has overheating issues related to art, which can't be solved by thermal management. That's why strictly speaking, lollipop has to be recalled. In my view it can't be fixed.
A little question
Hello optimumpro
I only need put the thermanager in the path system/etc to make it work? or need something else?. Sorry by the queastion I noob an recently I repair de display and touchscreen for my xperia z1 C6902 and a have the flickering problem.
Thanks for your help.
optimumpro said:
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Click to expand...
Click to collapse
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
This works for me!
before flash this file, my Phone only receives 90ma from any changer, and now reciving 1080ma. Thanks a lot!
Room: Ressurection Remix
Android version: 5.1.1, Xperia Z1 C6943
Sent from my Xperia Z1 using XDA Free mobile app
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
Sent from my C6903 using Tapatalk
agha_jo0n said:
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
View attachment 3434889
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I don't think that app is accurate tbh with the fix it says no higher than 300ma for me and my phone is charging pretty well I'm using 2100ma charger as well
Sent from my Xperia Z1 using Tapatalk
Sorry bro but i don't have this file in system /etc??? Wtf???
ninjasoft said:
Sorry bro but i don't have this file in system /etc??? Wtf???
Click to expand...
Click to collapse
You are probably on kitkat. If that's the case, you don't need thermanager. If you are on lollipop, look again, the files are not necessarily in alphabetical order...
And remember, this one is for custom roms: CM and/or AOSP based. I just looked at your signature, you have stock...
zhuoyang said:
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
Click to expand...
Click to collapse
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
optimumpro said:
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
Click to expand...
Click to collapse
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
zhuoyang said:
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
Click to expand...
Click to collapse
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
optimumpro said:
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
Advantages of undervolting Android
Thank God for Android where we can easily modify and customize our lovely Android devices to the way we want. Being said this, undervolting is one of the biggest attraction for Android! Simply by undervolting an Android you will or might experience:
A longer battery life
More responsive smartphone
Less heat produced by the phone
Super-charge your Android to go further than what it can do (overclocking Android)
Click to expand...
Click to collapse
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
Note: UnderVolting is widely used as a cooling solution and in my opinion more effective than any other cooling solution available for free. Results can will show decrease in the temperature of smartphone. I recommend undervolting to anyone with enough confidence and knowledge to do so. The benefits easily outweigh the risks. I dont see why one shouldn’t do this for a cool and better smartphone experience.Undervolting will NOT compromise performance at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1956346
Undervolting is actually a very good thing for your smart phone when you do it correctly. Undervolting has one major positive effect on your CPU: it will extend the life of your processor by allowing it to do demanding things with lower heat generation
Click to expand...
Click to collapse
zhuoyang said:
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
http://forum.xda-developers.com/showthread.php?t=1956346
Click to expand...
Click to collapse
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
optimumpro said:
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
Click to expand...
Click to collapse
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
zhuoyang said:
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
Click to expand...
Click to collapse
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
optimumpro said:
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
Click to expand...
Click to collapse
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
zhuoyang said:
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
Click to expand...
Click to collapse
"I am not attacking you" Yes you were, I said that some bloggers don't know what they are talking about and you replied that I didn't know what I was talking about. Anyway, I accept your veiled apology.
Neither overvoltage nor undervoltage makes the phone cooler. There is an optimal regime for each cpu and if you go outside of it (in either direction), you are inviting trouble. You are not going to destroy your cpu by either under or over voltage, as there is protection in kernel. The phone runs cooler when cpu works less and the optimal regime causes the cpu work less. If you are reducing juice (voltage), you make cpu work longer, which results in overheating.
I gave you an example of performance governor to make a point that this is counterintuitive: while cpu is set at the higher frequencies, it actually performs the tasks and rushes to idle faster, which results in cooler condition. When the same cpu is set lower (and especially if it is under volted), it works longer, jumps to different frequencies, plugs/unplugs cores, which all contributes to overheating....
What is normal values for this phone ? I have diferent chargers, Samnsung - around 600mA, one HTC - around 400mA and another one with 200mA according to that app. Wich one should i use ? So far i used samsung one because it charges fast...2 hours or less, but the battery dies also fast ....so it may be because of the charger ?
So I've been following this section for months and just got my a2017u 2 weeks ago. I'm rooted with tenfars tool still locked on b20. I've noticed in the last few weeks a tapering off of new and useful info for this phone and would really like to see what and where everyone is with it? LSpeed? Kernel Auditor? Or any tweaks that have helped either performance or battery life!!! Looking for anything to make this already great phone better!!! TIA
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
aPexalpha said:
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
Click to expand...
Click to collapse
Overclocking can't really harm anything. The excess heat might but it would take a long time and really high temps (you couldn't keep the device in your hands). The only thing you risk by overclocking is a system crash. Just reboot, lower the clock values and voilà ! So no, underclocking can't hurt anything. Overvolting however poses a real threat to the integrity of the components. It's quite the same thing as in computers (except for the heat, you don't always realize it's too hot in a computer).
That being said, is overclocking still even possible on smartphones nowadays ? Just for the fun of it because it's not needed in the least on the Axon 7 .
That's impressive results ! Not sure those hours are needed since the battery is doing well with the software power saver but still a good thing to know.
Still any extra sot is welcome. I'm not a gamer, don't really have any apps that truly need the full power of the sd820 so might give it a shot. Greenify does wonders for standby time.
Not sure if the built in 'intelligent country control' does anything tbh
I'm on my phone most of the day whether it be YouTube play music, texts,calls,etc.. I'm just hoping to find a balance between battery and my multitasking ADHD LOL
Nik2424 said:
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
Click to expand...
Click to collapse
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
aPexalpha said:
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
Click to expand...
Click to collapse
Yup, I had that problem too initially.
First, I made system changes persistent upon reboot by running this command in Terminal emulator(you can also use adb shell):
reboot disemmcwp
Secondly, you have to disable smart power in the quick toggles.
Once this is done, set your new max values, select the arrow next to it to make it applied on every boot and then reboot your device. It should work.
Note: Everytime you open the EX Kernel manager you will see the speeds jump to max for like 1 sec but if you actually check the cpu statistics you'll see that your settings are sticking and the max clock speed was just for everytime you open the app.
The smart power! I forgot that thing controls the CPU.
So that round arrow thing means apply on boot? I selected that, figured it meant something like that.
Cheers!
Hi there,
Is it possible to overclock the cpu and gpu?
If so how? Or which rom/kernel?
Running G model 4gb ram
Even if you can, it will chew the battery and heat up.
RobboW said:
Even if you can, it will chew the battery and heat up.
Click to expand...
Click to collapse
Not a problem as I would only be using it sometimes not permanently
Kendal21 said:
Not a problem as I would only be using it sometimes not permanently
Click to expand...
Click to collapse
in theory it is, we had a a kernel that OC'd the CPU way back then, but the SoCs on the Axons are probably low-binned - shutdowns and stuff like that are commonplace
But still, do you know what OC does to a phone? New phones are thermally constrained devices, starting from the snapdragon 800 series onwards. remember the sd805/810 disaster? Well...
If you run your phone at 100% load, it will run at max speed (1.56/2.15) for a very short time (say, 30 seconds), until the SoC reaches a specific temperature. After that it'll go down to a more manageable frequency, eventually going even further down or staying at 1.8 ghz, depending on your specific situation (the pink thermal blob might be bad).
That's why VR mode sets your cores at around 1.8 ghz, to keep them from going hot and lowering frequency even more. Sustained performance is better than burst performance on gaming.
Day to day usage is another matter, because more frequency won't mean thermal throttling when opening apps or unlocking the phone, beside the obvious battery usage
TL/DR: Be prepared to make your own kernel if you want to OC. It might not work