Related
I'm playing around with voltage control and setcpu and I'm getting mixed results. I'm running the latest stable samurai kernel.
With setcpu it shows speeds in the app of more then 1100 mhz. (When using the slider it shows jumps of up to 1200 mhz when I select 1200 mhz)
In voltage control I see jumps of up to 1100 mhz when I select 1200 mhz on slider (or faster).
Just curious what settings daily use overclockers are running? 1100 seems stable and my friend has had theirs at 1200 mhz for months.
Any reason why I'm not seeing voltage control show more then 1100 mhz (not in the slider but in a 'status' type display above the slider)
Pull right to the voltage section and enable 1200
Sent from my SPH-D700 using XDA App
You would definitely know.. thanks for the reply. Great work on everything btw.
That was what I was missing.. seeing 1200 mhz now.
Also just a recommendation if you are running the samurai kernel I would use voltage control being that it will keep it stable and the developer is always updating it (making it better) as appose to setcpu
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
I have read very conflicting things about undervolting; some say it doesn't do much at all, others say it's worth the effort. What most can agree on though, is that it depends on the phone, so I want to get some input to see if people have had success with it on the Fascinate. I tried a mild undervolt today and while I didn't notice much change with the screen on (while using it) I did notice it held a lot better charge while in stand-by. My settings as of right now are:
1200 MHz - 1300mV (-50)
1000 MHz - 1225mV (-50)
800 MHz - 1150mV (-50)
400 MHz - 950mV (-100)
200 MHz - 850mV (-100)
100 MHz - 850mV (-100)
I have been running the over / under volts for a while on different test builds with really good results...
I did do a live o/c for a while but have settled on normal o/c
My over / under settings as of right now are:
1200 mhz O/C
100 mhz minimum
1200 MHz - 1400mV (+50)
1000 MHz - 1325mV (+50)
800 MHz - 1250mV (+50)
400 MHz - 1025mV (-25)
200 MHz - 900mV (-50)
100 MHz - 875mV (-75)
------------------------
------------------------
But i have been wanting to test some other stuff too
I figured i would test this::
And see how it runs
1200 MHz - 1350mV (+00)
1000 MHz - 1275mV (+00)
800 MHz - 1200mV (+00)
400 MHz - 1000mV (-50)
200 MHz - 850mV (-100)
100 MHz - 850mV (-100)
sent from my swagger
aokp 10/22 test / devil kernel
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Crawshayi said:
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Click to expand...
Click to collapse
Just came from all the reading in the original devil ics thread...
Somebody 'Crack' ran these settings...
http://forum.xda-developers.com/showthread.php?t=1699141
It has so many great answers and Such great info,,, just realized i need to go back and read some more,,,
Think ... devil idle .... :thumbup:
sent from my swagger
aokp 10/22 test / devil kernel
From all the roms/kernels I ever ran on my fascinate undervolting did help slightly. It seems if I remember correctly that pulling -50uv across the board helped with battery life without decreasing stability. Anymore than that is when the random reboots started. Also disabling the 100mhz step made a big difference with SOD's and reboots.
Crawshayi said:
Just curious, but what was your reasoning to raise the voltage? It seems like that would just be a battery drain because at those steps the stock voltage should be more than enough for stability.
I also don't Live OC but that's only because my phone will crash at 110% Live OC so I don't see the point in doing 105% Live OC... so I just do what you do and have 1200 MHz regular OC now
Click to expand...
Click to collapse
You can do both a live oc (fsb overclock), and a regular overclock (multiplier overclock) at the same time. I use 110 live oc and a 200 mhz regular overclock giving me a total of 1320mhz. Set your live oc then use rom controlor whatever to do your regular overclock on top of it.
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.
When running the scaling stability test my CPU always stays at 1512 MHz (occasionally drops to 1188 MHZ and then right back up to 1512 MHz) instead of scaling throughout all the frequencies, according to the cpu speed in the top left. Is it just me?