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?
Related
What would you recommend for daily use but extremely fast with out melting cpu or cracking the motherboard?
I'm using droid overclock I wanna make this baby run but without harming her ya know? Any ideas??
Sent from my DROIDX using XDA App
for some reason it's different on different people's devices. I run mine at 1.25 and it will usually reboot under heavy stress above that setting, other people can run up to 1.4 or 1.45 and remain stable.
Ya I've notice the reboot under stress running at 1.4 so im at 1.35 and it seems flawless so far but on the quadrant test it comes to about 1350 when a t mobile rep tested his g2 he showed around 1600+ on complete stock.
Sent from my DROIDX using XDA App
I've been getting around 1700-1800, rubiX focused 1.8.6 jrummy app set to 1.25 ulv
Sent from my DROIDX using XDA App
Mine is odd
When I first started using overclock about a month ago I was running 1400 at low voltage and everything was cool. Then silly me I tried 1450 at medium and it was constantlty hot. Then i tried 1450 at ultra low voltage and from then it constantly reboots at anything over 1250!!!!...? So now I run 1100 at ultra low voltage. I guess I'll benchmark it and see what I get.
I am using CM7 ROM and Glitch kernel together on the Verizon Fascinate and was just wondering what everyone is using for the I/O Scheduler and the CPU Governor with Voltage control.
I have mine OC'd to 1.5GHz and using bfq and performance.
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
davwman said:
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
Click to expand...
Click to collapse
smartass is best in my opinion. It seems to run lower clocks more often when high clock is not needed.. I don't have smartass v2 for some reason
Sent from a beautiful miui fascinate
I use cfq and smartassv2. Here is a thread with explanations of all of the schedulers and governers, how they work and what ones are the best.
http://forum.xda-developers.com/showthread.php?t=1309698
Using noop/smartass the last day or so...seems to be running smooth.
Smartass never seems to go below 400mhz on my phone. I've been using OnDemand.
I haven't really noticed any performance difference with any of the IO schedulers. Probably because it's flash and not a disk based drive in the phones.
jimv2000 said:
Smartass never seems to go below 400mhz on my phone. I've been using OnDemand.
I haven't really noticed any performance difference with any of the IO schedulers. Probably because it's flash and not a disk based drive in the phones.
Click to expand...
Click to collapse
actually, I just noticed that as well. interesting find. Ill give ondemand with deadline a shot.
sageDieu said:
I use cfq and smartassv2. Here is a thread with explanations of all of the schedulers and governers, how they work and what ones are the best.
http://forum.xda-developers.com/showthread.php?t=1309698
Click to expand...
Click to collapse
Thanks! This is an awesome post!
davwman said:
that setup you are using will suck down battery in no time. Im running v13 from paid glitch app, smartass v2 with deadline and underclocked to 800mhz and get 5 hours of ACTUAL PHONE USE/SCREEN ON TIME and about a full day before needing a re-charge on an 1800ma samaung battery and the phone still flys. zero lag! You really dont need to run any more than 1 ghz, but 1.2ghz will give you crazy speed and still allow for some good batterylife. 1.5 is overkill.
Click to expand...
Click to collapse
I do have it a little overkill, but I enjoy the speed when using some apps like games. My battery does last a whole day however with the 1800ma battery life, but then again all I use my phone for during the day is texting or VNC. I'm gonna try the smartass V2 and Deadline. Thanks!
I do quite a bit of gaming on my device (9mm, Dungeon Defenders, etc...). Overclock is set at 1.4 no UV, with absolutely no lock ups. BFQ and smartass yield the highest fps for me on V13RC.
Sent from my SCH-I500 using XDA App
I thought we weren't supposed to use performance because it doesn't respect thermal safeguards. Am I correct?
Sent from my HP Touchpad using xda premium
bobloblaw1 said:
I thought we weren't supposed to use performance because it doesn't respect thermal safeguards. Am I correct?
Sent from my HP Touchpad using xda premium
Click to expand...
Click to collapse
I did not know that
Sent from a beautiful miui fascinate
Performance would be a bad idea over long periods of time. Essentially since it runs the phone at the highest possible frequency for 100% of the time, it stresses the CPU much more than any other option. This could cause overheating if used for too long, not to mention the toll on your battery. We all assume that it would decrease the life of your processor because it logically could, but that isn't a big deal sienc you'll likely be upgrading long before the processor would begin to fail regardless of what you do with it now.
lordnikko said:
I do quite a bit of gaming on my device (9mm, Dungeon Defenders, etc...). Overclock is set at 1.4 no UV, with absolutely no lock ups. BFQ and smartass yield the highest fps for me on V13RC.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Interesting, when I set BFQ and Smartass on mine I get force closes on the simple apps, for instance the internet browser or file viewer. But when I play games on it I dont get any force closes on the games.
Maybe try clearing data on voltage control & reflashing kernel. I have been running my current configuration on MIUI, CM7, and now Pool Party for the last 90 days or so with no issues.
Sent from my SCH-I500 using XDA App
Ok will do thanks!
Sent from my SCH-I500 using XDA App
Is performance save
Sent from my SCH-I500 using XDA App
Enyo. said:
Is performance save
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
?
Sent from my SCH-I500 using xda premium
Enyo. said:
Is performance save
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Assuming you mean "safe" then yes over short periods of time it's fine. If you tried to run at a high clock on performance all the time you would probably get heat and battery life problems.
I'm running miui and glitch v12 and I find it very strange that my phone runs really good (almost as good as any combination that I tested) on conservative governor.
Sent from my SCH-I500 using xda premium
mkropf said:
I'm running miui and glitch v12 and I find it very strange that my phone runs really good (almost as good as any combination that I tested) on conservative governor.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Thats not strange at all really. I've had it last multiple days with data and everything off, conservative, and underclocled to 800mhz when I needed to be away from a charger for a while.
and it performed really well.
Sent from my MIUI SCH-i500
Every TF is different. Someone has reported being able to unvervolt by -250 or more. I don't know how the hell he did it. Anyway, I thought I'd start this thread to let people show off their OC and UV settings. I thought I could get a feel on what the stable limits are.
Remember, guys, it's only considered stable if the camera doesn't freeze. I don't care how much stress test you do. If your camera doesn't work, then it's not stable.
The 2 lowest clock settings there are, it's like 250 and 320 mhz or something I can run a 250 undervolt. This is extremely useful because I run on interactive and my tablet runs on almost no battery at all while on standby.
As for my underclocks up from that to about 1590s(My tablet can't handle 1600s) I have a steady 65 undervolt for all frequencies. I found battery life to be amazing...
Sent from my Inspire 4G using XDA Premium App
Hi there! What are you using to undervolt and/or overclock? I'm using CPU Master Free to overclock, but it doesn't have any undervolting options.
EDIT: also, which kernel are you using that supports Undervolting and Overclock?
Prime kernel doesnt seem to support uV at the moment
Blades does
Clemsyn does
Dont think netformer does
Settings im still playing and waiting for uV on prime kernel as ive found it the most stable at the moment will post back later
ThEiiNoCeNT said:
The 2 lowest clock settings there are, it's like 250 and 320 mhz or something I can run a 250 undervolt. This is extremely useful because I run on interactive and my tablet runs on almost no battery at all while on standby.
As for my underclocks up from that to about 1590s(My tablet can't handle 1600s) I have a steady 65 undervolt for all frequencies. I found battery life to be amazing...
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Does your camera work when you set everything to -65? My camera will not work if I unvervolt 608 or 456 mhz.
QQ
Sent from my Transformer TF101 using Tapatalk
Yes it works, everything does.
Sent from my Transformer TF101 using xda premium
Hey im just wondering what other peoples specs are for SetCpu?
12000-1000 is what I'm normally set at..
but as far as Voltage and Advance settings I don't know to much in these 2 area's...
so just curious in what people do with these options, and if it increases performance?
Kernal: Matr1x 11.5
Sent from my Nexus S 4G using XDA Premium App
I usually set mine to 1200 200 set it on lazy and its really smooth and very good battery life. I don't mess with the voltage.
Sent from my Nexus S 4G using xda premium
I usually undervolt and keep the stock 1000 / 100 (usually able to get about -75mV from each level w/ 100% stable. At -125mV I start to notice some instability.)
When I OC though I usually keep the voltage at stock and go 1200 / 250.
Anything over 1200 at stock and I find my phone starts getting unstable - everyone's is different though.
Interactive or Lazy Governors for both.
Currently running NexusBeam 4.1 and Glados 2.2.
Thinking about flashing back to ver. 3 though.
Thanks guys.. you guys dont touch options in advance?
Sent from my Nexus S 4G using XDA Premium App
-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