Related
This thread has been created to share Undervolting Settings (UV).
Undervolting makes CPU/GPU/Modem to consume less power, thus extend battery life. This is allowed by flashing modified kernels that allow UV (Thanks to raspdeep's work). One can use Voltage Control to change settings (Thanks to xan).
Setting format is -x mV for a given CPU clock as used in xan's app: [1200Mhz] [1000Mhz] [800Mhz] [400Mhz] [200Mhz] [100Mhz]
What are your settings?
PS: Please edit your very first post with settings instead of reposting. Thank you!
Stable: 50 50 75 100 100 100
1200 max: 50
1000 max: 50
800 max: 75
I am currently running 50 50 50 75 100 100 with no stability problems. It has made 4 back-to-back quadrant runs and a couple days of general usage without any crashes so far.
Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.
TheVisitorX said:
Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.
Click to expand...
Click to collapse
My system hangs in sleep mode when I have setCPU or Superpower with sidekick on.
I have the max cpu capped at 800mhz using SetCpu.
Undervolted -50 for 800mhz 600 400 200 and 100 each.Phone was at 50% last night and 6 hours later it's dead.Battery was completely discharged.All i did was set everything at 50Mvs less.Correct ? i think i'm missing something.Do help.thanks.
hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently
i have cm7 #19 with the (latest) glitch v10b-VC kernel..no oc, bu uv
100mhz -50,200mhz -50,400mhz -50, 800mhz -25 and 1000mhz @stock
What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175
hackeron said:
What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175
Click to expand...
Click to collapse
Negative effects come in the form of stability issues and random reboots. Is doesn't physically damage the processor. By lowering the core voltage supplied to the CPU, you also decrease the noise margin for the CPU to properly differentiate between logic 1 and logic 0. This is why -75, for example, works for some and not for others because processors are not 100% identical. The obvious benefit UV is lower power consumption.
gtda said:
hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently
Click to expand...
Click to collapse
I'm also using Tegrak's overclock apk for some time now (from beginning) and it's really good!
Just lower the core voltage (start with cpu level 0) until it's unstable (random reboots), then add a few mv (+5) to make it stable again (no reboots). do this for every core frequency (only one at the time, so you know witch one is making the system unstable). I never touch the internal frequency... Undervolting will NOT damage your CPU (overclocking can if you're not carefull)
Don't be stupid testing just a few hours, test (stress test) for days. Only then you are sure it's stable
These are my settings:
(rock stable after a few weeks => playing asphalt6, running quadrant and smartbench hours a day for a few weeks,...)
cpu level 0
frequency 1000
core 1205mv (-70) => could get it stable at 1200 but had one reboot after one week, so I added +5
internel 1100
cpu level 1
frequency 800
core 1105 (-95) => could get it stable at 1100 but had one reboot after one week, so I added +5
internel 1100
cpu level 2
frequency 400
core 950 (-100)
internal 1100
cpu level 3
frequency 200
core 825 (-125)
internal 1100
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Now I know what my lowest core voltage is, I can start overclocking (not for now).
I'm on stock deodexed JVP 2.3.4 with Hardcore (latest) Speedmod (partition EXT4), Tegrack Overclock Ultimate and Voodoo Control Plus (holy combo => Quadrant 2400+ (no OC, just UV) and wow, what a great battery life!
edit: yes, I need to update my signature
SamHaLeKe said:
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Click to expand...
Click to collapse
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.
kiwijunglist said:
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.
Click to expand...
Click to collapse
Default value is 950mV on my phone according to pimpmycpu. According to SamHaLeKe's post, he's reducing his by -125 so 825mV is correct
I'm new to UV, and just experimenting. My current values are
1200 = -50mV
800 = -50mV
400 = -100mV
200 = -100mV
100 = -150mV
Seems ok so far, more aggressive cutting gave me reboots
$$$
The most i could get from my phone w/o stability issues
1500 - 50
1400 - 50
1300 - 50
1200 - 50
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 150
Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !
Mine are;
1000 : 50
800 : 50
400 : 75
200 : 75
100 : 100
Works great for me
Sent from my GT-I9000 using Tapatalk
swaakx said:
Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !
Click to expand...
Click to collapse
i have the same!
my phone now cold as ice. and greatly stable
I'm a noob at this UV stuff but I'm quite interesting about that.
I tried with Control Freak, should I set first a low voltage on 100Mhz and try to stress the cpu only with this change on 100MHZ? or should I set all voltages and test?
thx for help
i'm on jvq darkyrom
using tegrak overclock ultimate
1200mhz 1255 (-20)
800mhz 1105 (-95)
400mhz 950 (-100)
200mhz 850 (-100)
100mhz 810 (-140)
Mhz vs Quadscore on [beta] desire hd2 #Update
hey here same interesting tests i did
if i locked my phone in power saving mode u get
CPU and Score
Mhz ScoreA CPU Mem IOps Linpack
256Mhz 900 1750 525 1600 11
384Mhz 1050 2580 618 2000 16
460Mhz 1350 3000 990 2600 19
500Mhz 1600 3250 1050 2800 20
768Mhz 2200 4600 1120 3500 29
1000Mhz 2500 5400 1120 4150 35.5
1200Mhz 2700 6200 1120 4380 40
maybe there could be another mode that will use
500mhz most of the time [for normal using or one app using Cpu]
and when playing or using heavy 1000Mhz
[Dev]
i see that memory score is not linear
maybe could fixed by our greatest devers
I hope u do understand that these results are total bullcrap.
The newest dual core chips dont even get 2.7k scores in that benchmark.
Something in the desire HD build farks up the scores simple as that.
If you look at the quadrant advanced score, you'll notice it only gets those scores because of the I/O score. The processor one is about the same or a little more than teh Nexux 2.2, so if you underclock to 500 mhz you may get a total of 1600, but your processor score will suck badly and your phone will lag and really suck.
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
orangekid said:
If you look at the quadrant advanced score, you'll notice it only gets those scores because of the I/O score. The processor one is about the same or a little more than teh Nexux 2.2, so if you underclock to 500 mhz you may get a total of 1600mhz, but your processor score will suck badly and your phone will lag and really suck.
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
Click to expand...
Click to collapse
Agree.
Sent from my HTC HD2
orangekid said:
Keep your max at 998 and your min at 245 and use smartass and you should be fine.
Click to expand...
Click to collapse
+1 for this.
My HD2 has been running smoothly with 245-998MHz smartass for weeks now, battery life has been great too.
i update it with more info check post1
i see that memory score is not linear
maybe could fixed by our greatest devers
Quadrant scores are useless. RUn it, then run it again, you'll get different results.
I don't use SetCPU at all, it's just not needed.
According to my Quad Test im getting a total of 2196 with 245-998mhz with smartass on SetCPU my CPU: 4450 Mem: 1127 I/O: 4716 2D: 273 3D: 412 Work that one out
LiveOC and Custom Voltage guide by TkGlitch
for Glitch kernel V14
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warning!
Overclocking is dangerous and is meant only for experienced users!
1- Introduction :
The "normal" overclocking system on SGS til now was the addition of some frequency steps past the stock 1GHz step. V13 kernel was using 7 overclocked steps
to push the maximum selectable speed to 1.7GHz.
In V14, less overclocked steps are present, but you can still overclock to 1.7GHz if you want (and if your phone is able to do it), and even up to 2.25GHz as a maximum.
You will need NSTools to use LiveOC and custom Voltage features in Glitch kernel V14.
To begin with, I'll explain you some basic things you have to know.
2- Clocks :
The CPU speed is the result of a bus speed and a multiplier.
Bus speed is linked to and equal to GPU and RAM speed.
The multiplier is per step and hardcoded by the kernel developer.
It does look like that : CPU speed = bus speed x multiplier.
Here are my values in V14 :
1500 MHz = 200 x 7.5
1400 MHz = 200 x 7
1300 MHz = 200 x 6.5
1200 MHz = 200 x 6
1000 MHz = 200 x 5
800 MHz = 200 x 4
400 MHz = 200 x 2
200 MHz = 200 x 1
100 MHz = 100 x 1
LiveOC gives you the access to direct and on-the-fly bus overclocking by 1% steps (150% being the maximum available). I'll say it again : BUS overclocking !
Though, it'll overclock the bus on all the steps at the same time, for the same percentage.
We'll talk about that later.
So if I want to overclock my 1GHz step to 1.1GHz, I'll have to select 1GHz as max frequency, and push LiveOC to 110%.
My bus speed beeing overclocked by 10% will give the following :
220 x 5 (1GHz multiplier) = 1100 MHz.
If you want to go higher than 1.5GHz, it's the same :
Set 1500 MHz as maximum frequency (for example), and push LiveOC. Let's say to 110%. You will get the following :
220 x 7.5 (1.5GHz multiplier) = 1650 MHz.
Pushing it to 114% will give 1710 MHz (228MHz bus) and so on, up to 150% giving 2250 MHz running an inachievable 300MHz bus.
SINCE V14 BETA 6, 100, 200 and 400 MHz steps won't be affected by LiveOC. It should help to stabilize your overclock in most cases.
3- The limits :
THE MAIN LIMIT AND PHONE KILLER IS HIGH TEMPERATURE. WARM IS OK, HOT IS TOO HOT. DON'T PLAY STUPID.
Obviously, so much control over the bus speed, frozen til now to what the kernel developer set, will also give you the ability to find the limits of your chip.
The main clocking limit is generally the RAM, corrupting itself when the bus speed is too high. And since the GPU uses the RAM as well, it'll become crashy too. That's why I have decided to add some steps with a bigger multiplier, to lower the bus for a higher CPU frequency.
The bus speed limits for you will be anywhere between 240 and 270 Mhz, depending on your device potential (higher and lower exists but rare).
Average is 240 MHz.
The CPU speed limits will be anywhere between 1300 and 1800 MHz (higher and lower exists but rare as well).
Average is 1400 MHz.
With that in mind, I wouldn't go too far past 130% (giving 260MHz bus speed).
4- The sweet spot :
What you want when overclocking is to get the best balance for each part. Since the bus is linked to RAM and GPU, you obviously want it as high as possible for gaming, video playing, web browsing etc. (even more now with GPU acceleration in Android 4.0+). Though, as you know already if you've read this guide til now, all steps in V14 are using the stock 200MHz frequency.
So what to do if I want a lower CPU speed with a higher bus/GPU speed ? Simple ! Just select a lower frequency step as starting point.
Let's say we want 250 MHz bus speed, so we'll use 125% LiveOC :
Using 800MHz step, you'll get 1GHz.
Using 1GHz step, you'll get 1.250GHz.
Using 1.2GHz step, you'll get 1.500GHz.
Using 1.3GHz step, you'll get 1.625GHz.
Using 1.4GHz step, you'll get 1.750GHz.
Using 1.5GHz step, you'll get 1.875GHz.
5- The issues :
With a new overclocking system obviously comes some new problems related to it.
With the ability to fine tune the frequencies, you'll find that some frequencies are buggy somewhat, giving low performances. For example, using 115% Live OC with the 1.3GHz step will give some poor performances, when 114 and 116% won't. It could be a NSTools issue, but I think it has more to do with the hardware. It's well known that on CPUs some frequencies or even frequency ranges can be buggy, unstable, or slow. If you encounter that, try to add or remove a percent to LiveOC.
As said earlier, LiveOC will overclock the bus for all steps at the same time by the same amount of %.
Knowing that, you'll have to adapt your voltages for all the frequencies to stay stable, and this for any sensible change on LiveOC percentage.
6- Custom Voltage :
What would be LiveOC without Custom Voltages ?!
I did add leakage values to Glitch kernel features when I saw that some phones were overclocking much better with the right balance between ARM and Int voltages, depending on the phone, with very different results. The leakage value was basically that : balance between the two.
Well, as you probably know if you did read the changelogs, you have now the capacity to overvolt/undervolt both the ARM voltage (the CPU voltage you know well already), and the Int (internal) voltage. The last one is the voltage going to the GPU/memory controller, and will need to be tweaked accordingly to your phone.
As a starting point, here are the Int voltage values I was using for each leakage, adapted for V14 new frequency table :
HIGH LEAKAGE :
1500 : 1.225
1400 : 1.200
1300 : 1.175
1200 : 1.150
1000 : 1.125
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
MEDIUM LEAKAGE :
1500 : 1.200
1400 : 1.175
1300 : 1.150
1200 : 1.125
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
LOW LEAKAGE :
1500 : 1.175
1400 : 1.150
1300 : 1.125
1200 : 1.100
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
Of course, using LiveOC will force you to change these voltages accordingly.
Here are some advices about this :
- Try to stay around 1.225 - 1.250V for your highest frequencies;
- Try not to ever go past 1.300V if you don't want to kill your phone quickly;
- Be VERY gentle when tweaking it as it is VERY sensitive;
- Try to follow a more or less linear curve for Int voltage on OC frequencies;
- Going below 1.000V on 100MHz step will generally kill stability with no battery gain.
This guide may change depending on my decisions related to the Glitch kernel development, or to polish / add things to it.
Thanks to Ezekeel from Nexus S section for these awesome tools.
LiveOC : http://forum.xda-developers.com/showthread.php?t=1288015
Custom Voltages : http://forum.xda-developers.com/showthread.php?t=1331610
23/01/2012 - UPDATED TO REFLECT V14-B1 CHANGES.
09/02/2012 - UPDATED TO REFLECT V14-B3 CHANGES.
24/03/2012 - UPDATED TO REFLECT V14-B6 CHANGES.
Reserved. Just in case.
Awesome, this new LiveOC system really is something else.
Thanks Glitch. This is a really great and comprehensive guide from which many people will benefit.
Bow to tk-glitch. new year gift by glitch .
My 'love' oc value is 110% with Max over clock to 1320 MHz and min to 110 MHz and governed on on demand.
I didn't touched arm voltages
My int voltages are as follows:-
Max- 1225
1400-1200
1304-1175
1200-1125
1000-1100
800-1075
400-1050
200-1025
100-1000
Phone is pretty damn stable on these frequencies , I was facing some instability earlier but not now. Phone is dancing on my fingers, but will this effect battery a lot. Tk-glitch did I did it correctly or anything else have to be done??
@BHuvan goyal : Looks good to me
Tk-Glitch said:
@BHuvan goyal : Looks good to me
Click to expand...
Click to collapse
Will test at different frequencies from time to time and will report here once build 12 comes out as build 11 has some minor problems. Btw I accidentally went up to 150% and screen started to display weird lines ( horizontal ) and phone rebooted but that's bound to happen as I know that was at maximum.
As said, the bus limits are around 250 MHz for most phones, so with 150% pushing it to 300 MHz (and even more on the 1.3GHz step) your device will instantly freeze or crash
~ 130% is around the hardware limits
So what is the best method to save energy? Lower int and/or arm voltages?
"- Going below 1.000V on 100MHz step will generally kill stability with no battery gain."
Does it makes sense to lower arm voltage on 100mhz if >1V int causes instability?
Underclock and lower ARM voltage (both). If you only lower voltage, or only underclock, the gains will be poorer.
I just want to undervolt (same performance, lower energy consumption), but I'm not sure how to find the lowest arm and int voltages.
Frist int, then arm? I guess balance is the problem^^
just testing, not stable:
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 850/875/1000/1175/1250
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 800/800/950/1125/1200
frist arm, then int.. for tomorrow
reborn90 said:
I just want to undervolt (same performance, lower energy consumption), but I'm not sure how to find the lowest arm and int voltages.
Frist int, then arm? I guess balance is the problem^^
just testing:
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 850/875/1000/1175/1250
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 800/800/950/1125/1200
Click to expand...
Click to collapse
First arm, then int.
Thanks for the amazing kernel and the OC/UV options to puch our silicon to it's limits!
Question...
f.e.
I can change Max CPU freq to 1200 MHz with no other adjustments to voltage or Live OC and system is totally stable (can even go all the way to 1300 MHz without changing voltages, stable)
or
I can change Live OC Value to 115 % with no other adjustments to voltage and Max CPU freq set to 800 and system is totally stable. (CPU will be 920 MHZ and GPU 230 MHz)
but
When I change both to let say Live OC Value to 115 % and CPU freq set to 1000
the system becomes unstable (CPU will be 1150 MHz and GPU 230 MHz)
So I can run my CPU at an even higher freq then 1150 MHz totally stable but not together with Live OC (separately also totally stable). What's the catch? I even tried 114 % 116% 113% but can't get it stable together (separately no problem). Also some suggestions on voltage settings (Int) would be nice to see... Thanks again
-Sam-
@SamHaLeKe :
As you guessed, it's probably the Int voltage causing problems. Push it a bit (let's say 0.050V), and see if it's any better. It's obviously not the CPU freq causing problem, but more probably the bus freq. BTW, stock ARM voltage for 1GHz could be too low for 1150MHz, so pushing it a bit, towards 1.3V, should help too.
Good luck.
Tk-Glitch said:
@SamHaLeKe :
As you guessed, it's probably the Int voltage causing problems. Push it a bit (let's say 0.050V), and see if it's any better. It's obviously not the CPU freq causing problem, but more probably the bus freq. BTW, stock ARM voltage for 1GHz could be too low for 1150MHz, so pushing it a bit, towards 1.3V, should help too.
Good luck.
Click to expand...
Click to collapse
Thanks for the quick answer. The strange thing is that separately it's working perfectly fine without changing any voltages. Like I said, separately I can go all the way to 1200 MHz CPU freq without changing ARM voltage and system is totally stable (I have a good silicon...). So there is no need to push my voltage for 1150 MHz and I already tested that option. Also bus freq is working fine separately but not together with changing CPU freq. Adding voltage for bus freq makes it even unstable, while it is working stable when changing bus freq separately on default Int. voltages. Very strange but will sertainly do more testings and find the sweet spot....
Thanks again
-Sam-
I noticed a strange behavior when I was testing a new frequency. For example 400mhz:
min 100mhz max 400mhz, stock int V; the phone freezes with >1V if I try to wake it from idle, but it passes every stress test (performance gov.) with >1V..
SamHaLeKe said:
Thanks for the quick answer. The strange thing is that separately it's working perfectly fine without changing any voltages. Like I said, separately I can go all the way to 1200 MHz CPU freq without changing ARM voltage and system is totally stable (I have a good silicon...). So there is no need to push my voltage for 1150 MHz and I already tested that option. Also bus freq is working fine separately but not together with changing CPU freq. Adding voltage for bus freq makes it even unstable, while it is working stable when changing bus freq separately on default Int. voltages. Very strange but will sertainly do more testings and find the sweet spot....
Thanks again
-Sam-
Click to expand...
Click to collapse
Default voltage is higher @ 1.2 than @ 1GHz. It won't magically change because you did use LiveOC.
reborn90 said:
I noticed a strange behavior when I was testing a new frequency. For example 400mhz:
min 100mhz max 400mhz, stock int V; the phone freezes with >1V if I try to wake it from idle, but it passes every stress test (performance gov.) with >1V..
Click to expand...
Click to collapse
To get one isolated step stable is one thing, to get it stable with others is another story. Nothing strange in that, it's as old as the world of clocks ^^
please share your settings which is good in performance.... Im already blurred...
Sent from my GT-I9000 using Tapatalk
DaxIΠFIΠITY said:
please share your settings which is good in performance.... Im already blurred...
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Try the once that I use, first page 5 or 6th post. My phone is blazing fast.
Yeah am new To xda and i want to overclock my defy @ 1.2 ghz ... and whenever
i try to overclock above 1000 mhz it starts heating upto 43 degrees... plz give me the overclocking values @ stable ... and is this overheating do serious damage to phones hardware!.....! thanks
My setting :
300 Mhz / 30 Vsel
600 Mhz / 42 Vsel
800 Mhz /50 Vsel or 900 Mhz / 54 Vsel
1.0 Ghz / 58 Vsel or 1.2 Ghz / 66 Vsel
You can use this setting without any risk. 1.2 Ghz is the original value of OMAP 3630 on Droid2.
But i think you have another problem on your phone (something running) to get 43° for your battery. Mine is allways between 30° and 37° max running at 1.2 GHZ...
Note : original Defy+ settings = 300/33 ; 600/48 ; 800/58 ; 1000/68
devilthehellraiser said:
Yeah am new To xda and i want to overclock my defy @ 1.2 ghz ... and whenever
i try to overclock above 1000 mhz it starts heating upto 43 degrees... plz give me the overclocking values @ stable ... and is this overheating do serious damage to phones hardware!.....! thanks
Click to expand...
Click to collapse
300mhz @ 26Vsel
600mhz @ 38Vsel
1200 mhz @ 58 Vsel
what vsel do u use for 1ghz?
For 1.2ghz try using a low vsel and test if it works. Keep increasing it by 1 until it is stable.
For my phone the minimum it could handle wihtout crashing immediately is 56. Its pretty stable at 58 and for games or if i need more stability i try to raise it to 60-64. But it starts heating faster
i use 48 for 1 ghz its rock stable as it never crashed ...
minez - 320 at 17 ,,, 650 at 38 ,,, 1.2GHz at 60 ..... very stable
Mine is:
[email protected]
[email protected]
[email protected]
very stable and not too much heating
Mine is
22 300mhz
32 600mhz
52 1ghz
Been using them settings for many months
devilthehellraiser said:
Yeah am new To xda and i want to overclock my defy @ 1.2 ghz ... and whenever
i try to overclock above 1000 mhz it starts heating upto 43 degrees... plz give me the overclocking values @ stable ... and is this overheating do serious damage to phones hardware!.....! thanks
Click to expand...
Click to collapse
Do you really need 1.2ghz? Don't set high frecuencies if you dont need it.
Anyway, dont worry too much about temp. I'm on a hot country, and when i'm heavy using my defy, temp raises to 45C, no problem.
All android phones have automatic cooling mode when you reach critic temps. You dont have to worry about that.
Sent from my MB525 using XDA App
my settings are:
[email protected]
[email protected]
[email protected]
i could lower each setting with 2 vsel and still get a stable phone, but i increased it just in case. and yeah, you dont need 1.2GHz, 1GHz will do just fine, dont worry.
My settings are:
[email protected]
[email protected]
[email protected]
1.2ghz is awesome and what it supposed to be
Just stumbled across this thread, wanting to test 1.2ghz and was wondering what app you guys are using to monitor temperatures? is set cpu good enough?
dude i use battery xl and it displays temp in the notifications !
My settings are:
[email protected]
[email protected]
[email protected]
greetings!
Com4nd3r said:
My settings are:
[email protected]
[email protected]
[email protected]
greetings!
Click to expand...
Click to collapse
These settings seem to be the most stable ive tried so far on my defy, and temp is very cool at 27 degrees. Thanks
I do suppose it depends on your phone i had 2 zte blades and one of the them was stable at 826mhz but the other would not go above 710mhz without constant reboots
Wait until we get unlocked boot loader that is when the overclocking gets serious XD my nexus is at 1.2ghz with smartassV2 govenor and its rock stable, saying that with unlocked bootloader the potential is endless like with my xperia arc it has qualcomm snapdragon msm8255 @ 1ghz but with DooMLoRD's kernel can have a max of 1.9ghz But then again i hate my xperia arc lol
furrabbit.nh said:
These settings seem to be the most stable ive tried so far on my defy, and temp is very cool at 27 degrees. Thanks
I do suppose it depends on your phone i had 2 zte blades and one of the them was stable at 826mhz but the other would not go above 710mhz without constant reboots
Wait until we get unlocked boot loader that is when the overclocking gets serious XD my nexus is at 1.2ghz with smartassV2 govenor and its rock stable, saying that with unlocked bootloader the potential is endless like with my xperia arc it has qualcomm snapdragon msm8255 @ 1ghz but with DooMLoRD's kernel can have a max of 1.9ghz But then again i hate my xperia arc lol
Click to expand...
Click to collapse
not every cpu is identical , thats why not every phone can reach the same clock rates. To avoid damaging your cpu , its important not to set the vsel too high.
On my defy i never had it set over 65vsel.
70vsel is the max. limit so ive heard.
when yous settings are unstabile you could either clock down or set your vsel higher.
I AM USING [ROM]Android 2.3.6 - 4.5.2-109_DHT-25(mod. "spear1403")
I CHANGE A VERY FEW VALUES FROM: RECOVERY, SYSTEM, OVERLOCK. AND MY PHONE GONE SLOW, LIMPACK SHOW ME: 4 MFLOP!!!
SOME ONE TRY THIS?
1.2 GHz!!! the battery drains very fast or not?
My Defy is stable with:
vsel1: 25 vsel @ 0330 mhz
vsel2: 38 vsel @ 0800 mhz
vsel3: 51 vsel @ 1200 mhz
vsel4: 62 vsel @ 1400 mhz
The Defy of my GF crashes with these settings...
she uses:
vsel1: 31 vsel @ 0330 mhz
vsel2: 41 vsel @ 0800 mhz
vsel3: 58 vsel @ 1000 mhz
vsel4: 64 vsel @ 1200 mhz
EDIT: I need 1400 mhz to play GTAIII lagfree also lot of stuff like Skype calling / Fritz Fon / PhotoShop Express are working better on 1400 than on 1000, I don't understand why everybody says we do not need more than 1000, also the battery drain is about the vsel and not the frequency. My battery lasts loger on 62 vsel @ 1400 than on 64 vsel @ 1200
I am reading the posts in XDA about changing the default frequency of processor in DEFY as I am a beginner of CPU overclock, would like to ask for advice:
1. What is "vsel"? Is it the voltage set for the processor to run in certain frequency?
2. What is the default "vsel" for DEFY in 800MHz? I guess it is 58, right?
Correct me if I am wrong. Thanks a lot!
Hello!
So this app was created originally for Motorola Defy, but i would like to test it on other devices.
It calculates the ideal Vsel based on your CPU frequency.
If you have 4 Vsels it will show you 4 results. If you have 3 it will show you 3
You can find the download link in the original thread (link below).
I hope you will enjoy it!
http://forum.xda-developers.com/showthread.php?t=1815142
i gave it a try
the app is working, however i guess the results are way to low for the milestone
for comparison my milestone with cm7.2 has these settings:
800mhz @ 59
600mhz @ 52
400mhz @ 40
250mhz @ 32
125mhz @ 26
vsel calc gives me:
800mhz @ 42
600mhz @ 32
400mhz @ 22
250mhz @ 14
this is a big difference
UnitedOceanic said:
i gave it a try
the app is working, however i guess the results are way to low for the milestone
for comparison my milestone with cm7.2 has these settings:
800mhz @ 59
600mhz @ 52
400mhz @ 40
250mhz @ 32
125mhz @ 26
vsel calc gives me:
800mhz @ 42
600mhz @ 32
400mhz @ 22
250mhz @ 14
this is a big difference
Click to expand...
Click to collapse
Fix on the way. Expect new build roday
Sent from my MB525 using xda app-developers app
UnitedOceanic said:
i gave it a try
the app is working, however i guess the results are way to low for the milestone
for comparison my milestone with cm7.2 has these settings:
800mhz @ 59
600mhz @ 52
400mhz @ 40
250mhz @ 32
125mhz @ 26
vsel calc gives me:
800mhz @ 42
600mhz @ 32
400mhz @ 22
250mhz @ 14
this is a big difference
Click to expand...
Click to collapse
Our kernel (motorola milestone (A853)) supports 5 slots for frequency. Have you deleted the 1000MHz/64vsel that kabaldan's cm7 includes by default?
btw, I've been running 1ghz at 60vsel for a while and it was stable. I guess it depends, up to a point, on individual device how high/low can mhz/vsel go.
But those values indeed seem too low.
mrvek said:
Our kernel (motorola milestone (A853)) supports 5 slots for frequency. Have you deleted the 1000MHz/64vsel that kabaldan's cm7 includes by default?
btw, I've been running 1ghz at 60vsel for a while and it was stable. I guess it depends, up to a point, on individual device how high/low can mhz/vsel go.
But those values indeed seem too low.
Click to expand...
Click to collapse
yeah i deleted the default, i played some psx games with fpse and my milestone was pretty hot in couple of minutes. first i changed the cpu clock via cyanogen performance settings. everything worked fine but i wanted to save some battery too. so i looked until i found a 800mhz 10overclock file.
Added 5th row. Haven't fixed milestone settings yet...i'm on vacation
TO UPDATE THE APP JUST OPEN IT AND IN NOTIFICATION BAR THERE SHOULD BE UPDATE NOTIFICATION!