Related
Hi anyone who use this soft for under/overclocking your BA ?
What settings do you use ?
Do you notice a difference ?
When undercloking does the battery last much longer ?
Please tell me all i have to know
Thanx
you will find overclocking does make a noticeable difference to performance, admittedly its not huge but it is a decent improvement.
unclocking is wonderful and has significantly improved battery life for me, can go for over 24 hours on and off usage including some BT and WIFI usage.
during experimentation i have tried most of the speed settings. currently i am using six different speeds for my scaling gears.
CPU RAM PXBus
149 100 50
199 100 100
299 100 100
398 100 100
498 100 100
597 100 100
I find that 4-6 gears is the best number to use, any less and you don't get enough range, any more and there are too many screen flickers and jumps as it has to change speed all the time.
The default scaling settings are quite good, that is the cpu usage percentages that are set for increasing and decreasing the gear. However since i have a car charger and am at home a lot i have changed my settings so that it increases gear faster to gain better performance (altho this does use marginally more battery life). My current settings are:
Scale down trigger 30%
Scale up trigger 45%
Scale Max trigger 70%
Hi, I'm a noob to undervolting here (just rooted and flashed Vanilla Froyo to my Defy a week ago, and I'm hoping to squeeze out as much battery life as I can); just some quick questions about undervolting that I haven't found answers to in other threads:
1) What exactly is "vsel" and how does it relate to the actual battery voltage? For example, even though I've changed the maximum voltage in setvsel and Milestone Overclock (down to about 45 vsel at 800 Mhz so far, haven't tried lower), the battery voltage reported by Spare Parts is still reading between 3800 mV and 4000 mV. Does this mean that setvsel/milestone aren't working or does a ~30% decrease in vsel *not* equal a 30% decrease in battery voltage?
2) If anyone else has undervolted their Defy, can they testify as to what kind of battery life improvements they've gotten? I've heard that custom ROMs are already fairly undervolted
If laptops are anything to go by.. laptops can be undervolted to make them run less hot, thereby extending their life. Though battery life is increased too, this increase is virtually negligible.
Since the limits of undervolting (and over/underclocking), are done on a per-cpu/gpu basis for computers, because they are not all exactly the same and may not work with the same non-default values, I think it's a bad idea to assume that phones will run without problems when using values only tested by people with a phone that is not yours.
If you want to undervolt/over- or underclock, test your device, find out the lowest/highest values and then inrease or decrease that value, to have a safety margin, do not copy someone elses' settings.
A common issue with undervolting on 2.1 (at least with me on 2.1) is that if the minimum clock speed is below 300 mhz, it takes around 3-5 sec to actually respond to incomming call on your defy when defy is on stand-by mode.
Undervolting + Ondemand made my battery work at 23ºC vs +29ºC
I did not wrote down numbers, but battery life increased AT LEAST in 8 hours.
My values
vsel 1; 18 -300
vsel 2; 33 - 600
vsel 3; 43 - 800
(-15 points each value VS factory values)
Removing bloatware, root apps, autostart at boot apps, widgets (they autostart too) etc. or freezing them with "antitek app manager"
Decreased phone memory ussage from 140Mib to 80Mib; Also decreased cpu ussage from 10%-15% average idle to just 1%-5%
Apps / Widgets / Many System preinstalled apps, are autoloaded when phone is turned on, and they run 24/7. waste of resources and app auto killers just aren't good enough, coz apps reload themselves, you have to remove them or freeze them.
fortunely modders are realeasing their custom roms with most of this optimizations
45 vsel
using milestone oc I got 1ghz @ 45vsel from the day I got it I have owned the device for 1 1/2 months now not one single problem but it depends from device to device I must have a bin'd cpu
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)
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
hshaikh said:
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
Click to expand...
Click to collapse
I suggest to decrease your max CPU until you feel it affects performance too much. You can also try switching to a governor less aggressive than interactive (try ondemand).
Don't expect magic though. I've played with decreasing max CPU clock, max CPU screen off, governor settings etc with three different kernels. Gathered stats for at least one week each time. Never noticed a difference large enough to actually matter to me. For maximizing battery life, you can gain more by hunting apps that cause a lot of (partial) wakelocks and alarms, and use low screen brightness.
hshaikh said:
and screen off max is 384.
with all that information, what do you suggest?
Click to expand...
Click to collapse
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Darunion said:
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Click to expand...
Click to collapse
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Petrovski80 said:
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Click to expand...
Click to collapse
you are correct. there is a magic middle ground because power consumption doesnt scale in a linear way. but finding that spot would take massive testing and even getting to the center, would still probably only gain about 10-15mins average use on a battery charge :/
bk201doesntexist said:
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
Click to expand...
Click to collapse
what speed show i set to max when screen is off.
did you read anything that Darunion and Petrovski80 wrote? I keep mine at it's max, i don't care, i don't live in the woods with no electricity.
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
hshaikh said:
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
Click to expand...
Click to collapse
Exactly. I get similar performance.
Sent from my Galaxy Nexus using Tapatalk 2
I do the following to get my phone to last a full day and sometimes more i use battery guru as well as advanced task kill i have auto kill on in advanced task killer and have it set to aggressive every 30 minutes to kill all background tasks. make sure in battery guru u have low power mode on. greenify also saves huge amounts of battery but root is required. also my fave app i use is android tuner i change my cpu governors to on demand and have all four cores running at GHz this saves the most battery i have noticed and my phone never over heats ever good luck to those out there
I have big problems with Battery Overheating.
I'll try and report back
dragonmhawk said:
I do the following to get my phone to last a full day and sometimes more i use battery guru as well as advanced task kill i have auto kill on in advanced task killer and have it set to aggressive every 30 minutes to kill all background tasks. make sure in battery guru u have low power mode on. greenify also saves huge amounts of battery but root is required. also my fave app i use is android tuner i change my cpu governors to on demand and have all four cores running at GHz this saves the most battery i have noticed and my phone never over heats ever good luck to those out there
Click to expand...
Click to collapse
So, what you're basically saying is you're aggressively patrolling your tasks, and reducing the cpu speed down to 1ghz max?
How responsive does your phone stay after reducing your speed?
My phone is the same because I have all four cores of the cpu running at a max of 1ghz ondemand for the governor of each core. this enables less overheating and easier multitasking with all four cores running and less demand on the other cores so the cpu is also able to last longer cause no cores will burn out as fast as say having only one or two cores of the cpu running because the phone doesnt get as hot as it does with less cores running. so I get a huge improvement in the responsiveness because of this phone has never gone over 35 degrees celcius since ive been doing all this
dragonmhawk said:
My phone is the same because I have all four cores of the cpu running at a max of 1ghz ondemand for the governor of each core. this enables less overheating and easier multitasking with all four cores running and less demand on the other cores so the cpu is also able to last longer cause no cores will burn out as fast as say having only one or two cores of the cpu running because the phone doesnt get as hot as it does with less cores running. so I get a huge improvement in the responsiveness because of this phone has never gone over 35 degrees celcius since ive been doing all this
Click to expand...
Click to collapse
I'll give it a try...
this works with any rooted phone actually with the xperia zl ive had 15 hour battery life with heavy use. just got a nexus 5 so ive upgraded got just over 24 hours of battery since i charged it last night at 10 pm
dragonmhawk said:
I do the following to get my phone to last a full day and sometimes more i use battery guru as well as advanced task kill i have auto kill on in advanced task killer and have it set to aggressive every 30 minutes to kill all background tasks. make sure in battery guru u have low power mode on. greenify also saves huge amounts of battery but root is required. also my fave app i use is android tuner i change my cpu governors to on demand and have all four cores running at GHz this saves the most battery i have noticed and my phone never over heats ever good luck to those out there
Click to expand...
Click to collapse
How to set "all four cores running"? Is it by enabling multi-processor control on? Sorry nubie question
renzzoman said:
How to set "all four cores running"? Is it by enabling multi-processor control on? Sorry nubie question
Click to expand...
Click to collapse
Toggle between online and ofline in the right side..
Sent from my C6502 using xda app-developers app