So im using a CM7 nighlies right now and i just got SetCPU and i was wondering what profiles should i set up and how should i set them up cause all i care about right now is making battery life a better.
As for me, I only have two profiles set up. One for screen off set at 245mhz min/max on powersave/conservative @ 90 priority and one for battery temp greater >45 degree C set at 614 mhz max 245mhz min @ 95 priority, on conservative. I've been using this setup on Fresh 3.5 with Netarchy's 4.3.1 stable kernel and my phone has been off the charger for 22 hours with about 20% remaining battery and thats with moderate usage and with WiFi on entire time. You can have unlimited profiles set up based on remaining battery, battery temp, etc and set up the profiles with higher priorities with higher priority number designation. Even though Net's kernel allows me to underclock all the way to 128 mhz, my phone does not like to me underclocked that low.
I'll try that out see how it works
Related
If I've found a combination of rom/kernal/voltage that's stable for me to run at 1500MHz, is it safe to run that way full-time? I mean, I would still use profiles in setcpu for in-call and screen-off...but would this damage my phone? I do keep the phone in a case, if that has any bearings. I can feel it considerably warmer when I oc it than when I leave it at 1GHz.
what kernel do you use? the new trinity kernel doesnt scale and stays up at 1500 100% of the time, i havent had any problems with heat using 1500 on other kernels, i have a profile to underclcok if over 40C but never kicks in while running faux's kernel and screen off underclock, long term a constant temperature of 40C plus would damage the phone as heat damages any electronics.
I'm running faux's froyo kernal. I have setcpu profiles setup for:
in-call 500/400
screen-off 500/400
and now I just added temp>40c (following your lead) 1000/400
I have 1300mV set for 1500MHz and 950mV set for 1000Mhz...and I believe it's 770 for 400MHz. If I understood Faux correctly, that's already -50 undervolted.
Is there a recommended app for monitoring cpu temp?
just set set cpu notification for your temp profile itll beeep if you go over 40, you could test if you can go an extra -25 it worked on my device any higher it reboots, in my case -25 extra is perfectly stable. i think also , setcpu has a widget you can place on your screen that shows temperature and cpu frequency
if you try to see if your proc can handle an extra -25 i would recomend you take the set at boot option off or you could get stuck in a reboot loop till you restore from clockwork.
For those on custom kernels such as faux/trininty i would like to just point out that battery life can be increased by about 50% in idle/calling/display by simply undervolting the lowest frequencies by almost half of their value and applying min/max to the lowest setting on that kernel for such operations such as being idle or in call.
Here is a little chart of how low i can go and probably a good starting point for those who wish to extend their battery life some. "on faux123 0.3.4"
Faux" The OC freqs are pretty optimal and probably only can go about 25-50 lower given at 1000mhz you are already limited to about 50/75mv in most cases.
1552:1350mv "default"
1408:1250mv "default"
1216:1150mv "default"
1100:1050mv "default"
1015:900mv "unstable at 850mv"
816:650mv "have not benched lower
503:425mv "have not benched lower
389:370mv "have not benched lower
Other kernels
216:350mv "unstable at 250"
1. Overall lowering everything a small amount will improve battery life but the main increase is in idle time.
2. Add +25mv after finding that bare minimum on your chip
3. ALL chips are different and this is not guaranteed for every phone but would be a good starting point for those who dont want to waste time testing each interval day after day.
4. Alternate input is appreciated and can/will be edited into thread if requested to make things easier for others such as other clock/mv settings from different kernels.
5. Own results extended idle battery life by about 40% in total "inaccurate but a fairly good estimation based on a few days test"
6. DO NOT apply at boot unless you are absolutely certain that it is stable and you have the update.zip from setcpu and are aware of how to restore default values or are able to reformat your phone in the event you apply unstable boot settings.
personally i believe the stock settings are incredibly high for the lower freqs given for those settings the phone is not doing anything so chances of errors at unstable settings are lower. for instance if you OC 2600k cpu to 5ghz on air you may be able to boot into windows and it sit there idle for days to come. The second you perform a task your os will lock up because its not stable, for the phone if it boots into that frequency and that low setting is ONLY used for IDLE then you can squeeze every little bit out of that setting since its only job is to scale back up to the next setting for usage which is not even that much as well.
Thanks for posting this, really helped me under volt my phone. I'm still making adjustments but here is what I have now.
216 --400mV
432 -- 475mV
594 -- 575mV
750 -- 675mV
1000 -- 850mV
--- --------------
un-tested with the volts above but worked previously with my other undervolts
1200 -- 1050mV
1400 -- 1225mV
1560 -- 1325mV
So far its been stable under a 30min stress test (216mhz - 1000mhz) I did so it should be fine.
Running ICS EaglesBlood With Trinity Kernel
Anything with a step of of 125mv or greater will make it run at stockage.
Anything under 750mv for Trinity kernel is stock voltage, anything under 770mv on Faux kernel is stock.
Wait stock voltage for which mHz? Because the stock voltage for 1000mhz on mine was 1150mV
Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance
What's your min frequency in setcpu?
Oh yeah, I should have posted that.
100MHz min
1000MHz max
lazy scaling
i heard that ...
force phone running in low mV MAY damage the CPU and other parts of it and destablize it...
=================================
i have seen some applications that would ignore your input value when it is not logical ...
for example like NS tools , one of them , i don't remember which exactly , perhaps it's live OC, for live OC, if you set value lower then 100 , it would automatically set back to 100 ... i think this may be same as your min frequency case...
nathanson666 said:
Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance
Click to expand...
Click to collapse
The method you are using is wrong. I did the same thing a few days ago, and changing the values like that won't work.
What I found out is that to easily find stable values, in SetCPU put your max as 200MHz and your min at 100MHz. Use ondemand. Keep 200MHz at stock volts and 100MHz try an undervolt.
Apply everything then slide the minimum frequency slider around a bit. I guarantee you 600mv will freeze. Do the same for each value, if testing 200MHz, use 400MHz as your max and 200MHz as your min, stock volts for 400MHz. Slide the minimum frequency left and right.
Sounds weird, but it works. Do this until you find a voltage for each frequency. Then put your frequency max and frequency min at the same value (IE 200MHz) and launch a game or a demanding app and play for a lil while, even if performance suck. Hope it doesn't freeze on you, but if it does, bump the voltage a bit.
If you want good starting values, here's the values I have found that work for me and are 100% stable. No force close over the last few days since I started using those:
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)
I am using:
Rom: Insertcoin
Kernel: Bricked 1.5
Could you give me some tips to setup the best way setcpu.
I've seen some guys mentioning setting lowest frequency to around 400 and etc. and I don't know why. Could you give me some advice on setting up the program correctly.
Hi, I personally set the lowest frequency to somewhere around the 500mhz and smaller and set the govenor to ondemand as this will only use the the speed of your kernel when its needed thus, will use less battery.
Why around 500mhz and not 194. And will 5 sec refresh on the widget drain much battery? It's now on passive because I don't want to loose battery on bull****.
SsBloodY said:
Why around 500mhz and not 194. And will 5 sec refresh on the widget drain much battery? It's now on passive because I don't want to loose battery on bull****.
Click to expand...
Click to collapse
I put at 500mhz because sometimes the phone may slow down on its own and I don't think that setting the refresh rate to 5sec will steal much battery because its only a small widget
Any more opinions? Would be nice
Don't set it to 500 minimum. This will lock the phone to at least 500 mhz at all times and will cause substantial battery drain.
Go with 192 minimum or the next step up.
Sdobron said:
Don't set it to 500 minimum. This will lock the phone to at least 500 mhz at all times and will cause substantial battery drain.
Go with 192 minimum or the next step up.
Click to expand...
Click to collapse
+1 on that.
My personal settings (most of the time) are:
Screen On 192/648
Screen Off 192/384
Governer OnDemand
Sometimes I up the frequency if I need to run something heavy, not all that often though.
agreed 192 minimum is much better. if you are having issues with the phone being slow then get rid of sense...
Just wanted to say thanks to the three users above this post as I tried 192mhz and it is in fact a lot better now (please realise I've only just turned 17 and play a lot of games hence 500mhz)
Coming from the HTC Desire, where SetCPU was the only to manage the CPU, I have developed a habit of using SetCPU with several frequency profiles and different governors for various situations. For instance, I use battery<80, <60, <40, <30, screen off, temp >40, >50, and a charging profile. For governors I use lulzactive2 for higher frequency ranges, interactive for mid range frequencies and on demand for the lower frequencies. Oh, this is all with the latest matr1x kernel.
Seeing how a lot of ROMs allow extensive controll of the CPU I was wondering if it wouldn't be more efficient to just set a min/max frequency, chose a governor, turn deep idle on (which is off while I'm using SetCPU) and leave it be.
What are your thoughts and experiences on the matter?
/// endmessage / COMPUTOR5000
profile ? that's completely unnecessary...
just set governor and min-max is enough.
we have NSTOOL, so looks like extended ROM controll also not necessary because not good enough compare to NSTOOL , but lots lots ROM has it build-in
I've never bothered with profiles. I can feel if the phone needs a break from the heat and performance is good for me with 100/1200 set and slight undervolting.
Battery life while idling won't change, only while using intensive apps, and with deep idle working and max freq screen off, music playback and the likes drains very little battery.
Try it and see, you need to be comfortable with it.
I agree with qtwrk. Profiles are, in most cases, detrimental. The following is especially true since Deep Idle was implemented: always let the CPU run as fast as possible to save energy. Sounds counterintuitive, but here's why: while lower CPU frequencies in general consume less energy PER TIME than higher CPU frequencies, the faster the CPU can finish it's job, the faster it can return to energy saving states. So in the end, reducing CPU frequency actually uses more energy... Just overclock to save values, use undervoltage to set lowest possible voltage values and go to sleep.
What's the minimum you can set the screen off max frequency so that music playback isn't choppy?
Also, is the phone always idle on screen off, or does music playback, or any other activity make the phone come out of idle, even if the screen is still off?
/// endmessage / COMPUTOR5000
zyrill said:
I agree with qtwrk. Profiles are, in most cases, detrimental. The following is especially true since Deep Idle was implemented: always let the CPU run as fast as possible to save energy. Sounds counterintuitive, but here's why: while lower CPU frequencies in general consume less energy PER TIME than higher CPU frequencies, the faster the CPU can finish it's job, the faster it can return to energy saving states. So in the end, reducing CPU frequency actually uses more energy... Just overclock to save values, use undervoltage to set lowest possible voltage values and go to sleep.
Click to expand...
Click to collapse
Very good point, for exemple cpu at 1000 MHz takes 1100 juices per second and 10 seconds to finish a task, total cost 10 x 1100 (11000 ) juice
If it runs at 1200 MHz takes 1200 juices per second, same task only needs 8.34 seconds, 8.34 x 1200 (10008) juices... this isn't real just number assumption and theoretically appears that way
Sent from my Nexus S using xda premium
I agree with everything that was said here and actually posted about this very topic earlier on in the matr1x thread in regards to the lulzactive settings. People putting settings too much towards battery saving are actually not getting battery savings. They are making the CPU run longer and therefore more cycles and more power. Profiles are a bad idea too. They cause problems.
I decided to ask hear instead of creating new thread, etc.
In the amazing post of droidphile http://forum.xda-developers.com/showthread.php?t=1369817 there's an information about SGS II, that
'energetically efficient' frequency for CPU is 200 mhz
Click to expand...
Click to collapse
(it's Cortex-A9).
And what about Cortex-A8 on Nexus S?
droidphile also says that on Milestone (Cortex-A8) 550Mhz is the frequency used in the calculations based on the optimal energy to run. Don't know what's the source of this info...