Related
I used to use setcpu on my first rom (LeeDroid) but it lagged my phone bad, so uninstalled it. Now have came back to it on droidzone RoM and its running fine, I only want screen off profile, but whats the best setting? am using smartass 245 max-128min is smartass best scaling?
EDIT
Topic started of has a question thread, so I thought on changing this to setCPU General CHAT
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
dexter93 said:
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Same here. I'm using smartass at screen-off for same reason.
shankly1985 said:
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Click to expand...
Click to collapse
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
rootSU said:
I use on demand with eviollet kernel min 128 max 245. Only thing that happens screen off is Poweramp, so can't comment for other back ground apps. But wake up is fine and power amp runs fine.
Of course with teh eviolet kernel you can set your own voltage levels so the next frequency up from 245 (384) can be set with the same voltages as 245, so having max of 384 would be no different power drain wise than 245.
Smartass is very bad for waking the phone so I steer clear of that all together.
Once thing that is important to note, using a different governor for screen off than screen on will also slow down your wake time. Changing governors can take time so will produce a lag when turning on the screen so find your governor and stick with it through out.
The most efficient governor for screen off if min and max are the same is either powersave or performance. The reason for this is they as default run at min or max (respectively) so they do not poll the CPU to check for load as they do not care. That said of course, these governors are no good fro screen on use IMHO so it would need a different one which then gives you the governor change issue.
Click to expand...
Click to collapse
That's interesting. Thanks! Didn't know the governor change issue.
MatDrOiD said:
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
Click to expand...
Click to collapse
Very good read thanks, am using ondemand for both default and screen off and its perfect screen off set to min128 max384 priority 100
works smooth not so sure about battery saving tho? but I have noticed display in battery settings is now down to 40% used to be always 55-65%
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
I am pretty sure 128 mhz cosumes less battery than 245 mhz, because clock is lower, even if the vdd level (the tension) is the same.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
shankly1985 said:
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
I hope shocked in a good way?
MatDrOiD said:
I hope shocked in a good way?
Click to expand...
Click to collapse
Very good way ha ha
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
There is no real risk mate, just don't go over clocking it all the way, right away. Start of small steps. Under clocking is very safe
Sent from my HTC Desire using XDA App
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
http://www.setcpu.com/
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
What settings is that with mate?
tbaxter08700 said:
What settings is that with mate?
Click to expand...
Click to collapse
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Uploaded pic to show.
shankly1985 said:
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
And what other stuff do you have on/off? Mobile internet, WiFi?
tbaxter08700 said:
And what other stuff do you have on/off? Mobile internet, WiFi?
Click to expand...
Click to collapse
Mobile data always on, wifi only when download Apps, sync only when I want it to.
Screen brightness just under halfway, dont use bluetooth that much, never use GPS.
Anything else that I missed?
I'm experiencing a very big battery drain when the screen is off for a long time. I just left the phone screen off for 2 hours because I took a nap. When I woke up, the battery went from 60% to 40%. (via Juice Plotter) That was 10%, per hour, while screen off. I did not experience this from the AcesMod v35 original kernel. My SetCPU profile for screenoff was 128-345Mhz, smartass V2. Could this be the problem?
Thanks in advance.
I'll give you the best piece of advice concerning changing CPU frequencies.
.......................................................
Don't.
bortak said:
I'll give you the best piece of advice concerning changing CPU frequencies.
.......................................................
Don't.
Click to expand...
Click to collapse
This.
Deleting setcpu will be a move of your life.
erklat said:
This.
Deleting setcpu will be a move of your life.
Click to expand...
Click to collapse
Can i ask whats wrong with setcpu then?
A) Android manages it's CPU frequencies absolutely fine by itself.
B) By running SetCPU, it constantly needs to monitor your phone for it's state, so it can change the CPU frequency, which will just use more battery.
C) Overclocking your CPU will kill it faster.
Hello,
i hope you can help me.
I'm using MildWild 4.3 based on Oxygen 2.3.2 with Thalamus kernel.
When my desire is on stand-by modus, it consumes 1 % per 45-55 minutes. Because of that i'm very glad.
But when i use my desire, p.e when iuse play store without anything downloading it consumes 1 % per 2-4 minutes.
My question is: is that normal? Or must i change any settings or an another kernel etc???
Can nobody help me?
I don't know why you don't reply? This is my second thread, and the first thread I've not recieved any answers either.
Well, it is 18 hours past after unplugging my phone and I have 71 %. But I'm used my phone 15 minutes after unplugging.
Is there all right?
it seems maybe a little high. screen should be the biggest consumer of battery once you start using your phone.
however i don't know your screen brightness and age of battery.
in standby seems ok, you can use something like 'betterbatterystats' to double check no app is keeping it in partial wakelock.
inbuilt kernel, or stock thalamus kernel (in my sig) should be fine. personally i use inbuilt cpu settings ondemand 245 - 998MHz, no other apps needed, and i think battery use is fine.
for what it's worth, here's another response to another battery use query...
Yes ,Its normal
eddiehk6 said:
it seems maybe a little high. screen should be the biggest consumer of battery once you start using your phone.
however i don't know your screen brightness and age of battery.
in standby seems ok, you can use something like 'betterbatterystats' to double check no app is keeping it in partial wakelock.
inbuilt kernel, or stock thalamus kernel (in my sig) should be fine. personally i use inbuilt cpu settings ondemand 245 - 998MHz, no other apps needed, and i think battery use is fine.
for what it's worth, here's another response to another battery use query...
Click to expand...
Click to collapse
hi
in the android phone its normal battery usage , but for better test u can change CPU governor to smartassv2.
don't forget battery Consumption mostly depend on kind of Battery and thats Amper
thanks for the answers,
I'm using thalamus kernel, 2.6.35.14_r-stable.
Screen brightness is automatic and i've bought my battery 1-1,5 years ago, original desire battery.
I also have Better Bacttery Stats, by partial wakelocks i have since unplugged:
Activity Manager-Launch with 2m 6s and 318 counts.
Alarm Manager with 1m 7s and 1244 counts.
wifi with 10s and 501 counts
sleep broadcoast with 8s and 460 counts
and other programs.
Since unplugged: 10 h
deep spleep: 8h 7m
Awake: 1h 54m
Screen on: 1h 43m
KWL: 8m 20s
PWL: 6m 9s
İs there all right, and I don't know which programs are these.
and under cpu governor I don't have smartassv2, i have powersave, ondemand, performance. Min CPU frequency 245 MHz, max CPU frequency 998 MHz, and what is smartassv2?
And can you please explain in a bit simple English?
My English isn't good.
Can you post a screenshot of your battery usage graph?
I'm my case, almost all the power consuption comes from the screen (Never under 50%).. I have to use very low brightness if I want the battery life to last.
Best regards.
http://s14.directupload.net/file/d/2944/dn53ux3u_png.htm
How i said, it drains by using my desire. On standby, its all right.
Sent from my HTC Desire using xda app-developers app
Lonely_Boz said:
thanks for the answers,
I'm using thalamus kernel, 2.6.35.14_r-stable.
Screen brightness is automatic and i've bought my battery 1-1,5 years ago, original desire battery.
I also have Better Bacttery Stats, by partial wakelocks i have since unplugged:
Activity Manager-Launch with 2m 6s and 318 counts.
Alarm Manager with 1m 7s and 1244 counts.
wifi with 10s and 501 counts
sleep broadcoast with 8s and 460 counts
and other programs.
Since unplugged: 10 h
deep spleep: 8h 7m
Awake: 1h 54m
Screen on: 1h 43m
KWL: 8m 20s
PWL: 6m 9s
İs there all right, and I don't know which programs are these.
and under cpu governor I don't have smartassv2, i have powersave, ondemand, performance. Min CPU frequency 245 MHz, max CPU frequency 998 MHz, and what is smartassv2?
And can you please explain in a bit simple English?
My English isn't good.
Click to expand...
Click to collapse
looks fine, you can see that there is no app keeping the phone awake for very long...max 2m 6s.
smartassV2 is another CPU governor. whether it is better than ondemand will require you to measure the drain for similar activities, though personally i don't think it's worth it.
screen is still meant to consume the most battery as long as you are using the phone, regardless of govenor. no change of rom/kernel/touch screen phone will change this fact.
i can suggest turning off auto brightness and using a lower manual one. have a widget to toggle between low and high when you need to (many in google play).
Thanks for the answer. It is possible, the Battery is defect or it doesn't function well because of his age? Is there an app which measure the battery if it is all right with the battery?
Sent from my HTC Desire using xda app-developers app
theres lots of battery apps in the market but they only really tell ya basic things, health, voltage, battery percent etc.
Sent from my HTC Desire
Well... I've seen things with the same rom, same kernel and different results... mainly due apps keeping the phone awake, but in your scenario is not that bad. I loose 3% overnight with CM 5 MW's version which is awesome, but once i start using my phone.. let me see. I've lost 10% with about 20 minutes of browsing and 20 minutes of gaming... I'm using ManU kernel which is pretty good with battery life, but not compatible with oxygen version of MildWild.
Do a Nandroid backup and try CM version, just to check the differences if you're up to it.
Also, flash ManU kernel afterwards
Let us know if you need help, you have a drain but not awfully bad. However 1% every couple of minutes seems a bit too much .
Well, i don't think that there is a ROM problem. Many people using this ROM have good results than me.
Nevertheless, i will try MW CM 5. After testing i will write here.
I think, there is a battery problem .
Even if it is, you're not spending money without ruling out software issues right?
MidnightDevil said:
Even if it is, you're not spending money without ruling out software issues right?
Click to expand...
Click to collapse
I'm sorry, but unfortunately i didn' understand you what you mean
Well, i tested a lot of ROM's (MW, ICS Nikez Sandvold Oxy) and i've notice that there isn't a kernel or ROM problem, it's just battery problem.
My battery is still working, but it doesn't work well. I've bought the battery 1,5 years ago, and this is my second battery (genuine HTC battery).
I've also problems with my first battery.
I don't know, should i buy a new battery? If yes, which battery do yu suggest, genuine or another?
And i don't have any good experiences with HTC batteries. Perhaps i didn't use the batteries well.
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
Title says it all. is there anything I can do to get better battery life besides the basic turn radios off and brightness down? Thanks.
You could try HoloMusic. It's supposed to be the most energy efficient music app.
warfexion said:
Title says it all. is there anything I can do to get better battery life besides the basic turn radios off and brightness down? Thanks.
Click to expand...
Click to collapse
I use Franco Kernel, and just change the CPU frequencies. I use min 192, and max 500 - great battery life with it!
just connect the phone to charger while listing to music and you wont lose any battery
k786 said:
just connect the phone to charger while listing to music and you wont lose any battery
Click to expand...
Click to collapse
Lol.... do you have like a energy cell to recharge the phone inside your backpack wherever you go no? Thats cool.
Sent from my i9250
Holomusic
Sent from my Galaxy Nexus using xda app-developers app
Hmm guess I'm gonna try out holo music thanks guys.
fpradhan said:
I use Franco Kernel, and just change the CPU frequencies. I use min 192, and max 500 - great battery life with it!
Click to expand...
Click to collapse
Minimum set that low is begging for a sleep of death lvl 99.
Sent from my Galaxy Nexus
Soldier 2.0 said:
Minimum set that low is begging for a sleep of death lvl 99.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Actually, i used 192 as lowest step, 1200mhz as max step for a long time, never seen a sod.
The issue lies in maximum freq for screen off, and the time cpu takes to execute stuff in the background.
Min freq can be 192, np. Just control voltage at that freq.
sent from my i9250
HoloMusic is definitely the way to go, along with custom voltage and cpu settings.