Are profiles necessary to preserve battery life? If sohow should my profiles be set?
Sent from my HTC Vision using XDA App
I get much better battery life without using any profiles... screen off profiles make the phone lag. I'm squeezing a good 18 hours out of my phone, and I am a HEAVY texter. No profiles - ondemand governor - stock clock settings at 806MHz
Running 1.5 ghz
im running 1.5ghz
I've found battery to be better without profiles. Just make sure you have setcpu set to on demand. I'm running CM 6.1.1, 1209/346 on demand for set cpu. I'm getting about 18 hours with moderate to heavy use of music and data.
Would agree that screen off profiles aren't that great (and really aren't that necessary). I've had issues with answering calls or the phone being laggy when the phone wakes.
Sent from my HTC Vision using XDA App
It's kind of controversial. Depends on the governor, scheduler, etc. You either trust the system to be smart enough to wind itself down with the screen off, or you don't.
I think you'll find that even when you overclock, your CPU shouldn't spend THAT much time at the higher frequencies...
I'm running 1.5mhz and use a screen off profile on 386mhz.
Get much better battery out of it when using this!!!
Without the profile, i have 9 hours of batterylife. Now i'm having around 14 hours...
Just try it and see what's best for you
Sh0rty007 said:
I'm running 1.5mhz and use a screen off profile on 386mhz.
Get much better battery out of it when using this!!!
Without the profile, i have 9 hours of batterylife. Now i'm having around 14 hours...
Just try it and see what's best for you
Click to expand...
Click to collapse
What gov. are you using? I know some need profiles but ones like the interactive governor don't and actually perform worse with profiles. I'd always set a temp profile though - you don't want to go iPhone on something and set it on fire.
Im running the CyanogenMod 6.1.1 ROM with Pershoot 1.516GHZ kernel on my G2. I have my setcpu profiles setup as below (recommended by another G2 user from another forum):
screen off-
Max: 368
min: 245
priority: 100
Temp>39.7c
max: 768
min: 245
priority: 88
Battery<10%
max: 245
min: 245
priority: 70
Battery <15%
max: 368
min: 245
priority: 66
Battery< 25%
max: 768
Min: 245
priority: 60
charging/full
max: 1516
min: 245
priority: 50
charging ac/full
max: 1516
min: 245
priority: 50
charging usb/full
max: 1516
min: 245
priority: 50
Anyone notice any possible issues with these profiles?
KCRic said:
What gov. are you using? I know some need profiles but ones like the interactive governor don't and actually perform worse with profiles. I'd always set a temp profile though - you don't want to go iPhone on something and set it on fire.
Click to expand...
Click to collapse
I'm on cm6.1.1 now...
sent from my htc desire z using tapatalk.
Related
I see that several ROMs now have settings for "CPUfrec interactive, powersave, ondemand".
What do these do?
I am aware of SetCPU that was used to save battery, but how does this fit in with the above?
Do I need to use SetCPU on these ROMS, or is it automatic? Is it better with these new settings? What about Perflock?
An explanation of what all this is about would be useful.
Cheers.
Interactive is the one to toggle if you want performances with acceptable battery time. Ondemand is a little less reactive but saves more battery witout harming performances too much. Use powersave instead if you only care about battery time. That's it (i guess).
Sent from my HTC Desire using XDA App
Cheers, that explains it.
vnvman said:
Use powersave instead if you only care about battery time.
Click to expand...
Click to collapse
Keep in mind that Powersave keeps the phone running at 245 MHz. That is the very reason battery time becomes longer.
For me this is too low - the machine becomes too slow - and I did not buy a 1 GHz phone to only have it running at 245 MHz all the time.
Just play with the settings and see what works best for you.
An example of decent settings by people who know what there doing would be good.
Mine is set at screen off, 245min 245 max powersave.
Main profile is 998 max 245 min, interactive, with set on boot ticked.
Temp selected to 38 degrees, 245/245 powersave.
If battery becomes more or less important, what to change to in terms of govnor but also up threshold on advanced settings.
Thanks
Hi,
I've just noticed the Performance settings menu under the CyanogenMod Settings menu and I wanted to give overclock and other features a try...safely.
I'm looking for increasing my Wildfire's performance in a remarkable way but without harming or causing any trouble to the phone. So I'd like to start in a quite conservative way.
What governor should I choose? (default: smartass)
What max and min CPU frequency? (default 518 and 352 Mhz)
What about the VM heap size? (default 24m)
What do you guys use as your settings?
Thanks a lot!
Governor : Smartass
CPU Speeds : 264 Min, 652 Max
VM Heap Size : 32 M
Remember, don't expect miracles by OC'ing your CPU. You'll probably be disappointed.
Thanks for answering!
In the meanwhile I set up 264 as min and 691 as max...is that too much and potentially dangerous?
No miracles indeed but the phone felt a bit more snappy when playing games for example.
Do you know where I can find some info about the different governors?
Also, what is exactly the VM heap size?
Thank you!
No, wont harm it. Only if you experience instability, reduce it to the next (Or rather, Previous) level.
CPU Governors:
* ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
* conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
* performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
* powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
* userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
(The above wall of text is lifted from SetCPU's site)
In addition to that , Smartass is really the smart one. When your screen is on, the minimum frequency will automatically be set to 518 MHz, making your phone seem it is flying, and, when the screen is off, then, it reverts back to the minimum set value, and saves battery - Best of both worlds!
As for VM Heap Size, it is the maximum amount of heap space (i.e. memory) a single instance of the Dalvik VM (application) can obtain. Technical concept, but, you can read it up more if you like.
Thanks a lot for the insigthful reply, everything's clearer now!
i put everything on max. but thats just me. phone works fine though :L
Hi,
What's the best setting for my battery? It drains so fast.
Mine is as following:
Min.: 245 Mhz
Max.: 537 Mhz
INTERACTIVE
I have to charge the Phone every evening, thats a bit annoying.
Thank you in advance
When using the cyanogenmod settings for the cpu speed,setcpu isn't required anymore right?
Sent from my HTC Wildfire using XDA App
FrydaeXIII said:
When using the cyanogenmod settings for the cpu speed,setcpu isn't required anymore right?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Yes, you are right. Conflicting apps are never recommended.
thanks for the tip...
I bet there are some of you use either the setCPU or CPU tuner on your play..
I heard it will help save some valuable juice...
I tried setCPU/CPU tuner and i think the default setting have reduce the performance when batt go before 50% or temp over certain temperature, I get annoy when i trying to fight on a 3d game...
so I really hope any expert here can advise which is the best setCPu you have used on play, for a reference for me...
beside setCPU, i like CPU tuner for the ability to toggle 3g/2g when batt is low.. so if anyone using CPU tuner instead, please share your setting for your PLAY...
heres the profiles i have on mine, in order (setcpu)gives me tripple the battery life.
ScreenOff - max 368640, min 122880
Charging - max 1024000, min 122880
Battery <10% max 368640, min 122880
Battery <35% max 768000, min 122880
scaling is OnDemand for all of them!
looks simple... but just wonder, when it move to 368... on screen off, will it automatically switch back to 1024... when we turn on the screen?
yeah. unless its below 35% or 10%
been trying out for 1 day, havnt see much improvement, but does see the batt last longer in 20% below...
i think I will try to mimic this setting to CPU tuner, which can turn off 3G somemore on extreme batt save setting, it might help more tho..
Any new tests given to improve battery life? My xperia play is rooted and am hoping that someone out there has found the best settings\profiles to use.
Please post it here. Many thanks
Anyone else use this or a similar program, if so do you get good results ?.
mug2k said:
Anyone else use this or a similar program, if so do you get good results ?.
Click to expand...
Click to collapse
I noticed an improved battery usage after using 245 max/122 min (Powersave scaling) on Screen Off and then 1024 max/122 min (Ondemand scaling) as normal.
That combined with stopping all unnecessary services seems to work great so far (although I'm still looking for alternatives to improve things).
lagfree governor on main, min 122Mhz and 1.6Ghz on max
powersave governor, 122mhz min and max, screen off profile
performance governor, 600mhz max, 122 mhz min, on call profile
all priorities set on 100, using SETCPU
Except when gaming, I have it set to 768 conservative governor, stock ROM.
Also, I have screen off set to 245 max 122 min with powersave governor.
Edit/update: for some weird reason my battery life actually decreased when using setcpu, no matter how it was set. I've now disabled it, and the battery life went back to how it was before. Weird.
Sent from Silent Earth 3
What are your best-working values on SetCPU?
Let's gather some information and create a "golden standard"
These are the values that work for me, but my average battery life is 1,5 days:
Main
Max: 710
Min: 352
OnDemand
Profiles:
Screen Off
Max: 352
Min: 245
Priority: 95
OnDemand
Battery<30%
Max: 352
Min: 245
Priority: 50
OnDemand
temp>40oC
Max: 352
Min: 245
Priority: 50
OnDemand
---------------------------
Device: HTC Wildfire
HBOOT: 6.01.1022 (Buzz PVT SHIP S-OFF)
Kernel: OC_2.6.32_v8
Recovery: Clockworkmod Recovery v3.2.0.0 + ROM Manager v2.5.0.7
ROM: WildPuzzleROM 2.2.1 v0.8
That's pretty much what I used when I used SetCPU. Except that my normal max clock was 652MHz, and, on the temp and battery settings, the max was 480MHz. (352MHz will crawl IMO)
3xeno said:
That's pretty much what I used when I used SetCPU. Except that my normal max clock was 652MHz, and, on the temp and battery settings, the max was 480MHz. (352MHz will crawl IMO)
Click to expand...
Click to collapse
I am thinking of downgrading my main max clock, because battery seems to drain out quite fast. But with 352 values it works pretty good. A bit laggy, but it saves lots of battery on low battery case...
You said that you don't use SetCPU now? What do you use instead?
CM7 has in-built settings for OC. It's not as exhaustive as SetCPU Profiles, but, it does the job. Besides, using two apps for the same purpose can cause potential clashes.
I have DoomKernal installed. I have the max set to 1.5Ghz, but what should I set the minimum to?
also, any suggestions on governor?
Usually you can just set the minimum frequency to the minimum allowed. Personally, I like the SmartA**v2 governor
Looks like my phone doesn't like 2Ghz, it crashed.
My settings are Max 1.5 Ghz Min 122 Mhz, Governor: On Demand.
Works pretty fine and saves a lot battery.
For ondemand, did you set anything in the advanced settings? Sampling rate and stuff.