I'm newly rooted and was wondering how much difference does overclocking make
You know.. I would probably compare it to, if you have an HDTV, changing out the component cables for HDMI.
You might not actually notice a huge difference(in some cases), but you just know it's better.
If you're rooted, you must OC
The Following User Says Thank You to cableguynoe For This Useful Post:
Device(s): Galaxy Nexus running a new ROM everyday
Carrier: Not Provided
Thanks: 18
Thanked 112 Times in 59 Posts
Quote:
Originally Posted by chuck2530
I'm newly rooted and was wondering how much difference does overclocking make
Quote:
Originally Posted by cableguynoe
You know.. I would probably compare it to, if you have an HDTV, changing out the component cables for HDMI.
You might not actually notice a huge difference(in some cases), but you just know it's better.
If you're rooted, you must OC
I beg to differ. You notice it when you run multiple apps. When I use BT, wifi and radio before OC, phone would lag like no other. After I OC'd to 806 (dont try this as most ppl phones cant handle this) I run those 3 plus RunKeeper and text and it slows down just a lil bit.
To each is their own but I can see the diff in speed. And my batt life is actually better too since I have it set to 480/240 in sleep mode.
The Following User Says Thank You to droidkevlar For This Useful Post:
Device(s): Droid X w/Root & OC -HTC Droid Eris (EOL)
Carrier: Not Provided
Thanks: 73
Thanked 154 Times in 79 Posts
The MOST IMPORTANT and yet, often overlooked part of SetCPU is the Failsafe Temperature setting. In Profiles, set it to 245/480 and temp to around 43 degrees C. It will prevent you from damaging your phone/cpu/battery. Make sure profiles are ON!! and set your "sleep" profile also, otherwise your cpu could stay running at full speed even whiles its asleep. I use 245/245 or 245/480 for my sleep profile.
The Following 2 Users Say Thank You to LexusBrian400 For This Useful Post:
The MOST IMPORTANT and yet, often overlooked part of SetCPU is the Failsafe Temperature setting. In Profiles, set it to 245/480 and temp to around 43 degrees C. It will prevent you from damaging your phone/cpu/battery. Make sure profiles are ON!! and set your "sleep" profile also, otherwise your cpu could stay running at full speed even whiles its asleep. I use 245/245 or 245/480 for my sleep profile.
LexusBrian400 (Brian?), I'm running Ivan's Eris Official 1.0 and its base setting is at 710 MHz / 19 Mhz.
I'm thinking that I want to / should set the failsafe temperature setting like you advised, but I'm happy with the ROM's default overclocking settings (i.e., I don't think I need to crank it up any higher, but I'm all for being safe).
Should I only enable/set the Failsafe profile? and maybe the sleep profile (will it save more battery than my default settings)? Not sure that 19 MHz is really what the phone sleeps at...can that be right?
set top slider to 710ish
set bottom slider to 528ish
make sure "set on boot" checkbox is NOT ticked until you get everything set and after a few reboots.
"on demand" should be your daily settings, use "performance" from the dropdown when you are setting up your setcpu.
ondemand = if you dont need it it will automatically knock your cpu down to help battery and temp, when needed it cranks it to your top setting
performance = it is pegged at top setting
click profiles
tick the top profiles on box
enable sleep/stanby
click modify
set to 245/245
if you phone lags waking up then you can turn this up a bit to remedy that.
enable failsafe profile
set temp to around 40-45c and set the cpu to 245/245
this is so you dont toast your phone....very important.
now that that is all set, if your ROM can overclock more then 710, slowly crank up the OC'ing (on main setcpu screen) and test your phone to see how high you can go without forcecloses/reboots/issues etc. once you find that point set it down a notch and you are good to go.
__________________ DO NOT PM ME FOR SUPPORT....POST IT ON THE FORUM
The Following 8 Users Say Thank You to Caddyman For This Useful Post:
set top slider to 710ish
set bottom slider to 528ish
make sure "set on boot" checkbox is NOT ticked until you get everything set and after a few reboots.
"on demand" should be your daily settings, use "performance" from the dropdown when you are setting up your setcpu.
ondemand = if you dont need it it will automatically knock your cpu down to help battery and temp, when needed it cranks it to your top setting
performance = it is pegged at top setting
click profiles
tick the top profiles on box
enable sleep/stanby
click modify
set to 245/245
if you phone lags waking up then you can turn this up a bit to remedy that.
enable failsafe profile
set temp to around 40-45c and set the cpu to 245/245
this is so you dont toast your phone....very important.
now that that is all set, if your ROM can overclock more then 710, slowly crank up the OC'ing (on main setcpu screen) and test your phone to see how high you can go without forcecloses/reboots/issues etc. once you find that point set it down a notch and you are good to go.
Caddyman, thanks for the info! Okay, so I enabled profiles, enabled sleep/standby at 245/245, enabled failsafe at 41-degrees and 245/245.
Doesn't look like Ivan's ROM goes higher than 710 (okay w/me for now), but I didn't change the minimum on the main screen from 19 MHz (i.e., to 528-ish).
Last question: so, not setting "set on boot" simply keeps these settings between boot cycles? Set-on-boot would be to keep me from having to reset the above values after each reboot?
Thanks again! Not quite as scary / fun as the initial root process, but a small thrill nonetheless Appreciate everyone's help!
Device(s): Galaxy Nexus running a new ROM everyday
Carrier: Not Provided
Thanks: 18
Thanked 112 Times in 59 Posts
Quote:
Originally Posted by scary alien
Caddyman, thanks for the info! Okay, so I enabled profiles, enabled sleep/standby at 245/245, enabled failsafe at 41-degrees and 245/245.
Doesn't look like Ivan's ROM goes higher than 710 (okay w/me for now), but I didn't change the minimum on the main screen from 19 MHz (i.e., to 528-ish).
Last question: so, not setting "set on boot" simply keeps these settings between boot cycles? Set-on-boot would be to keep me from having to reset the above values after each reboot?
Thanks again! Not quite as scary / fun as the initial root process, but a small thrill nonetheless Appreciate everyone's help!
Correct on set on boot. And I would change main and any profiles that have min set to 19MHz. Can cause lock ups. just remember the lower you go, the slower the proc will go to. Some things may then lock up the phone in that MHz since it cannot handle it. I recommend 480 min for in use and 245 min for when in sleep.
But to each is their own. But those min's dont make my phone lag when waking up from sleep or any other use.
For sleep stand by, I would do 480/245. 245/245 I noticed will make phone lag when trying to answer calls or waking up.
Correct on set on boot. And I would change main and any profiles that have min set to 19MHz. Can cause lock ups. just remember the lower you go, the slower the proc will go to. Some things may then lock up the phone in that MHz since it cannot handle it. I recommend 480 min for in use and 245 min for when in sleep.
But to each is their own. But those min's dont make my phone lag when waking up from sleep or any other use.
For sleep stand by, I would do 480/245. 245/245 I noticed will make phone lag when trying to answer calls or waking up.
Thanks for the suggestions droidkevlar. I adjusted my 19 MHz main minimum to 245 Mhz (and I juiced-up my sleep to 480/245), although I have never seen an issue with this (its default 19 MHz) since I rooted in early May.
I did read the zanfur's overclocking page over at xda--wow! that guy is crazy smart!--in which he discussed the issues related to using/setting 19 MHz. This was part of the reason why I never thought that Ivan's ROM came with overclocking enabled--I didn't think that the settings (710/19) would actually work without modifying them.
I'll watch how everything feels (response time, battery life) since making the suggestions from LexusBrian400, Caddyman, and you, kind Sir!
Thanks again to everyone! We all appreciate and benefit from your feedback.
Device(s): Rooted Eris- Alyosius V12, MM Kevlar Mash v3
Carrier: Not Provided
Thanks: 13
Thanked 6 Times in 5 Posts
So apparently I can't use SetCPU... when ever I move the min bar or the max bar, the program freezes up on me... and I just bought it... errrr... Anyways, do you guys know of a fix, and if not, what other program can I use?
i have it set to 768 with the latest OC kernel, works quite smooth. I know most of the roms that people are running are using the last OC kernel. If you think your running the last kernel, chekc into upgrading. Make sure you NAND backup first, just download and flash on your current rom. Then jump into SetCPU and have at it.
I did have my Eris running at 806 on WW3.2, the phone was damn fast
__________________ WARNING Posts May Contain Anywhere between 30 - 100% SARCASM PM me if you need any further help, i'm here to help Google+ 4 Life
i have it set to 768 with the latest OC kernel, works quite smooth. I know most of the roms that people are running are using the last OC kernel. If you think your running the last kernel, chekc into upgrading. Make sure you NAND backup first, just download and flash on your current rom. Then jump into SetCPU and have at it.
I did have my Eris running at 806 on WW3.2, the phone was damn fast
I'm running Sensable and I think it has the older kernal since the max is 710. I'm primarily concerned about battery life, so I wouldn't be going above that. But would upgrading to the zanfur kernal help with battery life too?
I'm running Sensable and I think it has the older kernal since the max is 710. I'm primarily concerned about battery life, so I wouldn't be going above that. But would upgrading to the zanfur kernal help with battery life too?
It might... wont hurt to have the latest and greatest, even if you're not planning on OCing past 710
Device(s): Rooted Eris- Alyosius V12, MM Kevlar Mash v3
Carrier: Not Provided
Thanks: 13
Thanked 6 Times in 5 Posts
Sorry... guess I should have specified (DETAILS, DETAILS, DETAILS ), I am actually rooted. I did it this morning (followed with cableguy had for advice) and I flashed EE 3.0. I downloaded the SETCPU program, but when I go to move any of the bars in either direction, is freezes and I have to battery pull. To note, it only lets me go up to 528 for the max cpu. I rooted cause I wanted to take advantage of this. So, in light of the new info, got any suggestions? Anyone?
Device(s): Rooted Eris- Alyosius V12, MM Kevlar Mash v3
Carrier: Not Provided
Thanks: 13
Thanked 6 Times in 5 Posts
Could it be that im moving the slider too fast? I was just reading a thread of xda for the patch fix and he says to move slowly... which (DETAILS) I don't, I just take it from default all the way to the max...
Sorry... guess I should have specified (DETAILS, DETAILS, DETAILS ), I am actually rooted. I did it this morning (followed with cableguy had for advice) and I flashed EE 3.0. I downloaded the SETCPU program, but when I go to move any of the bars in either direction, is freezes and I have to battery pull. To note, it only lets me go up to 528 for the max cpu. I rooted cause I wanted to take advantage of this. So, in light of the new info, got any suggestions? Anyone?
And I'll change my info (<---) right now
I've accidently silide that thing way too fast before and the thing freezes up.
Very important to NOT have 'set on boot' checked. A simple battery pull will fix this.
However, this might not be your problem since you said your max is 528, right?
I think this might be because the SetCPU DEV requested that this not be included with roms, that way user have the option to donate when they download it. I'm assuming this is the SetCPU that was included with EE?
Or did you get it from the MArket?
Try flashing a newer one with the link above. Where did you get your version of SetCPU?
Device(s): Rooted Eris- Alyosius V12, MM Kevlar Mash v3
Carrier: Not Provided
Thanks: 13
Thanked 6 Times in 5 Posts
Nope.. still not working. I am at work right now so I'll have to try deleting the setcpu.txt in the morning. This is just getting frustrated. Could flashing to another rom help?
Device(s): Rooted Eris- Alyosius V12, MM Kevlar Mash v3
Carrier: Not Provided
Thanks: 13
Thanked 6 Times in 5 Posts
Thought I would give you guys a heads up on what I noticed. I was laying in bed today trying to organize things on my phone. I noticed there was a TERRRRRIIIIIIBBBBBLLLLLEEE lag, and that my phone kept going into failsafe mode. I thought it was a custom lock screen I had installed, but I did a wipe and restored a NAND recovery of before that and it was still failing. Then I POSSIBLY pinpointed the culprit.... My phone was on the charger, and the battery was getting warm because of its charge, so it kicked it into FS mode. I know, you guys probably are thinking "duh, that's obvious", but if you didn't know that, and you ever have this problem, then here is a possible explanation.
Plus, the silicone covering I think was keeping in the heat. Took it off and its cooling down now.
Last edited by namu1107; June 14th, 2010 at 08:06 AM.
I have to say that, in Ivan's, I changed to Caddyman's suggestions and it was suddenly battery-eating time. I set the mins back to 19200 and my battery is doing much better again, and there is still no lag. YMMV, I guess.
I have to say that, in Ivan's, I changed to Caddyman's suggestions and it was suddenly battery-eating time. I set the mins back to 19200 and my battery is doing much better again, and there is still no lag. YMMV, I guess.
Weird...I've still got mine set to Caddyman's suggestions and my battery life seems better ( but ). No statistics or emperical evidence to support this, but I'm sort of thinking that not having previously set a sleep profile, I wasn't sleeping at a lower clock rate and now I am.
Overclocking ?? Hmm.?
), I am actually rooted. I did it this morning (followed with cableguy had for advice) and I flashed EE 3.0. I downloaded the SETCPU program, but when I go to move any of the bars in either direction, is freezes and I have to battery pull. To note, it only lets me go up to 528 for the max cpu. I rooted cause I wanted to take advantage of this. So, in light of the new info, got any suggestions? Anyone?
