Database Users

Post your Glitch v14 live OC and step values

Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.

I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium

I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.

I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium

mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium

For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium

mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium

Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.

If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064

100-800 mhz, 125% live oc.

So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though

Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize

I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?

What is a safe level to over clock?

Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium

fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I run trinity kernel on my Gnex and N7 and on my N7 I keep it stock speeds because I've seen no reason to realistically OC it. Most of the improvements I see are from the kernel software changes over stock. You can OC to 1.6 safely but I'm not sure of the power usage difference but I'm pretty sure the loss in power isn't worth the gain from OCing.
Sent from my Galaxy Nexus using xda app-developers app

I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.

brando56894 said:
I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.
Click to expand...
Click to collapse
For the benefit of the community, can you tell us any major changes at 1.6 GHz?
Is there anything noticeably faster?

Hi, I have a related question but can't post since I'm new.
Using the glazed rom which i like but it apparently has gpu overclock. I would like to know how to adjust that back to stock setting or at least see what it currently is. I found the CPU section but there is no gpu I can see.
Is there a tool I can use?
Sorry for the hijack...at least its sort of on topic

IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app

Harry GT-S5830 said:
IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My thoughts exactly. I play some light games and web browse on my Nexus 7.
For those purposes, my Nexus 7 is already extremely fast, so I don't think I would be able to notice if it was over clocked.
But I guess it depends, maybe there's a big difference when running GPU heavy games.

I have OC mine upto 1640 MHz for bench marking alone for half and hour or probably more and it went fine although the tablet was getting warmer more than usual.
Sent from my Nexus 7 using xda premium

Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Thanks again
Cheers
Corey
Edit,
I over clocked my galaxy s2 ages ago, and I noticed a huge difference in performance.
So that is why I want to over clock my n7 too lol
Corey
Sent from my GT-I9100 using xda premium

there is no such thing as a safe overclock. overclocking, by nature, carries some risk. that said, i havent seen anyone brick their device from overclocking.

fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Just wondering
Why do you feel the need to OC?

I go to 1.6 but use the Trinity App to go back to stock when OC not needed
Sent from my GT-I9300 using xda app-developers app

I have not over clocked the Nexus 7 yet but one way to test your devices max is to use setcpu. Make sure you do not have "set on boot" option selected. Then step up your cpu. If your cpu can not handle the over clock it will force restart. If you do not have the set at boot selected it will revert back to the last good state on restart.
Each device is different on what it can handle for over clock.
Sent from my Nexus 7 using xda app-developers app

fishingfon said:
Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Click to expand...
Click to collapse
To be honest I doubt you'll notice much increase from oc the CPU since the CPU already is so powerful nothing pushes it to max really.
Only thing worth overclocking is GPU really. And at that, your not going to notice a difference unless your playing some intense games.

-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

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

Overclocking

Can someone please explain to me why none of the kernel's have OC ability?// I think it's due to quad core overheating but I'm not sure and would really love an actual explanation.. Thanks
Sent from my Nexus 4 using xda premium

they all started with OC ability right at the beginning, then .. a good few number of people had HARDWARE bricked devices, that had a fault with the battery no longer being connected or something
they all had overclocking in common, since then , its been removed on most or all kernels

I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium

zephiK said:
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..

italia0101 said:
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
Click to expand...
Click to collapse
Will I certainly don't need it. Would it be nice to have? Yeah but it isn't on the top of my priority list.
What he's saying about mpdecision is true. If you read the change log for Franco kernel he removed mpdecision and is working towards a open platform for kernels. So we should hopefully be seeing more goodies.
Sent from my Nexus 4 using xda premium