Database Info

Overclock Kernel Question

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

Gb battery life

Just curious what everyone is getting for battery life on the gb Rom? seems like i have been getting about 11hours at the most and 9 hours normally on barely any talk time with the phone and little texting almost nothing cause im at work for 9 hours. Basically.from 6am to 5pm is all i can squeeze. Btw running the screen at the lowest brightness and even clocked the cpu at 800 mhz
Sent from my SGH-T959V using XDA App

Oh damn, I just keep seeing bad things about the new GB ROM (bricks and everything). :T I haven't flashed it myself yet, but with that minimal kind of use, I could've gotten over 24 hours on Bionix.
Not a pro here, but maybe you can try calibrating your battery?

bkoon1218 said:
Oh damn, I just keep seeing bad things about the new GB ROM (bricks and everything). :T I haven't flashed it myself yet, but with that minimal kind of use, I could've gotten over 24 hours on Bionix.
Not a pro here, but maybe you can try calibrating your battery?
Click to expand...
Click to collapse
Try to calibrate your battery. Stay away from flashing GB right now. It will screw your bootloader up for future reference. The bootloader in it is bunk.

I flashed it with open it works great i did notice it changes stock voltage on the cpu to 1325 which most likely caused the drain issue. I can get into recovery though.
Sent from my SGH-T959V using XDA App

I already flashed thru heimdall before the warning came out about bootloaders. So far it's running pretty good. I need an oc/uv kernel though cuz I noticed battery runs warm at times.
Sent from my SGH-T959V using XDA Premium App

Its running warm from the voltages used on the cpu in the kernel dl tagrak pay for it and changed the value of 1325 on the core voltage to 1275 stock or 1250 which i run at currently
Sent from my SGH-T959V using XDA App

Setting the CPU to 400Mhz freezes?

I'm having an issue with my phone not being responsive if I set the CPU to 400Mhz. I first found this problem using Juice Defender then I uninstalled that and did it under SetCPU and it still did the same thing. The phone pretty much doesn't wake up after a while. I have to do a reboot in order for it to work again.

Don't get mad at me but IMHO overclocking and messing with a phones core features (what makes it run, processor, ram, etc.) is unsafe and can cause instability. And no I have no scientific research to back this up but it's just my two cents.
Sent from my SGH-I997 using xda premium

Lol I'm not mad. I don't really like to over clock. I just figured under clocking would work better. But nooooo lol
Sent from my SAMSUNG-SGH-I997 using XDA App

It does that under 800 mhz I forget why but I've read that in a couple places
Sent from my SGH-I997 using XDA App

underclocking that much is using less than 1/3rd of your true processor power.
your processor simply is not able to draw enough power to perform its background tasks - even when the phone is idle - when you underclock to such an extreme extent. therefore, it freezes trying to complete these processes.
if you're going to underclock, i'd say that 800 MHz is the lowest you can go if you are expecting your phone to do everything it is supposed to do. although it isn't going to save you THAT much battery life anyway, so you might as well just run it at the stock setting of 1200 MHz.

Focustom said:
Lol I'm not mad. I don't really like to over clock. I just figured under clocking would work better. But nooooo lol
Click to expand...
Click to collapse
I understand LOL. And he's right underclocking honestly doesn't
Save much battery.
Sent from my SGH-I997 using xda premium

There's a known issue with setting CPU profiles to less than 800 MHz. A fix exists but some kernels don't have it.
Many of our Gingerbread kernels fix it, Infusion-GB is one of the few that hasn't pulled in the fix yet. (Although version 1.1 may have pulled it in, haven't checked github lately.)
None of the Froyo kernels have an explicit fix, but I'm not sure if the flaw even applies to our Froyo kernels as the clocking architecture is VERY different.

Hi, Rogers stock 2.3.3
It's using up 60% battery over night. Most likely I should turn off Wi-Fi.
I have underclocked to 100, 200, and 400 and it's stable --- minus the delay/lag at 100 and 200 . Sorry to seem like a troll.
I find that by default this phone either runs at 100mhz or 1200 on average, and 200 400 800 under 10%
Sent from my SAMSUNG-SGH-I997R using XDA App

ierdna said:
Hi, Rogers stock 2.3.3
It's using up 60% battery over night. Most likely I should turn off Wi-Fi.
I have underclocked to 100, 200, and 400 and it's stable --- minus the delay/lag at 100 and 200 . Sorry to seem like a troll.
I find that by default this phone either runs at 100mhz or 1200 on average, and 200 400 800 under 10%
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
Bumping from 100 to 1200 is classic ondemand governor behavior.
Also, some people never had problems even without netarchy's sleep patch running the CPU capped to 400 - but others have. I don't think anyone has had a problem with a patched kernel.

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] dragon ota kernel 1.1.1 (i think)

i never used custom kernels before but overclocking to 1.5ghz is awesome. one downfall, phone gets super hot and my phone restarts. i've heard of undervolting but i have no clue on how to set it using setcpu. i've heard 1.5ghz to be something like -100mv but do i set -100mv to all of the frequencies?

marine417 said:
i never used custom kernels before but overclocking to 1.5ghz is awesome. one downfall, phone gets super hot and my phone restarts. i've heard of undervolting but i have no clue on how to set it using setcpu. i've heard 1.5ghz to be something like -100mv but do i set -100mv to all of the frequencies?
Click to expand...
Click to collapse
What do you need the phone to do if you want it to be constantly at 1.5ghz?
You can try using Faux's or Trinity kernel. Both have versions that are already UV'd upon flash. Although some chips can't handle UV. Also, I believe you have to use a different app to control your voltage.

When i play games or watch movies i set it up to 1.5ghz and since school is out and no job... im kinda on my phone for a few hours. Also, i tend to forget to turn it down.
Oh yea my bad, its cpu master. I tried -100mv to all frequencies and it'll work for like a minute then it'll freeze and have to pull out the batt.
I'll check out those other kernels but this one has really fast boot. Although, which of the other kernels gets updated the most?
Sent from my LG-P999 using XDA App

marine417 said:
When i play games or watch movies i set it up to 1.5ghz and since school is out and no job... im kinda on my phone for a few hours. Also, i tend to forget to turn it down.
Oh yea my bad, its cpu master. I tried -100mv to all frequencies and it'll work for like a minute then it'll freeze and have to pull out the batt.
I'll check out those other kernels but this one has really fast boot. Although, which of the other kernels gets updated the most?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Faux boots up in less than 30 seconds for me so give that a shot. Both Faux and Trinity get's updated very often. So you can't go wrong with either.

marine417 said:
When i play games or watch movies i set it up to 1.5ghz and since school is out and no job... im kinda on my phone for a few hours. Also, i tend to forget to turn it down.
Oh yea my bad, its cpu master. I tried -100mv to all frequencies and it'll work for like a minute then it'll freeze and have to pull out the batt.
I'll check out those other kernels but this one has really fast boot. Although, which of the other kernels gets updated the most?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I play games like dead space and Nova at 1.2 and have no lag whatsoever, basically they only time overclocking to 1.5 does anything is when you're running some type of performance test.
Sent from my LG-P999 using xda premium

mackster248 said:
Faux boots up in less than 30 seconds for me so give that a shot. Both Faux and Trinity get's updated very often. So you can't go wrong with either.
Click to expand...
Click to collapse
95Z28 said:
I play games like dead space and Nova at 1.2 and have no lag whatsoever, basically they only time overclocking to 1.5 does anything is when you're running some type of performance test.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
aaahh yea im starting to c wat u mean. keeping it 1.1 and its still good. got used to the old phones under 1ghz and single core.
oh, do guys have to links to the kernels? im trying to find it but its usually part of a rom.

Go in the development section and look for [kernel] in the titles and not ones that say [rom].