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
Related
I have a question about this kernel, i have it installed on the phone and flashed on it, it said in the post from nemesis2all that there was a Battery hack, i was curious how to use it, i currently have settings at Min=400 max=1300 all settings undervolted 50mV, how good are these settings? and would this be the optimal settings for performance and battery life? or anyone have a better setup that would help. seem to be getting high 1700 quadrant scores with how it is now.
In order to get the best battery life you would not want your phone over clocked, I run otb kernel as well and just uv the stock setting starting at 50 for the 1000, and progressively stepping down to negative 100. Anyways I run, 1000 -50, 800 and 600 -75, 400 200 & 100 at -100 and I have great battery life even with heavy usage and playing memory intensive games, paradise island, drag racing, pocket soccer. Unless your phone is laggy after you enable lagfix I think overclocking is probably just killing your battery faster the only roms I used light oc' ing for was phoenix and miuiwiz, where both launchers seemed to get some lag after a long days use
Sent from my SCH-I500 using XDA App
The other school of thought on battery life is, if you overclock the processor, it will finish the task faster and return to a lower power idle state sooner.
well also i used SuperOneClick to root the phone, is rageagainstthecage a good root to use? or are there better ones out there? also sometimes this kernel like to freeze at start up and i have to re flash it. im pretty sure this isnt supposed to happen. any help or advise is greatly appreciated
I've had issues with OTB kernals before. Your problem could be the kernel, but I see you oc'd it to 1300. That too could be causing it. Each phone reacts differently to kernels and oc/uv.
Sent from my SCH-I500 using XDA App
Are we able to still use any touchwiz kernal from ec10 on the new heintz 57 ee19 updated rom?
Well I re-flashed it and used same ovetclock just lower volts and am pulling a average 2100 quadrant score. Don't know if it means much but no lock ups anymore
Sent from my SCH-I500 using XDA Premium App
This could just be my stupidity, but if you can flash kernels then you have a custom recovery, right? What's the point of using super one click? Wouldn't having the recovery and the ability to change kernels, etc mean your already rooted? Just seems redundant, I never used a rooting app and still use all the root only apps....
Sent from my SCH-I500 using XDA App
evilntention said:
This could just be my stupidity, but if you can flash kernels then you have a custom recovery, right? What's the point of using super one click? Wouldn't having the recovery and the ability to change kernels, etc mean your already rooted? Just seems redundant, I never used a rooting app and still use all the root only apps....
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Kinda. The only way to flash a kernel is with a custom recovery but you don't necessarily have to be rooted to do that. EE19 is not rooted so that's why you need SOC if you want to root. Rooting opens up a lot of options for apps and moving and copying system files but isn't required for Roms/Kernels.
Anyone have any other general good ideas or cool tricks to do to this phone?
Sent from my SCH-I500 using XDA Premium App
Currently, im doing a bit of testing with the new phoenix 1.1 rom.
This baby can handle some crazy undervolting.
Currently:
1000 : -100
800 : - 100
600: -100
400: -100
200: -150
Going to see what i can get this down to...a bit more tweaking i bet the battery life can get phenomenal.
Try opening and closing the camera a few times in a row and see if it freezes. Or try a quad test, those are usually the things that will cause issues with too much under volting.
Sent from my SCH-I500 using XDA App
akellar said:
Try opening and closing the camera a few times in a row and see if it freezes. Or try a quad test, those are usually the things that will cause issues with too much under volting.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Already ahead of you. Up to:
1000 : -100
800 : - 100
600: -100
400: -150
200: -175
Usually ill run 4 quadrant tests and if it passes that it should be stable. Currently ran a 2187 is that a good score for 1.4ghz?
Sent from my SCH-I500 using XDA Premium App
also when using the OTB kernal what are safe settings to use? ive been running it at 1400Mhz but it lockes up and geeps giving me force close things on start up and never stops and i have to reflash to stock and start over? im assuming this isnt typical, can any one help out?
Actually that's probably pretty typical for an OC that high. I know I can't run it that high without lockups. From what I see in the original thread, most people don't run above 1300 most of the time.
SetCPU master coolbho3000 has updated his app to include support for the Tegra 2. It's available at all the familiar places.
2.2.0 - Added an "In Call" profile. Improved the Set on Boot safemode function by including a flashable zip that toggles SetCPU's safemode. Press menu on the main tab for more details. Added autodetect support for all Tegra 2 fakeShmoo kernels (ie. G2x). Added a "Voltage" tab for undervolting the CPU on fakeShmoo kernels, some custom Galaxy S kernels, and some Nexus S kernels. This is a full-fledged interface for undervolting these devices, and includes backing up and restoring and a Set on Boot checkbox. Improved the way SetCPU initially requests root. Various miscellaneous bugfixes.
Undervolting in SetCPU, now that's fantastic. By far the best purchase I've made on the market.
GideonX said:
Undervolting in SetCPU, now that's fantastic. By far the best purchase I've made on the market.
Click to expand...
Click to collapse
Also has a cool feature that allows you to extract a zip file to your sdcard in case you've set it to 1.5/1.5 and your phone freaks out. You can just boot into recovery, flash the zip and it resets setcpu.
I must say, SetCPU 2.20 is quite amazing... worth every penny
Note to ppl who upgraded from existing setcpu...re-detect your cpu speeds from the main screen. Otherwise, voltage tab will force close on you.
What would you set "in-call" to?
mmapcpro said:
What would you set "in-call" to?
Click to expand...
Click to collapse
I have 400/400 for screen off. I set in call to slightly higher at 400/500.
I'll need to test it tomorrow during calls and see if the screen wakes up quicker after a call ends.
For benching, I set it at 1500/1500 at 1300mV with no profile set for maximum power, and I'm getting much lower benchmarks in Smartbench 2011, than I was with pimpmycpu. Why do you think that would be?
pimpmycpu: 4400-4700
setcpu: 3700-4000
Wow very nice.
yes nice news ! Im happy to see old school
Great news. Just re-downloaded this and uninstalled pimp my cpu.
Sent from my LG-P999
Epiccccc. Bye bye pimp my CPU.
I love setcpu profiles
Sent from my LG-P999 using Tapatalk
I'm so pissed off by this. I legit bought cpu master at like noon on the 20th. Then I come home from work too setcpu being updated. dammit I want my two dollars back, I'm broke enough, and that could be bus money lol.
Sent from my LG-P999 using XDA Premium App
McFroger3 said:
I'm so pissed off by this. I legit bought cpu master at like noon on the 20th. Then I come home from work too setcpu being updated. dammit I want my two dollars back, I'm broke enough, and that could be bus money lol.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
womp womp. Broke but have a G2x! legit! lol. theres nothing that can come inbetween a man and his phone and car lol!
I didn't pay anything for the phone lol.
Sent from my LG-P999 using XDA Premium App
New setcpu is working like a champ. OP, thanks for bringing this to our attention.
Sent from my LG-P999 using XDA Premium App
diablos991 said:
Great news. Just re-downloaded this and uninstalled pimp my cpu.
Sent from my LG-P999
Click to expand...
Click to collapse
I did the same, but unfroze SETCPU and FROZE pimpmycpu.
In the transition, the battery got drained quite a bit over a few minutes, and heated up pretty fast when initially recharging. I had rebooted in between, but there may still have been some residual conflicts between the apps.
It froze at one point, but after a battery pull, it settled down. Overnight battery drain (with screen-off profile set pretty low) was only 4% over 8 hours. This is on EB 1.0.2 and faux stock kernel. Quadrent "only" around 4000, but everything works and this has apparently improved battery life.
A note on pimpmycpu - I thought scaling to min had stuck, but apparently not. Battery consumption was 12-15 % overnight compared to the above.
Thanks OP! I severely dislike pimpmycpu...
Sent from my LG-P999 using Tapatalk
So am I the only one that is getting significantly lower smartbench 2011 results with this updated setcpu as opposed to pimpmycpu?
mmapcpro said:
So am I the only one that is getting significantly lower smartbench 2011 results with this updated setcpu as opposed to pimpmycpu?
Click to expand...
Click to collapse
I have not seen that, although compared to Quadrent, I had not seen the very high scores that some had. I doubt SETCPU would impact you OC'd performance at max setting (although pimp had scheduler settings and SETCPU does not).
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.
Could some give me a quick rundown on undervolting a kernel. I'm using faux's 0.4.2 oc/uv cm7 kernel. From my understanding its already undervolted but I'm confused about whether I should/can adjust those settings for better results or if I should leave them alone.
Info greatly appreciated.
Sent from my LG-P999 using xda premium
Each chip is built differently, so you have to experiment on that yourself. That kernel may already be undervolted but it may not be right for you. I say adjust until you hit instability and then go from there.
tweeklulz said:
Each chip is built differently, so you have to experiment on that yourself. That kernel may already be undervolted but it may not be right for you. I say adjust until you hit instability and then go from there.
Click to expand...
Click to collapse
Sorry to jump in on this thread as well, but could you give us some info on how you would undervolt a kernel?
I have setcpu installed, is that enough? Is it possible to break my phone?
barqers said:
Sorry to jump in on this thread as well, but could you give us some info on how you would undervolt a kernel?
I have setcpu installed, is that enough? Is it possible to break my phone?
Click to expand...
Click to collapse
Yes anytime you make you phone do something it didn't do from the factory there is a chance you could damage your device..its thx to all the great devs and people that test that make it easier and less likely also the more you read and understand what it is you are actually doing to the device helps alot!
If you have a kernel able to be overclocked/undervolted yes just use set CPU to adjust the settings.
All chips are different just cause a specific setting is working for someone else means it will work the same for you!
That being said I use:
Trigger 8/22 rom with faux123'a 0.4.2 kernel.
My settings:
Max-1408mhz
Min-389mhz
And have 1.1 GHz down to 389 mhz undervolted by 50 and no undervolt above 1.1
also have different profiles set for screen off and in call..
Good luck how this helps..
Sent from my LG-P999 using xda premium
MisfitX said:
Yes anytime you make you phone do something it didn't do from the factory there is a chance you could damage your device..its thx to all the great devs and people that test that make it easier and less likely also the more you read and understand what it is you are actually doing to the device helps alot!
If you have a kernel able to be overclocked/undervolted yes just use set CPU to adjust the settings.
All chips are different just cause a specific setting is working for someone else means it will work the same for you!
That being said I use:
Trigger 8/22 rom with faux123'a 0.4.2 kernel.
My settings:
Max-1408mhz
Min-389mhz
And have 1.1 GHz down to 389 mhz undervolted by 50 and no undervolt above 1.1
also have different profiles set for screen off and in call..
Good luck how this helps..
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Thank you for such a detailed explanation! I'll be more weary of fooling around with settings. I'll probably set mine similar to yours.
Thanks everyone. I understood that setcpu would be used for the changes I was more wondering what the changes would do. Like undervolting by 50 for instance, what does that give as far as battery life? Im a moderate to heavy user and I only get roughly 8 hours off the charger before it needs to be back on, great signal all day too.
I suppose I'll just have to tinker with it till I get crashes then adjust from there.
Sent from my LG-P999 using xda premium
wgrant said:
Thanks everyone. I understood that setcpu would be used for the changes I was more wondering what the changes would do. Like undervolting by 50 for instance, what does that give as far as battery life? Im a moderate to heavy user and I only get roughly 8 hours off the charger before it needs to be back on, great signal all day too.
I suppose I'll just have to tinker with it till I get crashes then adjust from there.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
How do u get the undervoltage adjustment? i have set cpu and when i try the voltage button on set cpu, i got forced closed. Thanks in advance.
Sounds like a bad install, try uninstalling setcpu then re-installing it or fix permissions in CWM or terminal
su
fix permissions
Used to have that issue too. Try the setcpu available here on the forums, I think that's the one the worked for me.
Sent from my LG-P999 using xda premium
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