Database Info

Overclock GPU

Hi there, is it possible to overclock GPU?

i guess on most devices overclocking DOES overclock cpu and gpu at the same time

elgubbo said:
i guess on most devices overclocking DOES overclock cpu and gpu at the same time
Click to expand...
Click to collapse
i don't think so bcs they are different hardware parts and when you overclock cpu it is sth about cpufrec but yeah when you overclock cpu it effects graphics too bcs it makes processes faster ...( i just think like that bcs of being a linux user open source foreveeeeeeeeeer )

If we could overclock the gpu on the android then the android would take over the world

kifno said:
If we could overclock the gpu on the android then the android would take over the world
Click to expand...
Click to collapse
android has already became a legend by being the first os in USA(Apple's IOS is losing users. )

So it is still impossible, right?

kanek06 said:
So it is still impossible, right?
Click to expand...
Click to collapse
i think it is possible ( when i think that they are like little computers) but i dunno how to do it.

to start, youd probably want to dissect the software driver and see what it offers.

Well, when we will able to overclock GPU - we should not buy new and new devices, because our present devices are old. But how about temperature? Will battery get hot like in overclocking CPU?

well, from what i understand the gpu for most devices shares space with the cpu on dye and that there is a divider of sorts that keeps the gpu speed a percentage of the cpu.. and since cpus can oc better then gpus, the whole reason we can oc is due to the fact that devs have figured out how to uncouple the clock increase of the cpu from the gpu, otherwise the gpus clock would limit the cpu.. now overclocking itself doesnt increase heat and most of the time (depending on what governor is used) it doesnt always run at full clock so theres not a high constant current drain causing the battery to get hot (unless you run an intensive app continually) also, you wont see the cpu overheat as long as the voltage stays stock, but increasing cpu voltage is how you will get past the th max (thermal maximum)
now if you could adjust that divider you could oc the gpu..

[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

[Q] - Overclocked kernels - What's the point ?

I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?

Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium

I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!

I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2

You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?

i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on

tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.

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.

Can different kernels help increasing battery life?

Hi
When flashing XtreStoLite Aroma Installer I can choose 4 different kernels.
Right now i'm on "stock" XtreStoLite Unikernel, but is it a possibility that the other kernels will increase my battery life?
Which kernel available right now would you guys say is the best when looking from a battery perspective?
Thanks in advance

Faspaiso said:
Hi
When flashing XtreStoLite Aroma Installer I can choose 4 different kernels.
Right now i'm on "stock" XtreStoLite Unikernel, but is it a possibility that the other kernels will increase my battery life?
Which kernel available right now would you guys say is the best when looking from a battery perspective?
Thanks in advance
Click to expand...
Click to collapse
If they can undervolt but your device can get unstable undervolting, mine always have but maybe I have been unlucky with my socs

I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.

godutch said:
If they can undervolt but your device can get unstable undervolting, mine always have but maybe I have been unlucky with my socs
Click to expand...
Click to collapse
vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance

Faspaiso said:
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance
Click to expand...
Click to collapse
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....

Faspaiso said:
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance
Click to expand...
Click to collapse
godutch said:
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....
Click to expand...
Click to collapse
In the specific case Simpl kernel is bundled with the Synapse kernel tuner app, which has a failsafe mechanism related to undervolting. After every restart the voltage settings are applied and after X minutes, if there is no reboot, they are marked "safe". If you get too low and have problems before you reach those X minutes, Synapse will not apply the voltage settings, allowing you to make the needed changes.

vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
godutch said:
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....
Click to expand...
Click to collapse
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.

Faspaiso said:
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.
Click to expand...
Click to collapse
If you see frequent reboots you know you have undervolted too much

Faspaiso said:
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.
Click to expand...
Click to collapse
When unstable also can cause your phone to freeze and lock up. You could run stress tests for each frequency if you really wanted to go the extra mile. Usually I lower by 5mv for all steps and then when i start noticing weird behaviors I increase by 5mv and call it a day.
Lower frequencies can only go so low, so eventually you'll just be decreasing the high freq steps. Just like a computer, youll need a high enough voltage to keep the phone stable.

godutch said:
If you see frequent reboots you know you have undervolted too much
Click to expand...
Click to collapse
tlxxxsracer said:
When unstable also can cause your phone to freeze and lock up. You could run stress tests for each frequency if you really wanted to go the extra mile. Usually I lower by 5mv for all steps and then when i start noticing weird behaviors I increase by 5mv and call it a day.
Lower frequencies can only go so low, so eventually you'll just be decreasing the high freq steps. Just like a computer, youll need a high enough voltage to keep the phone stable.
Click to expand...
Click to collapse
Well it might not work for me then. I undervolted all that Simpelkernel is capable off and have just ran a two hour stress test. Nothing. Phone works like charm.

Faspaiso said:
Well it might not work for me then. I undervolted all that Simpelkernel is capable off and have just ran a two hour stress test. Nothing. Phone works like charm.
Click to expand...
Click to collapse
I believe some kernels allow for lower undervolting.. Im still on 5.0.2

vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
Oh, I undervolted busses. Can you explain me which I should undervolt and what is the difference between busses, A57 Cluster, GPU, A53 Cluster and so on and which is the right to undervolt?
Thanks in advance

Faspaiso said:
Oh, I undervolted busses. Can you explain me which I should undervolt and what is the difference between busses, A57 Cluster, GPU, A53 Cluster and so on and which is the right to undervolt?
Thanks in advance
Click to expand...
Click to collapse
Well I am not an expert in these matters, but from what I have read, roughly Power = Voltage^2 * Frequency. This exponential relation between voltage and power consumption is the reason undervolting is so effective in incresing battery life. As @tlxxxsracer said, lower frequencies already use lower voltages and pushing those too low will cause problems, but you can experiment boldly on higher ones.
Regarding your question about different voltage groups:
Our ARM CPU is following the big.LITTLE architecture. This means it has 2 groups of 4 cores - one is the "big" one (A57 Cluster) which is very powerfull, but also not very efficient and is put online when a heavier task load is put on the system. The other is the "LITTLE" group (A53 Cluster) which is what you usually use outside of gaming and short CPU usage spikes. The GPU is the graphics chip and the bus is the memory bus controller, which is basically what connects the RAM, the CPU and the GPU and handles data transfer between them.
What should you undervolt? I would say - whatever you can [get away with]. Push voltages as far as you can without compromsing stability. Lowering the voltage on the A53 and the GPU should be most beneficial. I am perfectly fine with my battery life and did not want to concern myself over stability, so I just undervolted with 25 mV. You however can be the brave man who spent a week in undervoltage experiments and share your results with us.
Now another thing to consider is what quality is your Exynos chip. If you are not familiar with the semiconductor production process, you can read on it over wikipedia, but in short - there are many processors produced on one "waffle" and about half of them are completely unusable. The other half are of varying quality (almost none of them perfect) and based on that imperfections they are sorted in different "bins" (this is known as CPU binning). This means that an almost perfect chip, from a higher bin can sustain much lower voltages, without issues, in comparison with a lower grade chip.
You can take a look in this thread to see what avs group (bin) people have and also how to see yours. I was not able to look it trough the method described in the OP, though, but you can see it in the kernel dmesg.

vordhosbnbg said:
Well I am not an expert in these matters, but from what I have read, roughly Power = Voltage^2 * Frequency. This exponential relation between voltage and power consumption is the reason undervolting is so effective in incresing battery life. As @tlxxxsracer said, lower frequencies already use lower voltages and pushing those too low will cause problems, but you can experiment boldly on higher ones.
Regarding your question about different voltage groups:
Our ARM CPU is following the big.LITTLE architecture. This means it has 2 groups of 4 cores - one is the "big" one (A57 Cluster) which is very powerfull, but also not very efficient and is put online when a heavier task load is put on the system. The other is the "LITTLE" group (A53 Cluster) which is what you usually use outside of gaming and short CPU usage spikes. The GPU is the graphics chip and the bus is the memory bus controller, which is basically what connects the RAM, the CPU and the GPU and handles data transfer between them.
What should you undervolt? I would say - whatever you can [get away with]. Push voltages as far as you can without compromsing stability. Lowering the voltage on the A53 and the GPU should be most beneficial. I am perfectly fine with my battery life and did not want to concern myself over stability, so I just undervolted with 25 mV. You however can be the brave man who spent a week in undervoltage experiments and share your results with us.
Now another thing to consider is what quality is your Exynos chip. If you are not familiar with the semiconductor production process, you can read on it over wikipedia, but in short - there are many processors produced on one "waffle" and about half of them are completely unusable. The other half are of varying quality (almost none of them perfect) and based on that imperfections they are sorted in different "bins" (this is known as CPU binning). This means that an almost perfect chip, from a higher bin can sustain much lower voltages, without issues, in comparison with a lower grade chip.
You can take a look in this thread to see what avs group (bin) people have and also how to see yours. I was not able to look it trough the method described in the OP, though, but you can see it in the kernel dmesg.
Click to expand...
Click to collapse
This is the most in depth answer I have ever gotten. Thanks for that!
Mind if I ask one more question? What is HPM voltage control and when undervolting is that the thing I should undervolt (it's in all of the 4 sections you explained)? Or should I undervolt each core individually?
Thanks in advance!

If I would have to guess, I would say, based on the description that increasing this increases the range, which you can change the volatage on each individual frequency, but I may be wrong, you should ask in the simpl kernel thread.