Related
I want to over clock my HTC Desire using Set CPU
What should my max over clocking be , and what temperature should my CPU run at to be safe ?
I'm currently using the RCMixHD kernel.
Depends on your kernel.
Also, li-ion batteries are designed for use around 20c-60c, but as it goes past 40c, I think it has higher discharge rate.
Depends on your phone & kernel combo - 1113 Mhz is stable for the most of the people.
I suggest playing around with and test it - 1113+ is OK for some, but if you'll get reboots and the phone gets hot, then it is not recommended.
Also if you are OCing, you'll get more power, but worse battery life.
wont it consume more battery ??
I have Coutts 2.6.38 kernel and it allows me to underclock to 128MHz and 1190MHz overclock and I use ondemand since games don't like other governers. The underclock is bloody great to have as it consumes bugger all battery life and kind of balances out the overclock. However, as nagypapi said, you might not be able to get these speeds since your phone might get hot or reboot. I think people fail to realise that not all devices are the same and what works for one person, might not work for another.
Max. clock should depend on kernel support(if the kernel supports it, then that's your maximum clock). As for temperature, I have a profile on SetCPU which down-clocks the CPU when the temperature reading goes above 36 degree celsius. All other times it works between 806MHz-245MHz OnDemand.
Walter1115 said:
I want to over clock my HTC Desire using Set CPU
What should my max over clocking be , and what temperature should my CPU run at to be safe ?
I'm currently using the RCMixHD kernel.
Click to expand...
Click to collapse
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
bono2804 said:
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
Click to expand...
Click to collapse
I would like to try this settings, but could you please also add priorities for each setting?
Also what is your main governor? (when you startup SetCPU)
Other thing i dont understand why people use such high cpu freq for battery charging (when its charging and im never using phone then, isnt it better to put some low freq. and power saving profile?)
Same about Standy/Screen off.
128 is too low, it makes my phone slow, 245 is better IMO.
Sordep said:
128 is too low, it makes my phone slow, 245 is better IMO.
Click to expand...
Click to collapse
set 245 for screen off only ... Its not meant to make your phone quick its meant to conserve battery lol
BigMrB said:
set 245 for screen off only ... Its not meant to make your phone quick its meant to conserve battery lol
Click to expand...
Click to collapse
I know it, but weird, when I set the lowest value to 128, my phone's reaction become laggy, but 245 has no such problem. Maybe it's affected by kernel or rom.
sorry for my poor english
I know some roms/kernels have issues with dropping to 128 but my rom seems quite happy with it. I use higher CPU on charge and with battery above 75% to give me the performance when I have the most charge. When my phone boots it will adjust CPU according to battery life or charging profile. The settings seems to work fine for me although battery does drain quicker when I have it fully charged but that's my own fault for setting the performance govenor when I have high charge!
bono2804 said:
Sort of goes without saying that the higher the CPU cycles the more battery juice your phone will consume and the quicker your battery will drain. I use GingerVillain which supports speeds 128Mhz - 1113mhz and using Richard Trips 2.0b OC kernel (based 2.6.37.4) seems to keep battery alive for a good 24hrs. If it's any help my SetCPU profiles are as follows :
On Charge : 128-1113 performance govenor
Sleep/Standby : 128-576 conservative
Battery < 100% : 128-998 performance
Battery < 75% : 128-883 ondemand
Battery < 30% : 128-652 ondemand
Failsafe Temp > 45.1c : 128-768 conservative
Seems to give me a good balance of speed and battery life, but would be interested to hear from anyone else that thinks my settings are wrong, always looking to improve my phone!
Click to expand...
Click to collapse
I'm using your way! thanks!
No!
Using any CPU frequency that is not default ( underclocked or overclocked ) requires testing and manipulating the various variables. The CPU needs to be in sync with the GPU and the other parameters. Needs modifications in the kernel itself. The device is not made to run at those frequencies. You will burn your device, sooner or later.
Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
kazemagic said:
Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
Click to expand...
Click to collapse
i i think that ondemand is the best for daily using... i'm using cm10 rom and i have some music problem so i'm using interactive and it's ok. if you don't use games or heavy apps, you can underclock it to 1ghz or even less and put on powersave.. but you have to try and find the best for you
My setup is a little complicated. I use the ondemand governor, then for the profiles I make it use powersave and under 760mhz between 1am and 8:30am which seems to really help during the night. Also set it to use 760mhz max when the screen is off.
When charging or above 40% battery I allow it to run full speed, but only when the screen is on, therefore helping charge times. On charge or above 80% I set the governor to performance.
In call I set the clock to max 1000mhz and conservative to try and allow calls on low-battery to work properly without lag but also without killing the battery.
I have a couple of other options set for very low battery ( < 12% ) too, but those are only to extend the battery if it's dying.
I wouldn't say all this is necessary... but I need my phone to keep working at all times as I use it for receiving business calls.
It's just a matter of playing around really... depends what you use the phone for. For the most part tell it to use lower clock speeds when you don't need them so much (when phone is off, during the night, during call etc) but you will really notice the speed difference if it's underclocked while you use it, so I tend to allow it to use full whack when screen is on, unless the battery is low.
I also set up profiles to make things like Bloons TD4 run in performance mode and min of 1000mhz, to keep them smooth . Drains the battery though!
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
kazemagic said:
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
Click to expand...
Click to collapse
If you mean decreasing the voltage on the CPU, no I haven't. From my experience in desktop PCs however, if the CPU voltage is too low it can lead to hardware issues and instability.
If something needs a certain amount of power, and you give it less, it will either try and draw more amps which increases heat and can fry components, or won't work properly. You could probably "under-volt" the CPU at the same time as reducing the clock speed however, but your performance will suffer. When the processor is set to be ondemand it underclocks itself when not in use anyway
The biggest battery drain is screen and radios, concentrate on using them less. Underclocking the CPU will make the phone last longer when in use, but usability will suffer and turn your super fast smart phone into a sluggish one. I only make mine stay underclocked when the screen is off, during a call, or on low battery. During general use I let it do its thing .
UV(Under volt) is actually not to bad. Don't ever set those values at boot, else when they are too low, it will cause BOOTLOOPS. It just reduces the amount of power allowed for the cpu to use, thus it won't use more than required. You can't really ask a person for his/her uv values, as no 2 chips are created equal.
People stating that they UC(underclock) their device is not quite right. We don't have much control over our cpu's to be honest. If you run tegra stats whilst using you're phone, you'll see what I mean. It will sometimes(happens quite often) just bump up to higher frequencies to which you UC them. Also as soon as the screen is locked and unlocked the max cpu frequency set by the governor will just return(for example: say stock is 1500mhz, and you set it to 1400mhz, it will return to 1500mhz after an unlock). Ondemand is very very good for battery and performance. But remember you have to tweak those values individually in order to optain the best possible performace for the given task you want. Whether it is for battery or performance.
It's actually also a lot better to just tweak those values as to TRY and uc. Uv will stick, UC not!
Here is a small example as to battery saving and performance values for ondemand governor:
sampling rate:---------60 000 ----- 30 000
up threshold:--------------95 ----- 60
sampling down factor:-------2 ----- 8
powersave bios: ------------3 ----- 0
ignore nice load:------------0 ----- 0
io is busy:------------------0 ----- 0
A couple weeks ago, I installed SetCPU to help with battery life. It did great! But, I didn't see the amazing improvement that I thought I would.
So, I did some research and found out about Profiles. Profiles are settings that you can make that will be applied when certain conditions are met.
Below are the profiles that I have created on my Nitro. I have seen 11 to 12 hours of medium use from my phone with these settings. If you have any suggestions on changes, please let me know. I'd like to find the absolute best settings and share them for everybody.
Profile Name: Screen Off
Conditions: Screen Off
CPU Max: 384Mhz
CPU Min: 192Mhz
Governor: powersave
Priority: 90, Exclusive
Profile Name: Charging Any
Conditions: Charging Any
CPU Max: 1512Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 85, Exclusive
Profile Name: In Call
Conditions: In Call
CPU Max: 810Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 80, Exclusive
Profile Name: Battery <= 10%
Conditions: Battery <= 10%
CPU Max: 594Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 75, Exclusive
Profile Name: Battery <= 25%
Conditions: Battery <= 25%
CPU Max: 972Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 70, Exclusive
Profile Name: Battery <= 50%
Conditions: Battery <= 50%
CPU Max: 1242Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 65, Exclusive
Profile Name: Battery <= 75%
Conditions: Battery <= 75%
CPU Max: 1350Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 60, Exclusive
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
noemtfj said:
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
Click to expand...
Click to collapse
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
drumist said:
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
Click to expand...
Click to collapse
I don't do much with my phone in the way of heavy gaming or video watching. I am going off of the last couple days of having SetCPU enabled and getting almost 15 hours of medium use out of my phone.
noemtfj said:
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
Click to expand...
Click to collapse
It was an arbitrary number.
Does anybody find this kind of post meant to make peoples phones better helpful? It seems like every time I post something that I personally have found to make the Nitro even more awesome gets a tone of comments basically telling me that none of it will ever work. I'm sure that if people would just try the things I post, they would be happy.
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
scott0 said:
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
Click to expand...
Click to collapse
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
mattman86 said:
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
Click to expand...
Click to collapse
yeah, i guess it's diff for everybody, just like the roms eh, some get great batt perf on 1 and sucky on another and someone has exactly opposite.
anyhoo, my jd ultimate settings are
Status
advanced profile
graphical notification->quickbox
Controls
wifi enabled->wifi preferred
brightness min 20% mid 45% max 150% (gotta get the most of this screen in the sunlight!)
light sensor fast
cpu min 192 mid 918 max 1512
governor ondemand
schedules
none, i also turned off night schedule as i have the phone plugged in during those hours.
triggers
Apps enabled
Configure->configure apps allow on during screen off->pandora
Location enabled
****************i find it makes a world of difference to give jd =>3 days to get it all right.
make sure setcpu is out of the way as well.
So I have started playing around with those. I searched over google for some awsners but since my brain started bleeding i tought i'd create thread. ( hey I work overnight, I should be sleeping).
So far it looks like this (On CM9 stable with Darkside 6.1)
Prio 100
Screen off 540-192 ON DEMAND
Prio 90
BAT > 122F 756-384 ON DEMAND
Prio 85
Charging ANY 1728 - 1026 BADASS
Prio 82
IN CALL 1080 - 384 ON DEMAND
I/O NOOP
Prio 80
APP CHROME 1512 - 1026 ON DEMAND
I/O NOOP
Battery > 10% 1782 - 1092 BADASS
I/O NOOP
So not sue if the combo of screen on screen off is ok...Also Should i ALWAYS set a I/O Scheduler ??
Thank you for your time
NLPUNITED said:
Need advice on combos for Governors and I/O Schedulers. I searched a bit on google and the forums but did not quite find what i was looking for.
Currently on CM9 and Darkside 6.1
SETCPU:
100
screen off 540-192 ONDEMAND
90
batt> 122f 756-284 ONDEMAND
85
Charging Any 1728-1026 BADASS
82
IN CALL 1080-384 ON DEMANDE I/O NOOP
80
Chrome APP 1512 -1026 ON DEMAND i/o noop
79
Batt > 10% 1728-192 BADASS I/O NOOP
Not sure on when or how to use NOOP. Also, not sure about my screen off/ on combo
Should noop be always ON ? Looking for Good battery life since mostly texting and fooling around the phone. Games at times.
Click to expand...
Click to collapse
Your setup looks good. Not sure about you Chrome profile, why have the min so high? I like having my screen off at that exact range, exept on conservative As for the i/o scheduler, it depends on the kernel. Im using TDJ;s also, and he recommended noop on his, so thats what I use
Setcpu
100
Screen off 540-192 conservative
99
In Call 1188-192 badass
98
Battery <=15% 1026-192 badass
97
Screen on 1512-192 badass
Battery lasts all day, no juicedefender, on AOKP, lets me switch to 2G on screen off.
I play games and xda app, get an easy 4 hours screen time
LoopDoGG79 said:
Your setup looks good. Not sure about you Chrome profile, why have the min so high? I like having my screen off at that exact range, exept on conservative As for the i/o scheduler, it depends on the kernel. Im using TDJ;s also, and he recommended noop on his, so thats what I use
Setcpu
100
Screen off 540-192 conservative
99
In Call 1188-192 badass
98
Battery <=15% 1026-192 badass
97
Screen on 1512-192 badass
Battery lasts all day, no juicedefender, on AOKP, lets me switch to 2G on screen off.
I play games and xda app, get an easy 4 hours screen time
Click to expand...
Click to collapse
Will try it with conservative on Screen Off...Tought i read somewere it's better to keep it on Demand so you dont have bugs when going on ?
NLPUNITED said:
Will try it with conservative on Screen Off...Tought i read somewere it's better to keep it on Demand so you dont have bugs when going on ?
Click to expand...
Click to collapse
On AOKP ICS, havent noticed any bugs due or SOD (Sleep of Death) I get an easy 20hrs batt life with moderate use
So far 1:30 screen up time, played games and such. Still at 60% Bat. Prety damn good and i use a screen lock pattern wich must drain a bit more.
Am using AndroidRevolution HD and PopcornKernel for the maximum battery life.
I am using agressiveX governor.. its basically conservative with tweaks and hotplugging
At first I used franco's updater app to change my cpu min and max.. this app did not have a scheduler option but when i used SetCPU i chose deadline.. my batt life became a bit shorter.
I had 300+ min and 700+max. Was running smoothly and got about 6h on screen time thanks to both the rom and kernel being built for batt life and the conservative-like governer.
So basically i have 2 questions:
Which scheduler do I use to maximize battery life and Why is it when my device is off screen it runs out of batt so fast.. could it be due to hotplugging or the low cpu speed i have?
Sent from my Galaxy Nexus (Jelly Bean)
What are your battery stats like while the screen is off? If the phone is being held awake, you have an app that is constantly waking the phone up. Next charge cycle, provide a screenshot. I don't know just how much different schedulers help in terms of battery. I've hopped between noop and deadline and never really noticed a difference. Best bet would be to try each one. YMMV because my usage pattern may not match yours.
I have checked with CPUSpy and yes my device is entering deep sleep.. i wanna know if such a low voltage affects my phone sleep since i have hotplugging enabled
Sent from my Galaxy Nexus (Jelly Bean)