[Q] SetCPU scaling governor?? Which is bes? - EVO 4G Q&A, Help & Troubleshooting

I'm running calks rom, and i have setcpu with his profile settings, i just flashed the the newer kernel in the development section for superior battery charging and it has the "smartass" scaling as an option?
Which scaling governor works best? with battery and performance both in mind
"smartass" or "on-demand"

A lot of people say that interactive is really good. my phone doesn't like to play nice with it. I use performance with screen on, battery life isn't a huge factor for me. I set mine to the lowest possible with screen off. I have also heard a lot of good things about smartass, but I have never used it. I would play around with smartass and interactive and see which one works best for you
Swyped from my dark and cyanogenized EVO

I have mine all set to Smartass.
If you select a governer leave setcpu turned on and let your phone idle with the screen on and watch it.
You don't want you CPU maxing out when it's not in use.
I find smartass to keep it at the lowest clock (245 for me) better than any other governers.
Probably should add, i'm getting 20+ hours off a charge with pretty heavy use. but that's with profiles scaling my cpu down as my battery dies, all set to smartass.

With an evo and fresh 3.5.1, n4.3.1 kernal havs, bfs, sbc, the phone has been running very stable @ 1190 but the smartass setting doesnt seem to be playing too well w my phone after many benches w basic setcpu program "long bench" I have determined my phone runs optimal at conservative and performance. Battery isnt terrible on performance as if I stayed by a router for 60% of a full seidio 3500 would be 48-55 hours. This has been best combo for me for speed and life that I have found. no reboots or basic lockups occasionally for an extended time. Maybe its the way smartass looks for what to do by scaling when performance is all way looking for next task that would help it work. But thats my phone, my old droid reponded very dif to kernal swaps as I flashed many too. Battery life off the wifi more has netted me in the 40ish hour charge point. Regardlesd has held 2 days morning to evening routine.

Related

How does SetCPU harm HAVS?

If the point of HAVS if to regulate voltage, etc. Wouldn't using SetCPU, well profiles in SetCPU, work with HAVS? Example:
I have a profile set to minimize frequencies from 128-245 mhz when screen is off. If HAVS worked with these frequencies to lower voltage, wouldn't keeping the frequency threshold between those two numbers keep HAVS maintaining a lower voltage?
I see a lot of people saying not to use SetCPU profiles with kernels that include HAVS, but never really explanation why.
Also, If one would decide to only use a profile while the phone was charging, that would have no effect on HAVS when the phone is unplugged, correct? I want to be able to switch the CPU governor to ondemand while the phone is charging so I can get the maximum performance, but when it's not charging to just go back to the kernel default, which is conservative. If using profiles negatively effects the performance of HAVS, can I just use a charging profile without negatively effecting HAVS?
Explanations people!
Snap 7.6 (which has nHAVS) works fine with SetCPU, and you're encouraged to use SetCPU. I don't know where you're seeing this "Don't use SetCPU!" stuff, but it's probably just people who are trying to prevent a deluge of complaints about their phones acting wonky.
Use SetCPU. The worst that can happen... Is your phone acts wonky/poor battery life. Make sure to NOT check the "Set at boot" options in SetCPU while you're testing!
drmacinyasha said:
Snap 7.6 (which has nHAVS) works fine with SetCPU, and you're encouraged to use SetCPU. I don't know where you're seeing this "Don't use SetCPU!" stuff, but it's probably just people who are trying to prevent a deluge of complaints about their phones acting wonky.
Use SetCPU. The worst that can happen... Is your phone acts wonky/poor battery life. Make sure to NOT check the "Set at boot" options in SetCPU while you're testing!
Click to expand...
Click to collapse
Figured as much. Thanks!
Ya know, I never understood why people were saying not to use SetCPU with HAVS kernels either especially since, like, for example, Calkulin highly recommends SetCPU for use with his ROM and that comes packed with Kings #10 nowadays. I figure if Calk (or any other reputable ROM/kernel dev) says to do it he's probably saying it for your benefit. Now, on to find a real reason as to why or why not
I think that what is meant is that you don't have to use SetCPU because HAVS already reduces voltage to the processor when it isn't being used. Using SetCPU profiles won't mess anything up, but it is redundant to do so if the HAVS kernel is already controlling the amount of juice that goes into the processor at any given time.
Please note this is a hypothesis. I am not an expert by any means. If someone knows any better, please clarify, because I have been curious about this, too.
rugedraw said:
I think that what is meant is that you don't have to use SetCPU because HAVS already reduces voltage to the processor when it isn't being used. Using SetCPU profiles won't mess anything up, but it is redundant to do so if the HAVS kernel is already controlling the amount of juice that goes into the processor at any given time.
Please note this is a hypothesis. I am not an expert by any means. If someone knows any better, please clarify, because I have been curious about this, too.
Click to expand...
Click to collapse
It makes sense, but isn't HAVS only a voltage regulator? Using SetCPU to lower frequencies should theoretically compliment HAVS especially with screen off profiles as to keep the voltage low with HAVS, and frequencies low with SetCPU. I know that Android/CPUs clock down when idle or when the screen is off, but their maximum frequencies aren't lowered as well are they? Using SetCPU to set a maximum frequency that's low should be even better. That's my take anyway.
Here is a comparison someone did with SetCPU and various kernels and went so far as to say they've read several places that using SetCPU in conjunction with 'newer' kernels may be counterproductive, since the inclusion of HAVS. However, I haven't been able to find that many posts to backup this claim. That or I just suck at searching. lol
http://androidforums.com/evo-4g-all-things-root/179761-kernels-setcpu-battery-comparison.html
I'll run a test
hayabusa1300cc said:
i use the dc compaitble one and i love it the best
there is one i want to try today, its
netarchy-toastmod-5.0-cfs-havs-preview-universal-signed
Click to expand...
Click to collapse
Okay. Been running the Netarchy CFS HAVS 4.1.9.1 universal kernal in conjunction with set cpu and using Virus Anthrax v4.....battery life is bad so far. I don't know how it could be better on anyone else's phone either. I have set CPU set to minimal settings (profiles) and conservative. My up time (display)has been around an 45 min total. One call and a couple of MMS sent. My power manager settings keep the screen set to 80 on battery power. Total time 7 hours with 32 percent remaining.
Wifi, 4G, GPS, and push are TURNED OFF. Nothing that drains battery above normal system apps, is running.
This is not a good Kernal UNLESS........its because I just started using it this morning with my first run through of the battery being fully charged and the stats reset at the time of full charge.
So the question is:
How long should we run a kernal after:
1. Installing it
2. Starting with fresh 100% battery charge
3. Wiping battery stats.
Does it need one drain and one full charge before you throw the kernal to the dogs?
Should set CPU be disabled / uninstalled after HAVS kernals are flashed? I think I remember reading somewhere that you should not use set CPU with HAVS kernals. It doesnt make sense to me as set CPU sets the clock frequency and HAVS is for voltage scaling?
Im going to try and recharge the phone tonight after full run down and disable the set on boot setting for set CPU.
Anyone have any answer on this?
-JZ
Well my understanding is that havs and setcpu do the same thing sorta, depending on how you set your profiles up. Because havs underclocks while the screen is off, which can be done with setcpu, and if you set setcpu to conservative then you might be getting the same affect you would get from havs. Having them both run is like overkill, your phone would be doing double the work for the same results.
Battery still gonna be a pain while the screen is on so it's not like both of these will drastically increase battery life while in use. It'll just manage the battery alot better while the phone is idle.
ms79723 said:
Well my understanding is that havs and setcpu do the same thing sorta, depending on how you set your profiles up. Because havs underclocks while the screen is off, which can be done with setcpu, and if you set setcpu to conservative then you might be getting the same affect you would get from havs. Having them both run is like overkill, your phone would be doing double the work for the same results.
Battery still gonna be a pain while the screen is on so it's not like both of these will drastically increase battery life while in use. It'll just manage the battery alot better while the phone is idle.
Click to expand...
Click to collapse
Hmm.. I should probably do some more reading on HAVS, because if it is responsible for regulating clock frequencies as well, then it would be counterproductive. HOWEVER, if HAVS does indeed regulate clock frequencies, the question would be what is the minimum/maximum frequency that our current HAVS kernel allows when the phone is asleep or idle? Because on my SetCPU profile, it is 128/245MHz for screen off.
freeza said:
Hmm.. I should probably do some more reading on HAVS, because if it is responsible for regulating clock frequencies as well, then it would be counterproductive. HOWEVER, if HAVS does indeed regulate clock frequencies, the question would be what is the minimum/maximum frequency that our current HAVS kernel allows when the phone is asleep or idle? Because on my SetCPU profile, it is 128/245MHz for screen off.
Click to expand...
Click to collapse
I don't set my set cpu that low because, again......I read this somewhere....., set CPU with frequencies below 384 will disable the WIFI. Sounds wacky.....I know...if there is any truth to this let me know. I guess I could check to see if the WIFI enables after the screen off.....eg....its looking for the ip....
Great idea on a thread OP. Its obvious we need a place to gather some real information from reliable sourses on:
1. SET CPU and its use with newer Kernals / Kernals with HAVS in them
2. Are the newer kernals so evolved that set CPU is no longer needed. (I'd love that as Im a bit tired of setting my profiles every time I flash a ROM)
jasonziter said:
I don't set my set cpu that low because, again......I read this somewhere....., set CPU with frequencies below 384 will disable the WIFI. Sounds wacky.....I know...if there is any truth to this let me know. I guess I could check to see if the WIFI enables after the screen off.....eg....its looking for the ip....
Great idea on a thread OP. Its obvious we need a place to gather some real information from reliable sourses on:
1. SET CPU and its use with newer Kernals / Kernals with HAVS in them
2. Are the newer kernals so evolved that set CPU is no longer needed. (I'd love that as Im a bit tired of setting my profiles every time I flash a ROM)
Click to expand...
Click to collapse
I have my WiFi turned on and connected to my home network all the time and have never noticed it shutting itself off or disconnecting with my frequencies that low
I don't think SetCPU will ever be obsolete unless devs compile a kernel that can automatically do the following:
-set max frequency to higher than default. (but probably wont for max compatibility reasons, since no evos are made equal and that said frequency is guaranteed to work with all evos.)
-set minimum frequency to the lowest possible without adverse reaction.
-dynamically change governor based on either charge state/load state/or remaining battery life.
-dynamically change max/min clock frequencies based on either charge state/or remaining battery life.
SetCPU will probably always be in my bag of must haves, BUT if there is proof that using profiles negatively effects HAVS, I will just remove the screen off profile. With netarchy's 4.1.9.1cfs kernel, conservative governor is the default, and SetCPU allows me to change governor to ondemand with a profile of charging/full. This is perfect.
Speaking of HAVS and SetCPU, a snippet from the common misconceptions thread:
If using a kernel with HAVS, you do not need SetCPU to under clock. That is exactly what HAVS does, lowers voltages when your phone is idling. You are defeating the purpose by using SetCPU. This is why Kingklick himself tells everyone not to use SetCPU with his kernels.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=790427
There's quite a bit of information in the Ultimate Kernel Review here ...
http://forum.xda-developers.com/showthread.php?t=790559
In a recent post, the author (skydeaner), posts his own personal settings which include Kings #9 (havs) and SetCPU ...
http://forum.xda-developers.com/showpost.php?p=8465730&postcount=104
Nice post man. Finally... some real info to use. I think I'm going to airborne virus with kk9.
Sent from my PC36100 using XDA App
One King hasn't said to NOT use SetCPU, he said that setting profiles in it might interfere with his kernels sometimes and cause a slight conflict. You still have to use setcpu for overclocking your phone.
Also this snipit is from the other well known Dev in his Rom thread.
Calkulin said:
I think some people have forgotten what HAVS/AVS actually do. They voltage scale based on CPU speed, so SetCPU shouldn't interfere with HAVS/AVS since it can only control CPU speed/governor not voltage.
Now if SetCPU gets updated and starts controlling voltage then we'll see issues with HAVS/AVS kernels
Click to expand...
Click to collapse
palmdude said:
Calc thanks! But for simple people like us could clarify what it is better in terms of battery life, setcpu installed or uninstalled (on king#10)?
This is what we were guessing/debating
Click to expand...
Click to collapse
Caulkin said:
Installed since it gives you better control over which governor to use and the parameters for that governor. Plus let's not forget the benefit of profiles which if done right, will improve performance & battery life.
But on a side note, here's what I've noticed for the 2 main kernels here on my phone
King's kernel is better on battery life but Netarchy's kernel has a better overall smoothness feel
Click to expand...
Click to collapse
sgt. slaughter said:
One King hasn't said to NOT use SetCPU, he said that setting profiles in it might interfere with his kernels sometimes and cause a slight conflict. You still have to use setcpu for overclocking your phone.
Also this snipit is from the other well known Dev in his Rom thread.
Click to expand...
Click to collapse
+1 on all of those points.
I just got my Evo not too long ago, so I am still trying to figure out all of the SetCPU/HAVS/OC/UV nonsense to try and optimize my battery.
I am trying to translate all of the information this thread provides (plus all linked threads and relevant searches) in to stupid (the only language I understand)
HAVS and SetCPU can be used together (in theory) because
HAVS only effects voltage
SetCPU only effects processor speed
Anecdotally HAVS is a little wonkier than a non-HAVS kernel (from a benchmarking perspective)
Anecdotally HAVS and SetCPU have not returned the expected increase in battery life (possibly due to redundancy)
All should be taken with a grain of salt as each evo is a little different
In theory, Kings or Netarchy + SetCPU should equal great battery life when on standby (and depending on OC options should help when in use as well)
---
Is that an adequate translation to stupid?
Psichi said:
I just got my Evo not too long ago, so I am still trying to figure out all of the SetCPU/HAVS/OC/UV nonsense to try and optimize my battery.
I am trying to translate all of the information this thread provides (plus all linked threads and relevant searches) in to stupid (the only language I understand)
HAVS and SetCPU can be used together (in theory) because
HAVS only effects voltage
SetCPU only effects processor speed
Anecdotally HAVS is a little wonkier than a non-HAVS kernel (from a benchmarking perspective)
Anecdotally HAVS and SetCPU have not returned the expected increase in battery life (possibly due to redundancy)
All should be taken with a grain of salt as each evo is a little different
In theory, Kings or Netarchy + SetCPU should equal great battery life when on standby (and depending on OC options should help when in use as well)
---
Is that an adequate translation to stupid?
Click to expand...
Click to collapse
Well without the kernels, setcpu can help a lot when on standby. But Havs is now being focused on when the screen is on, and undervolting to help save battery while you are currently using your phone. Check out Netarchy's universal kernels, the more aggressive undervolting ones and then go to one of king's kernels and you'll see a huge difference between battery drain while the phone is on from the kernels. The more aggressive undervolting kernels hold on to that battery like there's no tomorrow.

[Q] OverClock CM7

I was wondering what were "optimum" SetCPU settings while running cyanogenmod 7?
Optimum for what? battery life? performance?
Of course, you could just keep it overclocked, as high as 1.8ghz I think depending on your kernel. But your battery life won't be that great.
You can also keep it at the stock 800mhz.
Most people I bet keep it around 1ghz, and have SetCPU profiles set up to lower CPU speed as battery levels get lower and lower.
I personally (not on CM7) set mine up to lower CPU a tad at 40%, even lower at 20%, and drastically lower at 10%.
I guess optimum for performance while saving battery life. I'm new to the whole overclocking and I'm not sure what profiles to set up
Sent from my HTC Vision using XDA App
Well the thing is its really all personal preference when it comes down to it. Just tweak with your settings and check out your results.
I mean optimal performance with maximizing battery life would follow a few basic profiles:
Screen off: 245min/245max
When <10%: 245min/~500max (my personal preference)
And if you're trying to keep your battery pretty decent, I would recommend keeping your clock speed at 1ghz or lower maximum. Anything higher you're gonna start seeing negative battery life.
There are many other things to do to lengthen battery life that aren't SetCPU related, such as managing your radios and networks.

[Q] Recommended SetCPU Settings for HTC Desire

I want to over clock my HTC Desire using Set CPU
What should my max over clocking be , and what temperature should my CPU run at to be safe ?
I'm currently using the RCMixHD kernel.
Depends on your kernel.
Also, li-ion batteries are designed for use around 20c-60c, but as it goes past 40c, I think it has higher discharge rate.
Depends on your phone & kernel combo - 1113 Mhz is stable for the most of the people.
I suggest playing around with and test it - 1113+ is OK for some, but if you'll get reboots and the phone gets hot, then it is not recommended.
Also if you are OCing, you'll get more power, but worse battery life.
wont it consume more battery ??
I have Coutts 2.6.38 kernel and it allows me to underclock to 128MHz and 1190MHz overclock and I use ondemand since games don't like other governers. The underclock is bloody great to have as it consumes bugger all battery life and kind of balances out the overclock. However, as nagypapi said, you might not be able to get these speeds since your phone might get hot or reboot. I think people fail to realise that not all devices are the same and what works for one person, might not work for another.
Max. clock should depend on kernel support(if the kernel supports it, then that's your maximum clock). As for temperature, I have a profile on SetCPU which down-clocks the CPU when the temperature reading goes above 36 degree celsius. All other times it works between 806MHz-245MHz OnDemand.
Walter1115 said:
I want to over clock my HTC Desire using Set CPU
What should my max over clocking be , and what temperature should my CPU run at to be safe ?
I'm currently using the RCMixHD kernel.
Click to expand...
Click to collapse
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
bono2804 said:
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
Click to expand...
Click to collapse
I would like to try this settings, but could you please also add priorities for each setting?
Also what is your main governor? (when you startup SetCPU)
Other thing i dont understand why people use such high cpu freq for battery charging (when its charging and im never using phone then, isnt it better to put some low freq. and power saving profile?)
Same about Standy/Screen off.
128 is too low, it makes my phone slow, 245 is better IMO.
Sordep said:
128 is too low, it makes my phone slow, 245 is better IMO.
Click to expand...
Click to collapse
set 245 for screen off only ... Its not meant to make your phone quick its meant to conserve battery lol
BigMrB said:
set 245 for screen off only ... Its not meant to make your phone quick its meant to conserve battery lol
Click to expand...
Click to collapse
I know it, but weird, when I set the lowest value to 128, my phone's reaction become laggy, but 245 has no such problem. Maybe it's affected by kernel or rom.
sorry for my poor english
I know some roms/kernels have issues with dropping to 128 but my rom seems quite happy with it. I use higher CPU on charge and with battery above 75% to give me the performance when I have the most charge. When my phone boots it will adjust CPU according to battery life or charging profile. The settings seems to work fine for me although battery does drain quicker when I have it fully charged but that's my own fault for setting the performance govenor when I have high charge!
bono2804 said:
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
Click to expand...
Click to collapse
I'm using your way! thanks!
No!
Using any CPU frequency that is not default ( underclocked or overclocked ) requires testing and manipulating the various variables. The CPU needs to be in sync with the GPU and the other parameters. Needs modifications in the kernel itself. The device is not made to run at those frequencies. You will burn your device, sooner or later.

Undervolting - good idea or not?

I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.
Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium
Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X
If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.
Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.
Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.
I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
I've read many times undervolting isn't worth it.
Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.
I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse
I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).
Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?
Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.
Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.

Setcpu Profiles

Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
kazemagic said:
Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
Click to expand...
Click to collapse
i i think that ondemand is the best for daily using... i'm using cm10 rom and i have some music problem so i'm using interactive and it's ok. if you don't use games or heavy apps, you can underclock it to 1ghz or even less and put on powersave.. but you have to try and find the best for you
My setup is a little complicated. I use the ondemand governor, then for the profiles I make it use powersave and under 760mhz between 1am and 8:30am which seems to really help during the night. Also set it to use 760mhz max when the screen is off.
When charging or above 40% battery I allow it to run full speed, but only when the screen is on, therefore helping charge times. On charge or above 80% I set the governor to performance.
In call I set the clock to max 1000mhz and conservative to try and allow calls on low-battery to work properly without lag but also without killing the battery.
I have a couple of other options set for very low battery ( < 12% ) too, but those are only to extend the battery if it's dying.
I wouldn't say all this is necessary... but I need my phone to keep working at all times as I use it for receiving business calls.
It's just a matter of playing around really... depends what you use the phone for. For the most part tell it to use lower clock speeds when you don't need them so much (when phone is off, during the night, during call etc) but you will really notice the speed difference if it's underclocked while you use it, so I tend to allow it to use full whack when screen is on, unless the battery is low.
I also set up profiles to make things like Bloons TD4 run in performance mode and min of 1000mhz, to keep them smooth . Drains the battery though!
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
kazemagic said:
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
Click to expand...
Click to collapse
If you mean decreasing the voltage on the CPU, no I haven't. From my experience in desktop PCs however, if the CPU voltage is too low it can lead to hardware issues and instability.
If something needs a certain amount of power, and you give it less, it will either try and draw more amps which increases heat and can fry components, or won't work properly. You could probably "under-volt" the CPU at the same time as reducing the clock speed however, but your performance will suffer. When the processor is set to be ondemand it underclocks itself when not in use anyway
The biggest battery drain is screen and radios, concentrate on using them less. Underclocking the CPU will make the phone last longer when in use, but usability will suffer and turn your super fast smart phone into a sluggish one. I only make mine stay underclocked when the screen is off, during a call, or on low battery. During general use I let it do its thing .
UV(Under volt) is actually not to bad. Don't ever set those values at boot, else when they are too low, it will cause BOOTLOOPS. It just reduces the amount of power allowed for the cpu to use, thus it won't use more than required. You can't really ask a person for his/her uv values, as no 2 chips are created equal.
People stating that they UC(underclock) their device is not quite right. We don't have much control over our cpu's to be honest. If you run tegra stats whilst using you're phone, you'll see what I mean. It will sometimes(happens quite often) just bump up to higher frequencies to which you UC them. Also as soon as the screen is locked and unlocked the max cpu frequency set by the governor will just return(for example: say stock is 1500mhz, and you set it to 1400mhz, it will return to 1500mhz after an unlock). Ondemand is very very good for battery and performance. But remember you have to tweak those values individually in order to optain the best possible performace for the given task you want. Whether it is for battery or performance.
It's actually also a lot better to just tweak those values as to TRY and uc. Uv will stick, UC not!
Here is a small example as to battery saving and performance values for ondemand governor:
sampling rate:---------60 000 ----- 30 000
up threshold:--------------95 ----- 60
sampling down factor:-------2 ----- 8
powersave bios: ------------3 ----- 0
ignore nice load:------------0 ----- 0
io is busy:------------------0 ----- 0

Categories

Resources