I don't quite understand what I'd need this particular profile for. If its charging and full, usually my screen is going to be off, so wouldnt the screen off profile have a higher priority, therefore it'd use that profile?
or should the charging/full profile be higher than the screen off?
mine is set as follows, i just set it today, so i havent been able to really see how it helps my battery yet.
Main: 1152max, 245min, ondemand, set on boot
Temp > 39.1c: 576max, 245min, ondemand, priority 100
Batt < 10%: 245max, 245min, powersave, priority 97
Screen off: 384max, 245min, ondemand, priority 96
Batt < 17%: 460max, 245min, ondemand, priority 95
Batt < 27%: 768max, 245min, ondemand, priority 89
Batt < 37%: 883max, 245min, ondemand, priority 79
Batt < 45%: 998max, 245min, ondemand, priority 69
I think it's fine like that, but if a Charging/Full (or charging/ac) profile would work in there somewhere, what priority and max/min should it be?
thanks in advance.
Temp > 39.1c: 576max, 245min, ondemand, priority 90
Batt < 10%: 245max, 245min, powersave, priority 80
Screen off: 384max, 245min, ondemand, priority 100
Batt < 17%: 460max, 245min, ondemand, priority 40
Batt < 27%: 768max, 245min, ondemand, priority 50
Batt < 37%: 883max, 245min, ondemand, priority 60
Charging/full: 1152 max, 245min, whatever you want, priority 70
Now they are all out of order thats how your set cpu profiles should basically be
The reason that you want a charging profile is so your phone can be super quick on a charger so you can always do whatever you want. Also screen off should be at the top because even if your phone over heats the screen off is a lower frequency so that will cool it even quicker. And i dont feel like explaining everything else
Batt < 45%: 998max, 245min, ondemand, priority 69
I kinda disagree on the screen off being at the top. I think temp should be at the top. If it overheats, weather the screen is on or off, it'll still knock the cpu down to my temperature profile right?
ufvj217 said:
I kinda disagree on the screen off being at the top. I think temp should be at the top. If it overheats, weather the screen is on or off, it'll still knock the cpu down to my temperature profile right?
Click to expand...
Click to collapse
Since your temp profile is set to 576 and screen off is set to 384, it makes sense to have screen off set at a higher priority. This way, say your phone overheats while you're using it, it goes to 576. If you turn the screen off, since it's higher priority, it will clock even lower to 384 and cool off faster.
If you keep the temp profile the highest priority at the speeds you currently have set, if the phone gets too hot, it will again go to 576 if the screen is on. But, when you turn the screen off it's going to stay at 576 instead of clocking down further to 384 since the faster clock speed you set the temp profile set to is taking priority.
Personally, I assume if my phone is getting that hot, it's sitting in the sun or I left it in my car on a hot day, etc. In attempt to prevent the most damage as possible, I set the temp to highest priority at 245 max, right above screen off at 384. But that's just me!
Sent from my Droid Incredible
Thanks for explaining man
XideXL said:
Since your temp profile is set to 576 and screen off is set to 384, it makes sense to have screen off set at a higher priority. This way, say your phone overheats while you're using it, it goes to 576. If you turn the screen off, since it's higher priority, it will clock even lower to 384 and cool off faster.
If you keep the temp profile the highest priority at the speeds you currently have set, if the phone gets too hot, it will again go to 576 if the screen is on. But, when you turn the screen off it's going to stay at 576 instead of clocking down further to 384 since the faster clock speed you set the temp profile set to is taking priority.
Personally, I assume if my phone is getting that hot, it's sitting in the sun or I left it in my car on a hot day, etc. In attempt to prevent the most damage as possible, I set the temp to highest priority at 245 max, right above screen off at 384. But that's just me!
Sent from my Droid Incredible
Click to expand...
Click to collapse
That makes sense.
I'm going to change around some of the profiles now.
edit
i changed it around a tad, to this-
Main: 1152max, 245min, ondemand, set on boot
Temp > 39.1c: 245max, 245min, powersave, priority 100
Charging USB/Full: 1152max, 245min, ondemand, priority 99
Charging AC/Full: 998max, 245min, ondemand, priority 98
Batt < 10%: 245max, 245min, powersave, priority 97
Screen off: 384max, 245min, ondemand, priority 96
Batt < 17%: 652max, 245min, ondemand, priority 95
Batt < 27%: 806max, 245min, ondemand, priority 89
Batt < 37%: 883max, 245min, ondemand, priority 79
Batt < 45%: 998max, 245min, ondemand, priority 69
reason i left screen off at 96 is because i changed the temp to 245 max, and so reguardless of the screen or battery percentage, itll be at 100 so itll go to 245 if it overheats.
charging usb i put to 1152 max becuase i usually charge it at work at my desk via usb, and i use it while charging as well, so i want it to be able to run to 1152 if needed.
charging ac i left at stock 998 becuase i only usually charge via ac while im asleep, so i dont use it, but my alarm needs to go off so i dont want to take a chance and set it real low and cause an issue.
hows the priority settings look now? lol.
Looks good to me just maybe play around with those battery < profiles they seem a little low to me. When i used to set my phone really low like that it was almost unusable
Gahh Its Lee said:
Looks good to me just maybe play around with those battery < profiles they seem a little low to me. When i used to set my phone really low like that it was almost unusable
Click to expand...
Click to collapse
i did, and still am as each day goes by and the battery gets low so i can see how it works. with those settings, when i got to like 27% it was going incredibly slow and alot of things would make me FC or "wait" i guess becuase i clicked it too many times wanting it to open. i just disabled the last 4 battery < profiles, might even disable the 10% profile, and see how it works out with just the screen off, temp, and charging profiles.
Related
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
So I've noticed since I installed SetCPU now that it supports Tegra 2 devices that buttons when I'm in-call lag. I'm running EB 1.05 FR with stock kernel which I believe is faux's. Anyway's I have setcpu set to run at max 1500 and min of 400. I have 2 profiles set up one is to run 1500 max and 1500 min when charging AC and the other profile is set 400 max and 400 min when screen is off. I've noticed though that when I'm in a call and I take the phone away from my face and the screen turns back on and I go to hit speakerphone or end call it lags really bad and takes a few seconds to register the press. Anyone else experience this since using SetCPU? Thanks in advance!
Nope. Running cm7 and faux older kernel. No overclock on mine but do have profile for in call at 500. Also running it on a powersave governor
ITS ALL WONKY!!!
pettigrew95 said:
. Anyway's I have setcpu set to run at max 1500 and min of 400. I have 2 profiles set up one is to run 1500 max and 1500 min when charging AC and the other profile is set 400 max and 400 min when screen is off.
Click to expand...
Click to collapse
Quick question. What is the benefit of locking the cpu at 1500 when charging?
I allow a range for the phone. On my screen off profile I have a min of 216 and max of 312 and my lock screen issues went away. I have been experimenting with different ranges and priorities for an in-call profile but have not found the sweet spot that completely eliminates the call screen lag.
Would love to know the settings others are using including priority.
For example, should I make my in-call profile a priority of 100 and the screen off profile a 90 so it does not interfere with the in-call profile?
I have at max: 1200 MHz ,at min 83 and in typeerformance, are these values corecct or wrong for a custom rom?
-Greeting-
PD:Andro's Rom (3 days for release)
Yes, or no, because you need a screen off profile or your battery life will be damn short.
I think this should be in the general section and i recommend using the conservative governor over the performance since conservative goes to the minimum frequency when phone is not being used i.e. when screen is off. This is best for performance since it automatically goes to the maximum frequency when screen is on and when screen is off it goes to the minimum which is good for battery.
1200 is too high....
It will damage your battery....
I use 100 MHz to 800 MHz....
Its average and most of the users use the same....
[email protected] said:
1200 is too high....
It will damage your battery....
I use 100 MHz to 800 MHz....
Its average and most of the users use the same....
Click to expand...
Click to collapse
I think that is a very wise thing to do. I shall see how my phone runs at that speed.
Oks.thx.
Now:
MAX:800
MIN:83
Type: Conservative.
Are these values correctly now?
-Greettings-
AndroKite said:
Oks.thx.
Now:
MAX:800
MIN:83
Type: Conservative.
Are these values correctly now?
-Greettings-
Click to expand...
Click to collapse
Yeah its good.... ^_^
Happy to help..... ^_^
My batery temp is 27º - 28º celcius,is a good temp or maybe it can be danger for my battery?
-Grettings-
AndroKite said:
My batery temp is 27º - 28º celcius,is a good temp or maybe it can be danger for my battery?
-Grettings-
Click to expand...
Click to collapse
Aslong as its not 35+ degrees you are ok
Sent from my GT-I5800 using XDA App
Lol! Did you make a mistake by posting this question in the development section? Suppose to put at general section.
Accidentally sent from my ultra speedy SG3 phone using tapatalk.
P.S If my post have helped you, don't feel shy to click the thanks button
That frecuency will eat your battery.
I use my SetCPU at frecuencies 400-800Mhz, and use profiles for screen off (83-400Mhz), battery <20% (200-600Mhz), time (2am-6am) (83-83Mhz powersave)
always on demand (except time profile)
Greetings
My config is
Main 400-800 Mhz Ondemand Set on boot
Profiles
Temp >45°C 200-500 Mhz priority 100 Ondemand
time 2am-6am 83-83 Mhz priority 95 powesave
screen off 83-500 Mhz priority 90 Ondemand
Battery <20% 200-600 Mhz priority 80 Ondemand
I have g3mod 2.0 OC kernel
Greetings
I just use basic settings, no profiles or anything. Look in my signature.
I may add a few profiles after my lil bro is finished playing games on my phone.
My battery temp is 39 degrees Celsius is it that a good tempeture?
anything between 83 and 800 would work like charm and enough for day to day tasks..use conservative governor..set profile for screen off and on call..
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...