Database Info

[Q] Difference between under-clocking and under-volting

I'm using the Faux Kernel on my Skyrocket. I'm using Set CPU for speed control, under-clocking for more battery life.
I head the terms UC, OC, UV and OC. When I use Set CPU, I assume that when I set maximum CPU speeds, I'm under-clocking. But what is under-volting? Is that different? Is there an advantage to doing both?
Harry

There is an advantage to undervolting you need either fauxs app or systemmtuner to do so.
Undervolting is giving the cpu less power and asking it to do the same amount of work it was doing before
Sent from my GT-P7500 using xda premium

That sounds a bit more dangerous in terms of doing damage to the phone or having reboots etc. when you are giving the circuity less power than it was designed.
For those who chose to undervolt for power savings, it is usually done in conjunction with under-clocking, or is it a one or the other type thing?

Not really, under volting is not as dangerous as over volting (used to also achieve higher overclocks). Over volting can actually damage hardware if you provide too much juice.
Under volting just reduces the voltage, if its not enough the app freezes or worse the phone reboots. If that happens, bump it up one more step (+12500) and you should be fine. Find where you can go low but still be stable (for me it happens to be -87500) you will save more battery.
Dixit

all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good

icenight89 said:
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
Click to expand...
Click to collapse
My exact setup. -100mV UV, and 1.188 gHz UC. Went from 100% to 0% in 1 day 7.5 hours with 3 hours of screen on time. No juice defender either. I think its pretty food. Using faux 009u, btw.
Sent from my SAMSUNG-SGH-I727 using XDA

Only issue I got with Fauxclock is that it saves the CPU clocks I set (say 1.298ghz max) but it doesnt actually save the voltage after a reboot. I look at the VDD table and its still stock.
So only way to get it to work is to manually edit the VDD table itself. Not sure if this is by default that fauxclock doesnt actually save the voltages after a reboot.
Dixit

Don't see fauxclock in the application store, sorry, Google Play Station.

Thats cause its not in the Google Play. Its a separate app at this location
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
Dixit

Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.

Fauxclock has very basic CPU clock settings, it was created just for that faux compatible kernels so the original developer didnt spend weeks on it. It was just a simple and fast and effective GUI to set min/max clocks and also voltages (global scale). You can however set one other clock which is the "screen off" clock, but thats about it.

harry_fine said:
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Click to expand...
Click to collapse
they will, use one or the other. U can manually change global vdd table and use setcpu, or forego advanced profiles in setcpu, but u can't/shouldn't use both

FauxClock force closes on launch for me..
EDIT: Getting a Faux kernal fixed that. Wow I feel dumb.

Shadeslayers said:
FauxClock force closes on launch for me..
Click to expand...
Click to collapse
Are u using faux kernel?

Any tips or thread about how to manually change global vdd table so that I can use SetCPU for the profiles and adjust voltage manually?
Is there a risk to that? If I set it and the phone won't boot, it sticks!

use Gideon UV/OC script and change vdd as u see fit. If it doesn't work u can always flash Gideon stock back

icenight89 said:
use Gideon UV/OC script and change bed as u see fit. If it doesn't work u can always flash Gideon stock back
Click to expand...
Click to collapse
What exactly is the difference between flashing Gideon's script or just using FauxClock? Thanks!

fauxclock gives u dynamic min/Max and voltage control as per user settings. Gideon is pre-set and makes use of init.d script. u can change it, but every change requires a reboot

Battery overheating

When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.

Same problem.
I'm having the same problem too. Would appreciate it if someone could post a solution here!

iscarechyu said:
I'm having the same problem too. Would appreciate it if someone could post a solution here!
Click to expand...
Click to collapse
Well the battery doesn't CAUSE overheating, the processors do. Always. ICS roms, the newer ones anyway don't overheat the phone as much, turn of your syncs, mobile network and decrease the brightness of the phone. Your phone will always overheat pretty much no matter what you are doing on it if it is charging.

benjdm said:
When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves

ganeshp said:
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)

benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
The governor sort of controls how the CPU speed will run on your kernel. You can change the governor using an app like SetCPU or System Tuner. BTW faux does tend to run a bit warmer, in my experience, but it's nothing to worry about if you know that you're running apps that are a bit heavy on the CPU.

benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
I had the same problem , and im now currently running ARHD.
First time i try stock kernel and everything was burning, tryed to change with sebastian kernel with stock cpu speed and nothing change (and so a hard battery drain), they suggest me re-flashing Sebastian kernel and now everything is ok, temperature is not going up..
im currently running Faux kernel, all stock, and everything is awsome, try it.
see ya
Lollaz

Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91

I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.

musa91 said:
Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91
Click to expand...
Click to collapse
DO NOT DO THIS!!!!!!!
This fix only works for Ondroid rom. And then it has mixed results as to effectiveness.
But ARHD requires firmware 3.32 to work. If you try 3.12 you are likely to get bootlooping.
Musa, you know this only works on Ondroid. You should not be recomending firmware twaeks for other roms you havent tested it on.

benjdm said:
I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.
Click to expand...
Click to collapse
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.

Skipjacks said:
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.
Click to expand...
Click to collapse
I was trying to re-do everything because I didn't know what the problem was.

benjdm said:
I was trying to re-do everything because I didn't know what the problem was.
Click to expand...
Click to collapse
That plan certainly has its place too! Ive relied on numerous times in various subjects.
I like to call it the Noahs Ark fix. When everything else fails, destroy the world and start over!
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)

More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)

benjdm said:
More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)
Click to expand...
Click to collapse
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA

sensation lover said:
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Well, darn it

benjdm said:
Well, darn it
Click to expand...
Click to collapse
dont hold me to this but you could try getting the htc evo 3d battery or the sensation xe which I think are 1720mah, their callibration should work.

I contacted Anker to see if they had any software or anything for reading temperature. They said they did not and offered to take the battery back (kudos.) I'm keeping the battery.
Underclocking the CPU to 1 GHz seems to be helping quite a bit. Also, something changed with the battery sensing. The Anker battery went from indicating 25C all the time to indicating 11.5-12C all the time. When I put the stock battery back in, it's reading 17C while charging and somewhat above that while playing games, but nowhere near as high as before.
I wonder what's going on...

Racing to 1000 [Q]

Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...

FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en

I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)

FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment

My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s

FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.

My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...

FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.

Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen

is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.

Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..

I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.

Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...

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.

cpu freq issue

Hey guys!
Mt s9+ snapdragon from tmobile, the cpu freq is not goi g loewr than 748mhz which I assume affect the battery life. In the screen shot you can see that lower freq steps are available but not used. Anyone is having this issue also?

Same way for me with s9+ on verizon
Sent from my SM-G965U using Tapatalk

I believe this has to do with how the cpu is designed with multiple cores that run at different freq.
I don't believe cpu info (the core package) hasn't been updated in a fair while, and just doesn't read the info correctly (or at least know how to display it)

Bestplayer55 said:
Hey guys!
Mt s9+ snapdragon from tmobile, the cpu freq is not goi g loewr than 748mhz which I assume affect the battery life. In the screen shot you can see that lower freq steps are available but not used. Anyone is having this issue also?
Click to expand...
Click to collapse
Look in battery stats to see what is draining battery. For me it was the email app after a samsung app cloud restore. I had to clear the data on stock email app and the cpu freq qent down to deep sleep when not in use.

DLD23 said:
Look in battery stats to see what is draining battery. For me it was the email app after a samsung app cloud restore. I had to clear the data on stock email app and the cpu freq qent down to deep sleep when not in use.
Click to expand...
Click to collapse
Deep sleep works good. My concnerns is that the cpu only use 745mhz as lower cpu step, but it can go lower down to 300mhz. For some reason it doesnt.

It is an app I am sure

Bestplayer55 said:
Deep sleep works good. My concnerns is that the cpu only use 745mhz as lower cpu step, but it can go lower down to 300mhz. For some reason it doesnt.
Click to expand...
Click to collapse
Wait lol mine too, holy crap! Good catch. I have u1 model

DLD23 said:
Wait lol mine too, holy crap! Good catch. I have u1 model
Click to expand...
Click to collapse
Hum! Mines is only U model. I thinks thats why people are complaining about battery life, my friends also have the u version and have the same problem. Do you know how we can address this or know someone who can help?

My battery lasts forever. But now that I know that I can try to make it even better I start my day at 3am and work in bad service area, can use it all day and have 55% wjen I plug it in at night.