Related
Is there a good resource/thread for learning more about using SetCPU? I just flashed nerov3 and im wondering if it'd be beneficial to install it. Not sure if its neccesary or compatible... etc. How does one even know how much is safe to over and underclock?
Vibrant, NeroV3, JL5, Voodoo...
With having nero v3 installed, you can't OC it because we don't have vibrant's froyo source code yet but we do have I9000's. You could use one of those kernels to oc/uc. Nero is speedy w/ voodoo anyways so you don't REALLY need it, if u want to use setCPU to uc you can. Underclocking i would recommend min100 max800 set scaling to conservative, which will automatically clock cpu to compensate for usage. (Just my 2cents, listen or don't its your choice)
I would highly recommend SetCPU with Nero V3 or any Rom for that matter. I know for some, It is just personal preference. For me, I run my phone at 800mhz max and 200mhz min. Gives me awesome speed, with voodoo there isn't really any lag. I'm basically reiterating what ucantak3dis has said, So until there is an OC kernel. Which I'm not sure if som and/or viral have plans for. I would stick with what you've got in addition with SetCPU. You'll get great battery life out of it! Enjoy.
Thanks for the feedback guys. I installed it and im running at 200 min, 800 max (set on boot).
What exactly does that mean?
Also, I've read people talk about underclocking when the phone is asleep to save battery. Do I need to create a profile to do that?
Vibrant, NeroV3, JL5, Voodoo...
trunkstar1 said:
Thanks for the feedback guys. I installed it and im running at 200 min, 800 max (set on boot).
What exactly does that mean?
Also, I've read people talk about underclocking when the phone is asleep to save battery. Do I need to create a profile to do that?
Vibrant, NeroV3, JL5, Voodoo...
Click to expand...
Click to collapse
It means that those values are SET on boot of your device. Your phone will run anywhere between 200 mhz and 800 mhz and ramp up to a max of 800 mhz (conservatively) when necessary. Versus, Without SetCPU your phone would constantly be running at 1Ghz. You can create profiles for doing such things to save battery while the screen is locked, I have had issues with my phone NOT being able to wake though. So, try this at your own risk.
Personally, i wouldn't recommend having the set on boot checked because it caused problems w/ some ppl. I did that once and when i rebooted, it froze on the vibrant screen. idk if that's been fixed but just having setCPU set at the values you want is fine i think. Profiles aren't necessary unless your overclocking the cpu.
Hi everyone,
Like most people I've been trying to find that optimum balance between performance and battery life in my Aria. I'm running CM7.0.3 and the latest version of drowningchild's kernel. With that kernel I switched setCPU from ondemand to smartass, and I can already see the CPU spending most of it's time in either 400 or 480 MHz, but when playing a graphic intensive game it'll go up to 806 MHz and run great.
But, here's the problem. With things like less graphic intensive games, or playing videos, smartass doesn't want to scale up to a useful clock speed, and things get choppy. I switch back to ondemand and everything smoothes out again. I don't want to keep it in ondemand all the time though, because then it's spending half the time in 806 MHz and eating up battery unnecessarily.
So, is there a better governor option for me? Or maybe a way to "whitelist" apps within setCPU, to designate apps that always get the max clock speed?
tl;dr: smartass isn't that smart in certain situations. Is there a better way?
Check out the app "Tasker" in the market. It will allow you to reconfig the governors automatically based on a slew of complex conditions.
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
drowningchild said:
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
Click to expand...
Click to collapse
Hey yea you're right, I didn't notice you had a new kernel out. I'm running 7-5 still but I'll upgrade once smartass is working in the new version.
I've been using "conservative" setting. Although when it initial opens a resource intensive app, its stutters a little, and then compensates by clocking up. I haven't had an issue where a game didnt want to run smooth (also at 806mhz).
I run on demand at 320/768. This to me seems to be a very good combo. The 320 min makes a noticeable difference in responsiveness without much sacrifice to battery. I've found the Max cpu setting doesn't make too much of a difference in most situations.
Sent from my cm7 Aria.
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Gooner88 said:
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Click to expand...
Click to collapse
hi you have to flash a kernel (you ll find all the information needed in the ic sunday topic)
i did do that and its far better
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
I'm having wake-up lag too! But I already gave up thinking that the SGA's CPU just sucks. Thanks for this info GerasVille, I did not think to tinker with the System settings of CyanoGen because of the "Dragons Ahead" prompt. I will try this smartass setting to see if the wake-up lag will be removed. It sucks when I have to send an emergency SMS and my phone is lagging like hell.
Anyway so let me get this straight. Does having the minimum CPU clocked at 122mhz mean that if the device is inactive, it dynamically clocks down the CPU to 122mhz to save battery? Hence the wake-up lag is caused by the CPU being clocked back up?
I'm also gonna try out slaidfastmod to see if it makes it even better.
You can put up with the lag and save a tiny bit of battery life, or speed up the CPU and lose some battery life. Whichever you feel is more useful. Personally I don't mind the small unlock delay. Happens on most phones low powered anyway.
Sent from a phone with an app.
Eniac77 said:
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Click to expand...
Click to collapse
The kernel that is currently installed is "2.6.35.7-perf-CL562111" Ketut-lenovo #4. I am not sure if it is an OC kernel.
GerasVille said:
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
Click to expand...
Click to collapse
I installed SlaidFastMod v2, set governor to Smartass and min CPU frequency to 245 MHz and this fixed the issue! It's much smoother when unlocking.
Is it safe to tick the "Set on boot" setting for CPU settings?
hey guys.
i have been wondering about this problem for a long time, and i could not find a solution to it. Thus, i wanted to ask you guys about it. The max i can overclock my phone to is 748. whenever i try to raise it to about 768 or 787, the phone will freeze and restart. is it due to the hardware limitations of my phone? or isit due to some software limitations?
Please help.
Just Hardware.
(I can overclock to 729 )
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use the performance gov. and it's worked well.
SacredGuy said:
Hi. I'm still using Gingerbread stock rom 2.3.3 but with latest franco's kernel. My max. clock is 710Mhz. Anything above that, my phone will get freeze very often. Is there any recommendation on what should i set for my min. clock as well as the Governor?
Click to expand...
Click to collapse
I use stock 2.3.3 v20g + franco kernel and set max clock at 729Mhz, sometimes it freeze, but normally work fine (with any gov).
Each CPU is a little different. My OV is stable at 600 with smartassv2 but once I step it up to 729 the phone will randomly freeze or reboot.
Sometimes you get a good cpu that can be OCed a bit, and sometimes you get one that can go no further then stock. If you can OC then consider yourself lucky.
Whenever you try to increase the max frequency beyond a certain limit the CPU can not handle that and tells the kernel about that and kernel starts to Panic... (reboots or freeze)
For example My phone remains stable upto 768 MHz (usually i keep it at 748Mhz....)
but if i increase it to beyond 806 MHz it starts to panic...
Hardware
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
karven said:
Has differences on hardware, already tried with 2 differents P500, one could overclock to 768 Mhz, the other can reach 800Mhz without freeze.
Click to expand...
Click to collapse
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
806! never freezes but she gets warm! can get over 40 celcius
EDIT
Mind you i only get about 16 hours of battery life LOL
shubhamjain001 said:
Since all the p500 have same hardware, they can be OC to same max frequency if they have same software config...
Click to expand...
Click to collapse
where did u get ur facts?
are u smart or just effin noob?
yours preferred governors????
actually the best one is....
Dude keep it around 652 and interactive otherwise UR Battery will drain fast
depends on ur ROM+kernel combo.
on oxygen v1.1 i smoothly ran on 480-768 and battery lasted around 2 days with average use.
Now on Cm7 nightly, equally smooth at 729-480 and battery is awesome too..
Overclock
Ohhh!!! lucky guys.. my phone only accepts 672Mhz at max or anything above that value leads to rebooting or freezing.
Rom: Cyanogenmod 9 (Android 4.0.3)[BETA4]
Kernal: Franco Kernal - 4
OC: 480/672 Max
I get 748MHz completely stable when pushing "performance" governor with franco #4.
But irrespective, this is not about bragging...one would see LITTLE real life difference (save for frying the CPU faster) going above 672MHz. Don't just look at synthetic benchmarks...feel your phone.
Oh...and it was mentioned multiple times that 600->806MHz uses the same voltage hence the same power consumption for Sidestep CPUs.
I am running max CPU @ 729 and it has been running smooth for days with no freeze/reboots, I also noticed having the Governer on Performance has helped my battery life and such, i havent noticed the phone getting any warmer whatsoever so no problems with heat, Also I am using a LG-P504 Optimus One which Ive heard is the final release for this phone, so maybe its more stable than the pervious versions.
My p500 can handle 768 max. With some kernels 787mhz. But i am running 245-710 with miui v4: lol:
Sent from my LG-P500 using XDA App
Yea mine can handle that too but it drains my battery faster I've noticed. So now I run Max @ around 720 which seems quite stable!! Only time I use the nitrous feature also is with playing more top end games which I otherwise wouldn't be able to play without really low fps.
Sent from my LG-P504 using XDA App
Im using cyanogenmod nightly 7.2.0 build 34 on 748 mhz with any governer and it's working very well.OC also depends on ROM's.each ROM has different capabilities to OC...
OK, so here's the deal, I am running SetCPU and I noticed the other day while watching it, the min jumps to the max value constantly.
i.e. - my max is set to 1026, my min is set to 540, and intermittently, the min value will change on the reported value to 1026, maxing the cpu, and then return to 540. No rhyme or reason as to when it changes.
This could obviously be an issue with SetCPU, but this is really the only way I know to monitor CPU speeds, specifically. I had QuickClock Advanced, but it isn't compatible. I've heard bad things about Antutu, and I don't like the interface anyway.
Any ideas on ideas or ways to prevent the frequencies from jumping like this?
use conservative. no issues with antutu but I'm surprised you don't have freezing with frequencies under 1188
dyetheskin said:
use conservative. no issues with antutu but I'm surprised you don't have freezing with frequencies under 1188
Click to expand...
Click to collapse
No freezing... I do use conservative, but the min value is actually changing, not just the reported frequency jumping. the reported jumps BECAUSE the min value changes.... It's confusing. If I can get a video, I'll post it.
which rom u got ? ics i guess i think i had it at ics
but with cleanrom gb is all good
Proz00 said:
which rom u got ? ics i guess i think i had it at ics
but with cleanrom gb is all good
Click to expand...
Click to collapse
yeah ICS, cleanrom. it might be ics, i didnt run a gb rom on this yet.