Database Develop

Am I using Voltage Control right?

Okay so I'm running the Assonance 5.0 rom and I read a big thread on how to use voltage control so I've been fiddling with it and I'm curious if I'm using it right, here's my settings;
1200 Mhz: 1300 - 0 = 1300mV
1000 Mhz: 1275 - 100 = 1175mV
800 Mhz: 1200 - 150 = 1050mV
400 Mhz: 1050 - 175 = 875mV
200 Mhz: 950 - 175 = 775mV
100 Mhz: 950 - 200 = 750mV
My phone has been running stable while I've been testing over the past 3 days and the only time I ever get a force close is when i occasionally start up Asphalt 5 but that's happened ever since I bought the app. I'm still decreasing voltages in the mid levels. Do these stats seem like they'd be legit or am I using the app wrong lol?

You've got the right idea. If your phone is stable with these settings then your battery should last significantly longer too. Good job.
BTW there's a voltage settings thread in the dev sectiom
Sent from my SAMSUNG-SGH-I897 using XDA App

Nexus 5 Undervolt tables

Guys I created this thread to compare our undervolt tables and be able to find stable values ​​used in the various PVS. My Nexus 5 is PVS 3 with Franco kernel R25.
My tables are as follows:
-75 global
300 MHz
650mV
422 MHz
675mV
652 MHz
700 mV

daniel84cs said:
Guys I created this thread to compare our undervolt tables and be able to find stable values ​​used in the various PVS. My Nexus 5 is PVS 3 with Franco kernel R25.
My tables are as follows:
-85 global
300 MHz
625mV
422 MHz
635mV
Click to expand...
Click to collapse
I have a PVS 3 Nexus 5 too, and I can barely undervolt it. Undervolting it -50 globally would reboot the phone during Antutu benchmark. I tried doing -50 at just 300 MHz, and ran stability test with the phone locked in at the frequency. It crashed after 30 minutes. I think I am going to leave the voltages alone, as my phone seems to already be running at the lowest voltages that it is stable at. I can run it at -25 mV globally, but why bother.

I have done many tests as you can see above, I had to increase the voltages. Now I had no reboot with the entire charge cycle, unfortunately not all CPUs are equal then my values ​​are not suitable for everyone.
Inviato dal mio Nexus 5 utilizzando Tapatalk

I also started undervolting with the values of the OP and it's working pretty good with my phone.
-75 globally and 300mhz starting at 650 with the next 5 steps also less then -75. So far I had no crash in several benchmarks and no crash after 2 hours stress test at 300mhz and 422mhz.
My CPU is PVS 1 so I wonder a bit about it^^

There's an undervolting thread here if anyone's interested: http://forum.xda-developers.com/showthread.php?t=2537000
Although it hasn't been posted in in a while to be fair

I am PVS 1 I can only under volt by -25 tops. Anything more is a crash on bench... Sucks. So no point in even undervolting for me.
Sent from my Nexus 5 using xda app-developers app

Hey guys.
What is pvs? What does it mean and how do i find out?

nad4321 said:
Hey guys.
What is pvs? What does it mean and how do i find out?
Click to expand...
Click to collapse
Hi,
Take a look here: http://forum.xda-developers.com/showthread.php?t=2515593.

Please continue discussions in the existing thread HERE.
Thread closed.

Nexus 5 Voltage How Low Can You Go.

When I start my day with my phone my ultimate goal is to get the most out of my battery. I have a Nexus 5 which is great phone but one downside is that the battery which is 2300mah can barely get you through the day. One way to help this issue is to under volt your CPU, the nexus 5 has a snapdragon 800 CPU clocked at 2.26GHz which is power CPU but at times it can run a bit hot and use more juice than it needs. By Under Volting your CPU your device will run much cooler without losing performance. (Warning if you go too low with the voltages your device will freeze and randomly reboot. ). The voltages than the nexus 5 ships with are a bit high I've been able to under volt up to -75mah without losing any performance however your experience may be different. To under-volt your device you need to have a rooted phone with a custom kernel installed. Franco, ElementalX, and Codeblue are few a few of the many kernels you can use with the nexus 5. I've been using ElementalX as my kernel for a while now, although Franco is also a good one. I use the ElementalX kernel app to manage my voltages, its a paid app but its definitely worth it. you could also use the Kernel tweaker app to manager voltages as well. I've set the governer to elementalx and i set the max cpu freq to 1574MHz, and the max screen off frequency is set to 729MHz. Don't go to extremes take small steps. Please let us know your results here.
This is what i have so far.
300MHz = 650mV
422MHz = 650mV
652MHz = 700mV
729MHz = 720mV
883MHz = 740mV
960MHz = 750mV
1036MHz = 760mV
1190MHz = 780mV
1267MHz = 790mV
1497MHz = 830mV
1574MHz = 845mV
1728MHz = 875mV
1958MHz = 945mV
2265MHz = 1000mV
Edit:
my pvs is 2
300MHz = 650mV
422MHz = 650mV
652MHz = 700mV
729MHz = 710mV
883MHz = 730mV
960MHz = 740mV
1036MHz = 750mV
1190MHz = 770mV
1267MHz = 780mV
1497MHz = 835mV
1574MHz = 840mV
1728MHz = 875mV
1958MHz = 965mV
2265MHz = 975mV

I have franco kernel, I will try your settings, Report later !

Avg sot ?

doctor_droid said:
Avg sot ?
Click to expand...
Click to collapse
I can manage about 5-6 hours but Ive made other changes as well I haven't only undervolted

apatel321 said:
I can manage about 5-6 hours but Ive made other changes as well I haven't only undervolted
Click to expand...
Click to collapse
Anything above 5hrs sot is good

doctor_droid said:
Anything above 5hrs sot is good
Click to expand...
Click to collapse
I keep my brightness at the minimum with adaptive brightness enabled also my max CPU is set to 1190MHz, I do mostly web browsing I

cranknet said:
I have franco kernel, I will try your settings, Report later !
Click to expand...
Click to collapse
Just wondering which governor are you using with the Franco kernel.

apatel321 said:
I keep my brightness at the minimum with adaptive brightness enabled also my max CPU is set to 1190MHz, I do mostly web browsing I
Click to expand...
Click to collapse
That is sweet do you live in total dark and browsing html pages LOL

apatel321 said:
Just wondering which governor are you using with the Franco kernel.
Click to expand...
Click to collapse
I'm using Interactive.

nedooo said:
That is sweet do you live in total dark and browsing html pages LOL
Click to expand...
Click to collapse
Most of the time adaptive brightness keeps the brightness at the right level however I I do wish you could adjust the sensitivity of it

[update] I was experiencing some random reboots
It wasn't as stable as it should be

apatel321 said:
Most of the time adaptive brightness keeps the brightness at the right level however I I do wish you could adjust the sensitivity of it
Click to expand...
Click to collapse
Sorry for my sarcasm
BTW back to topic I use Code_Blue kernel and I lower voltage -35 wirh Synapse and my voltage is from 740mV for 300MHz to 990mV for 2265MHz

nedooo said:
Sorry for my sarcasm
BTW back to topic I use Code_Blue kernel and I lower voltage -35 wirh Synapse and my voltage is from 740mV for 300MHz to 990mV for 2265MHz
Click to expand...
Click to collapse
You should be able to go as low as 650mV for both 300MHz and 422MHz., without experience unstable behavior.

pvs bin?

varuntis1993 said:
pvs bin?
Click to expand...
Click to collapse
Mine showed 3 on synapse.

varuntis1993 said:
pvs bin?
Click to expand...
Click to collapse
its 2

Just remember in a couple weeks if you notice stability issues or your phone rebooting, it's probably because of these changes.
Personally I value 100% stability, and I'm already able to achieve the same battery lifeout of default clocks and voltages as well as stock ROM and kernel. Such as these 5-6 hour SoT examples using 40% Adaptive Brightness.
http://imgur.com/a/vQpoz
http://imgur.com/a/sdx3a
Also I think you'll find lowering the voltages by 5-10% doesn't make a noticeable difference in battery usage, thought it should run cooler and throttle less.

apatel321 said:
You should be able to go as low as 650mV for both 300MHz and 422MHz., without experience unstable behavior.
Click to expand...
Click to collapse
Going to give this a try. I've had good success undervolting other handsets.

With latest code blue and adiutor app cannot set 650mv for 300mhz and 422mhz, lowest i can go is 700mhz not sure why though. Thank you anyway, I'm trying this out.
Enviado desde mi Nexus 5

It's the kernel the lowest you can go with code blue is 700

What's your undervolt?

I've been playing with the undervolt limit of this phone and it seems to have a large amount of play. Obviously every processor is unique so some of your S6's have a lower tolerance for undervolting. I'm using Hacker v11 with Synapse and I can get my A53 cluster @ 1.5 GHz down to 1000mV though I feel it can go lower. I have the A53 underclocked to 1.2 GHz @ 900mV for now and the A57 running 2 processors @ 1.4GHz and sitting at 825mV (just flashed v11 so Synapse reset the values and I've yet to UV the A57 much). Aside from benchmarking with various apps I notice no lag or slow downs running at the lower clocks and using only 6 cores.
My GPU is OC'd to 852MHz but I haven't UV'd it yet. Before v11 I had it at 856.25mV and still stable. HPM and various busses are going to be UV'd again and they seem to take it very well. I'll update this, hopefully later this evening, with more UV values.
I'd like to put our data together and figure out an average UV this phone can take and also see some more extreme values as well. It should be a good starting reference for anyone wanting to get longer life out of their battery along with the phone itself. While we're at it I'd lie to get some lower limits for the clocks and number of cores while still maintaining a smooth experience.
A53 (Hacker v11, starting w/ highest freq.)
1056
1012
962
918
875
843
806
781
750
725
693
675
650
631
625
A57 (Same as above)
1081
1065
1043
1012
981
943
912
875
943
818
800
775
750
731
718
693
675
662
650
643
637
631
GPU
887
831
787
743
718
675
668
Memory Bus(Lowest to highest)
575
575
581
593
593
600
650
675
725
743
768
800
831
Internal Bus(Lowest to highest)
637
637
643
675
712
737
737
743
743
750
793
800
Image Signal Processor(Lowest to highest)
650
650
700
737
806
These are what I'm using right now. I plan to take them down even more in the near future (I already have on some). Of course dropping the power doesn't count for much if the CPU is running too many cycles to finish a task so I'll be messing with the amount of cores and frequency as well.

I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.

benjmiester said:
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
Click to expand...
Click to collapse
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?

KCRic said:
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
Click to expand...
Click to collapse
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.

benjmiester said:
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
Click to expand...
Click to collapse
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.

KCRic said:
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
Click to expand...
Click to collapse
It is very interesting. I'm now backing off max clock, one increment at a time on both core sets to see where they meet. So far just down to 1500 little and 2000 on the big. Seems to be pretty good.

Hey, kinda late to the party but I recently got an s6 and starting to mess around with undervolting... Problem is I don't know where to start. Where do I get synapse? I'm not familiar with synapse but I did use kernel adiutor in the past.
I'm using this ROM:
https://forum.xda-developers.com/galaxy-s6/development/rom-galaxy-s6-stock-debloated-t3812822
Along with this kernel:
https://forum.xda-developers.com/tm...oc-uc-twsited-kernel-7-0-t-w8-f-flat-t3652139
Any help is appreciated. ?

So, I managed to overclock my GPU to 2 GHz ("TURBO" Profile) with KonaBess and it's rock solid. Have I been extremely lucky or...?

So, I went on a "boredom rampage" and I've read an article about a guy overclocking his 865 GPU to 865 MHz and reaching Adreno 660-levels of performance and I decided to give it a try and it was awesome.
Problem is, I'm too much of a thinkerer and I pushed the GPU as much as I could. I ended up on 2000 MHz with "TURBO" voltage profile and it's rock solid even on 2100 MHz with the same profile but KonaBess gives me an error if I try to edit the GPU tables after I booted at 2100 MHz.
I even edited the clock profiles to make it smoother, starting from 305 MHz to 600, 800, 1000, 1200, 1400, 1600, 1800 and 2000 with the right voltages.
Now, the battery and SoC temperatures are the same, the battery drain is basically the same, some other fellow modders with the same device (Mi 10T Pro 5G 8/256 with Pixel Experience Plus ROM) didn't manage to hit the same clocks, crashing even with 1000 or 1200 MHz, with my file from the KonaBess app.
So, have I been extremely lucky with the silicon lottery or it's just an illusion?
Please ask if you need ANY benchmark or proof. I've been monitoring the GPU clock with Franco Kernel Manager Live Monitoring and the clock is solid at 2000 MHz and the 3D performance has at first jumped and then slowly climbed, especially on 3DMark Wild Life Extreme. Wild Life Extreme Stress Test is stable the temperatures are fine.
Do you guys have any questions/suggestions/requests?
Edit: Here are some 3DMark runs, both Wild Life and Wild Life Extreme at stock and 2 GHz. I use Greenify, my storage is 94% full and all my processes in the background take up 4 GB of RAM and I didn't touch the bus for the various steppings for the clocks, so I believe that if heavily tuned, this could make a difference.

post before and after pictures of 3dmark.

TOMPPIX said:
post before and after pictures of 3dmark.
Click to expand...
Click to collapse
I have the history of all the bench on 3DMark, because I downloaded it just for this. Would that be ok?

it seems fishy, a 1ghz+ oc would increase your fps by more than that.

TOMPPIX said:
it seems fishy, a 1ghz+ oc would increase your fps by more than that.
Click to expand...
Click to collapse
It doesn't have the biggest of bumps from 900 MHz to 1 GHz or 2 GHz, but still, is capable of doing it and rock solid too.

Enzucuni said:
It doesn't have the biggest of bumps from 900 MHz to 1 GHz or 2 GHz, but still, is capable of doing it and rock solid too.
Click to expand...
Click to collapse
i don't think your gpu is actually running at 2ghz while you are running a benchmark. going from stock to 2ghz would at least have to give you an extra 20-30 fps in Wild Life.

TOMPPIX said:
i don't think your gpu is actually running at 2ghz while you are running a benchmark. going from stock to 2ghz would at least have to give you an extra 20-30 fps in Wild Life.
Click to expand...
Click to collapse
Not necessarily. The GPU IS running at 2 GHz but I think that the problem might be some diminishing returns where the clock doesn't mean anything after a certain point.

Are you try locking the freq on 2ghz in Kernel maneger ? Set min and max to 2gzhz with performance governor .

astronomy2021 said:
Are you try locking the freq on 2ghz in Kernel maneger ? Set min and max to 2gzhz with performance governor .
Click to expand...
Click to collapse
I've made various frequency steps. 400, 600, 800, 1000, 1200, 1400, 1600, 1800 and 2000 MHz. But if I change the governor, after I reboot, it will be msm-adreno-tz again. Max frequency is still 2000 MHz and minimum 400 MHz.

Yes after reboot is resets like on every phone you have to check apply on boot and select min 2000GHZ and max 2000ghz GPu freq in tap in FKM and set gov to performance and do benchmark like 3dmark wild life . Like that. And in Smart pack Kernel manager free app is GPU throttle turn that off.
Check box apply on boot and after boot will be apply.
And that you can show improvements of OC

Enzucuni said:
I've made various frequency steps. 400, 600, 800, 1000, 1200, 1400, 1600, 1800 and 2000 MHz. But if I change the governor, after I reboot, it will be msm-adreno-tz again. Max frequency is still 2000 MHz and minimum 400 MHz.
Click to expand...
Click to collapse
Can you share your Konabess txt file to import. I"m buying it I and want overclock.

astronomy2021 said:
Can you share your Konabess txt file to import. I"m buying it I and want overclock.
Click to expand...
Click to collapse

Thanks What is temperature ? Do you game with that or this just experiment ?

Temperatures are roughly the same. I do game with that. On normal games, frequency stays at 400 MHz, but on really heavy games like Genshin Impact, completely maxed out, depending on the scene, the GPU goes to 1.6 or 1.8 GHz and rarely at 2 GHz during some heavy cutscenes. 3DMark keeps it at 2 GHz all the time.

Enzucuni said:
Temperatures are roughly the same. I do game with that. On normal games, frequency stays at 400 MHz, but on really heavy games like Genshin Impact, completely maxed out, depending on the scene, the GPU goes to 1.6 or 1.8 GHz and rarely at 2 GHz during some heavy cutscenes. 3DMark keeps it at 2 GHz all the time.
Click to expand...
Click to collapse
That super. What ROM do you use ?

Pixel Experience Plus

Enzucuni said:
Pixel Experience Plus
Click to expand...
Click to collapse
Thianks

Hello, excuse my ignorance, but I want to learn what konabess is, it's an app or a magisk module, I also have the xiaomi mi 10t pro with DotOs rum android 11 and then I want to play more fluently, could you help me

konabess app is software you can overclock GPU and undervolt.
You need root and that it.
https://github.com/libxzr/KonaBess
Here tutorial but it old I need make new one because there isn't good one tutorial about it.

This doesn't make any sense. Why would Qualcomm leave so much on the table ?