Database Info

Can't overclock my Nexus S

Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.

Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.

I've tried this already dude, probably should of mentioned it in my steps cheers anyhows

risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?

kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )

risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon

I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.

Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.

What the heck? I keep hitting edit but it keeps quoting =( please delete.

sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!

Blah please delete.

I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.

sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?

I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App

sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.

Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.

Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.

[Q] Tiamat Kernel Question

I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?

SetCPU is needed

Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.

anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom

Do you know what the set Max is on the tiamat kernel?

anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom

bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?

Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100

bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?

Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .

Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.

[Tiamat kernel 1.4.1) Random reboots on Xoom

Hi all,
I've been having random reboots/freeze-ups ever since I rooted.
This happens regardless of whether I am OC'ed or at 1ghz. These reboots tend to happen when watching Youtube or when browsing.
Would just like to have a feel of the ground if any of you who are rooted experiencing this?
Maybe we can start off by stating the following:
Kernel:
Clock Speed:
OC app: Setcpu or Droid OC
Governor setting: Interactive, on-demand etc..
Last app you were in that caused reboot:
For me, I am on the following:
Kernel: Tiamat 1.41
Clock Speed: 1ghz or 1.2 ghz
OC app: Setcpu
Governor setting: Interactive
Last app you were in that caused reboot: Youtube, browser
Im not sure if this thread shld belong here but since this is Dev where most of us root and OC, I thought I'd ask it here and hopefully we spot some trends with regard to the reboots.
Pls dun flame me Thanks!

wrong section

Moved to Q&A.

I have the same issue - Canada WIFI version

same problem, Canadian WiFi Version.
Not sure if it's because I flashed 1.4.0 then flash 1.4.1 to get the external sd card to show up. But I noticed after I got the external sd card to work, my usbOTG started working too, but from what I've read that should have been removed in 1.4.1 for stability issues.

Same issue. Using the tiamat kernel. It happens with different apps so its not any one for me.
Sent from my Xoom using XDA App

Switch to Droid oc and delete setcpu. Worked for me. Interactive. On demand is junk on Xoom. I use on demand on DroidX.
The kernel will Max to 1504 causing reboot (on some Xooms). Some device can't handle 1504, mine included. Superuser will throw up an occasional user permission for Droid oc as it brings the MHz back down to user setting.

I was experiencing random reboots with the same kernel, mostly just browsing in Dolphin HD. I first stopped OC in setcpu but the reboots still occurred. Then I uninstalled/reinstalled Flash 10.2 and cleared Dolphin's data.
So far, it seems to be much more stable and even battery usage has toned down.

This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk

I installed temp+CPU and don't see two cores. Only one display for MHz and it cycles from 216 to 1200. Is there a screen I'm missing?

crauzz said:
This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100

bwcorvus said:
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100
Click to expand...
Click to collapse
Remove it? So no more overclocking? Can't a ROM allow OC and voltage control? But I guess it always comes back to the lack of source code.

Mandelbrot.Benoit said:
But I guess it always comes back to the lack of source code.
Click to expand...
Click to collapse
Kernel source is available. It's the rest of Honeycomb that isn't.

So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.

I had a harder time getting it to reboot with Droid OC so I think that's your best solution for now.
Sent from my Xoom using Tapatalk

ruvanist said:
So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.
Click to expand...
Click to collapse
Flash back the stock kernel.

solarnz said:
Flash back the stock kernel.
Click to expand...
Click to collapse
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk

crauzz said:
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.

ruvanist said:
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.
Click to expand...
Click to collapse
Yes. Go here > http://forum.xda-developers.com/showthread.php?p=13178555
Sent from my Xoom using Tapatalk

[Q] Random Reboot with +1.5Ghz OC Kernels

Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez

I have the same issues and have been wondering the same thing.

I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !

nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?

watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.

Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk

tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer

[Q] Kernel? crashing phone when OC

Ok, I'm running infusion A2, not OC'd, UV'd 100 across the board just fine.
My problem starts fast when I OC to 1600, it rans ok there, for the few minutes I tested it at stock voltages. The problem is when I change ANY CPU step to UV it just crashes and reboots my phone instantly. Tried it 3 times. It comes back on fine, even if I left set as boot checked (accidentally), but the settings were not saved. Haven't tried B2 yet to see it is repeatable on 1400, and don't really want to repeat it at all.
Any ideas why this is happening? On Doctorz ROM using SetCPU to OC/UV.
Thanks y'all

Try voltage control instead (free in the market) but honestly, not all Infuses can handle 1.6 ghz. In your case, you are most likely right on the line of crashing at 1.6, when you change the voltages, you cross that line.

Its well know messing with the native clock speed can AT some phones and some times cause low stability and reboots also force closes etc. I suggest you to try lower OC speeds like 1.4 Ghz ive been running my Infuse on 1.4 forever without one single problem.

Yeah, was gonna go to B2 and try 1.4, but figured I would get some suggestions first.
Had VC at first, but didn't try OC, just UV, gonna try that tomorrow.

jonrobertd - did you flash a certain kernal to OC your Infuse? Everything I've read says either the Infuse can't be OCed. I even tried using SetCPU but it kept giving me errors when I'd run it, telling me something like "no profiles loaded" or something like that.
---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------
koriotto said:
...ive been running my Infuse on 1.4 forever without one single problem.
Click to expand...
Click to collapse
koriotto - how are you overclocking your Infuse? What OS are you using (Froyo, GB, etc.)?

You have to have a kernel that supports overclocking....and yes the infuse can be overclocked...I'm running it at 1.6 myself on my rom....the infusion gb kernel can be overclocked....entropy's daily driver can't...the community kernel is Froyo....if your running gingerbread rom and flash the community kernel your phone will bootloop.....read...
Sent from my SAMSUNG-SGH-I997 using xda premium

Overclock to high frequencies and lower the voltage too much and the CPU becomes unstable. Some can handle it, some can't, all cpus are different.
Sent from my SAMSUNG-SGH-I997 using XDA App