• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Overclocking questions

129260

129260

Well-Known Member
I have some questions on overclocking with latest backside in cynagenmod settings.

Ok, I currently have the cpu min set to 245, 600max.

Is that the default? Or is it higher or lower?

Also, when you choose a governor, how come the min and max do not stay saved for each governor profile?

(Like, I can't seem to choose lower settings for powersave and also have different setting for on demand, etc.)

What are good safe levels to run it at so a tiny little more performance is gained, but does not significantly lessen the battery life?

Thank you. I am very confused about all this. I am more poking around then anything, I am honestly fine with the defaults. (at least i think what its at now is the default)

Anyways, if for the sake of battery life its not worth it, then ill not even consider it. I get about a day and that's with managing all my wifi gps etc. and such. I'm on my phone a lot :cool:

Thanks for any and all help. You guys (and girls), are the best!
 
The best settings for both battery life and performance is min. 480MHZ- max 768MHz.
If that is to high the try 480MHz min and 748MHz max. InteractiveX seems to work the best for me to get both battery life and performance.
 
I used AndyOpie's suggestion, he said the same to me a few weeks ago. My Op is running great, and I haven't had any overheating since. I'm running those settings on Quattrimus right now, same results.
 
I use 787/480 with the smartassv2 governor. I agree with andyopie150's advice above though. I used those exact settings for a long time. smartassv2 gets less battery life but I don't care since I charge nightly and my phone always makes it through the day.
 
G19 said:
I use 787/480 with the smartassv2 governor. I agree with andyopie150's advice above though. I used those exact settings for a long time. smartassv2 gets less battery life but I don't care since I charge nightly and my phone always makes it through the day.
Click to expand...

So why DO you use Smartass? I haven't quite figured out the differences in governors.
 
This is just a broad explanation, but basically it changes how the cpu responds to changes in workload. For example, in conservative the cpu might clock up to just above 600 when running an app even though the max is set to 806. While in performance in might clock all the way up to 806.
 
MonsterNo7 said:
So why DO you use Smartass? I haven't quite figured out the differences in governors.
Click to expand...

I searched google to read about the differences between all the governors. I also read about other peoples experiences with overclocking on the OpV. I use smartassv2 because I thought it sounded best based on what I've read. It does have less battery life than using the interactivex governor though. I've used that one for a while also
 
Thanks everyone! My confusion is now starting to go away. I took AndyOpie150 advice and set it for this: 480mhz min ----748 max

"The best settings for both battery life and performance is min. 480MHZ- max 768MHz."

Ya that one rebooted my phone after I launched gallery. So i went for the other.
 
129260 said:
Thanks everyone! My confusion is now starting to go away. I took AndyOpie150 advice and set it for this: 480mhz min ----748 max

"The best settings for both battery life and performance is min. 480MHZ- max 768MHz."

Ya that one rebooted my phone after I launched gallery. So i went for the other.
Click to expand...

also make sure to change the governor to interactivex.

Once you use those settings and are sure your phone is stable, you can check the set on boot box
 
thanks. Ya I rapid fire launched a crap load of apps and it didn't restart. And i have to say, man what a improvement! Holy crap!

I feel like my web browsing is actually decent now haha. Big improvement. I love it. Hopefully its like AndyOpie150
said and it doesnt effect battery life to much.
 
129260 said:
thanks. Ya I rapid fire launched a crap load of apps and it didn't restart. And i have to say, man what a improvement! Holy crap!

I feel like my web browsing is actually decent now haha. Big improvement. I love it. Hopefully its like AndyOpie150
said and it doesnt effect battery life to much.
Click to expand...

My battery life always greatly improved when I overclock and change the governor
 
That's interesting....Because I know when you overclock computers like I have done in the past, it seems to draw more power, not less....

I wonder why battery life would get better? Not saying your wrong, just not sure how that would work.
 
Scratch that, my phone now constantly keeps rebooting randomly.....seems like it doesn't like any setting, I started at 768 for max then went down to 748, then down to 729...keeping it at 480mhz min. Still kept rebooting when playing angry birds or gallery sometimes. So I then put the default that it was originally....and it still reboots....I have it back at 245mhz min 600 max ondemand gov. I just wanted only a 100 mhz quicker then it was......guess thats what I get for fixing something that isn't broken....ha.

What should I do?
 
It could be a corrupt download of the ROM or Gapps, the recovery could be incompatible with the ROM or the ROM. What ROM and recovery are you using? It could be you forgot a step in the wipe and format procedure. Your phone should not be acting this way. Something is way wrong, but it can be cured by just changing what don't work.
 
I had the same sort of problem. I actually use 600 min and anywhere from 806 to 864 max with SmartAssV2 and I almost never get reboots. Every once in a while though I may get a random restart, then more and more. Then I have to reflash because going back to 245 min 600 max ondemand governor seems to still cause random restarts. It's very odd.
 
metal571 said:
I had the same sort of problem. I actually use 600 min and anywhere from 806 to 864 max with SmartAssV2 and I almost never get reboots. Every once in a while though I may get a random restart, then more and more. Then I have to reflash because going back to 245 min 600 max ondemand governor seems to still cause random restarts. It's very odd.
Click to expand...
The min is where the phone idle's. If the min is set to 600MHz then the CPU is working way to hard at idle and your battery life goes way down. For any max above 700MHz the best min is 480MHz. If the min is lower the CPU has to work to hard to ramp up when you need it. This eats up the battery as well.
480MHz min and 768MHz max (some have to go down to 748MHz, others can go to 787MHz) is the best setting for battery life. The best governor for battery life is InteractiveX.

Try 480MHz min and 768MHz max. Most IHO CM-7 ROM's have a built in CPU control in the cyanogenMod settings. If you try to use a app to do this it will sometimes conflict with the built in control and cause all kinds of force closures and system glitches.
 
When I use SetCPU instead of the built-in settings, it still works fine for me. I actually just tried 480 min 806 max with interactiveX and it didn't crash on Maps (which is what almost always crashes if my overclock is set wrong) so that seemed to work fine. My particular OV seems to be able to handle 864 MHz as well being a max somehow, so I tend to use that. Makes me wonder how much that would reduce the life of the phone...or is phone life related to heat only? I have a profile that sets the phone back to stock CPU settings if the battery temp goes over about 95 F.

Will using a speed over 787, as you mentioned, start to eat into the battery life significantly without much gain in performance? What's the optimal max clock for efficiency, given a condition that the phone will never randomly restart on any clock speed?

What I know is a problem is using a governor other than interactiveX or SmartAssV2. Using ondemand actually gives me a lot of random restarts with the same 480 min 806+ max. I find this whole overclocking thing to be a lot touchier than overclocking a PC CPU, for example. Sorry, don't mean to be too off topic, just thought I'd throw some stuff out there since I know you are an expert, Andy. BTW I'm running BACKside IHO, newest version (5/2).
 
This thread is about overclocking Questions. The more we throw out there the better the chance the OP might see something that turns the light switch on (solves the problem).

You will get way better battery life at 480MHz min and 768MHz max. This has been tested and proven over the course of a year with the CM-7 ROM's. Froyo ROM's vary widely.
Your phone may be able to handle 864 (it has to do with the quality of the processor), but what is the point. That speed is really not needed for to many games that I know of. You can always set to what I mentioned and if you need to play a game bump it up. When done set it back.
You might make your CPU last longer as heat is the enemy of any electronic component.
 
Even after doing a proper full wipe and rebooting the phone a few times, I still get a freeze on Google Maps within about 30 seconds of starting it and then the phone restarts. This happens now on InteractiveX, SmartAssV2, and ondemand governors if I so much as set 480/729. Any ideas? I'm on the BobZHome recovery and Harmonia 2.07. I verified the MD5 of Harmonia before flashing to make sure it was correct. Before flashing I wiped the cache partition, Dalvik, then formatted system, boot, data, and cache. Still does the freeze and reboot. How does Maps work on your OV, Andy? I can't seem to get it to work on anything other than a max of 600 MHz.

EDIT: Interesting...Maps is stable if I set the max and min to 729, however. Could this have something to do with the change of frequencies making Maps very unhappy?
 
metal571 said:
Even after doing a proper full wipe and rebooting the phone a few times, I still get a freeze on Google Maps within about 30 seconds of starting it and then the phone restarts. This happens now on InteractiveX, SmartAssV2, and ondemand governors if I so much as set 480/729. Any ideas? I'm on the BobZHome recovery and Harmonia 2.07. I verified the MD5 of Harmonia before flashing to make sure it was correct. Before flashing I wiped the cache partition, Dalvik, then formatted system, boot, data, and cache. Still does the freeze and reboot. How does Maps work on your OV, Andy? I can't seem to get it to work on anything other than a max of 600 MHz.
Click to expand...

From my experience, if the overclocking number is too high you will not get a freeze then a reboot. You just get a reboot. If it's a freeze and reboot it may be a problem with something else (like the overclock software or the app itself). How long is it freezing for?

My current settings are 787/480 smartassv2 and every application including maps works perfectly.
 
BTW I'm using the included overclocking settings within the CM7 settings menu for this ROM. It is freezing for around 15 seconds (the screen locks and it doesn't respond to any touch input, and the lock button does not lock or unlock the phone), then the phone reboots to the LG logo and boots back into the ROM. It's strange because this only happens when the phone is overclocked and the minimum MHz is not = to the maximum. Could something else be messed up with my phone?

BTW thanks so much guys for all the advice.
 
Thanks everyone. After a couple reboots and being back at stock 245mhz min and 600mhz max its stable again. I'm using the default governor ondemand. I am thinking about trying again to the least 700 mhz one? 720 I think it was? And maybe Ill put the min at 300 something.

I don't know. What should I do from here? Should I just leave it alone? I have no complaints with performance, just miss that really quick web browsing I had before ;)
As well as launching apps. Even just 100mhz more satisfied me well. Just not sure where to go from here now that it is stable. For rom and all my info, its right beneath my name :)
 
129260 said:
Thanks everyone. After a couple reboots and being back at stock 245mhz min and 600mhz max its stable again. I'm using the default governor ondemand. I am thinking about trying again to the least 700 mhz one? 720 I think it was? And maybe Ill put the min at 300 something.

I don't know. What should I do from here? Should I just leave it alone? I have no complaints with performance, just miss that really quick web browsing I had before ;)
As well as launching apps. Even just 100mhz more satisfied me well. Just not sure where to go from here now that it is stable. For rom and all my info, its right beneath my name :)
Click to expand...

I would keep your minimum at 480 MHz. As Andy said earlier in the thread, it actually eats up extra battery if you go lower than this for the minimum frequency. As for the max, set to taste as long as you're stable and the phone doesn't get overly hot. Obviously I'm not having as good of luck as you are, lol. Also, for reference, I was (before having these strange issues) a special profile using the app SetCPU that put my phone back to a 480 min 600 max setting automatically if the battery exceeded a certain temperature. I personally deemed about 95 F to be too hot, so I set my temperature threshold to that. Just an idea.
 
It could be a theme, a launcher, live wallpaper, an app. or the ROM.
Do a fresh download of the ROM and Gapps and make sure you check the MD5 sum before you go to your recovery menu. If the MD5 sum's don't match try again.

Reboot the ROM a couple of times after you have singed in to google and sync'd your acount and set up WiFi. Then go back to the recovery and install the theme, just wiping the cache partition and the dalvik cache before install.

Live wallpaper's do not like are processors, don't run them.

If you have a launcher and you have more than 5 screen's get rid of all but the 5 (this seems to be to much for our processors).

After you have your apps installed reboot. Go to: settings/applications/running. Stop an app. If it turns right back on in just a couple of min. write it down. If it doesn't don't worry about that one. If it's a system app, don't worry about it.

All apps that are still on you list. One by one do this: If it's on the sd card move it to the system. If it fixes the problem leave it there.
If it's on the system delete it. If it fixes the problem find another one that will do the same thing from Google play.
 
Actually, this time when I flashed, I made sure to install nothing but Google Maps. I kept everything else the same as the ROM came, and rebooted multiple times after syncing my data over via WiFi. I'm using the default blank wallpaper, so no live wallpaper there. The launcher is GB's stock. I'll try that thing with killing the apps. Also, correct me if I'm wrong, but I don't think Harmonia 2 requires Gapps. I'm also running the theme that came with the ROM as well. Thanks for all the thoughts, though, much appreciated again. I may do a redownload of the ROM and verify the MD5 once again after it is on the root of my SD card.

Also: I'm using the new screen. Maybe this could have something to do with it? This ROM has the MiRaGe kernel, I believe.
 
You must log in or register to reply here.
Back
Top Bottom