Related
Ezekeel has created the ability for user control of cpu overclock and bus/gpu overclock. He has also made it possible to change the cpu and internal voltages, so that this can be done without sacrificing stability. Several awesome kernel developers have implemented his work. Thanks to all of you.
I have seen kernel development threads degenerate into "help me with my voltages" threads. No more!
Please post:
- Your kernel and version/date.
- Your live_oc value.
- Your dvsarm (cpu voltage) values.
- Your dvsint (internal voltage) values.
You can vote for settings you have found to be stable by thanking that post.
Default cpu / bus clock speeds
Trinity teuv:
5 steps:
100 200 400 800 880 MHz;
bus: 220 MHz
Trinity T144:
5 steps:
100 400 800 1000 1440 MHz;
bus: 240 MHz
franco:
5 steps:
100 200 400 800 1000 MHz
bus: 200 MHz
Please post the frequencies for your kernel of choice, so we can make this list complete.
Reserved for bacon.
PM simms if you want chocolate on it.
good idea!
btw, reserved for chocolate covered bacon. Mmm..
Reserved for:
Spank me Ezekeel!
I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock
is it possible that my nexus dislike liveoc.
no matter which kernel (matrix/franco) + rom (markvis/superosr) combo i am on, 110% and 20 - 30ov
will freeze the phone
currently on
kernel: franco.kernel 0611
live_oc: 100
voltage: stock
Kernel: Franco 06november bfs
live_oc: 120
dsvarm (cpu voltage): 1285, 1190, 960, 835, 800
dsvint (internal voltage): stock
Sent from my Nexus S using Tapatalk
Go Go
250~1G freq with 250 bus/GPU speed! Cool~
- kernel and version/date : franco.Kernel 11/6
- live_oc value :125
(max freq :800 / min freq : 200)
- dsvarm (cpu voltage) values : 1250 1250 1080 950 950
- dsvint (internal voltage) values : 1100 1130 1130 1130 1000
#!/system/bin/sh
echo "1250 1250 1080 950 950" > /sys/class/misc/customvoltage/arm_volt
echo "1100 1130 1130 1130 1000" > /sys/class/misc/customvoltage/int_volt
echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "125" > /sys/class/misc/liveoc/oc_value
Click to expand...
Click to collapse
Kernel: Franco 06november bfs
live_oc: 110
Min_freq: 440
Max_freq:1100
dsvarm (cpu voltage): 1210, 1160, 1010, 900, 900
dsvint (internal voltage): stock
What's a good max arm volt to liveoc 110 on franco's 06
Ill go with stock on the ones I can control with set cpu
Cool update on nstools! Now can adjust voltages,that's why I ask lol...
Sent from my I9020T NSCOLLAB + FRANCO'S 06 BEAST LIVEOC 105
Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
---------- Post added at 03:12 PM ---------- Previous post was at 02:58 PM ----------
LKNim said:
Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
Click to expand...
Click to collapse
I got it solved by a brainless method
1.Flash TEUV kernel which doesn't support liveOC
2.Clear the data of NSTools
3.Back to franco kernel
4.Done
It's useful for those don't know much about command and init.d such as me
franciscofranco said:
I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock
Click to expand...
Click to collapse
get reboot with this settings..
strange...
al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV
LKNim said:
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV
Click to expand...
Click to collapse
I think I am confused with stock voltage for internal voltage...
this one??
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Or this one??
1000mhz : 1100mV
800mhz :1100mV
400mhz :1100mV
200mhz :1100mV
because when change my intenal voltage with stock voltage....immediately hang and after that reboot
100mhz :1000mV
al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
with this settings i have no reboot
al_madd said:
with this internal voltage right???
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Click to expand...
Click to collapse
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you
LKNim said:
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you
Click to expand...
Click to collapse
Oh...sorry..because everyone says internal voltage using stock..I thought these value 1250 1200 1050 950 950...sorry..
yes..with 1100 1100 1100 1100 1000...My phone have no problems at all..thanx...
when i change the voltages in terminal emulator:
echo "1250 1200 1000 950 950" > /sys/class/misc/customvoltage/arm_volt
does the voltage change take place instantly or do i need to reboot?
Changes are instant. Rebooting will only reset you to stock values, if you don't have an init.d script for them.
You can check your changes after an echo by typing the following in Terminal:
Code:
cat /sys/class/misc/customvoltage/arm_volt
Hi @all,
everyone is invited to post
1. ROM
2. Kernel
3. Kernel settings
4. UV settings
independently of ROM or Kernel used.
It might be a good starting point to compare other user´s experience.
Before using the settings postet in this thread please keep in mind that each device is different. Good settings for device A might produce freezes on device B.
So share your and enjoy other´s experience´s ...
here are my stable settings:
ROM: CheckROM RevoHD v6
Kernel: N.E.A.K. 1.4x
CPU Gorvernor: conservative (with all tweaks over CWM recovery enabled)
I/O Sched: sio
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 850 mV (... can´t go lower for testing with voltage control )
200 Mhz - 850 mV (... can´t go lower for testing with voltage control )
500 Mhz - 875 mV
800 Mhz - 975 mV
1000 Mhz - 1075 mV
1200 Mhz - 1175 mv
GPU settings:
Low: 133 Mhz - 800 mV
High: 133 Mhz - 800 mV
I am not a gamer and this settings are solid stable for my device. I use the phone mainly for (heavy) phone call´s (I know its old fashion ) and @home for surfing via WIFI. I enable my mobile data connection only when I need it.
This setting´s give me 3 - 4 days battery life.
I use lulzactive governor and vr I/O sched before and I feel NO difference in performance compared with the above settings (regarding scrolling through menus, starting apps ...), but the above settings gives me better battery.
Regards
Antonio
Update: I have to mention that I have the 2000 mAh Samsung battery.
OROM: Stock 2.3.5
Kernel: N.E.A.K 1.3.3.x
Voltage controls: All default.
100-800mhz
Lulzactive, VR
I usually get 1 & a half days battery, with an average of 7 hours screen time. The phone still runs beautifully while playing games and such so I have no problems in that category.
Edit:
Wifi on 80% of the time, a few hours of XDA. Skype on 100% while wifi is on. A few hours of games (dolphin, mc3, cut the rope, etc.), hours of Internet browsing, etc.
Sent from my GT-I9100 using XDA
A last note:
Posting your settings and your battery charge cycle, please also mention the way you using your phone during the day to make your post more comparable ...
have fun
Voltages
Using Checkrom V6, lulzactive gov. NEAK Kernel
1200mhz @ 1150mV
1000 @ 1050
800 @ 975
500 @ 875
200 @ 850
100 @ 825 (min freq is 200mhz anyway, so this freq is not used at all)
Rock solid, never a kernel panic/crash
My battery last 2 days with push Exchange connectivity, gmail pushing too, some gaming (no more than 1h x day), 1h voice calls x day, normal texting activity (30-50 daily text messages) and automatic brightness customized to be darker than default.
Battery last longer if you do not let fully discharge it (plug it at night if you can, no matter the charge left).
@Floodland
I usually don´t let the battery go down below 15% - 20%, then I start a new charge ... I break this rule only in case on an emergency when no charger is near by me
I´ll try your 1000 MHz and 1200 MHz voltage setting´s, will post back if they work on my phone
ROM:Custom Made DXKL3
Kernel:SiyahKernel 2.6.13
Governor:SIO,ondemand
Voltages:
100 Mhz - 800 mV
200 Mhz - 850 mV
500 Mhz - 900 mV (default)
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mv
1400 Mhz - 1250 mV
1600 Mhz - 1350 mV
GPU settings:
1: 133 Mhz - 800 mV
2: 266 Mhz - 950 mV
3: 400 Mhz - 1100mV
battery life around 2 days with light usage, 8 hours for heavy usage.
at present 44% after 32 hours, with 2:15 hours display on, wifi on, 3G off
ROM: All GB ROMs
KERNEL: Siyah, NEAK and Redpill
SCHEDULER: Usually I keep it unchaged
GOVERNOR: ondemand or conservative
FREQUENCY: 200MHz- 800 or 1000 or 1200MHz
UV:
-CPU
200MHz - 800 mV
500MHz - 850 mV
800MHz - 950 mV
1000MHz-1050mV
1200MHz-1150 mV
FYI, I always use this cpu uv settings from 6 months ago -- since the first time I got my SGS2 undervolted while using ninphetamine kernel, to be exact. It always stable on my SGS2.
GPU:
133 MHz - 800 MHz
267 MHz - 950 MHz
Sent from my GT-I9100 using xda premium
New voltages ...
Hi @all,
here are my settings after new tests. The stability was testet by three sequential cycles of the N.E.A.K tester in each (fix) frequency:
100 Mhz - 850 mV
200 Mhz - 850 mV
500 Mhz - 850 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1150 mv
Will test in next bettery cycle if they are stable in daily use, and report. Fell quite secure cause i´m not a heavy user...
Will test the settings starting tomorrow with the new N.E.A.K 1.4.1x kernel (simone told in his thread that the kernel should be released this afternoon).
ROM: Fatal1ty Extreme Edition (XWLA4)
Kernel: Red Pill 1.3
CPU Gorvernor: conservative
I/O Sched: sio
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 825 mV (Stable but not in use as it tends to lag a bit)
200 Mhz - 825 mV
500 Mhz - 875 mV
800 Mhz - 950 mV
1000 Mhz - 1025 mV
1200 Mhz - 1125 mv
1400 Mhz - 1225 mv (Stable but not in use as don't need it)
1500 Mhz - 1350 mv (Stable but not in use as don't need it)
GPU settings:
Low: 114 Mhz - 800 mV
High: 267 Mhz - 950 mV
I have 2 Exchange accounts on push, Gmail Push, hotmail every hour, and moderate use. Screen time Usually between 2-4 hours. Used to get 2 days, but getting epic wakelocks from google services since the Google Play update. so im trying work that out. at the moment of about 14 hours i have 2hours screen time and 34% battery left.
Red pill rules
ROM: Checkrom revo hd V6 (XWLA4)
Kernel: Red Pill 1.3
CPU Gorvernor: Hyper
I/O Sched: N/A
200 Mhz - 1200 Mhz
Voltages:
100 Mhz - 900 mV
200 Mhz - 900 mV
500 Mhz - 950 mV
800 Mhz - 1000 mV
1000 Mhz - 1100 mV
1200 Mhz - 1200 mv
1400 Mhz - N/A
1500 Mhz - N/A
I USED THE KERNEL Neak BUT I'll take the RED PILL IS SIMPLY THE BEST BUT THE BEST OF SIYAH MORE FLUID AND ENHANCED THIS LAST
TWO CORES ARE ENABLED
did a test for each freq and volt with STABILITY TEST app.
ROM: cognition 1.51
Kernel: Siyah 2.6.14
I/O Schrduler: sio
CPU Gorvernor: smartassV2
CPU:
100 Mhz - 1600 Mhz
Voltages:
100 Mhz - 850 mV
200 Mhz - 850 mV
500 Mhz - 875 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
1200 Mhz - 1200 mv
1400 Mhz - 1275
1600 Mhz - 1400 mv
GPU:
100Mhz-800mv
267Mhz-950mV
normally working from 100mhz-800mhz.
i managed to get lower mv for the cpu and stable but it was the limit. so i added 25mv more for more stable results.
Who dares trying my extreme UV values ?
My UV stable table (Mhz/mA) :
1200 (1125) | 1000 (1025) | 800 (950) | 500 (850) | 200 (800) | 100 (800)
Noop + On demand.
Thanks to NEAK for its magic on my S2
ROM: CM9
Kernel: NEAK 2.0.2x
I/O Schrduler: vr
CPU Gorvernor: ondemand
CPU:
200 Mhz - 1000 Mhz
Voltages:
200 Mhz - 850 mV
500 Mhz - 900 mV
800 Mhz - 950 mV
1000 Mhz - 1050 mV
GPU:
133Mhz-800mv
166Mhz-800mV
Works perfect for me. Always heavy usage and get nearly 24hours with standard battery. Screen on time 4 hours. With siyah I had nearly the half of the uptime.
Wifi always on. Sync on. I mean this is what it was made for
-sent from sgs2 tapatalk
Hello xda forums.
I've recently come into posession of a Nexus 7 (C80) and beside from a slight lift on the left that gets a little worse from heat and the screen flicker issue, it works fine.
I've been trying to undervolt this thing using franco's kernel (tried r41 and r42) but noticed a very peculiar issue apparent in Trickster Mod (which what I was using).
It seems that changing the voltage for a single frequency has no effect, while applying a global offset seems to take effect. Let me try to explain this further...
Let's say I want to undervolt the 1300 MHz frequency, and want to try 975 mV.
So I run Stability Test app in the background and set performance governor. This pretty much ensures the tegra 3 is running at 1.3 GHz.
So I go in trickster mod, "Specific" tab, and I tap 1300 Mhz and I set 975 mV and press the tick mark at the top to apply... It says "Applied".
No crash... Then I try 950 mV... still no crash, 925, 900, 700 (!), no crash...
so I reboot the n7 and try to reach 975 mV by applying a global offset of -150 (stock is 1125 mV for 1.3 GHz as it appears to me). Immediately after I tick apply, I get freeze / reboot, meaning it worked.
Using the global offset method, I can get stable UV by a global offset of -75 mV (ie: 1050 mV for 1.3 GHz) on my N7.
In both cases, I verified that changing 1 frequency or changing all of them does apply correctly, I opened a terminal and su'd and I did a:
cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
it shows the expected results, but it doesn't seem to actually take effect when changing 1 frequency only (otherwise it would have froze by now).
Am I the only one missing this ? Is this a bug in trickster ? Is there a hidden catch ?
ROM: SmoothROM 4.3
Kernel: Franco Kernel r41 and r42 (tested this behavior on both).
First, your post is very difficult to read. You are using "MHz" for both frequency and voltage (in mV).
I can't speak to the kernel you're using, but 1300mhz is one of the frequencies that is not "directly" supported as a voltage set point on the Tegra 3, as far as I can tell.
Per my understanding of the chip, the voltage set points are separate from the frequency set points, and it uses the "closest" one.
At least with the M-Kernel (somewhat overclocked), I have the following frequency steps (in mhz):
51, 102, 204, 340, 475, 666, 860, 1000, 1100, 1200, 1300, 1400, 1500, 1600, 1700
However, the frequency set points are:
(LP core) 204, 342, 475, 555, 666
(G core) 550, 770, 910, 1050, 1230, 1280, 1330, 1370, 1400, 1500, 1600, 1700
As the chip picks the "closest" voltage, what this means is that for the 1300mhz frequency, the 1280mhz slot is the one selecting the voltage. This also means that you cannot set the voltage for each frequency step in some cases, as multiple frequencies may share a slot.
You may have to look at the kernel settings directly through the exported variables if TricksterMod is not displaying the correct data.
For me, I can only get down to 1005-1000mv at 1300mhz.
What do you get when you cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ?
On M-Kernel a33, I get:
Code:
1600mhz: 1095 mV
1500mhz: 1040 mV
1400mhz: 1000 mV
1370mhz: 1000 mV
1330mhz: 1005 mV
1280mhz: 1005 mV
1230mhz: 1005 mV
1150mhz: 965 mV
910mhz: 915 mV
910mhz: 915 mV
770mhz: 850 mV
770mhz: 850 mV
550mhz: 800 mV
550mhz: 800 mV
I apologize for the difficulty of reading my post. The issue is difficult to explain precisely and I was in haste.
I've edited my post to fix some mistakes, thanks for the feedback.
on Franco Kernel (r41), I get the following table on reading the table directly (without any UV applied). Trickster is displaying the same readings.
Code:
1300 1125
1200 1100
1100 1075
1000 1050
900 1025
800 1000
700 975
600 950
500 925
400 900
300 875
200 850
100 825
Very interesting. That doesn't map with what I've seen of the Tegra3 documentation elsewhere.
I wonder if the kernel is setting values that the hardware doesn't support.
What is stock voltage at stock speeds?
I heard mixed reviews with under volting... And place where I can read about this to get the right answer??
Thanks
Nexus 4 Rooted
Running Paranoid Android
gd6noob said:
What is stock voltage at stock speeds?
I heard mixed reviews with under volting... And place where I can read about this to get the right answer??
Thanks
Nexus 4 Rooted
Running Paranoid Android
Click to expand...
Click to collapse
That depends on what binning you have (what kind of CPU)
For Fast & Faster:
384MHz -850 mV
486MHz - 875 mV
594MHz - 900 mV
702MHz - 925 mV
1026MHz - 1025 mV
1188MHz - 1100 mV
1350MHz - 1125 mV
1512MHz - 1150 mV
------------
For Nominal & Slow
384MHz - 900 mV
486MHz - 925 mV
594MHz - 950 mV
702MHz - 975 mV
1026MHz - 1075 mV
1188MHz - 1150 mV
1350MHz - 1175 mV
1512MHz - 1200 mV
Hope that helped
If I remember, I have the fast CPU...
Thanks for the info...
Nexus 4 Rooted
Running Paranoid Android
Hi,
I have used Tegrak Overclock Ultimate to overclock my Galaxy Note 1 (N7000) at stock kernel. It works with Cyanogenmod11 (Kitkat 4.4.4.). This are my settings:
1748 mhz: 1500 mV - 1300 mV (+200 mV) (stock is 1400 mhz)
1200 mhz: 1100 mV - 1275 mV(-175 mV)
1000 mhz: 1000 mV - 1175 mV (-175 mV)
800 mhz: 950 mV - 1100 mV (-150 mV)
500 mhz: 900 mV - 1000 mV (-100 mV)
200 mhz: 850 mV - 975 mV (-125 mV)
I have also underclocked my GPU, but I don't remember the stock voltages:
267 mhz: 900 mV -
160 mhz: 850 mV -
134 mhz: 850 mV -
I hope this could help you!
- Olivier