Has anyone overclocked a Defy+ MB526 with Quarx CM10 27.10 build?
Which CPU Clock and Vsel should I choose? Where?
nastys said:
Has anyone overclocked a Defy+ MB526 with Quarx CM10 27.10 build?
Which CPU Clock and Vsel should I choose? Where?
Click to expand...
Click to collapse
go to recovery.choose cpu and there will be values,clk1 clk2...clk4
these are the clock values,update them to whatever u need.and set the vsel accordingly,in vsel1 ...vsel4 respectively
bds bamrah said:
go to recovery.choose cpu and there will be values,clk1 clk2...clk4
these are the clock values,update them to whatever u need.and set the vsel accordingly,in vsel1 ...vsel4 respectively
Click to expand...
Click to collapse
I know how to, but I'd like to know safe values first. What happens if I set something wrong?
Sent from my MB526 using xda app-developers app
nastys said:
I know how to, but I'd like to know safe values first. What happens if I set something wrong?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Use vsel calculator app.will give u optimum values.u can test them by lowering ur vsels 1 ir 2 points at a time .if u lower them too much.the phone will reboot randomly.if u increase them too much.there is a risk to burn the cpu.
Sent from my MB526 using xda app-developers app
nastys said:
I know how to, but I'd like to know safe values first. What happens if I set something wrong?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
I use 300/17 600/32 800/42 1000/52 without problems. To get the vsel I do frec/20+2.
How can I prevent burning my CPU? Is Vsel Calculator safe?
nastys said:
How can I prevent burning my CPU? Is Vsel Calculator safe?
Click to expand...
Click to collapse
Stay within the safe clock frequency.less than 1300mhz.u wouldnt need dat much.defy is pretty much lagless on 1100mhz.and always set vsel less than tha omtimised value.vsel calculator is perfectly safe.doesnt do anything.just tells u the optimum safe values of vsel corresponding to the clock value by a formula.just simple calculation.nothing more
Sent from my MB526 using xda app-developers app
bds bamrah said:
Stay within the safe clock frequency.less than 1300mhz.u wouldnt need dat much.defy is pretty much lagless on 1100mhz.and always set vsel less than tha omtimised value.vsel calculator is perfectly safe.doesnt do anything.just tells u the optimum safe values of vsel corresponding to the clock value by a formula.just simple calculation.nothing more
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Calculated:
CPU Freq Recommended Voltage
1100 MHz 57 +/-2
800 MHz 42 +/-2
600 MHz 32 +/-2
300 MHz 17 +/-2
So I should set frequency 4 to 1100 and vsel to 57, right?
And what are Vsel and Recommended Voltage?
nastys said:
Calculated:
CPU Freq Recommended Voltage
1100 MHz 57 +/-2
800 MHz 42 +/-2
600 MHz 32 +/-2
300 MHz 17 +/-2
So I should set frequency 4 to 1100 and vsel to 57, right?
And what are Vsel and Recommended Voltage?
Click to expand...
Click to collapse
Yup, you got it right. Set vsel 4 to 57±2... and freq 4 to 1100.
Vsel is CPU voltage... this is the recommended voltage for the freq u selected.
WAIT... I went to Bootmenu CPU settings and Vsel values are different from Vsel Calculator.
Clk Vsel
300 MHz 30
600 MHz 46
800 MHz 54
1000 MHz 58
Why are they different from Vsel Calculator values? Isn't it dangerous to change voltage values? What happens if I set a totally different voltage?
Sorry for the questions, I'm not an expert of OC...
EDIT: I searched online and I found that voltages are high by default because CPUs are stable at different voltages from phones to phones.
How do I safely determine my CPU's stable voltage without damaging the hardware?
I think you can use the vsel=freq/20+2 formula.
It's always working for me and stable!
My current values 300/17,600/32, 800/42, 1100/57
nastys said:
WAIT... I went to Bootmenu CPU settings and Vsel values are different from Vsel Calculator.
Clk Vsel
300 MHz 30
600 MHz 46
800 MHz 54
1000 MHz 58
Why are they different from Vsel Calculator values? Isn't it dangerous to change voltage values? What happens if I set a totally different voltage?
Sorry for the questions, I'm not an expert of OC...
EDIT: I searched online and I found that voltages are high by default because CPUs are stable at different voltages from phones to phones.
How do I safely determine my CPU's stable voltage without damaging the hardware?
Click to expand...
Click to collapse
Its different from vselcalc bcoz it only calculates and estimates that your hardware will run ok with these values.doesnt mean that its your actual values.
You can select any one clock at a time.and lower its vsel by 1 or 2.than reboot into system.and check if it is stable.like you dont face any fc.and reboots.this way your hardware will not damage.and you can find optimum values.if it reboots.simply increase the corresponding vsel by 1 or 2.just try not to go beyond vsel 65.it will not burn.but its not safe.so try to be within 65.. its not that hard.give it a try.i hope this clear things up for you. :thumbup:
sent from flying machine with qkernel ..
so, how is it working?
ovu85 said:
so, how is it working?
Click to expand...
Click to collapse
I set Clock 4 to 1100 MHz and leaved Vsel to default (58). I saved and booted 2ndboot from bootmenu, and CyanogenMod boot animation showed for a while, then black screen. I removed and inserted the battery and it booted successfully. I played Subway Surfers so I think it's stable, but animations seem slower. Maybe Vsel is too low?
And is it stable at 1.2 GHz and Vsel 62?
EDIT: it's not very stable, it rebooted in the app drawer....
Sent from my MB526 using xda app-developers app
nastys said:
I set Clock 4 to 1100 MHz and leaved Vsel to default (58). I saved and booted 2ndboot from bootmenu, and CyanogenMod boot animation showed for a while, then black screen. I removed and inserted the battery and it booted successfully. I played Subway Surfers so I think it's stable, but animations seem slower. Maybe Vsel is too low?
And is it stable at 1.2 GHz and Vsel 62?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Animation doesnt depend on your vsels...and its safe to go for that.but it wont be needed.1100 is more than enuff
sent from flying machine with qkernel ..
Two more things: which settings does Bootmenu use? If it uses my settings and they are not stable how can I enter bootmenu?
And I read in the user's manual that if the phone heats too much it shows a warning and you can only call emergency, does it apply only for stock ROM or also for CM10?
Sent from my MB526 using xda app-developers app
nastys said:
Two more things: which settings does Bootmenu use? If it uses my settings and they are not stable how can I enter bootmenu?
And I read in the user's manual that if the phone heats too much it shows a warning and you can only call emergency, does it apply only for stock ROM or also for CM10?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
U can always enter into bootmenu.by pressing vol down at blue led.
And there is no such thing as only emrgency at overheat
sent from flying machine with qkernel ..
bds bamrah said:
U can always enter into bootmenu.by pressing vol down at blue led.
And there is no such thing as only emrgency at overheat
sent from flying machine with qkernel ..
Click to expand...
Click to collapse
I know how to enter bootmenu, but if I set a totally unstable Vsel, the phone should always reboot, so it would be impossible to restore default settings, right? Or does bootmenu use different settings?
Sent from my MB526 using xda app-developers app
nastys said:
I know how to enter bootmenu, but if I set a totally unstable Vsel, the phone should always reboot, so it would be impossible to restore default settings, right? Or does bootmenu use different settings?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Phone will reboot after you are fully booted into your rom.after blue led and boot animation dude
sent from flying machine with qkernel ..
bds bamrah said:
Phone will reboot after you are fully booted into your rom.after blue led and boot animation dude
sent from flying machine with qkernel ..
Click to expand...
Click to collapse
Thank you very much! I think I will OC to 1.2 GHz 62 Vsel later.
Sent from my MB526 using xda app-developers app
Related
Why is my aria automatically underclocking itself everytime I lock my phone?
Sent from my HTC Liberty using XDA App
Since we're on the subject, does anybody know what mHz the arias cpu underclocks to when its screen locked/screen off (with NO music player or calls or anything like that going)?
245Mhz if I'm not mistaken.
Sent from my HTC Liberty
Shad0wguy said:
245Mhz if I'm not mistaken.
Sent from my HTC Liberty
Click to expand...
Click to collapse
Just to confirm. My CPU stats show:
245.76 mhz 74% of the time
480 mhz 20% of the time
600 mhz 6% of the time
manojsuper said:
Because it saves battery and tries to keep the battery maintained at a constant temperature. Your phone works through the "ondemand" mechanism...when ever you need more processing power, your phone will work up to that mHz.
Click to expand...
Click to collapse
It stays at 245 unless I overclock it back to 600, then when I locked it it went back to 245 and kept doing the same thing.
I had to uninstall setcpu and restart my phone and its fine now
Sent from my HTC Liberty using XDA App
If defy can be OC to 1.1~1.3 GHz from 800 mhz then y can't defy plus be OC to 1.4~1.6 GHz from 1GHz ? Since defy+ has better chip set than defy though CPU n gpu used remains same ...
Sent from my MB526 using xda app-developers app
Hi, 1200mhz vsl60 is enough. Or you want kill the lifetime of your cpu and over this the battery drain empty before the handy is on.
Sent from my MB526 using xda premium
Defy and Defy+ have the same CPU but different kernel (which is software). The kernel limits the clock. Defy+ stock gingerbread kernel adds Clk4 and Vsel4 which are 1 GHz and 58 Vsel by default. I have a Defy+ overclocked to 1.2 GHz Vsel 60. The clock is limited by the kernel and Vsel by the hardware. My hardware at 1.2 GHz is stable at 60 Vsel, yours may be stable at 58 or 62. I know some people OC their Defy at 1.4 GHz but they set a dangerous Vsel to be stable (70 and above). 1.2 GHz is enough.
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
nastys said:
Defy and Defy+ have the same CPU but different kernel (which is software). The kernel limits the clock. Defy+ stock gingerbread kernel adds Clk4 and Vsel4 which are 1 GHz and 58 Vsel by default. I have a Defy+ overclocked to 1.2 GHz Vsel 60. The clock is limited by the kernel and Vsel by the hardware. My hardware at 1.2 GHz is stable at 60 Vsel, yours may be stable at 58 or 62. I know some people OC their Defy at 1.4 GHz but they set a dangerous Vsel to be stable (70 and above). 1.2 GHz is enough.
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
Click to expand...
Click to collapse
Haven't u tried over clicking at 1.4ghz ? coz some say we find optimum vsel will be 68 n anything less than this would be stable ?
Sent from my MB526 using xda app-developers app
Its blocks ma defy + ...go for 1.2
Sent from my MB526 using xda premium
suhasgudmi said:
Haven't u tried over clicking at 1.4ghz ? coz some say we find optimum vsel will be 68 n anything less than this would be stable ?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
You can try it yourself. The max I've gone to is 1300 MHz/ 68 vsel... battery heat was very high at 68... many others have also tried, and get the same result as I did.
But as they say, experience is the best teacher, so you're welcome to try it out yourself, and let us know.
krushnam said:
You can try it yourself. The max I've gone to is 1300 MHz/ 68 vsel... battery heat was very high at 68... many others have also tried, and get the same result as I did.
But as they say, experience is the best teacher, so you're welcome to try it out yourself, and let us know.
Click to expand...
Click to collapse
So u ve over clocked to 1.4 GHz o reduced to 1.3 GHz ? I really don't understand y defy+ can't be OC more whereas defy can be as it can also reach 1.2~1.3 GHz ...... buying defy would ve been better I guess .....
Sent from my MB526 using xda app-developers app
suhasgudmi said:
So u ve over clocked to 1.4 GHz o reduced to 1.3 GHz ? I really don't understand y defy+ can't be OC more whereas defy can be as it can also reach 1.2~1.3 GHz ...... buying defy would ve been better I guess .....
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
are you really telling me that you find a difference in 1.2 ghz and 1.4 ghz, while you're using your phone? all you're doing is encouraging battery drain and more wear and tear on your cpu..
syllogyking said:
are you really telling me that you find a difference in 1.2 ghz and 1.4 ghz, while you're using your phone? all you're doing is encouraging battery drain and more wear and tear on your cpu..
Click to expand...
Click to collapse
Ofcourse there is a huge difference betwn 1.2 n 1.4 GHz.........its all about processing speed which matters for smartfone users ...... Y would there be 3 ~4k rs difference for an 800 mhz n 1GHz cell phones?
Sent from my MB526 using xda app-developers app
Defy and Defy+ have the SAME CPU, but Defy+ is clocked at 1.0 GHz by default.
Cost difference is also for bigger battery and better camera
Sent from my MB526 using xda premium
So I was trying to mess around with CPU profiles and I noticed that the low end of the CPU is clocked at 1GHz. If I lower it with Rom Toolbox, it just goes right back up after I leave the menu. the profiles won't stick, governors don't make a difference, and I'm a little confused.
Can someone shed some light on this for me?
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
It is 384MHz. The lower frequency change because of project butter that make the cpu run at a higher frequency when you touch the screen.
Sent from my Nexus 4 using xda app-developers app
Dont you need a custom kernal in order to change the clock speeds?
sent via xda premium with nexus 7
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Is this somewhat similar to perflocker in HTC devices? It had to be disabled to change any cpu settings AT ALL with the stock kernel.
hervelo said:
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is why..
sent via xda premium with nexus 7
ed10000 said:
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
Click to expand...
Click to collapse
You're right. I guess it just has its own profile to set at 1GHz when the screen is on, because the CPU Spy showed it in Deep Sleep/384Mhz for the majority of the night.
test1
Hi is 1.2ghz safe to use for a long period of time?? Not on peformance gov coz im using it with smartassv2 i assume its safe because the defy got pumped up to 1ghz from the standard 800mhz on the plus and newer models and will it serious harm to cpu???
Sent from my MB525 using xda app-developers app
i had the clock frequency at 1.2 ghz for some days and it went good, so i think that's safe
My Defy (MB525) is running at 1.3 GHz for over a year. Not a single glitch. (SetVsel config: 16 Vsel1 @ 300 MHz, 28 Vsel2 @ 600 MHz, 70 Vsel3 @ 1300 MHz - up_treshold 86 %)
seckss said:
My Defy (MB525) is running at 1.3 GHz for over a year. Not a single glitch. (SetVsel config: 16 Vsel1 @ 300 MHz, 28 Vsel2 @ 600 MHz, 70 Vsel3 @ 1300 MHz - up_treshold 86 %)
Click to expand...
Click to collapse
So wats the battery consuption like and temprature
Sent from my MB525 using xda app-developers app
Well battery consumption mostly depends on using the 3G in my case. I am connected to mobile internet all day, so battery lasts from 12 - 30 hrs. Temp is at 30 °C on stand by. While playing, e.g. Predators, it is at 42 °C.
Sent from my MB525 using Tapatalk 2
seckss said:
Well battery consumption mostly depends on using the 3G in my case. I am connected to mobile internet all day, so battery lasts from 12 - 30 hrs. Temp is at 30 °C on stand by. While playing, e.g. Predators, it is at 42 °C.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Im a big predators fan and the alien franchise:thumbup::thumbup:
Sent from my MB525 using xda app-developers app
ttocs99 said:
Hi is 1.2ghz safe to use for a long period of time?? Not on peformance gov coz im using it with smartassv2 i assume its safe because the defy got pumped up to 1ghz from the standard 800mhz on the plus and newer models and will it serious harm to cpu???
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
Clk1/Vsel1: 300/17
Clk2/Vsel2: 800/42
Clk3/Vsel3: 1100/56
Clk4/Vsel4: 1300/66
Using this since 3 months. Brilliant performance
(no heating, no lags)
I use 1.1 ghz max...
I have read in some forums about the "sweet spot" of cpu frequency (The cpu frequency at which power consumption by the phone is the least possible).
I want to know what's the "sweet spot" of MB526.
Anyone?
300 mHz, because the vsel is lowest at that frequency? Not sure what exactly is meant by sweet spot
Sent from my MB526 using xda premium
reply
thekguy said:
300 mHz, because the vsel is lowest at that frequency? Not sure what exactly is meant by sweet spot
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Sweet spot is the cpu frequency at which power consumption is the lowest.... Any frequency lower than that will actually increase power consumption...Apparently, for the Galaxy SL, it is 400Mhz....
hotdog125 said:
Sweet spot is the cpu frequency at which power consumption is the lowest.... Any frequency lower than that will actually increase power consumption...Apparently, for the Galaxy SL, it is 400Mhz....
Click to expand...
Click to collapse
I think we need experiment for this. I am trying 350 mhz now
Sent from my MB525 using Tapatalk 2
Doesn't power consumed=>vsel logically? So 300mHz
Sent from my MB526 using xda premium
reply
thekguy said:
Doesn't power consumed=>vsel logically? So 300mHz
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Apparently not. Too low frequencies can make the phone unuseably slow + increase power consumption:cyclops:
I can understand the phone being slower, but why consume more battery at lowest vsel
Sent from my MB526 using xda premium
thekguy said:
I can understand the phone being slower, but why consume more battery at lowest vsel
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
No answer for that. But tests have shown that it's true.
How have you found that out? I have personally had a positive experience with lower vsels
Sent from my MB526 using Tapatalk 2
thekguy said:
How have you found that out? I have personally had a positive experience with lower vsels
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I think 300Mhz is the sweet spot.
hotdog125 said:
I think 300Mhz is the sweet spot.
Click to expand...
Click to collapse
Exactly. As vsel decreases, power consumption decreases and because 300 mHz has lowest vsel, it is the least power consuming state
hotdog125 said:
I think 300Mhz is the sweet spot.
Click to expand...
Click to collapse
OK, well...
I also don't understand this relation between low frequency and higher power consumption, but there is no real difference in battery usage between 300 and 600mHz for me at least. Just set Max Freq to 300 or 600 and use ondemand/conservative governor.