Can u guys share ur set CPU profile. I need profiles with great performance and less battery consumption. My profile is as followed :-
Charging AC/full 748 Max 480 min
Screen off 245 max 122 min
Performance n battery don't come together ..... I use ondemand 729/425 ... nothing different for screen off .... works really smooth n decent battery also
Sent from my LG-P500 using XDA App
But I Also need to manage my batteries...
My setup's kinda similar to yours,
480/720 ~ on demand ~ when charging/full
Otherwise 240/320 when screen is off. BTW How long does yours last?
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
I don't have many profiles, just 1.
245min / 748max
Battery's life is kinda good, usually I have to recharge one time a day. It's not a problem for me.
Toshir0 said:
Hey !
That's for me :
Charging/full : 729 - 245 / ondemand
Screen off : 320 - 245 / conservative
Battery < 40 : 600 - 245 / ondemand
Battery < 20 : 480 - 245 / conservative
Click to expand...
Click to collapse
I even used battery less than profile but it slows the phone too much....
Well It also depends on which ROM you have on your phone.
Mik_os CM7 port actually EATS the battery and It runs out of juice in less than 24 hours with a normal usage. A bit better with devoid v5, but I feel like openOptimus is the best one out of the three.
I use only one profile: battery < 101% @ 729/122 smartass
great advice so i must be changing my rom as soon as andy releases his new build!
729 max 480 min smartass
I use:
Main 729 max 320 min smartass
Charging 600 max 245 min ondemand
Battery < 40% 600 max 245 min conservative
Battery < 25% 480 max 122 min conservative
I used to keep a screen lock profile at 245 max but my phone lagged while receiving calls when the screen was locked and sometimes while playing music.
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Using stock ROM.
Normal: 729 max, 245 min, conservative
Charging: 768 max, 245 min, ondemand
Battery < 20%: 600 max, 122 min, conservatve
Battery life greatly depends on my usage. But, generally, I come home after classes (where I use it for internet, music, games etc.) with 30-40% battery left.
Javi V12 said:
I use devoid.franco and
729/480 interactive
Screen off: 600/240 ondemand
What is that of smartass? My SetCpu havent got that mode :/
have someone got a guide or something that explain each mode (ondemand, interactive...)
Click to expand...
Click to collapse
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Devil_Dude said:
i wish if some one had a guide on it but optimus users like u and me are recommended to use ondemand (no i am not a noob).
Click to expand...
Click to collapse
Look at this
http://forum.xda-developers.com/showpost.php?p=9272248&postcount=1
i got dis man
Program for controlling CPU frequency on Android in order to increase productivity or increase battery life.
Of the features worth noting customizable profiles.
Description of modes:
* Interactive - an interactive mode, driving frequency of the CPU in real time, almost always at full productivity.
* Smartass - a regime based on Interactive. Has a more rapid decline in frequency in a simple, but also lowers the frequency to a minimum at a turned off screen.
* Conservative - operates at a very low incidence of possible CPU and increases incrementally, as needed.
* Userspace - allows you to change the frequency of the CPU, either manually or dynamically, at the discretion of the software.
* Powersave - reduces the frequency of the CPU to the lowest possible level.
* Ondemand - operates at a very low incidence of possible CPU and increases the maximum reaches values of CPU usage - 100%.
* Performance - sets the maximum frequency of the CPU, not allowed to change frequency downward.
I was just wondering what people get for battery life with miui 1.7.8 and OTB .13 kernel.
Also, what does overclock actually mean? Does it mean that setting the min and max to 1400Mhz in Voltage Control or remain the min to 100 and max to 1400Mhz?
I'm currently on noop, ondemand and min=100Mhz, max=1400Mhz with nothing UV'ed.
Please help me to get better battery life!!!!!!!!
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
1n73rn37_j3d1 said:
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
Click to expand...
Click to collapse
What do you mean by two settings?
Like, what are I/O Schedulers and CPU Governors? That last question was me hijacking the thread.
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
mad_max911 said:
Siyah kernel + Checkrom...
Tried Voltage control, setcpu....
So, for specific frequency under performance governor, i can set any voltage...
Under all other governors it work ok...
Please help.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Performance governor uses only one single frequency (min freq = max freq) and is only useful for testing (benchmarks).
Do not use this governor for daily usage.
Select another governor, such as Ondemand.
You can still set min freq = max freq, if you want your phone to run on only one single frequency.
Thank you. Very good point to use, let say ondemand and min/max at same frequency... why didnt i think of that??... About performance governor, it does feel "snapier" in day to day usage, deep sleep still works and battery is not much worse as screen still uses 60% of battery.... only time when performance governor uses much more battery is if u are using gps or some background task that is preventing phone from going to sleep while screen is off...
Sent from my GT-I9100 using XDA
UPDATE: After some more research i conclude: problem is NOT due performance governor or kernel... Same think happens on any kernel and governor if you set min and max frequencies same(custom voltage set in any program will not apply). Solution is to have minimun 2 steps( for example 1200 min and 1400 max mhz in my case). Further, you can use setcpu profiles for "screen off" etc., and battery loss due this performance governor imitation gets minimal....
Sent from my GT-I9100 using XDA
has anyone else tried using setcpu with ics roms? does it actually do anything?? I'm trying now, and i set my lowest frequency to 192 and like max at 894...thing is I don't notice the phone being any slower... is it actually doing anything? it says it is.. system panel shows it maxing out at 894..but I'm still dropping battery like crazy lol clearly it doesn't help enough if it even works.
Sent from my ADR6425LVW using XDA App
Known bug with ics roms, will not work at all until source is released and we get someone to to build a kernel without HTC perflock built in
Sent from my aokpcb_tenderloin using xda premium
don't use any apps that control the CPU. that goes for frequency,governors,etc. it messes with perflock which causes the CPU to run at only the min/max frequency and no proper scaling. stick with this advice until custom ics kernels come
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
It works great for me, and was just updated recently and fixed all the little minor problems and occasional crashes that I used to have.
None of the stock kernels should ever be govern with a CPU app. I have no idea why people say it only applies to ICS. In fact this applies to BOTH GB and ICS kernels. GB and ICS kernels have the same battery life on stock roms.
If the kernel does not allow you to disable perflock, it won't scale right, stock kernels cannot have it disabled. I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Sent from my ADR6425LVW using XDA
nosympathy said:
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
That has happened to me once. But not since last update. It does bounce around sometimes but never goes above the max I specify so I'm happy with it. Keeps temps down under heavy use as well even though temps aren't much of an issue with latest leak
Sent from my ADR6425LVW using Tapatalk 2
Works fine after the latest update on conservative governor, scales throughout the range given. Cleanrom 4.4 stock kernel.
richii0207 said:
I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Click to expand...
Click to collapse
exactly...
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Quadrant only shows my CPUas being single core . I'm on CleanRom Standard Edition 4.5. Wasn't sure if that had been addressed in a thread yet or not . So I wasn't sure where to address this, but this seemed like a good place . I took a screenshot of it .
Sent from my ADR6425LVW using xda premium
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Kane5581 said:
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Click to expand...
Click to collapse
i'm running cleanrom 4.5 right now. when i set to conservative, it jumps all over, but it still maxes ouat at 1512 often.
i just stopped touching it because i didn't feel like breaking anything lol but again, some people are saying due to perflock it won't work, while others say they have experience of it working. so confusing.
Perflock being the pain it is, I'm staying away from it right now.
When I had it installed, my battery life was complete fail.
Sent from my ADR6425LVW using Tapatalk 2
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
All you can do is try it. Worst case scenario your battery drains too fast. Then uninstall it. Why it helps some and not others, I don't know. It helped me get 16 hrs of battery life with 4hr screen time with 4g on stock battery (ics) yesterday. No way in hell I could get that without setcpu
Sent from my ADR6425LVW using Tapatalk 2
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
a.mcdear said:
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
Click to expand...
Click to collapse
awesome analysis. ...so what's your battery life like?
I've gottent it to work a couple of times, other times it seems to do nothing at all, and i have also had it almost burn a hole in my pocket due to heat. I would say dont try to OC for now and wait until we have something more stable as they have previously stated. To be honest its a hit or miss type of mod for now.
jayochs said:
awesome analysis. ...so what's your battery life like?
Click to expand...
Click to collapse
My battery life is pretty good. I'm very surprised by how little i actually notice the difference in responsiveness and performance as my CPU throttles lower as my battery drains throughout the day.. However, I will admit that the only reason I have it scaling so low like that was to match the same battery life that I was getting on totally de-sensed GB builds...
I was wondering what CPU layout all of you guys are using. This including governor I/O and voltages. I have been experimenting but I'm not used to dual-core or having so many options. Let me know what you all think!
I like battery life, but I also have an extended battery and two spares, so there can be a little leeway for performance sake. I would like the phone to be able to play music with the screen off, but it seems I'm either clocking too high (gets warm often) or Pandora is using a lot of resource.
Thanks guys!
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
tmanschuette said:
I was wondering what CPU layout all of you guys are using. This including governor I/O and voltages. I have been experimenting but I'm not used to dual-core or having so many options. Let me know what you all think!
I like battery life, but I also have an extended battery and two spares, so there can be a little leeway for performance sake. I would like the phone to be able to play music with the screen off, but it seems I'm either clocking too high (gets warm often) or Pandora is using a lot of resource.
Thanks guys!
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
Click to expand...
Click to collapse
For a balance between batterylife and performance, I use wheatley on the first core, and lionheart on the second core. I/O scheduler is ROW.
I undervolt across the board by -50mV. First core UC to 1350 MHz, second core OC to 1620 MHz.
If you don't care about battery life, Lionheart both cores is probably gonna be very nice for you.
Also, for a rock solid, reliable governor, Intellidemand is pretty good.
I'll give it a try and see. What are your minimums?
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
which program have you used to set the different govs to different cores?
My minimum is 384 MHz both cores. I use Kernel Tuner to adjust my settings, but some people have reported problems with KT. Other options might be Trickstermod or Android Tuner.
i dont like android tuner, never seems to stick, i use trickstermod but KT ive heard some mixed things i want to try it
I use kernel tuner. Never tried the other two, but I also haven't had any of the issues others are having with ROMs hotboots or the like.
Sent From The PACMan Lair using Tapatalk 4 Beta On My Rezound.
i use kernel tuner/Snuzzo Kernel 3.5.1 at the time of this post/Unofficial Cm 10.1 Rom currently being built by Flyhalf
Heres my current ultimate setup lol, been running it for a few months. its completely stable
CPU0: Min 384 - Max 1350 - Lulzactive
CPU1: Min 384 - Max 1728 - DanceDance
Mp-Decision i changed the idle frequency to 384Mhz, that's the only option i touched in there.
Misc Tweaks:
Capacitive Buttons Blacklight: 30%
Fast Charge: On
Vsync: On (Having the Gpu processing extra FPS can drain battery, Lol on a phone its nothing but possibly can help)
Usb OTG: OFF (doesn't charge\access Sdcard when plugged into PC and i dont have a OTG cable)
Color Depth: 24
IO Scheduler: Sio (i also like Noop, look up which ones you like best) (sio is more performance and noop is balance)
Sdcard Cache: 4096
And in kernel Tuner hit the menu button on ur phone thats on the right of the little home button and select "Swap"and click activate Swap and set the Swappiness to 100 and click set Swappiness
Now on to Undervolting. ive benched over and over to find a super low and stable setting.
192 - 700mV
310 - 712mV
384 - 712mV
432 - 750mV
486 - 750mV
540 - 775mV
594 - 775mV
684 - 800mV
702 - 800mV
756 - 825mV
810 - 862mV
864 - 887mV
918 - 887mV
972 - 912mV
1026 - 912mV
1080 - 937mV
1134 - 937mV
1188 - 962mV
1242 - 987mV
1296 - 1012mV
1350 - 1037mV
1404 - 1062mV
1458 - 1062mV
1512 - 1125mV
1566 - 1137mV
1620 - 1162mV
1674 - 1187mV
1728 - 1212mV
If you decide to use my undervolt table THAN PLEASE MAKE SURE BEFORE you punch in the undervolt that you do a nandroid backup, your phone may act differently than mine. the table is pushing the line lol they can possibly be lowerd in some spots by i highly doubt it, you'll most likely boot loop if you try and lower it
lol and make sure you put in the right values. Writing those down and triple checking them was a little hard
Also i have a screen brightness table to if you want it.
--Delete-- Wrong thread