Hello everyone. I have had my Nexus S 4G for about 2 weeks now, and I have tried everything I can think of. However, I cannot overclock my phone higher than 1.2GHz. If I set it to 1.44GHz (or even 1.3GHz in most kernels), within the first five minutes, it locks up, requiring a battery pull. I have tried just about every kernel. Trinity, Netarchy, Matr1x, everything. However, I get the same result. I am assuming that it is just my phone. I know that when I had my Evo, it didn't want to OC past 1.1 GHz stably, but the refurb I got from Sprint ran at 1.21 GHz like a champ. I was just wondering if anyone had the same issue, and if so, if it was possible to alleviate this problem. I would love to run my Nexus at 1.44 GHz, because some of the Quadrant scores look amazing.
Thanks again for reading,
StompySan
Try v9.0 of matrix and set it to 1.3
Lemme know plz
Sent from my Nexus S using XDA App
mathkid95 said:
Try v9.0 of matrix and set it to 1.3
Lemme know plz
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
After running Quadrant twice with it set at 1.3, I got a lockup. 100% not responsive. Had to pull battery.
EDIT: I tried benchmarking my phone with CF-Bench, thinking maybe it could have been a fluke with Quadrant, and had the exact same results. At 1.3 and 1.46GHz.
1.2??
Sent from my Nexus S using XDA App
1??
Sent from my Nexus S using XDA App
Ok if neither of those work I need you to do 2 things.
1. Raise all voltages by 30
2. Set it to 1.2 ghz
Sent from my Nexus S using XDA App
I can overclock without reboots to 1.2. Any higher than that is when the problem arises.
Ok now once you flash v9.0, go into setcpu and raise all voltages by 30
Now try 1.3
Sent from my Nexus S using XDA App
mathkid95 said:
Ok now once you flash v9.0, go into setcpu and raise all voltages by 30
Now try 1.3
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When you say all voltages, you mean even the ones that it already runs stably on?
No no, just the unstable ones
Sent from my Nexus S using XDA App
OK, so Quadrant ran fine for 5 tests, and CF-Bench ran OK as well. Should I push it up to 1.46 now?
Try it, and if you get a reboot, raise voltage for 1.46 by 10.
Sent from my Nexus S using XDA App
No lockups yet! I have ran Quadrant 5 times, CF-Bench 2 times, and Linpack a couple times. Seems to be doing great! I am going to test it more thoroughly tomorrow (it's almost 1AM where I live, lol), but it seems great right now!
I have never increased the voltages on a phone CPU before. I have done it on my brother's computer when I overclocked his processor, but I generally try to avoid it. I am just really paranoid to mess with the amount of power going through the processor. That's why I turned to the professionals in this case. Thanks again for your extremely quick reply.
Cool! you just needed a bit of a voltage push, that's all
let's hope 1.46 ghz runs well
Mathkid Ive never been stable past 1.3 so I followed what you told him to do and what do you know! Perfectly stable so far at 1.44 on apocalypse kernel!! Might have to try your 9.0 at 1.46 soon!
Sent from my Nexus S 4G using XDA App
So is there a limit to how far one should overvolt? I upped the voltage at 1440 mhz to 1550 mV. Did run rather stable except for "Lets golf HD!" which froze. I would really like to be able to run at 1440, but not sure what to do. Im using Apocalypse Talon 3.2.1.
Do you think your kernel would handle OCing better, mathkid?
Yeah you can try it out and if you need to raise voltages go ahead
Related
Already? Or this old news?
http://www.droidforums.net/forum/thunderbolt-hacks/136976-officially-overclocked.html
Dlnp22 said:
Already? Or this old news?
http://www.droidforums.net/forum/thunderbolt-hacks/136976-officially-overclocked.html
Click to expand...
Click to collapse
Go to ROM manager and download OC
It's not there anymore.
Yea I wonder why iit was pulled. Worked great for me...
Thankfully, if it was already downloaded, it's still in your clockworkmod/ folder. Rejoice, those who have already downloaded it.
Direct download link is in that thread.
been running it at 1.4 since last night and loving every minute of it. runs greats, not one problem..
rulevoid said:
Yea I wonder why iit was pulled. Worked great for me...
Click to expand...
Click to collapse
Found out through twitter that the dev does not want anyone to distribute his kernel through the forums. However, if you ask nicely then you may receive.
Sent from my ADR6400L using XDA App
Follow him on Twitter and go through his tweets. He has a link for his kernels there. Even one for his 1.8ghz kernel
Sent from my ADR6400L using Tapatalk
Twitter name?
Sent from my ADR6400L using XDA App
bhazard451 said:
Twitter name?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
His twitter name is Drod2169
twitter.com/drod2169
Interesting. I'm not seeing much of a difference. Quadrant scores went from 1611 on adryn's 1.8 kernel to 1789 on the 1.5ghz. Seems very low for both. Wonder what's giving me issues...
Sent from my ADR6400L using XDA App
I get 2200+ on quadrant at 1.5ghz.. and 2700+ at 1.8ghz using Drod's kernels..
Can't wait to try his 1.9+ kernels soon
This is absolute insanity, I can't believe this but I was running this kernel to the max (1.5ghz) and the performance was insane. 2200 - 2500 quadrant scores (even one 2532). Well, drained my battery to 15% after about 3 hrs using "ondemand" scaling. So I flashed adrenelyn's 1.9, phone ran perfectly smoothly but I wasn't happy anymore with kernel scores in the 17's and 18's. So I reflashed drod's kernel and have been running at 1209 mhz (2064, 2216, 2092 quads.), phone is still super responsive and it is now 2 in the morning, I have been running it since roughly2pm and I have 37% battery left 12 hrs. later (ondemand). I have been using the crap out of this phone: 2.5 hrs. phone calls, 1.5 web time, texts all day, followed twitter, did some theme changes. I found my go to kernel for now.
Tried the 1.8 but SetCpu widget kept reporting 1.8 even after I slowed it down. Going into the app I could tell it was follow my settings. Went back to 1.5. Temp to high for me even though stable. I might try conservative setting if widget reports right.
Sent from my ADR6400L using XDA Premium App
houseboatwayne said:
Tried the 1.8 but SetCpu widget kept reporting 1.8 even after I slowed it down. Going into the app I could tell it was follow my settings. Went back to 1.5. Temp to high for me even though stable. I might try conservative setting if widget reports right.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
You have to disable the Perflock disabler in SetCPU options and you can downclock it
where is this 1.8ghz kernel?
Diversion said:
You have to disable the Perflock disabler in SetCPU options and you can downclock it
Click to expand...
Click to collapse
If the 1.8 is the same as the 1.5 you don't need to disable Perflock. It has already been been disabled.
Edit: I just read in drod2169 Twitter that in order to lower the clock speed on the 1.8 you do need to disable the Perflock...sorry.
So I found a kernel on the Fascinate forums that was built off of our EC10 froyo source that was from nemesis2all and I saw that he had added the ability to overclock and undervolt from within the ROM so I installed it just trying (backed up of course) and found that it does indeed work.
I then got the Voltage control app from the market and started playing around doing Quadrant scores throughout after each change. I found that at 1200 mhz I was getting 1600s instead of 1400s and the phone ran great. But when I tried 1400 mhz the phone froze up and restarted while doing the CPU section of the Quadrant test so I reverted back.
My question is, what would be safe to stay at for general use?
Second question, how do you use the voltage app to undervolt I see the settings but I don't know what to set them too.
Here is the link to the kernel
1200 has proven to be the most stable overclock, any higher and it will freeze up eventually.
With voltage control, the way it works is that you set the max clock and then it will give you increments that the phone will automatically clock to within the guidelines you give it. Then for each increment you can set the voltage it will use. Just look around and experiment with voltages, see how low you can go without having issues and never set it to apply at boot unless you know that's what you want, other than that go crazy and a reboot will fix it if you have a problem.
I recommend keeping setCPU installed along with it, that way you can still force it to underclock or overclock or whatever. It all depends on how much you use the phone and what for.
Sent from my MIUI SCH-i500
Thanks sage I'm glad someone who knows what their talking about replied lol.
Swyped using USCC Mesmerize
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
akellar said:
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
I've been running it for a week @ 1400 -25 undervolted and haven't had any issues. The new 1.6 gives me trouble. I don't think there's enough overvolting in that one to make it stable for pretty much anyone. I use the 1400, 800, 400, 200 steps all undervolted @50 except 1400 which as mentioned is -25. Battery life is good because during sleep it doesnt really hit the high end and by not having the other steps its snappy when in use. Fastest this phone has been by far. I don't use setcpu because I think it and the voltage app conflict. That was nemisis's instruction to install it.
Sent from my SCH-I500 using XDA App
sageDieu said:
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Yup I'm just lucky 1.4 worked for me too but I didn't see much of a performance difference so I didn't see the need to stress the cpu out anymore than I already was. battery life had been awesome for me with my setup as well.
Sent from my SCH-I500 using XDA App
I can't seemed to overclock over 1000 ghz. Am I missing anything?
Sent from my LG-P999 using XDA App
moshe22 said:
I can't seemed to overclock over 1000 ghz. Am I missing anything?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
You have to have a kernel that allows overclocking.
moshe22 said:
I can't seemed to overclock over 1000 ghz. Am I missing anything?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Are you using a custom kernel??
If you are use pimp my cpu to oc
G2X
Also, in case you didnt know.. Kernels may state 1.5Ghz and such but that doesnt mean YOUR phone will be able to go that high. Every device is different so every device's has a different max frequency.
Set CPU currently doesn't work with out kernels. You must install one of the OC/UV kernels from the development section and use the pimp my cpu app to overclock
Sent from my LG-P999 using XDA App
Ok, that makes sense I'm using the EB 1.04F trinity kernel +48 and was using pimp my cpu and I can overclock just fine there but I wanted to try out setcpu out.
I have it over clocked @ 1.2 -50 in all frequencies and scheduler is the default one. Force Min Frequency is checked as well.
Thanks
Sent from my LG-P999 using XDA App
On a side note, my g2x has been highly unstable after leaving it sit while using pimp my cpu. However, I created a .txt file with clock frequencies and I was able to use setcpu with little to no side effects. But after all, what is ocing even good for? Benchmarks... Mt4g, n1, g1, mt3g, hd2. Tried ocing on all of them and didn't see a noticeable day to day difference compared to stock frequency...
Sent from my LG-P999 using XDA App
crx4xharder said:
On a side note, my g2x has been highly unstable after leaving it sit while using pimp my cpu. However, I created a .txt file with clock frequencies and I was able to use setcpu with little to no side effects. But after all, what is ocing even good for? Benchmarks... Mt4g, n1, g1, mt3g, hd2. Tried ocing on all of them and didn't see a noticeable day to day difference compared to stock frequency...
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Over clock is good for overall performance.
Sent from my LG-P999 using XDA App
crx4xharder said:
On a side note, my g2x has been highly unstable after leaving it sit while using pimp my cpu. However, I created a .txt file with clock frequencies and I was able to use setcpu with little to no side effects. But after all, what is ocing even good for? Benchmarks... Mt4g, n1, g1, mt3g, hd2. Tried ocing on all of them and didn't see a noticeable day to day difference compared to stock frequency...
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
On the mt4g I was able to play dungeon defenders OCed at 1.5 without much lag. Without it the game was almost unplayable because it would lag like crazy when the graphics got too intense. But on the downside it sucked my battery dry within hours
Sent from my Xoom using XDA Premium App
Is there a maximum "safe" overclock speed?
I've been running mine undervolted and at 1.2 GHz without issue for several weeks now.
Sent from my Nexus S using XDA App
Hog Milanese said:
Is there a maximum "safe" overclock speed?
I've been running mine undervolted and at 1.2 GHz without issue for several weeks now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
no ! cause when you star OC its more than then samsung has planned for your CPU so no!
, but when youf Phone is stable with 1,2ghz than you could use it without any harm!
Sent from my Nexus S using XDA Premium App
Some phones handle handle overclocking better than others, even within a particular line. I was running mine at 1.4 ghz without any issues.
You can keep increasing it by one notch until it reaches to a point of instability. It'll freeze and reboot
I'm running stock myself, but I've heard a few people running stable @ 1.4, with overvolt.
Hello everyone. Ok so everytime i try doing a benchmark test with Antutu my phone reboots or freezes. But it only does this when im [email protected] 1.55ghz. Anything under 1.55, like 1.4ghz for example, it runs and does the bechmark test just fine.
Any input would be greatly appreciated.
BTW i'm currently running CM7 Nightly124 with Faux123v0.4.1 kernel and using SETCPU as my OC/UV app.
Sorry in advanced if this question has already come up many times...but i just couldn't find any threads referring to this same problem.
Its not the benchmark that is the problem...
Sent from my LG-P999 using xda premium
Hmmm..then what could it be? Cos I run quadrant at full 1.55ghz and it runs pretty smooth
Sent from my LG-P999 using Tapatalk
its the phone. Quadrant is not a multi threaded app so it does not use both cpus on the phone. I do belivie Antutu is so you are stressing the cpu more with Antutu then you are with quad. My phone does the same thing. Not every phone is the same so your chip might not be able to do 1.5ghz safely where someone elses can. If 1.4ghz runs fine that is your max.
Prod1702 said:
its the phone. Quadrant is not a multi threaded app so it does not use both cpus on the phone. I do belivie Antutu is so you are stressing the cpu more with Antutu then you are with quad. My phone does the same thing. Not every phone is the same so your chip might not be able to do 1.5ghz safely where someone elses can. If 1.4ghz runs fine that is your max.
Click to expand...
Click to collapse
Thanks i kinda figured that. Although i'm now running Eaglesblood 2.3.5 with Trinity15 Kernel. I am now able to run the Antutu test with [email protected] 1.56 without any problems and smoothly too. Hmmmm
Voltages might be different for each cpu speed scaling between the two kernels, which might make one more aggressive than the other at a particular speed.
Sent from my LG-P999 using xda premium