Undervolting (Custom Voltage, new approach)

Search This thread

djjonastybe

Senior Member
Sep 27, 2010
686
346
Tienen
I made a function to calculate voltages for the Google Nexus

As a minimum voltage I found for stock 840mv always.

Best stable undervolt for everyone start from 800mv

840-1000-1090-1200mv

--> VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY)

REQ= MIN FREQUENCY = 800

Results in table:

MARGIN OFFSET APPLIED: -40mv

350MHz - 800mv
700 - 945
920 - 1040
1200 - 1175
1350 - 1254
1400 - 1281
1500 - 1338
1600 - 1388

Please test the settings and post back here. I believe these are stable for everyone.
I am experimenting to try pushing these into the CM10 repositories.
 
Last edited:

strumcat

Senior Member
Mar 29, 2012
681
305
The standard setting for 1190 MHz with Trinity kernel is 1150 mV, and it's solid as a rock for many users. That would fit right into your chart easily, so that's at least some confirmation of its accuracy.

I'll test 800 mV @ 307 MHz, and 945 mV @ 691 MHz. Those are lower than Trinity's defaults of 850 mV and 1000 mV for those frequencies.

No immediate problems but I'll leave it this way and see what happens.
 
Last edited:
  • Like
Reactions: Karido Aziz

djjonastybe

Senior Member
Sep 27, 2010
686
346
Tienen
Not every phone under volts the same

Sent from my Galaxy Nexus using xda premium

that's why we could use the function:

VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY) + MARGIN

I am currently thinking about rewriting something for the Google Nexus

Let's disable Smart Reflex.
Replace it with stock voltages generated by this curve found by the frequencies the MPU runs at.
No need to program voltages!
Next is the availability of a voltage_margin value which users can modify with the android terminal emulator or a script.

How would you guys like this? This will make undervolting easier. Maybe little more limited but undervolting shouldn't take so much time in my opinion. You can't undervolt a Sandy Bridge CPU for each frequency separately. So why should phones.

Please let me know if you guys would like this feature. Then I will start developing.

GOALS:
- Making undervolting easy for everyone!
- Consumes less time!
 
Last edited:

t-rip

Member
Jul 11, 2011
31
2
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!


I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...

For example for 700MHz I get the Voltage "6,96"

I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)

put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432


Where's my mistake?
 

Xg3nFatality

Senior Member
Jun 14, 2012
145
26
Arizona
This sounds like a great idea, I hate trying to undervolt my phone cause I feel like I end up doing too much and start ruining the experience with ROMs so I stopped altogether.
 

scourge18a

Member
Mar 16, 2008
30
1
I Like The Idea Of Making It Simple But every Single CPU Is Different And OC Differently And Will UV Differently. Even with Different Kernels And Roms You Will Have Different Results.
I Do Applaud Your Efforts but The Only Way To see How Low You Can Go Is To set It And Test It.
It Will Either Run Or It Won't, You Can't Really Harm Your CPU With UV'ing Like With OC'ing.

Sorry About The Capitals, Only Way My Phone Does It On Here I Guess
 

grojas

Senior Member
May 22, 2007
136
4
Montevideo
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!


I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...

For example for 700MHz I get the Voltage "6,96"

I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)

put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432


Where's my mistake?

+1 ...But look awesone this idea!!

Cheers!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    I made a function to calculate voltages for the Google Nexus

    As a minimum voltage I found for stock 840mv always.

    Best stable undervolt for everyone start from 800mv

    840-1000-1090-1200mv

    --> VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY)

    REQ= MIN FREQUENCY = 800

    Results in table:

    MARGIN OFFSET APPLIED: -40mv

    350MHz - 800mv
    700 - 945
    920 - 1040
    1200 - 1175
    1350 - 1254
    1400 - 1281
    1500 - 1338
    1600 - 1388

    Please test the settings and post back here. I believe these are stable for everyone.
    I am experimenting to try pushing these into the CM10 repositories.
    1
    The standard setting for 1190 MHz with Trinity kernel is 1150 mV, and it's solid as a rock for many users. That would fit right into your chart easily, so that's at least some confirmation of its accuracy.

    I'll test 800 mV @ 307 MHz, and 945 mV @ 691 MHz. Those are lower than Trinity's defaults of 850 mV and 1000 mV for those frequencies.

    No immediate problems but I'll leave it this way and see what happens.