Related
I do it on my laptop, was wondering if I can do it on my phone to save power?
I looked aound a bit and everyone seems vey focused on overcloking. I don't have a problem with the 1Ghz speed, was ust wondering if I can stay at that speed and save some juice and if it' safe.
Yes you can. Get one of the apps off the market either unstable apps or jrummy. I use the unstable version to under clock from stock down to values of 50, 43, 36, 25. Which is quite a lot lower I think.
Sent from my DROIDX using XDA App
The apps are only .99 -so you can't go wrong with 'em. But I like learning this stuff and tinkering. So you may have already checked out this thread...
http://forum.xda-developers.com/showthread.php?t=812749
It is about overclocking- but you can use the same information to underclock. You just need the overclock.ko file and then adjust the setscaling.sh file so that it uses lower vsels.
I did a little write up in that thread...
http://forum.xda-developers.com/showpost.php?p=8771591&postcount=43
so if you want to check into- once you fool around with it a bit- it is not that hard. I now actually have 3 scripts I can run. 1 for stock clock speeds undervolted. 1 for stock speed stock voltage. and 1 for high voltage clocked to 1.3mhz.
good luck.
it has definitely been a great mod to my phone. I'm running stock speeds and ULV. Battery life has been phenomenal.
Aggie12 said:
it has definitely been a great mod to my phone. I'm running stock speeds and ULV. Battery life has been phenomenal.
Click to expand...
Click to collapse
Care to post the file you are using?
Sent from my DROIDX using XDA App
The stock vsel is 56, right? I've tried going down to 54 and the stress test in set CPU goes well for 5 minutes. At some point between 5 and 10 minutes I get an error.
Is that normal and I should go with 54 or should the test last a lot longer without an error? Or is the stock vsel higher?
Sent from my DROIDX using XDA App
coolj478 said:
The stock vsel is 56, right? I've tried going down to 54 and the stress test in set CPU goes well for 5 minutes. At some point between 5 and 10 minutes I get an error.
Is that normal and I should go with 54 or should the test last a lot longer without an error? Or is the stock vsel higher?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
58, 44, 33, 27 are my vsel values oc'd to 1.125. Any higher oc will slow me down to a crawl.
To answer your question, I think stock vsel is 62 on Froyo.
I have been running the Ultra low voltage 1.3ghz preset from jrummy's app for a couple of weeks now with zero stability problems. Improved my battery by about 15-20 percent. I have seen warnings about stability with ultra low voltage but I guess I got lucky. Low 18's in Linpack and upper 1600 quadrants.
@aggie12 Care to share your vsel numbers? Im doing the same stock cpu speed just undervolted but I have hardly noticed a difference in battery life. How many hrs does your phone last in average use?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I typically get 36 hours before I get nervous at 20%. This is without juice defender, just straight 1ghz use on regular battery manager
From my Droid X with love...
@aggie12 Care to share your vsel numbers? Im doing the same stock cpu speed just undervolted but I have hardly noticed a difference in battery life. How many hrs does your phone last in average use?
Sent from my DROIDX using XDA App
Daali said:
I typically get 36 hours before I get nervous at 20%. This is without juice defender, just straight 1ghz use on regular battery manager
From my Droid X with love...
Click to expand...
Click to collapse
How is 36s hours even possible? I get around 10-12 hours of use, but I'm a heavy phone user...
Also, is it possible to undervolt using setCPU?
DawidD said:
How is 36s hours even possible? I get around 10-12 hours of use, but I'm a heavy phone user...
Also, is it possible to undervolt using setCPU?
Click to expand...
Click to collapse
No- set cpu only adjust your clock speeds- not the amount of power the phone is drawing to obtain those speeds. The .99 apps will allow for undervolting though. Or if you do a little study on the OverClock thread- it is not to hard to do with a script.
@Daali What are your vsel numbers? Mine are:
1ghz/45vsel
800/40
600/30
300/18
I get only 12 hrs of heavy use.
Sent from my DROIDX using XDA App
^^ siphen^^i just set this i'll start my test 2/marrow after I unplug for the day. I have extended battery mild user mainly txt/mms/no more than 30 min a day calling but i do surf sites quite often and wifi is on 24/7 as I have it at work and home> i'll let you know how those work for me.
I have the latest cyanogen mod. I am new t overclocking. Can u tell me about it? Like what it is and how to do it safely
Sent from my Liberty using XDA App
changes the limits for the processor speed. I believe that the aria is limited to 600 mhz....I set mine to min 245 max 825 on demand, which means when the phone needs it, it will increase and I'm fine. makes the phone run smoother.
I also use it to save battery. for example when I'm at work and had forgotten to charge the phone, I limit it really low...makes the phone run like ****, but it saves the battery.
So I downloaded the DX/D2 Overclock app from the market, but I don't really know what to set it to. I'm a heavy texted that uses a bit of 3G. Not a lot of gaming, the most I do is Angry Birds or a GameBoy emulator.
Based on that information, what would be some good overclock values for me to set?
Sent from my DROID2 using XDA App
personally, i would set it at a medium voltage with the scaling govenor on performance and the scaling bars set to max 1000 and min whatever you like....i keep it at 1000/1000 but battery is costly
Chiggins said:
So I downloaded the DX/D2 Overclock app from the market, but I don't really know what to set it to. I'm a heavy texted that uses a bit of 3G. Not a lot of gaming, the most I do is Angry Birds or a GameBoy emulator.
Based on that information, what would be some good overclock values for me to set?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
If you want to overclock I use the 1.25 low voltage.
After seeing this thread I got the app and I'm at 1.15 ulta low voltage. Voltage is similar to stock.
Stock. Overclock
Slot 1 - 400Mhz 33v 400Mhz 36v
Slot 2 - 600Mhz 48v 700Mhz 51v
Slot 3 - 800Mhz 58v 900Mhz 56v
Slot 4 - 1000Mhz 62v 1150Mhz 62v
Not a massive increase in speed but still noticeable. Hopefully keeping the voltage close will help prevent overheating. Probably stay at 1.15 for a few days to see how everything goes. If it's stable and doesn't overheat and depending on how it affects battery life I might crank it up and see how it goes.
Sent from my DROID2 using XDA App
I run 1.35ghz low voltage. Rock solid and no heat issues.
As long as you don't set it to boot with untested settings you should be fine experimenting. I tweak settings and run quadrant to check for performance. Trial and error.
Sender: rooted D2, fission 2.1, 1.35g lv, R2D2 lock and boot
First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App
Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.
My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.
Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App
Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!
Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.
If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1
I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App
Never messed with these settings before and couldn't find anything with a search so if someone could explain for me to easily understand please
How do go_hispeed_load and hispeed_freq work exactly (what do they do)? I'd love to learn so I can start messing with these settings
Thanks everyone.
Sent from my Nexus 4 using xda premium
I think go_hispeed_load is the value that the CPU load has to reach before it ramps up to the Max CPU speed set. I think hispeed_freq is the clock speed used mainly before the load set in go_hispeed_load is reached I think.
I'm running Franco #22 and I've set
go_hispeed_load to 918 and hispeed_freq to 75 butter smooth running code fire x ROM and Max CPU to 1216
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
I think go_hispeed_load is the value that the CPU load has to reach before it ramps up to the Max CPU speed set. I think hispeed_freq is the clock speed used mainly before the load set in go_hispeed_load is reached I think.
I'm running Franco #22 and I've set
go_hispeed_load to 918 and hispeed_freq to 75 butter smooth running code fire x ROM and Max CPU to 1216
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah, that gives me a better understanding. So the phone will be running in the hispeed_freq before it reaches the load where it has to ramp up some more to handle the task, right? Can you explain to me how load works? Like how do you calculate how the load number adds up? (to your 75 for example)
Ngo93 said:
Ah, that gives me a better understanding. So the phone will be running in the hispeed_freq before it reaches the load where it has to ramp up some more to handle the task, right? Can you explain to me how load works? Like how do you calculate how the load number adds up? (to your 75 for example)
Click to expand...
Click to collapse
Yeah that's right. I'm not too sure the load value scale to be honest but Franco recommended 70 and a lot of users are stating that 75 is good (and in theory should save more battery life as you will use the higher frequencies less often). So its up to you
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
Yeah that's right. I'm not too sure the load value scale to be honest but Franco recommended 70 and a lot of users are stating that 75 is good (and in theory should save more battery life as you will use the higher frequencies less often). So its up to you
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your input, always learning something new everyday
So in essence a lower hispeed_freq is better to conserve battery as is a higher go_hispeed_load? And then just to find a good balance between the two to maintain smoothness, correct?
Ngo93 said:
Thanks for your input, always learning something new everyday
So in essence a lower hispeed_freq is better to conserve battery as is a higher go_hispeed_load? And then just to find a good balance between the two to maintain smoothness, correct?
Click to expand...
Click to collapse
I think any lower than 918 might be too laggy, I would suggest to stick to 918/75 for smoothness and good battery life. A bit off topic but I'm using these settings with code fire x ROM and I am getting unbelievable battery life (and this is not just me). I'm currently on track for over 6 hours screen on time!
Sent from my Nexus 4 using xda premium
samwebbo1990 said:
I think any lower than 918 might be too laggy, I would suggest to stick to 918/75 for smoothness and good battery life. A bit off topic but I'm using these settings with code fire x ROM and I am getting unbelievable battery life (and this is not just me). I'm currently on track for over 6 hours screen on time!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Wow that's nice! I hear a lot about that ROM too, I am sure to give it a spin in the future
Time to start tweaking some settings ^_^
read this thread about governor and all things related.
http://forum.xda-developers.com/showthread.php?t=1369817
i have franco kernel at hispeed freq at 810 and load at 60 max freq is at 1134mhz
i thought the load is in percentage ?, if i have it higher at that clock there is a delay in performance,