I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
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.
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?
How safe is it to overclock my Galaxy S II to 1.78 max and 1.78 min?
If not, what combination of max and min would be most safe but still give a noticeably boost in speed.
In theory overclocking isn't that good as is adding additional strain to the CPU than it was designed to.this will cause wear and tear faster possibly shortening the life of your phone. I would set your min much lower and place it on demand. There's no need for your CPU to be running at max all the time, set it on demand do it only runs at a faster speed when it's needed to...
PS this has been covered in other threads a search would have given you an answer oppose to starting another thread.
Sent from my SGH-T989 using XDA App
Voltage kills components, not overclocking.
You can google this and research it if you would like.
I keep mine min 810 max 1782 ondemand with setcpu.
810 is more than enough(still faster than Iphone4) to hold its own without lag when you actually start to bog it down.
I think the max itll go is 1.83ghz. in reality nothing over 1.65ish really adds anything.
Sent from my SGH-T989 using XDA App
locked mine at 1.51ghz which is plenty of fast, no throttling and no lag
Setting the min up that high will kill your battery in hours. You can over clock it by setting the max up to whatever you like. Set the min lower. Then set your governor. Overclocking will wear down your cpu faster and make it run hotter. Overvolting will do the same. I would only overclock when I need it. Normally mine is set at 1.5 for max and .3-.5 for min.
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.
Have a question regarding min CPU speed vs voltage. I run task's Roman with stock kernel. My phone is not stable unless I up the voltage on the CPU clock at both the 189 and 378 speeds to 925mv.
So here's the question... since both speeds use 925mv, wouldn't it make more sense just to leave the min CPU speed at 378? Seems to me the faster min speed would process faster allowing the phone to go into deep sleep faster and saving battery.
Thoughts?
192 and 384, you mean?
Personally, I prefer my min at 192 not cos of mV difference, but cos it keeps my phone lots cooler when at min speeds.
I asked a similar question with no response. mine goes down to 81mhz and stays stable but a higher clock speed uses the same voltage so I thought just run the higher one. unless deep sleep is consistent then it shouldnt matter. but for cases like bluetooth or music streaming the higher speed might seem better. but the more heat thing must cause more battery usage I would think
s384 said:
I asked a similar question with no response.....
....more heat thing must cause more battery usage I would think
Click to expand...
Click to collapse
Looks like some thread lost with time...
More heat isn't good... heat is nothing but energy dissipated... and that means energy lost... So more heat is an indicator that you are kinda pushing your CPU to work hard and harder the work, more the battery utilized.
The voltage consumption of a CPU is calculated by f*V^2. So to answer the question, even if two frequencies share the same voltage, the lower frequency will still consume less power than the higher frequency.
Sent from my SGH-I747 using xda app-developers app