Related
Was wondering what type of profiles people got setup on setcpu for some good battery durations oc'ed.
I'm currently running at 1417MHZ and only profile I have setup is screen off. 275 / 275 conservative. Priority is at 100.
Sent from my HTC Vision G2
I'm running at 1305MHz.
Screen off 245min/245max
Temp > 38.2 C 245min/768max
Battery < 15% 245min/768max
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
donaliar said:
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
Click to expand...
Click to collapse
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
mejorguille said:
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
Click to expand...
Click to collapse
Oh alright. my sampling rate is 50000. up threshold 95. ignore nice load 0. and powersave bias 200. does that sound about right? or should i change somehthing else? Thanks for the help!
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
Questions:
Did you notice battery drain with setcpu in memory?
How is the battery temp?
Does the powersave bias mean that you will never scale to the peak value?
Had the phone off the charger since 11am.
Moderate call usage
Heavy texting
Moderate internet usage
Music for roughly 3hours straight
Wireless tethering on Xbox live for roughly an hour
At 9:15pm I have exactly 40% with my profiles from my post above
what does 245/768 mean?
nvm i got it
potentdro said:
what does 245/768 mean?
Click to expand...
Click to collapse
245 min, 768 max
So its a bit after 1am and just over 14hrs after a full charge. While using my profiles and info as posted in my above 2 posts along with 2hrs of GPS usage, light phone call usage, and heavy internet usage my phone finally died 14hrs later with the Gov module on conservative with posted profiles and OC'd at 1459.
Although abought 10min prior to it dieing I did attempt to submit this post from the phone but near the end of the post it froze up, showed the desktop and my battery notification showed 0% and the phone then rebooted itself but I got a bootloop on the "g2" screen and had to pull the battery to fix it.
After 10% battery level I was experiencing lagging and slowness while online so I'm assuming because of my profile setting of 245/245 at that battery level and what probably caused my bootloop.
*Edit: I must say I'm pretty impressed. I had my Nexus one alot more heavily modified than my g2 and only OC'd to 1113 with similar daily usage and I would have to charge it one time at some point during the day to last me throughout the night.
SRT102JZ said:
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
Click to expand...
Click to collapse
What do you have set up in "Main" tab?
Thanks. I'm going to try your settings.Battery life is disappointing...
Sent from my T-Mobile G2 using Tapatalk
Okay, so I got my G2 about two weeks ago, and have been running set CPU with these settings since then.
Main profile: 1478 max / 245 min
Screen Off: 245/245, Priority 100
Temp > 100.4 F: 368/245 Priority 97
Temp > 96.8 F: 768/245 Priority 95
Battery < 20%: 245/245 Priority: 82
Battery < 30%: 368/245 Priority: 81
Battery < 40%: 768/245 Priority: 80
Charging/Full: 1478/245 Priority 60
Charging USB/Full: 768/245 Priority 55
Charging AC/Full: 1478/245 Priority 50
On light use I've gotten almost two days, by light use I mean only a few phone calls or text messages and data turned off. On Normal use I've been averaging around 16 hours, and on heavy use I've been getting around 10 hours. Pretty good battery life, I'm pleased with it being my first Android phone, was a black berry user before this.
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
ScottRTL said:
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Click to expand...
Click to collapse
you have to make sure the priority is at a higher level than all the others...like 100
abenco said:
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
Click to expand...
Click to collapse
You can get the full version on xda for free. It's nice to donate though.
Sent from my T-Mobile G2 using XDA App
need some help
my htc wont show any clock speeds past the 806mhz. ...any ideas? i tried to perflock disable and it says it is already..and in custom profiles it shows still only max up to 806
edt** read a custom kernal may be required...im on stock. thats probably why
I was wondering what would be considered optimal settings for SetCpu. I amn running BaconBits and am not sure how I should do the settings.
Any help would be appreciated!
Thanks.
i have mine set at:
Profile 1 : 806 MHz max, 245MHz min, On Demand, priority 50
Profile 2 : 245 MHz max , 245MHz min, On Demand, for when the screen is off, priority 50
if i change the MHz, i change it higher on profile 1 for whatever i need it for then i just scale it back down to 806 when i am done...
Mines pretty much the same as the one above save for max clock speed being 1500Mhz.
Sent from my HTC Vision using XDA App
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
If you search google for an "overclocking 101" thread you should find a rather large ongoing break down of setcpu and the most efficient way to use it. I believe its on one of the droid forums, awesome info.
tazz9690 said:
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
Click to expand...
Click to collapse
I just stole the rest of your settings, hope you dont mind!
WarBird87 said:
I just stole the rest of your settings, hope you dont mind!
Click to expand...
Click to collapse
By all means, have at it!
Main profile: 245 - 1017 on demand
Charging/Full: 1017 - 1017 performance 90 priority
Screen Off: 245 - 245 performance; mainly as this mode will bypass the need to poll/sample for CPU speeds, thus reduces some CPU load. 100 priority
Battery < 20%: 245 - 768 on demand 75 priority
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
WarBird87 said:
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
Click to expand...
Click to collapse
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Speaking of powersave bias, could anyone tell me some optimal settings for the setCPU advanced tab? Don't mean to derail this thread, I've just never used that tab.
Sent from my T-Mobile G2 using XDA App
SeReaction said:
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Click to expand...
Click to collapse
I believe i was right at 20% batt or right below,so that could have been the issue... I havent messed with anything on the advanced tab as i dont know much about it, the powersave bias is still set to 0
I have HTC heroc 200 alltel running fresh 2.40 rom firerat mtd 160 10. what should I set CPU to
Sent from my HERO200 using XDA App
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
j.books said:
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
Click to expand...
Click to collapse
I used to get about a whole day without setcpu. With setcpu, same amount of usage, I get well over a day and a half before having to charge it up.
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Jasonhunterx said:
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just got Voltage Control (the free one)
but I don't get how to use it. Can you please guide me? Which Mhz is sleep profile? and what do you mean build prop tweaks?
Well its pretty simple open app click second tab the you will see sliders you slide them down slide it down 1 notch
Sent from my GT-I9000 using XDA App
But like which ones? I set the 100 to -25 and went to sleep and most 13% overnight.
Which other ones should I set there.sorry for the questions I just don't want to mess up my phone
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
So basically, I have to go through the voltages (-#'s) and see how low i can go without crashing?
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
What would happen if you set it to 1000= -0 ??? Couldn't you just odin back to stock if the phone crashed?
}{Alienz}{ said:
Start with these
(Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
check this out
http://forum.xda-developers.com/showthread.php?t=829731
nbhnohome said:
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
Click to expand...
Click to collapse
I don't think I want to go THAT low, maybe it'll crash my phone or someting?
caldran said:
http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
that thread doesn't help. I've seen it before, its just info.
I think people are answering the wrong question. Or I should say, giving answers to a different question.
To the OP: You're talking about Deep Sleep battery usage, right? There's no way to undervolt Deep Sleep. It's already using very minimal voltage. I believe what causes excessive Deep Sleep battery drain is the number of apps still running and using the CPU during Deep Sleep.
Undervolting will help a bit with battery drain during normal usage. For Deep Sleep, turn off your various apps' syncing ability, as well as freezing programs you don't use but that run in the background. For instance, if you don't use navigation very often, consider freezing the Maps app, as it runs all the time in the background. A number of popular games like to run in the background like GunBros and Aqua Pets. Also switch from 2g/3g or 3g to 2g only at night to save battery there.
To recap, the less you have running in the background, the less battery you'll lose when you phone is in Deep Sleep.
I was also going to say switch to 2g if you don't need the speed. It helps a lot for me. I also usually put my phone in flight mode before I sleep. I lose like 0.5% of battery an hr on flight mode. I'm not on MIUI yet, still on froyo, but should still help.
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
mohitmoudgil said:
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
Click to expand...
Click to collapse
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Can I do voltage Control on stock MIUI Kernal or do I need Neo?
Sent from my Vibrant.
In my experience (admittedly only been on MIUI for a few weeks), Pimp my CPU, Voltage Control, and SetCPU all work fine on MIUI, so yes. You should be able to use Voltage Control. Not entirely sure about Stock MIUI, but if you use the (superior) Revamped version (either SS or Lithium editions) the kernel that comes stock with it allows you to change voltages, though I would still recommend moving to Glitch and using either the ML or LL versions if you want to maximize battery savings.
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Click to expand...
Click to collapse
OV/UV settings can vary widely between phones. Some offer little to no leeway at all, and can't even be overclocked to the rather tame 1200mhz. Others can sit at 1700mhz at 100uv. It's luck of the draw really. Also, Conservative Governor will be kinder to more exotic UV settings, while others like Smartass or OnDemand may only allow for a slight 25 or 50uv for most voltage levels.
Trial and error, my friend. Find what works best for your phone.
Thanks guys.
One more question
If when I test if my phone can handle a certain UV is it good to have it at the lowest I can?
Like example
My 400mhz can go down to -200UV is that good or bad? Should I keep it that low if its not crashing or anything
You need to do some stress testing to be sure it's stable at those frequencies. Depending on the governor you use, your phone may not hit 400mhz often enough for you to really tell if it's stable or not. You could set 800mhz to -800uv, but if your phone tends to skip over 800mhz most of the time...
Undervolting can cause other problems if it's not completely stable. For instance, on Froyo I would get annoying static during music playback. Took me nearly a month to figure out that it was because I was undervolting the 400 to 100mhz range too much.
Undervolting doesn't make THAT big a difference. If you don't want to tweak and stress test and tweak and tweak again and stress test again, etc etc etc, then just reasonable settings that most phones can handle. For instance, 1200 0uv, 1000 25uv, 800 50uv, 400 75uv, 200 100uv, 100 125uv.
xriderx66 said:
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Click to expand...
Click to collapse
In my experience when I switch to only use only 2G networks I get damn near twice the standy time. Also, changing wifi to never sleep and staying connected to wifi has about the same effect. This also holds true for CM7.
3G is a battery killer for MIUI and CM7
The only resolution I see to this is a GB source drop but I'm not holding my breath.
Off topic but does anyone know a good, fast device that runs CM7/MIUI without bugs or this horrible battery drain? I've been running some form of CM7 since Eugene's build this spring and it has gotten MUCH better but I'm kind of disappointed at the lack of vibrant-specific progress lately. There's only so much the devs can do without source (or a working vibrant and a T-Mobile data plan for that matter....). Don't get me wrong, I'm thankful for what we have and what the devs have given us but I'd love GPS that isn't f'd and 3G that doesn't suck my battery dry in a little over 10 hours (working 911 wouldn't hurt either.
Sent from my T959 using xda premium
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
cjbcjbchris said:
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
Click to expand...
Click to collapse
you have to install setcpu :good:
cjbcjbchris said:
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
Click to expand...
Click to collapse
or you use System Tuner
jstef said:
you have to install setcpu :good:
Click to expand...
Click to collapse
SetCPU's good. @OP, the SetCPU Dev is an XDA member and provides it for free from XDA so if you want to search for it and download it from the original thread you can. If you want to support him then please buy the app from the Play Store.
Also I personally feel that the advice you've been given is quite poor. 96MHz max with the screen off is definitely too low. I keep mine at 128 min and 4 something max, that way the battery usage is low but I get a fast response when I unlock the phone. With 96MHz max you're going to get tonnes of wakelocks. I tried to set mine to be at 128MHz once then tried playing music (with the screen off) and the phone froze, so I reckon with 96 max any background syncing or in fact any background processes could result in freezing.
geowolf1000 said:
Iarge amount of cpu which are enable by default can modified if you do not want extra press the stock pefomance per app at setings
Is was too on cm.12 nightles too but has optoon
Now disable it
IMPORTAMD
FIRST TIME BREAKS DIALER
ONLY REBOOT IS FINE!!
Download an cpu tool you preferp
I downloaded from here
Set to 300 minimum
Get userspace And linux governor cfq.
Set on boot .
Try it .
Noop breakes wifi
Click to expand...
Click to collapse
:good::good:
+50 mA battery power less
Watt?
No need to post
Last battery issue was less than 30 mA and consume your batterry
In one day
Default cyanogen clocks is 1572 minimum....
Perfomance will not affect
Has only stable little heat all the time
And sweater heat with full sensors awake
Lte.,nfc , bluetooth...and calls with proximityis bigger
Heater but not so obvious from previous sudden
Real hot Situations.
Is this battery saver app ?
The minimum frequency is so high because the stock kernel is using MPDecision as the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:
mumaster20 said:
The minimum frequency is so high because the stock kernel is using MPDecision als the hotplug. This boosts the minimum frequency when you use your phone to the 1.5 GHz frequency. When you dont use your phone that intensively it clocks itself down to lower frequencies. No need to put the min freq to 300 MHz, because it already is, it just says 1.5 GHz because of the hotplug :good:
Click to expand...
Click to collapse
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.
geowolf1000 said:
When?
The apps in background still runing and if they are in background the cpu still hold same frequencies as minimum.
Click to expand...
Click to collapse
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!
mumaster20 said:
Only when you touch the screen and a little while after that the min freq will be 1.5GHz, after that it chenges back to 300 MHz, thats how MPDecision works!
Click to expand...
Click to collapse
I will collect you the cpu stats with and op settings for all day
Perfomance will be same and post it after for more .
So the stats show that profile per app keep device at 1452mhz double time than without
I examine with same settings almost same hours and almost same usage
The white background screenshots is without
The black background is with
My perfomance is absolute same i only feel diference at low battery level
Lower than 8% at wake up
Ps there is a bug when change this settings
Battery show always awake device but is false
After full charge and shutdown all normal