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
Related
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
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?
-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
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
does over clocking the setcpu to high frequencies use more battery on mytouch 4G? I'm using the venom viper rom.
Sent from my HTC myTouch 4g using xda premium
Yes, If you keep it at 1200 it shouldn't be much of an issue.
My conclusion is you almost have to overclock the available sense kernels in order for them to work right.
so my max should be 1200 and what should be my min?
Sent from my HTC myTouch 4g using xda premium
1200 is just a real safe overclock value. You can try other values and see how your phone reacts. Would be nice if there was kernel that could be undervolted. But that just isn't the case.
Min value I would just leave set at 245 or 368. Again you can try other values and see how your phone reacts.
okay thank you for the advice
Sent from my HTC myTouch 4g using xda premium