Database Users

-0.25mv / 1500Mhz gives more quadranet vs stock 1400 mhz and stock voltage

-0.25mv / 1500Mhz gives more quadranet vs stock 1400 mhz and stock voltage
how healthy to keep it this way? any risk go up to 1600Mhz?
on last Omega JB rom i went from 4000 to 5130 in quadrant using this OC.
Thanks!

Of course higher clocks gives vigher benchmarks. Uv doesn't affect unless you uv to the point that voltage can't keep cpu stable.
Sent from my GT-I9300 using xda app-developers app

johku12 said:
Of course higher clocks gives vigher benchmarks. Uv doesn't affect unless you uv to the point that voltage can't keep cpu stable.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
The question: 1500-1600 levels risky to CPU ?
UV lower is good to keep temp lower...

From my experience, undervolting offers no benefits at all. Temperature remains the same and battery seems to be worse when idling.

with no overclocking and with stock 4.1.1 li7 i have 6300 scores in Quadrant..... with overclocking to 1600 mhz i reached 6700... no sense to overclock it
Sent from my GT-I9300 using xda premium

myname70 said:
with no overclocking and with stock 4.1.1 li7 i have 6300 scores in Quadrant..... with overclocking to 1600 mhz i reached 6700... no sense to overclock it
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Which rom you use ?

+1

Learning time!
-UV provides stability, its not to save battery. Its such a miniscule amount of volatge it wont mess up battery life, but it will help stability of the CPU...
-And when you OC, you need to undertand that it doesnt stay at the max speed on all four cores all the time. It changes to fit the needs of the user.
I think the CPU can reach 2.0GHz easily, i mean my single core Captivate with a Hummingbird 1.0GHz ARM cortex-A8 could reach 1.92GHz and stay stable with -50mV UV.
Sent from my GT-I9300 using xda premium

I wont oc.. it screwed battery on my galaxy tab...
Sent from my GT-I9300 using xda premium

[Q] Overclocking Defy+ MB526 with Quarx CM10 27.10

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

Defy + max OC ?

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

[Q] horrible battery life?

77% in 49 min and screen on for 49 min. Is this bad battery life? What would make it better? Thanks guys. I'm on cm10.1 with Franco. Clocked at 1026 min and 1512 max.

sounds average. Doesn't sound bad. Bad would be 49 mins screen on and you're at 50%. Screen brightness all the way down? Or is this cranked to the max?

kcbboy said:
sounds average. Doesn't sound bad. Bad would be 49 mins screen on and you're at 50%. Screen brightness all the way down? Or is this cranked to the max?
Click to expand...
Click to collapse
All the way down. Good to hear that's it's not too bad though

Wait, could you tell us your governor? Franco kernel uses interactive as a default which in that case, you don't need to put the minimum to that high
49 minutes unplugged and 49 minutes screen on on 77% isn't that good at all. You should get at least 1 hour-1.5 if you were using it constantly.
Sent from my Nexus 4 using xda app-developers app

That's not so good IMO, I attached some pictures of what I'm getting, I'm also on CM10.1 and Franco.
You should flash Franco's and let it be, don't put the lower value that high.
Autobrightness on, Sync on, wifi always on, but not always connected (I always forget turn it off )

Could you please check how many mA Battery Monitor Widget reports?
Mine only shows 1500mAh, even when the battery is fully charged.
Would be interesting to know if this is a faulty battery or just displayed wrong.
Maybe that's why some get pretty good battery life, and on some it's really ****ty.

OneFreshDude said:
77% in 49 min and screen on for 49 min. Is this bad battery life? What would make it better? Thanks guys. I'm on cm10.1 with Franco. Clocked at 1026 min and 1512 max.
Click to expand...
Click to collapse
Here's what i got
Sent from my Nexus 4 using Tapatalk 2

I'm getting ~5 hrs screen on (low brightnes) and 20 hrs standby with Aokp and Matr1x Kernel. 288 mhz - 1,5 ghz.
Sent from my Nexus 4 using xda premium

Delete

Nuu~ said:
Could you please check how many mA Battery Monitor Widget reports?
Mine only shows 1500mAh, even when the battery is fully charged.
Would be interesting to know if this is a faulty battery or just displayed wrong.
Maybe that's why some get pretty good battery life, and on some it's really ****ty.
Click to expand...
Click to collapse
Mine says the same.
Sent from my Nexus 4 using xda app-developers app

kyokeun1234 said:
Wait, could you tell us your governor? Franco kernel uses interactive as a default which in that case, you don't need to put the minimum to that high
49 minutes unplugged and 49 minutes screen on on 77% isn't that good at all. You should get at least 1 hour-1.5 if you were using it constantly.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was using ondemand because my nexus was lagging for some reason and it helped but a clean wipe fixed that. I'll try interactive again

OneFreshDude said:
77% in 49 min and screen on for 49 min. Is this bad battery life? What would make it better? Thanks guys. I'm on cm10.1 with Franco. Clocked at 1026 min and 1512 max.
Click to expand...
Click to collapse
Really depends on what you're doing in that 49 minutes. If you're playing games, have poor data connection, uploading to dropbox etc you can see the battery deplete really quickly. I never get great battery life because I use my phone a lot with the screen brightness all the way up.
Sent from my Nexus 4 using xda premium

OneFreshDude said:
I was using ondemand because my nexus was lagging for some reason and it helped but a clean wipe fixed that. I'll try interactive again
Click to expand...
Click to collapse
Also use latest Franco. He fixed a lot of things on the latest test version and it is smooth enough to use it in daily basis.
Also could you tell us what you were doing in that 49 minutes? Games take so much battery out thanks to beefy 1.5 GHz quad core processor. Thanks
Sent from my Nexus 4 using xda app-developers app

kyokeun1234 said:
Also use latest Franco. He fixed a lot of things on the latest test version and it is smooth enough to use it in daily basis.
Also could you tell us what you were doing in that 49 minutes? Games take so much battery out thanks to beefy 1.5 GHz quad core processor. Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was just web browsing and answering texts. It's all good now though. Thanks guys!
Sent from my Nexus 4 using xda app-developers app

Undervolting

Anyone who undervolted his g2 ?
How low can we go ?
Sent from my LG-D802 using xda app-developers app

Very good question.
I hope some guys will reply who have already undervolted.
My max cpu frequency is 1190 MHz.
I don't think you need more speed on 4.2.2 (actually i'm on stock rom).

Gonna depend on soc binning for your device
Sent from my VS980 4G using Tapatalk

My soc binning is 4 and I'm able to maintain stable undervolt by 50 mv (2.26 ghz @ 975 mv I think)
Sent from my ZTE Blade using XDA Premium 4 mobile app

-62.5 here, I'm sure I can do -75 ( done it before) but it get micro lag, so I go to -62.5 works fine, nice and cool.

-100
Sent from my LG-G2 using Tapatalk

Which app?

Trickstermod
Sent from my ZTE Blade using XDA Premium 4 mobile app

I'd like to hear more about this! At stock settings my phone overheats and throttles badly. Been testing different voltages and at the moment I'm down five -12,5mV steps @ 962,5mV. Better temperatures and better performance due to less throttling.

I wish I had a rooted phone to do that
Sent from my LG-D802 using xda app-developers app

Makrilli said:
My soc binning is 4 and I'm able to maintain stable undervolt by 50 mv (2.26 ghz @ 975 mv I think)
Sent from my ZTE Blade using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where can you find the SOC binning value?
Edit: Hey looks like I found it
You can see the binning of your SoC in the last_kmsg located in /proc/last_kmsg.
You can also found it in /sys/devices/system/soc0 and search for pvs_bin and speed_bin or /d/acpuclk.
Click to expand...
Click to collapse