I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
syrenz said:
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
Click to expand...
Click to collapse
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
SetCPU is used for setting CPU parameters. Like the range of mhz your CPU works at. Also setting profiles (CPU mhz when the phone is charging, reach temperature, battery lower than... etc.). But it cannot be used for overcharging, that's why we use Milestone overclock...
Sent from my XT720 using XDA App
jackfrost3821 said:
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
Click to expand...
Click to collapse
Setcpu is free for XDA members bud, find it here
how should i adjust my advanced settings? im overclocked at 850mhz
LibertyMonger said:
Setcpu is free for XDA members bud, find it here
Click to expand...
Click to collapse
Thank you I wasn't knowing it is free for xda members!
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Thanks for the answers
jackfrost3821 said:
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Click to expand...
Click to collapse
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
LibertyMonger said:
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
Click to expand...
Click to collapse
Exactly that is what I've tried, uninstalled SetCPU to see the battery performance. It was really unnoticeable the battery drain with and without Setcpu. I use Autokill Memory Optimizer which seems to be providing good results as well as performance enhancement.
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
exist2resist said:
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
jackfrost3821 said:
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
Click to expand...
Click to collapse
I guess you are correct.
But currently I removed the SetCPU. And I see much better performance now. I was min at 250MHz. Even the quadrant score is much better now.
Thanks for your insight
I remove setcpu and do a comparison too. I'm using CM 7.1.0 of fjfalcon and it lasts 1.5-2 days with minimal usage on setcpu. Now let's see if it's barely unnoticable.
but I think set cpu to 250mhz during the night when you don't use your phone may prolong battery life.
Woodrube said:
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
Click to expand...
Click to collapse
Dude! with those settings what is your battery life like?
my minimum is at 125mhz and max at 250mhz (when screen off) and I lose 30% over night! and it barely lasts 8hours D:
what ROM are you on?
Do you guys know how the smartass governor works?
Related
If you are using one of the Over-Clocked Undervolted Kernels please uninstall set-cpu and observe your battery life for 3 days and compare it to what you got when you used set-cpu. Then report as to if it is better, worse, or the same.
Just compare to what how long your battery lasts with your normal usage. Please do not give replies like "I only used 30% in two days with normal use."
Just reply with either better, worse, or same. Because usage is relative and that is not the purpose of this.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
IF YOU BELIEVE YOU HAVE BETTER BATTERY LIFE WITHOUT SETCPU, THEN GET LOGS WHILE IT IS RUNNING AND SEND THEM TO THE DEV.
I have also noticed lag on the home screen with setcpu, I started using Overclock Widget to detect the values and to diff freq screen off 245-576 and put the phone on sleep while charging so will stay cool. Battery life has been great so far! I'm using 2.6.33.4 [email protected] #1 about to upgrade to his newest 2.6.34...I think SetCpu has flaws!
Will let you know my results.
this thread may be of some help. im currently trying pershoots 5.12vfp release without setcpu at all.
i do, however, remember getting 37 hours with moderate use with setcpu and profiles set, but i cant remember which kernal it was exactly. i think it may have been IRs 4.29 release..
Just uninstalled SetCPU and I'm running Pershoot's newest 2.6.33.4 925 Kernel. I will report back my findings in a couple of days...
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
paulk_ said:
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
Click to expand...
Click to collapse
Nope, incredible and onwards only.
Did this Quite a bit ago... ran with and without for over a week and i have better battery life without setcpu
When you don't have setcpu, you're not running at 1113ghz..
persiansown said:
When you don't have setcpu, you're not running at 1113ghz..
Click to expand...
Click to collapse
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
You mean that the Incredible features CPU throttling?
jlevy73 said:
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
Click to expand...
Click to collapse
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Casao said:
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Click to expand...
Click to collapse
I completely agree however all the kernels I use are from the same person and the optimizations at the different clocks speeds are identical. Therefore the spread in my linpack scores indicate that setcpu is not required. At least, that's my theory
this and other threads have made me question why we need setcpu anyways. I have it running and its great but can't we just integrate what setcpu is doing from the get go instead of having an external app running a separate process?'seems a little inefficient to me. The reason I say this is that I noticed most people are using the same settings for set cpu.
anyways, I dunno how relevant all this is since froyo's just around the corner and that may alleviate some problems but bring more problems
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
Click to expand...
Click to collapse
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
chowlala said:
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
Click to expand...
Click to collapse
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Well there you have it, straight from the source
TL;DR - setCPU doesn't run code in background unless you use profiles, it doesn't make your phone hotter unless you use a 1113/1113 profile, & if you value battery life don't use setCPU Active widget.
SetCPU
coolbho3000 said:
...
Click to expand...
Click to collapse
Props dude. Keep up the good work.
To be honest I'm a user, donator and supporter of SetCPU. I've never had cause to complain.
Not bashing your app dude, in fact I have the paid version. I am only wondering why people are noticing better battery life without it than with it. Want to see if it really is setcpu or something else. To do that something has to be isolated.
And I believe that if the freq are set in the kernel then the phone will scale up an down on its own.
coolbho3000 said:
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Click to expand...
Click to collapse
I too am a fan of setcpu, and over the last week I did get curious due to this this thread. I found my battery ran down quite significantly faster without setcpu, maybe because I didn't have my sleep profile of lowest freq min/max, or my battery profile of max 756, or my low battery profiles scaling down my cpu max. Either way, stop bashing the app, it's awesome, and if you had concerns, take them to the dev rather than start a witch hunt in the forums trying to make a posse.
People that report better battery, may not have had setcpu set up correctly in the first place. A friend of mine at work installed it, ran for a day and uninstalled it, citing it didn't do anything and infact drained his battery. He had the widget running, and had upped the minimum cpu freq to 500 and something, max to the 1.13ghx. He didn't run profiles. But as such, he wasn't letting his phone scale down to the lowest freq when it wanted to, and had the widget drain. I got him to set t up as I have mine, and he was blown away with the change.
"My car wont go over 20km/h"
"Are you putting your foot on the accelerator?"
"Whats an accelerator?"
Things have to be used correctly to get the best out of them, and unless someone saying it's far worse than without actually comes in and puts up their values they have it set to, we have no idea why they are having the fault. My experience (I have worked tech call centres for years) is that 99/100 issues people experience are due to not using things as they are set out to be, or just have no idea how to do what they are trying to do. My work mates thing was that he thought all apps would go faster if he increased the minimum freq, so therefore use less battery because the processes are completed faster. In a way it's logical, but the result is that even when nothings running the cpu wont fall below that value, so the battery drained much faster than he expected.
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
I'm running Bullet 1.420 Kernal, what's a good setting for setcpu for profiles and such? I've been a vibrant rooter for a long time and never looked into it, thanks!
Sent from my SGH-T959 using XDA App
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
kaintfm said:
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
Click to expand...
Click to collapse
Oh okay, thanks, but what will happen if I put 1420 high and 100 min? Cause I want my Kernal to be free and not suppressed at the standard the phone puts, will that "free" it and will it kill battery faster? I hope you get what I mean, lol
Sent from my SGH-T959 using XDA App
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
kaintfm said:
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
Click to expand...
Click to collapse
Oh okay, and Overclocking OBVIOUSLY kills battery right? Ans would 1420 high, 800 min kill much battery?
Sent from my SGH-T959 using XDA App
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
kaintfm said:
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
Click to expand...
Click to collapse
Oh okay, that'll be it then I guess, I appreciate you answering all my questions when we both probably know I could've looked them up, ill be sure to thank you when I'm on a computer!
Sent from my SGH-T959 using XDA App
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Search for the setcpu thread by lennyuk.
All your answers are in there. Sorry don't have the link but you will find it. Think it might be in android development and hacking section??
Edit:
http://forum.xda-developers.com/showthread.php?t=1158102
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
UC/UV/OC can harm your phone if not properly taken care of.
Each cpu is different so there is no 'best settings'. If i share my settings, it might not be stable in your phone, or may be you can undervolt more than me which means your cpu can handle lower voltages better than mine.
You can use an init.d script (if your kernel supports) or SetCpu or Voltage Control to overclock/underclock/undervolt.
First thing, search through kernel threads and find a kernel you think suits your taste best.
Next, using setcpu or voltage control, set a min and max global frequency.
Now for each frequency lower the voltage by 25 mv (from stock). Keep doing this until your phone becomes unstable or hangs. Use the last settings that didn't cause any problems.
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
ProNewb said:
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
Click to expand...
Click to collapse
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
Deep Sleep doesn't mean locking on to lowest frequency supported by kernel. (200 mhz on stock).
Deep sleep is the state where both cores shut off, and system (O.S) goes to sleep, governor stays idle, etc etc. There will be some background processes running too, but cpu is not using 200 mhz throughout deep sleep.
EDIT: Or you meant a screen off profile.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
The phone should be in deep sleep, but some apps don't let the phone sleep at night thanks to there inefficient coding.
Anyway it does seem to use less battery, without this profile, I loose around 9% in 6 hours, but now I loose only 4-5%.
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
just unistall setcpu and then reboot your phone and then you go back to default values
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
I limited uv clocks, so there is a low limit. One day ill add more low end clocks but it won't matter because the photon uses a separate clock for suspend. I knew people would try to uv to 500 with it set on boot and screw there phone up. So this way I didn't have thousands of user error related uv issues. Uv does works but its more for high end than low end. Low end uv causes sleep of death.
w0lf215 said:
Ive been running the "cm7-1.4highpro-test-rev3" kernel and it runs great. I've been bumping up my undervolting slowly, and im at -475 at 216 mhz, which (in theory) should be the undervolt clock speed that will save me most battery becasue i have phone set to go between 216 mhz and 312 mhz when screens off. Ive got both 216 and 312 mhz undervolted extremely heavily and i haven't seen ANY issues. The rest of clock speeds are at -100 or so, and if i push much further than that the phone locks up and does weird stuff. This would lead me to believe that the undervolting IS indeed working. But can the processor really run at -475 @216mhz and [email protected] without any side affects?? I haven't once had it get stuck in sleep mode with screen off or ANYTHING, so im a bit unsure if it is actually undervolting or not.. Myrt undervolt shows that my phone is undervolted to the specific settings i set within SetCpu. I also havent seen much, if any, difference with battery life. With 10 hours of idle time, straight idle screen off whole time, wifi, gps, mobile data, 4g, bluetooth, all that stuff off and after 10 hours my battery is down to 85%.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Changing suspend voltage can only be done in source. I havnt played with it yet because i need to test it on a stable kernel that way i know any issues would come from it. As far as extra uv steps its planned after wifi fix. I wont add 500 new steps probably 2 steps at a time(-25 steps). Im also planning on changing my clock table(multiples of 216 only). I might make a half step 1.0 kernel underclocked to 108~192. It will be mem underclocked and gpu/avp underclocked. With lower voltage tables on everything. Default scheduling will be powersave. Which you can check out with cpu master right now. That kernel will also have a tweaked 2 core start/stop.
w0lf215 said:
haha ok I understand, just thought I was going crazy there for a bit, or had the most amazing tegra 2 known to man. is there a way to UV the suspend mode then or no? And is my battery life at idle about average or low considering the UV. do you have any kernels for CM7 that aren't limited for UV? Thanks for reply, and all your hard work on the photon!!
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
All new ones this week have tweaked 2nd core
DethMetalz69 said:
"That kernel will also have a tweaked 2 core start/stop. "
Holy ****!
That would be the best thing
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Im building a battery version of top secret now
Sent from my MB855 using XDA App