Database Info

Over 1.2GHz = Lock

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

[Q] Have you managed to OC to 1460MHZ and keep stability?

I'm using AOSP+ ICS ROM with the latest Matr1x kernel. Whenever I try to OC to 1460 the phone freezes and I have to pull the battery, so I'm forced to run at a maximum of 1300MHz.
Also, on a related matter, is it good practice to use SetCPU with various profiles (battery<, temp>, screenoff, charging) for various frequencies? Or should I just use AOSP+ tweaks to chose a min and max frequency and let it be?
Thanks for taking the time to answer these.

Raise all voltages by +30 across the board
Sent from my Nexus S using XDA App

My Phone freezes when i try to OC to 1460

Read the above comment or read my FAQ...god..
Lol
Sent from my Nexus S using XDA App

http://www.youtube.com/watch?v=DPclc3eKgiQ&feature=youtube_gdata_player
Sent from my Nexus S using XDA App

zgomot said:
Also, on a related matter, is it good practice to use SetCPU with various profiles (battery<, temp>, screenoff, charging) for various frequencies? Or should I just use AOSP+ tweaks to chose a min and max frequency and let it be?
Click to expand...
Click to collapse
If you are using deep idle you shouldn't underclock since it causes a race-to-idle condition. In other words your battery will drain faster. If you don't use deep idle, feel free to underclock when the screen is off or whatever you want.

sakisds said:
If you are using deep idle you shouldn't underclock since it causes a race-to-idle condition. In other words your battery will drain faster. If you don't use deep idle, feel free to underclock when the screen is off or whatever you want.
Click to expand...
Click to collapse
To the point and verry helpful, thanks a bunch
mathkid95 said:
Raise all voltages by +30 across the board
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Can I do this via AOSP+ tweaks and still use SetCpu to OC and UC? Are they conflicting apps? (Deep idle OFF)
Sent from my Nexus S using XDA App

I would recommend just using setcpu
Sent from my Nexus S using XDA App

mathkid95 said:
Raise all voltages by +30 across the board
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Just an update, Using CNA 1.4.0 and Matr1x v17, I am stable oc'ed to 1460.
this is what I am running
1)800/1460
2)gov =Ondemand
3)Scheduler =Noop
4)all voltages to +30 (used the cna rom's voltage tweaker)
I tried ShadowGun: the Leftover.. and It was flying. Of course, make sure that have enough battery or that you have a charger ready. But finally it works, try this and let me know

I can run it for 10-20 min of usage then get a freeze. I never raised the voltages before though. It seems like its working for other people. And the actual developer of Matrix Kernel is telling you to ....
Nexus S (GSM i9020a)
AOKP (Build 25)
Eugene's Kernel (Speedy 7)
OC 800/100 (Lionheart)
Live OC (105)

It still amazes me how so many people that ask about overclocking have no frigging idea at all how cpus/gpus in general are binned etc.

I have a question. Why do you guys overclock that much? It might be snappy but battery life is just bad and it just doesn't worth it in my opinion.
Sent from my Nexus S from Tapatalk

albundy2010 said:
It still amazes me how so many people that ask about overclocking have no frigging idea at all how cpus/gpus in general are binned etc.
Click to expand...
Click to collapse
Care to shed some light for us people that have no frigging idea at all how cpus/gpus in general are binned etc? If not, well... why did you even bother posting?
ljordan2 said:
I have a question. Why do you guys overclock that much? It might be snappy but battery life is just bad and it just doesn't worth it in my opinion.
Sent from my Nexus S from Tapatalk
Click to expand...
Click to collapse
Personally, I do it because I can. Seriously... I'm a geek, I love gadgets and tech and I like to tinker.
On the subject at hand, I'm still unable to OC to 1460 (ARM voltages +30, INT voltages +25) but at 1300 it runs fine, no issues whatsoever.

i can run 1460 stable all day. bigxie/matrix. just did +30 to all the voltages above 1000. deadline and lulzactive..

If you are a geek you would know about something as simple as binning chips. Do what a tech geek would do...look it up. Same thing the op should have done with his ?. Hell mathkid has a answer to his ? In the op of his kernel thread. Which is the kernel he is running

albundy2010 said:
If you are a geek you would know about something as simple as binning chips. Do what a tech geek would do...look it up. Same thing the op should have done with his ?. Hell mathkid has a answer to his ? In the op of his kernel thread. Which is the kernel he is running
Click to expand...
Click to collapse
You're kinda bitter for someone married to a busty redhead

jesusice said:
You're kinda bitter for someone married to a busty redhead
Click to expand...
Click to collapse
Haha, I thought so too.
Sent from my Nexus S

Better battery life?

Hey, I have been playing around with some rom to find the best battery life and recently I wonder if underclocking my CPU to 1000 MHz and below does extend nexus s battery life?
Sent from my Nexus S using xda premium

It does, but it also makes the OS noticeably less smooth and can often take a little longer to get things done. 1000MHz is a good compromise. However, TEUV for example defaults at 880Mhz with an overclocked GPU (220MHz over 200MHz) which is particularly smooth if your phone can handle it and saves an extra little chunk of battery through undervolting. I would go that route rather than 800MHz/200MHz GPU.

Is there any posibl
Sent from my Nexus S using xda premium

Is there any possible way to overclock gpu on 2.3.5 rom?
Sent from my Nexus S using xda premium

Any kernel with LiveOC. Matr1x 11.5 i believe was the latest for GB. You might find a link somewhere for Trinity TEUV for GB too. Unsure of others, wasn't on GB for very long myself.

What are you overclocked to?

I guess you can consider this thread part survey and part for my knowledge so I know how far I can push this phone. I am at 1728MHz max with the interactive governor and cfq scheduler. Not sure if I'm going to do any undervolting, I can get through the day with about 40% remaining, and I have profiles set up for low battery and such. I am running CM10 with the 747 (I think that's what its called..) kernel and can push it to 2.1GHz. Is it stable at that high of a clockspeed? I can assume it turns your pretty Galaxy S3 into a convenient portable stove
By the way, sorry if this is the wrong section.
Sent from my SCH-I535 using xda app-developers app

It really depends on your phone, I had mine at 2100 and it was stable. However it can very I had,a, Droid charge that ran the 1440 no problem, had it replaced and the new one could go above 1300 without hot boots. Some phones just hold up better
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
It really depends on your phone, I had mine at 2100 and it was stable. However it can very I had,a, Droid charge that ran the 1440 no problem, had it replaced and the new one could go above 1300 without hot boots. Some phones just hold up better
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Stock. I've had it clocked to 1.9. But can't tell a difference with real day to day function except for worse battery drain and phone hotter.
Sent from a SYNERGIZED GalaxySIII

I have run the KT747 AOSP kernel at 2.1 ghz for a day or more and had no noticeable increase in heat, or decrease in battery life. (lulzactive or smartass v2 with either cfq or sio scheduler, no voltage changes in KT tweaker) I also saw very little or no gain in real world performance increase, and the benchmarking apps seemed to back that up. Typically run mine at 1.809 currently. Every phone cpu is different in terms of top speed, and voltage settings. Best thing to do, is to test them and see what works best for you. These 2 links, courtesy of the Ktoonez thread, provide some great info on kernel governor and scheduler settings. Given the number of options in KT Tweaker, these helped me a great deal in terms of making changes.
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817

I've tried 1998MHz and as you said, it didn't yield much. I think I screwed something up, because now oc settings refuse to stick (resets itself to 1512) and short/long benches are not as great.
Sent from my SCH-I535 using xda app-developers app

xrawritsjack said:
I've tried 1998MHz and as you said, it didn't yield much. I think I screwed something up, because now oc settings refuse to stick (resets itself to 1512) and short/long benches are not as great.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Are you on CleanKernel by chance?

[Q] Safe to overclock?

Would it be safe to overclock to 2.8GHz with the CPU Governor as "intelliactive" and leave it there for normal use?
ROM: HD Revolution 5.5
Kernel: Faux

Probably.
Sent from my HTC6525LVW using Tapatalk

With some tweaking it should be stable. My one question though... Why? Who needs that much power lol
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
With some tweaking it should be stable. My one question though... Why? Who needs that much power lol
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The real question is why not? LOL. Honestly though I just like finding new things to do with my phone and coming from a locked Galaxy S4 I have to say I'm enjoying the amount of things I can do with this device that I couldn't on the S4. The extra 600MHz was because I was hoping it would drop any chances of lag with my favorite apps & Xposed which always seems to cause a delay or two for me. On the other hand I like squeezing what I can out of it. Same with my Desktop too, get maximum stable over clock and stick with it. ;D. If there's some downsides such as life shortage feel free to mention it though because I'd rather know early on than when it's too late. Sorta the point of this thread
Sent from my HTC6525LVW using XDA Premium 4 mobile app

S1L3nTShaDoWz said:
The real question is why not? LOL. Honestly though I just like finding new things to do with my phone and coming from a locked Galaxy S4 I have to say I'm enjoying the amount of things I can do with this device that I couldn't on the S4. The extra 600MHz was because I was hoping it would drop any chances of lag with my favorite apps & Xposed which always seems to cause a delay or two for me. On the other hand I like squeezing what I can out of it. Same with my Desktop too, get maximum stable over clock and stick with it. ;D. If there's some downsides such as life shortage feel free to mention it though because I'd rather know early on than when it's too late. Sorta the point of this thread
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've got my i5 2500k overclocked to 4.3 GHz now stock voltage . As for life shortage its hard to say. I would monitor temps on stock vs over clocked and compare. As long as it doesn't get considerably warmer which for mobile would be 10° more or less you should be fine
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
I've got my i5 2500k overclocked to 4.3 GHz now stock voltage . As for life shortage its hard to say. I would monitor temps on stock vs over clocked and compare. As long as it doesn't get considerably warmer which for mobile would be 10° more or less you should be fine
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Well with normal use it gets like 40-55 C (CPU) and during an Antutu benchmark just at the beginning it hit 75C sooo not very happy with that.... especially considering that's in the highs for a lot of desktop processors, can't even imagine how bad that must be for a phone processor LOL. It was @2.803 MHz with voltage of "1130" & ondemand governor. Not so sure as to what "1130" is based on though as I'm new to mobile over clocking, guess I'll figure it out tomorrow!
Edit: Forgot to include that just a few minutes ago I flashed a new kernel due to some random lag, old one never hit above 50 even on tests (with intelliactive). Also using ondemand/interactive now. Gonna re check the differences on those two governors tomorrow and decide which one I wanna go with! : D
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Very cool. Now you got me wanting to overclock. Bad things happen when I cross paths with those numbers
Sent from my HTC6525LVW using Tapatalk