Database Develop

[request, forum] setcpu configuration

Hello, anyone know how to configure setcpu to save the battery while maintaining a smooth flow of the phone?
I saw that we could create "rules": those who did, can you post your configuration.
Thank you

Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!

see this and I think should be added here. http://www.pokedev.com/setcpu/

Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
With this configuration, you save the battery?

If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?

Formel-LMS said:
If yu wanna have the longest battery time, just use all 245/245 Mhz.
But this makes no sense.
I think you wanna have it between battery/speed, isn't it?
Click to expand...
Click to collapse
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx

tcastel said:
obviously! I want my battery will hold at least two days! I will try your setup throughout the weekend and I'll make a return Monday.
thx
Click to expand...
Click to collapse
Don't hold your breath. Im being serious here. It wont last unless it sits in standby most of the time and then you're still pushing it.
Spend the 25$ extra and get a second battery.

2 DAYS?! Let me know if you are able to accomplish that somehow! I've tried everything; ROMS, Kernels, Juice Defender, SetCPU, anything you can think of and about the best I can get is 15-16 hours with moderate to heavy usage. I think I am actually going to buy a spare battery today.

.. that's not hard to do, 2days... even more.
Just stop all apps to update, stop auto sync, stop background sync...
you will be surprised*

I knocked down my cpu to 500 or so in all conditions, phone still feels responsive.
If you want two days, turn off 3g, turn off sync, turn off brightness. You'll not only get great battery life but a $600 dumbphone to boot!

this is what you need to do...
sleep/standby 245min 245 max cpu governer: powersave
charging 245min 883 max cpu governer: on demand
'normal': 460min 998max cpu governer: conservative
if u find that with normal use the phone isnt as snappy as it used to be, and this bothers u, then change the cpu governer back to on demand for the normal profile.
i've had amazing battery life since i tried these settings.
Also....some apps prevent the phone from sleeping so keep an eye out if ur battery is just literally disappearing!

Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.

djmcnz said:
Setting the max too low on any profile is not a good idea. This can cause tasks to take too long to complete and queues and memory to fill. This can make your phone unstable and arguably increase battery usage due to increased management overheads.
Some overhead above minimum is always preferable. I would consider anything less than 245/576 quite extreme and normally undesirable.
Click to expand...
Click to collapse
yeah i heard about this but i have never encountered any problems. obviously its different for everyone but i would say try 245/245...if your getting too much drain with the phone on standby then use 245/576 with on demand governor.

Formel-LMS said:
Yes, i've good settings!
Profile: Auto-detect
Max 998400
Min 245000
CPU Governor On demand
Set on boot checked
Profiles on
Sleep/standby enabled
Max 245
Min 245
Battery profiles
Power <30%
768 Max
245 Min
These are same settings as teknologist have. This is the man who did the kernel for MCR ROMs. In my eyes he is a god in this things. So I belive him full!
Click to expand...
Click to collapse
I do not see much difference!!

tcastel said:
I do not see much difference!!
Click to expand...
Click to collapse
To be honest everyone "thinks" you can see a night and say difference just by tweaking the clock's and installing more efficient kernels. You can't and wont.
Those things may save you 5-10% over the course of a day but don't expect miracles. If you look at your battery history information you'll see that the system and any CPU related item can become relatively low doing all the efficiency modifications yet the battery still poops too soon.
Now look at the display. Thats where it's all going and as far as I know there is nothing anyone can do about that on our side. I run with the display back lighting 100% OFF and it still shows at a HUGE portion of my energy use. ~50% and sometimes more.
The day we get more efficient screen technology is the day we will be able to possibly use these things for 2 days on one charge... Either that or more powerful battery technology.

You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?

ma1993 said:
You know guys, I only have 3 scales on the application. Userspace, ondemand, and performance. I also have no idea what Priority means and how high or low to put them for a good profile! What do I do?
Click to expand...
Click to collapse
Set a default scaling type that suits you, typically On Demand or Uberspace and then set up your profiles. All of your profiles can use the same scaling (mine do).
The set your profile priorities in the order you want them to apply, 100 is the highest priority. For example, you might want the phone to run with less overclock when the battery is low and you want this condition to apply all of the time then you would give it a higher priority than other rules so it always executes. A better example might be a temperature profile. If the phone is hot you want to clock it down and want this to NEVER be overridden by another profile then you would set this to very high (say 99) so it could NOT be substituted by another rule.

SetCPU usage/benefits?

I was thinking about installing SetCPU but I have heard stories of it not working very well on the Captivate. Does anyone use this, and if so what kind of battery life improvement are you seeing? Post config settings too please!

Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave

kenjindomini said:
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
Click to expand...
Click to collapse
Thanks for these, I was looking for a some decent settings. Mine were close to that to start, but I had no idea what I was doing, haha

I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.

CPU throttles itself. Any effects of setCPU is placebo effect

Err if you set the clocks yourself, you can produce a difference depending on what it's catered towards. I'm sure if I set the max clock to 200 (assuming the app works) for all situations there will be a difference.

Does the stock ROM have a perflock like the EVO that we need to disable?
Also, does the stock ROM automatically underclock at times, or???

I've now verified after clearing user data, the stock firmware already sets the conservative governor and allows it the full range of frequencies supported by the CPU. Only benefit from SetCPU should be profiles - reduce max clock when hot or low battery, that sort of thing.
Sent from my Samsung Captivate

I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already

Default Profile: 800 MHz
Profiles:
Temp > 46 C -- 400 Max 100 Min Conservative
Battery < 40 -- 400 Max 100 Min Conservative
Screen Off -- 400 Max 100 Min Conservative
This now gives my phone life of about 2 days with moderate use (1 hour calls, 1 hour browsing and another 30-45 mins of using apps that need screen on like games, etc)

brandonb81 said:
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Click to expand...
Click to collapse
One thing u got to keep in mind, CPU scales up when woken from low speeds (like when u set for 200 n this takes a second or two). After some R&D i realized 400 MHz when sleeping is optimal with hardly noticeable lag.

Unhelpful said:
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
Click to expand...
Click to collapse
well, i have tried playing heavy games like asphalt 5, dungeon hunter, assasin's creed... these all games seemed to work with no lag even at 400 MHz when my battery was less than 40. Most apps I have or used or saw were very comfortable even at 400 MHz. But with multiple apps open, sometimes there was lag, so i set the max at 800 MHz, instead of 1 GHz.
Also, I set my connection to EDGE from 3G. This helped reduce phone from getting heated up with long calls.

I tried using this app myself but uninstalled it after a week. While I'm sure there was some underlying cause, it made my phone never wake up from sleep mode when it turned off.
Honestly thou, I know several android phone owners with s lot of phones That didn't see any real change in their battery life as s result. And based on my experiences, I'd say stay away from it.
Just my 2 cents thou
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] dynamic overclocking

.
..

I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk

Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?

..

MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk

..

MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk

[Q] CPU speed and phone temperature

My specific issue involves SetCPU but I'm wondering about the larger scheme of how things work.
My phone gets hot in the car dock when running GPS, Navigation, and Bluetooth (I don't turn it on but I think my dock does it automatically). The general consensus is to underclock slightly when charging because charging generates heat, and I have a SetCPU profile to do that. Then comes the issue of heat generated from GPS and Bluetooth, and possibly processor load when running apps while docked, so I have two profiles for that: one to underclock a few steps down from the charging CPU speed when the temperature of the phone is at 40* C, another to clock down one more step when the temp hits 42* C, which I feel is at the point the phone gets a little too warm for use.
I've noticed that my phone doesn't necessarily stay cooler and in fact, sometimes it gets hotter than before I started using SetCPU. Over the past few days I've seen temps of near 45* C (113* F), toasty enough that I have to let my phone cool down before I can use it again.
So, my question is if underclocking too much is bad. For example, if I'm underclocking too much, does that strain the processor while it is trying to run apps and hardware? Is it better to let the system handle processor speed? I see this in driving a manual/standard transmission car - if I attack a hill in a high gear, I can eventually reach the top but with increased load on my engine. Maybe the processor speed works opposite - too low and it strains too much?
I used to be concerned about clock speed vs. battery life but now that I'm docking in my car more and noticing the heat, I'm more concerned about the heat. I'm currently using redstar's kernel but get the same results with that or the CM kernel that comes with the nightlies.
If it helps to troubleshoot, or if you want to critique me, here's my profile list.
Normal: 245 min, 998 max (default settings)
Priority 100 - temp > 42*C: 460 max, 245 min
P 90 - temp > 40*C: 499 max, 245 min
P 80 - screen off: 384 max, 245 min
P 70 - charging AC: 576 max, 245 min
(SetCPU related question, sorry if this is too far off forum topic) Are there better profile settings I could be using?
Also, I don't quite understand undervolting in terms of kernels. What effect does that have, if any?

High CPU States - Battery Impact

Have been monitoring for battery life, and tweaking settings, and testing different governors to find which keeps the device at the lowest state. I have noticed recently no matter what governor I select I am using higher lvl CPU states. Out of 4 hours on, I have:
300MHZ - 1h54m
1.19GHz - 1h
1.5GHZ - 26m
1.73GHZ - 36m
2.27GHZ - 13m
Also just monitoring the touch screen boost (by leaving a cpu monitoring program open and touching the screen), it automatically boosts to 1728MHZ on screen touch. Can anyone confirm that this is what they are seeing as well, and give me any of your numbers for CPU states. I know we don't have custom kernels like on my S3 and we can't customize the touch screen boost, just wondering what everyone else is getting. Also these CPU states are from just texting, web, and a couple of other basic apps. No Gaming.

jokesonme said:
Have been monitoring for battery life, and tweaking settings, and testing different governors to find which keeps the device at the lowest state. I have noticed recently no matter what governor I select I am using higher lvl CPU states. Out of 4 hours on, I have:
300MHZ - 1h54m
1.19GHz - 1h
1.5GHZ - 26m
1.73GHZ - 36m
2.27GHZ - 13m
Also just monitoring the touch screen boost (by leaving a cpu monitoring program open and touching the screen), it automatically boosts to 1728MHZ on screen touch. Can anyone confirm that this is what they are seeing as well, and give me any of your numbers for CPU states. I know we don't have custom kernels like on my S3 and we can't customize the touch screen boost, just wondering what everyone else is getting. Also these CPU states are from just texting, web, and a couple of other basic apps. No Gaming.
Click to expand...
Click to collapse
thats actually not bad at all and as for the spike when touching the screen idk if id want to change that, it does a lot of calulations when the screen is touched so if you downclock that it might make a lag effects