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.

Post your SetCPU Profiles

748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand

Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority

Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse

Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.

@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality

I've never lagged at 160mhz =p but that could just be my phones/ roms.

Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.

What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App

How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo

sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.

Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90

[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

how much does the governerr really effect the battary?

im just wondering how much does the governerr effect battary life? i changed from ondemand to smartass2 and im not sure i see any diffrent...
and im scheduales which one is best for multitasking and which is for when playing games?
and should i change the governerr setting?
i also read that sleep_ideal_frequency should be 200 and not 100 beacuse 100 wastes more or something like that, is that true?
using galaxy i9000 semaphore kernal jb

bump

I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.

Lavoslav said:
I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.
Click to expand...
Click to collapse
This is so wrong its a pain to read.:banghead: Why do we have the max and min frequency options in the semaphore app? Why do we have "Max Performance" and "Max Battery" power settings on laptops?
Sent from my GT-I9000

There was a thread some while ago that concluded in OnDemand and Performance being to two to give longest battery life and best performance.
I don't have specifics or even a link, but the thread was about schedulers and governors and which went together for best performance and battery life. I'm sure it's google'able
Sent from my GT-I9000 using xda premium

i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?

itzikd1 said:
i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?
Click to expand...
Click to collapse
maybe you can try and tell us

There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color

BlueFlame4 said:
There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color
Click to expand...
Click to collapse
I do use internet mostly so what will be the most effective governerr any idea?

itzikd1 said:
I do use internet mostly so what will be the most effective governerr any idea?
Click to expand...
Click to collapse
Try OnDemand or SmartAssV2.

Crazy overheating problems with Stock Kernel and even more with Stellar Kernel. Help?

Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.

You probably have a hardware problem

rhp07 said:
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
Click to expand...
Click to collapse
acquire kernels and other que rooms have different governors Study on them and the Best That was enough pro you and your needs .
I think this will help you , give will take this need to manually change the clock all, the governor will operate according to its governor preferably .
Read
http://androidforums.com/threads/android-cpu-governors-explained.513426/
:good::good::good::good::good::good:
Thanks if helped :highfive: