Develop Bugs

[Q] what exactly is undervolting

i have used the search and not found any solid info
what are the benefits of it if any

I haven't heard of people undervolting their fone, although i haven't looked to much.
This would mean though reducing the power that the CPU gets. I would imagine this increases battery life among other things.

Your right about what it is, but almost every custom rom/ kernel is undervolted in development section.
Sent from my HTC Desire using XDA App

Undervolting means, the CPU (or hardware in the phone) gets lower voltages, thus saving more battery & not loosing performance.
Undervolting is a process which reduces the excess "voltage" given to the CPU using a software. This is widely used as a cooling solution and in my opinion more effective than any other cooling solution available (thermal paste, cooling pad, etc) at NO cost. Undervolting will NOT compromise performance at all. Underclocking and Overclocking (clock speeds) is whats responsible in regards to performance. Benchmarks will also prove that performance remains the same.
Click to expand...
Click to collapse

Not excess voltage but fully, manufacturer guaranteed, stable Core voltage to lower guesswork voltages which may or may not work and may or may not cause data loss/corruption.
------------------------------
- Sent via HTC Desire -

A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.

koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
Very sensible answer..Thanks

koenvbeek said:
A cpu needs power for every 'clock cycle'. 1Ghz means there are a billion per second. IF you lower the voltage, there is less power used. But if you lower it too much, the cpu wo'nt be able to 'cycle its clock'...
So undervolting doesn't affect performance, since the cpu remains on 1Ghz. It decreases the power used, so you get better battery life.
Every single cpu is different, so HTC has chosen a default voltage that (shoud) work on all phones they sell. But your particular cpu could be able to work at a lower voltage. It's just a matter of trail and error. Decrease the voltage until the cpu stops working, then higher it a bit. That way you've undervolted your cpu so it uses the least power.
Click to expand...
Click to collapse
How would one go about under volting .i have tried everything suggested to me and nothing really seems to make a difference
Sent from my HTC Desire using XDA App

Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.

TheGhost1233 said:
Most kernels are undervolted and unless you can compile the kernel for yourself you are stuck with the values given by the creator. There are two exceptions for this, HAVS kernels which automaticly chose a voltage depending on temperature and some other stuff and SVS kernels with snq-'s volt selection interface (found in Leedroid and maybe some other kernels/roms).
So what exactly have you tried and what did you expect to see? Because the difference won't be that noticeable.
Click to expand...
Click to collapse
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %. And its only taken2 mins to write
Sent from my HTC Desire using XDA App

adz63 said:
I have tried battery calibration, using app watch dog to let me know which apps are using excessive CPU. Putting my brightness down to 10%, making sure not everything is synced, the only thing synced is beautiful widgets every 4 hours. And just about everything else that has been put forward to me. Here's another example I just taken my phone off charge at 100% and wrote this and I'm now at 73 %.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
So in short you havent tried any kernel with undervolting at all!

Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).

At the moment I have the havs kernel that comes with oxygen 2.0 rc6. I have posted another topic about is the kendal good for battery life etc and no1 has told that another kendal would make anything better
Sent from my HTC Desire using XDA App

TheGhost1233 said:
Well that all has nothing to do with undervolting, but (extra) undervolting will not fix the drain problem you have.
Do you use setCPU cause your sig says you run at 1113MHz, which cause higher consumption. Also did you set your wifi sleep policy to never(setting-wireless and network-wifi settings-press menu-advanced-wifi sleep police).
Click to expand...
Click to collapse
@TheGhost1233, how exactly does one decide which kernel suits us best..
Eg: I see two undervolted kernels (I think) at 875 and 925 mV. I have no idea how to decide. Trial and error?
Froyo Kernel [email protected] min
Froyo Kernel [email protected] min

@droidzone Yes trial and error. The mentioned voltage is the lowest the cpu will get at 245MHz. Not all devices are stable with 875mV (you will know if your phone freezes up) so then you move up to the 925mV min. Other than the voltage there is no difference between 875mV or 925mV.
With the HAVS kernels it can take a while before you notice the freezes cause the voltage is dynamic, so be careful if you need your phone as a alarm clock.

[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.

700 MHz vs 350 MHz minimum CPU setting, which one is better for battery life?

According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.

350mhz.
700mhz minimum is not more efficient.

Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
for francos kernel it might be the case...not others

I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
I've read that ondemand is more power-hungry than interactive...

anton2009 said:
I've read that ondemand is more power-hungry than interactive...
Click to expand...
Click to collapse
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone

Franco uses 700 because of the wake lag caused by 350 when using hot plug mod (shutting off cpu1)
Sent from my Galaxy Nexus using xda premium

With 350 or 700 I still get wake lag.

i'm on franco's latest and hotplug is on and my cpu gov is set to conservative and min freq is 350mhz. no lag on waking at all..

180
Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
I'm using 180 in imoseyon's Leankernel experimental builds.. works amazing, telephone spends 70% in this state on average, at 180 undervolting at 875mV.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.

adrynalyne said:
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.
Click to expand...
Click to collapse
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.

But it matters every time your phone wakes up, even if its momentarily.

Only get lag and signal loss when on 350. 700 seems to give me the best sleep and wake time with no lag. I had to learn the hard way. But figured out from reading around that 350 causes some problems on any kernel/governor.
Sent from my Galaxy Nexus using XDA Premium App

The only time 350mhz gives troubles is if you set the min/max to it for sleep.

ChongoDroid said:
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone
Click to expand...
Click to collapse
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
ArmanUV said:
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.
Click to expand...
Click to collapse
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.

Actually, stock kernel, onDemand is garbage, and Interactive is best.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
You're absolutely right, I had em backwards lol
Sent from my Galaxy Nexus using xda premium

Same here.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
it's not as simple as that. when the screen is off the phone enters deep sleep as much as possible which uses (almost) the same power regardsless of min frequency. The phone obviousely will wake up from deep sleep from time to time and that's when the minimum frequency comes into play. For example, for someone who has a lot of applications syncing every few minutes or someone who listens to music a lot with the screen off (which prevents deep sleep), setting the minimum to 350 will be better. Otherwise, the savings are negligible.
This was put to test by someone here on xda (the gnexus general section) by measuring voltage and current through the battery in different conditions.

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

SetCPU Profiles

A couple weeks ago, I installed SetCPU to help with battery life. It did great! But, I didn't see the amazing improvement that I thought I would.
So, I did some research and found out about Profiles. Profiles are settings that you can make that will be applied when certain conditions are met.
Below are the profiles that I have created on my Nitro. I have seen 11 to 12 hours of medium use from my phone with these settings. If you have any suggestions on changes, please let me know. I'd like to find the absolute best settings and share them for everybody.
Profile Name: Screen Off
Conditions: Screen Off
CPU Max: 384Mhz
CPU Min: 192Mhz
Governor: powersave
Priority: 90, Exclusive
Profile Name: Charging Any
Conditions: Charging Any
CPU Max: 1512Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 85, Exclusive
Profile Name: In Call
Conditions: In Call
CPU Max: 810Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 80, Exclusive
Profile Name: Battery <= 10%
Conditions: Battery <= 10%
CPU Max: 594Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 75, Exclusive
Profile Name: Battery <= 25%
Conditions: Battery <= 25%
CPU Max: 972Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 70, Exclusive
Profile Name: Battery <= 50%
Conditions: Battery <= 50%
CPU Max: 1242Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 65, Exclusive
Profile Name: Battery <= 75%
Conditions: Battery <= 75%
CPU Max: 1350Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 60, Exclusive

By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)

noemtfj said:
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
Click to expand...
Click to collapse
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.

mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.

mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU

drumist said:
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
Click to expand...
Click to collapse
I don't do much with my phone in the way of heavy gaming or video watching. I am going off of the last couple days of having SetCPU enabled and getting almost 15 hours of medium use out of my phone.
noemtfj said:
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
Click to expand...
Click to collapse
It was an arbitrary number.
Does anybody find this kind of post meant to make peoples phones better helpful? It seems like every time I post something that I personally have found to make the Nitro even more awesome gets a tone of comments basically telling me that none of it will ever work. I'm sure that if people would just try the things I post, they would be happy.

my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.

scott0 said:
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
Click to expand...
Click to collapse
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.

mattman86 said:
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
Click to expand...
Click to collapse
yeah, i guess it's diff for everybody, just like the roms eh, some get great batt perf on 1 and sucky on another and someone has exactly opposite.
anyhoo, my jd ultimate settings are
Status
advanced profile
graphical notification->quickbox
Controls
wifi enabled->wifi preferred
brightness min 20% mid 45% max 150% (gotta get the most of this screen in the sunlight!)
light sensor fast
cpu min 192 mid 918 max 1512
governor ondemand
schedules
none, i also turned off night schedule as i have the phone plugged in during those hours.
triggers
Apps enabled
Configure->configure apps allow on during screen off->pandora
Location enabled
****************i find it makes a world of difference to give jd =>3 days to get it all right.
make sure setcpu is out of the way as well.