Related
Surely it makes little difference on a processor with dynamic clk freq scaling?
Assuming its always clocking at its slowest during idle, which your phone is by default, then reducing the max clock speed during activity just extends the time its chugging away at max speed.
Only way to improve battery life is to reduce the amount of work you ask of your phone, not the speed at which it gets on with it.
For example, if my Desire has to process an image, it can either do that in 1ms at 1GHz, or 2ms at 500MHz, using the same amount of battery, no? At all other times its idling at the same 250MHz.
So the way forward is to reduce tasks, not underclock? And if anything the profile conditions in SetCpu are just one more thread.
Anyone actually noticed better battery performance from SetCpu?
I noticed bader Battery Life! So i dont use it anymore!
I don't think it will give you more battery life to reduce the cpu speed. more important i think is to watch the tasks that run on the background. some apps can drain you battery really fast. i just use advanced task killer and set it to kill apps when i turn my screen off, for me it helps more then lower the cpu speed.
Those apps drain battery by not letting the cpu idle, hence lowering max speed could improve battery life.
Sent from my HTC Magic using XDA App
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
Actually we could use some hard evidence regarding this. Theories are theories, but actual experience is golden. Maybe you could try some various processor settings are report back?
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Cyanidex00 said:
Well, before I posted this I was using 245/886 underclocked with 245/245 screen off profile. At the end of the day I had an average about 75-80% percent battery life with pretty moderate to heavy usage.
I'm current using 245/1574 overclocked and will report back, with same screen off profile.
And yes, I did wipe battery stats before I started this.
Click to expand...
Click to collapse
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
I personally haven't tried any music or apps running while screen is off, I'll give it a whirl when I get home from work.
I know this obviously will vary from phone to phone, and how the user uses the phone. I'm pretty moderate to heavy usage daily. Hopefully maybe we can compile some data on what works for people.
I have my screen off profile set at 245 and have no problem streaming music from my SD card with the screen off. When streaming from the cloud, I sometimes get a very long pause between songs that isn't there with the screen on. I will try raising my screen off speed to see if that changes anything.
Sent from my Desire HD using XDA Premium App
henrybravo said:
Cool, thanks for that info. Are you finding that forcing a 245 mhz screen off speed is impacting any apps running while your screen is off (e.g. music playing apps)? A couple of weeks ago I tried forcing the screen off at 122 mhz to see if that would help battery life, but I had big problems with music apps stuttering. I didn't play around with the speeds to see if raising the forced minimum to 245 would have fixed the problem. Some kernels advertise as a feature "Max speed - screen off 576MHz" or some other speed, but I don't know if it needs to be that high or not, for app stability.
Click to expand...
Click to collapse
I noticed this yesterday. My screen off is also 245. My music stuttered, but only once (and it was fairly brief).
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
biglittlegato said:
I raised the screen off speed to 368 and have not had any sputtering or long pauses between songs, even when streaming from the cloud.
Sent from my Inspire 4G using the power of the dark side.
Click to expand...
Click to collapse
Good to know, thanks!
Cyanidex00 said:
As the thread states, I obviously have a question about SetCPU and processor settings.
Is it better to have the processor underclocked and almost always using 100% to use programs, or it better off to overclock and have more processing power without using 100% or close to that mark.
And what would be more beneficial for battery life.
Edit: And if mods could move this to Q&A. Clicked the wrong forum.
Thanks,
Cyanide
Click to expand...
Click to collapse
I use SetCPU at 460/1152 brazilianwax, screen off 122/537 conservative and have good battery life and no issues when playing music w/ screenoff....
Overclocking is almost guaranteed to worsen battery life compared to say if it was at stock 1 ghz or a little less.
With a governor like on demand, its gonna scale from the lowest to to highest allowed as soon as it gets some load on it, eg from 245mhz to whatever Max is (1017, 1075, or 1920 etc), without stopping in between.
Even conservative with fast scaling will probably scale close to Max clock speed pretty quickly under load, so theoretically this should be a /little/ better for battery than on demand, but will not seem as fast and could possibly make the phone seem more laggy. Smartass is very similiar to conservative as it scales depending on a preset % of CPU load. If its set to 70%, when CPU reaches 70% load, it scales to next frequency, when that frequently hits 70% load, its scales again. The version of the on demand governor most of us have in out kernels is the fastest scaling option, which goes from min CPU - straight to max
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...
Hello all
My Galaxy Note runs hot.
Can someone tell me, preferably in methodical order, the steps that should be followed to sort out overheating issues.
If you watch the Australian Open tennis then you will see how hot it gets here in summer at the moment!
1. Root
2. Install SetCPU
3. Set some temperature profiles so when your Note reaches a certain temperature the clock speed is automatically dropped
4. Close unused apps and stuff
5. Don't use 100% brightness
If I was you, I would use, in fact, lowest brightness when indoors, and underclock the CPU (even when it's not hot, as opposed to what vantt1 says).
I underclocked my Sensation from 1'5 Ghz to 1'0 Ghz (both cores). And boy, It's running smooth with ICS, no lag at all.
In fact, my settings are:
Min clock: 192 Mhz
Max clock 1005 Mhz (or something around that)
Governor: Ondemand
But your CPU is probably different than mine... Keep in mind that I underclocked around 30% of it's total capacity. You might want to do the same.
Also, direct sunlight causes overheating. (Might be obvious, but when the sun hits our skin, the body starts several cooling methods, so that you only start to notice the overheating around 30 minutes of direct exposure... And 30 mins of direct sunlight for a phone is a total kill, so also one more tip for when you're on the beach: cover it with clothes, or something. It will also decrease posibilities of thieves )
My Galaxy S2 doesn't really overheat when clocked at 1.4 GHz ondemand. It's the maximum safe clock for the Exynos 4210 found in the S2 and Note. The speed is there when I need it (but that's only 2% of the time) and when I don't, it's around 200-800 MHz. I have a solid aluminium case on it, so when left on the table it can go down to 25°C. In my pocket it's a bit higher at 34°C but it's acceptable. When I play GTA3 though, it can go up to 56°.
Sent from my GT-I9100 using XDA App
force reboot of phone isn't always overheat. the kernel also depends on how high you can overclock.
i aleary set cpu to max 1.8ghz and min 1.6ghz how to st it?? i did try to set it too 1.8mina nd max but my phone hangs and powerd-off!!! how to set it?!
Hey. I wouldnt recommend your current srtup at all unless you want horrible battery life and massive amounts of heat however i sont have an answer for your predicament, try using another app with the same function?
Sent from my GT-I9100 using XDA
listen to me. set it like I say:
max frequency 1512
min frequency 384
governor interactive
go to profiles and create a new profile. set:
screen off
max 432
min 192
governor conservative
priority 100
this way you have a good performing phone and with screen off a power saving profile. with this configuration I have 15 hours battery (enough for a day) of mid use...with data activated and live wallpaper
Nice stats ! I'm going to try that!
Sent from my Sensation 4G using xda premium
Some phones can handle higher frequency then others if your phone can't go over 1.8 well there is nothing you can do..
Swyped From My Sensation.
I SET IT TO this But anyway i don't care battery life
Dont OC much
dude that's friggin gih frequency's. Dont push it too hard, it'll do no good to the processor. Besides, what do you need that kind of power for ? Runing Crysis ?