Related
Can someone point me to where I can learn how to use set cpu and set voltage properly. Just installed superotimized kernel and wondering how to take full advantage of it
p4ranoid4ndroid said:
Can someone point me to where I can learn how to use set cpu and set voltage properly. Just installed superotimized kernel and wondering how to take full advantage of it
Click to expand...
Click to collapse
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Dani897 said:
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Click to expand...
Click to collapse
I've been told that undervolting can improve the battery time. Of course, lots of varying opinions of how good/bad it may be to overclock.
If I want to just undervolt, is that possible with SetCPU?
Dani897 said:
overclocking is pre-enabled, under volting can be done through an app the link is in the thread. there are 2 settings. try about -50v each if that works fine bump one down to -75mv at a time. test the phone over a day or two and see how it runs, see if it has sleep death after a few periods of inactivity, especially extended periods, see if it has sleep death while charging, which seems to make a difference that will test the low setting.
see if the phone shuts down without freezing, and see if it shuts down without freezing while charging, the heat in the battery makes a big difference, play some 3d games. if you have freezing issues you can disable overclocking under different situation with set cpu or se t the volts to a more conservative setting.
Click to expand...
Click to collapse
ewingr said:
I've been told that undervolting can improve the battery time. Of course, lots of varying opinions of how good/bad it may be to overclock.
If I want to just undervolt, is that possible with SetCPU?
Click to expand...
Click to collapse
Interesting stuff...
I too would like to know if it is possible to simply under-volt. Does anyone know the optimal settings for SetCpu with the Captivate...or does it vary depending on each users profile/ phones?
So Ive been playing around with various settings for set cpu and voltage control and all has been well so far. The only problem im having is voltage control seems broke. I try to open the all but it just black screens. I tried to clear the memory and unistall and reinstall and still have the same problem. Any ideas?
http://forum.xda-developers.com/attachment.php?attachmentid=432086&d=1288709102
^you can under volt setirons kernel and disable overclocking with this app.
i find my battery life to be less than stock with this kernel, i need to see if it is a common issue, maybe because it is not a captivate kernel. but in the past with unhelpfuls kernel for 2.1 battery life was awesome.
spartan062984 said:
Interesting stuff...
I too would like to know if it is possible to simply under-volt. Does anyone know the optimal settings for SetCpu with the Captivate...or does it vary depending on each users profile/ phones?
Click to expand...
Click to collapse
It's going to depend on the individual CPU in your phone. Your best result is to start at a given clock speed and begin lowering voltage in the smallest step possible, test for stability, repeat until you begin to notice instability (or you just run out of voltage options). You can just undervolt without increasing clock speed any, or you can not undervolt yet raise clock speed, or you can overclock and undervolt, depending on how your particular chip reacts. Some might need additional voltage to stabilize the snapdragon at 1.2Ghz while others (mine for example) is stable Able @ -100mV and 1.2Ghz. Overclocking silicon is the ultimate in YMMV.
Another thing to bear in mind is that increasing clock speed necessarily increases power consumption. There is no way around this. So a chip at 1.2Ghz will use more juice than 1Ghz even with the same voltage. It's difficult to say at this point whether, say, the Snapdragon @ 1.2Ghz and -100mV uses more or less power than the same chip @1Ghz and stock voltage. It's absolutely possible that the former uses more power, which would explain why you see at least one claim here of battery life decreasing even when voltage settings are left untouched.
hawkeyefan said:
It's going to depend on the individual CPU in your phone. Your best result is to start at a given clock speed and begin lowering voltage in the smallest step possible, test for stability, repeat until you begin to notice instability (or you just run out of voltage options). You can just undervolt without increasing clock speed any, or you can not undervolt yet raise clock speed, or you can overclock and undervolt, depending on how your particular chip reacts. Some might need additional voltage to stabilize the snapdragon at 1.2Ghz while others (mine for example) is stable Able @ -100mV and 1.2Ghz. Overclocking silicon is the ultimate in YMMV.
Another thing to bear in mind is that increasing clock speed necessarily increases power consumption. There is no way around this. So a chip at 1.2Ghz will use more juice than 1Ghz even with the same voltage. It's difficult to say at this point whether, say, the Snapdragon @ 1.2Ghz and -100mV uses more or less power than the same chip @1Ghz and stock voltage. It's absolutely possible that the former uses more power, which would explain why you see at least one claim here of battery life decreasing even when voltage settings are left untouched.
Click to expand...
Click to collapse
Thanks for clarifying Hawkeye! I will report back on in a few days once i have tested out a few profiles. In my opinion, I feel that it is best to leave Over-clocking at default and maximize battery utilization with setcpu. However, the thought of over-clocking the Dragon beast is VERY tempting. Who wouldn't? I will definitely check out the differences when playing games and such.
spartan062984 said:
Thanks for clarifying Hawkeye! I will report back on in a few days once i have tested out a few profiles. In my opinion, I feel that it is best to leave Over-clocking at default and maximize battery utilization with setcpu. However, the thought of over-clocking the Dragon beast is VERY tempting. Who wouldn't? I will definitely check out the differences when playing games and such.
Click to expand...
Click to collapse
I have to tell you, I'm not personally very fond of SetCPU on this device, even though I paid for the app (ugh). With raspdeep's voltage control app and SetIron's OC/UV kernel, the CPU defaults to 1.2Ghz at stock voltage, which for a basic setup is fine. Voltage Control app is phenomenal for adjusting in increments of 25mv at a time...one setting is for high clocks (1Ghz - 1.2Ghz) and the other is for < 1Ghz. It's probably best actually to start with the lower clock setting in Voltage Control, as your phone will spend the lion's share of it's time at those clocks and so that is where you should see the most gain in battery life. My only gripe is that I can't get the boot settings to stick on the Captivate so I have to go in and adjust them each time I reboot the phone. no biggie there.
SetCPU, on the other hand, has caused me loads of problems in the past, including causing the phone not to wake up from sleep and just atrocious battery life, I assume from constantly polling the CPU clock to measure clock speed. I have not experienced any of that with Overclock Widget, but I also don't use any of the independent clockspeed controls in the app...basically it's just a widget to display clock speed the way I use it. Otherwise, Setiron's kernel gives the 200mhz overclock and I just let the Hummingbird deal with changing clocks on its own. Jmo, but it works for me with no resulting battery drain beyond the additional I expect as a result of the extra 200mhz.
edit: whoops, long day. hummingbird in my post from above, not snapdragon. I need a drinky poo.
hawkeyefan said:
I have to tell you, I'm not personally very fond of SetCPU on this device, even though I paid for the app (ugh). With raspdeep's voltage control app and SetIron's OC/UV kernel, the CPU defaults to 1.2Ghz at stock voltage, which for a basic setup is fine. Voltage Control app is phenomenal for adjusting in increments of 25mv at a time...one setting is for high clocks (1Ghz - 1.2Ghz) and the other is for < 1Ghz. It's probably best actually to start with the lower clock setting in Voltage Control, as your phone will spend the lion's share of it's time at those clocks and so that is where you should see the most gain in battery life. My only gripe is that I can't get the boot settings to stick on the Captivate so I have to go in and adjust them each time I reboot the phone. no biggie there.
SetCPU, on the other hand, has caused me loads of problems in the past, including causing the phone not to wake up from sleep and just atrocious battery life, I assume from constantly polling the CPU clock to measure clock speed. I have not experienced any of that with Overclock Widget, but I also don't use any of the independent clockspeed controls in the app...basically it's just a widget to display clock speed the way I use it. Otherwise, Setiron's kernel gives the 200mhz overclock and I just let the Hummingbird deal with changing clocks on its own. Jmo, but it works for me with no resulting battery drain beyond the additional I expect as a result of the extra 200mhz.
edit: whoops, long day. hummingbird in my post from above, not snapdragon. I need a drinky poo.
Click to expand...
Click to collapse
LOL. No Worries. I myself made the same mistake. I thought something was odd with my post. SnapDragon...Hummingbird....Bulbasaur.....I knew what you meant. lol
Still not having any luck with the voltage control app. Ive tried flashing different roms to see if it would work. I undervolted it to 100/75 the first time i did it and now i cant change. Only a little worried
i guess there was an issue with the set on boot scripts not working. supposedly that is fixed, i dont know for sure though, i haven't updated.
From what I'm gathering, in order to undervolt, you must have a kernel to su pport that, for example Setirons.
I'm not necessarily interested in overclocking, as it performs well as is. Of course there are arguments that overclocking may ultimately harm the phone, and arguments that by the time that happens, you'd be ready for a new phone. In any event, if I start getting slower, I may interest in overclocking.
Does anyone know if dramatic improvement in battery performance with underclocking?
I've noticed quite a bit of a difference, just pretty difficult to tune it precisely. (Coming from a person who enjoys overclocking computers a little too much). I just wish there was an app that would test each frequency and then let you know which one failed (without having to manually set it).
How can I go about overclocking my droid charge? I am running TWEAKSTOCK 1.0 rom and was wondering how to overclock my charge?
I haven't seen any over clockable kernels so until then I don't think you can.
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Chitala383 said:
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
With the same kernel?
Well, if you actually searched, this would be clearly stated in many threads.
For GB overclocking, use Tegrak for now, until we can get an actual OC kernel up and running. I think Tegrak will work on the stock kernel as long as you're rooted, as it uses a module to modify the CPU frequency.
Sent from my SCH-I510 using xda premium
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
xdadevnube said:
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
BattsNotIncld said:
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
Click to expand...
Click to collapse
Take what I say with a grain of sand, I'm expressing my views without much scientific validation.
Keep in mind that overclocking is like icing on the cake. There are far more beneficial things like changing the scheduler to noop or deadline. Fugu tweaks and V-6 are highly recommended to improve responsiveness and improve your launcher resiliency. That said, I feel overclocking has its place and helps in many cases. I've noticed, in general, various tasks and some web-browsing will benefit from the increased clock speed. Some things don't ramp up the CPU very much and you won't notice much difference in that case.
I monitor my CPU usage with CPUNotify as well as OS Monitor.
I monitor the CPU temps with TempMonitor (it allows for a notifcation icon that shows the CPU temp.)
I use StabilityTest to check for overclock settings stability. The cool thing about Tegrak is that when you apply overclock settings on boot (paid version only) and you choose settings that crash the phone, the settings don't apply until most of the phone is already booted up, so you aren't stuck in an infinite boot loop of crashing fun. You should be able to simply change up the settings after they apply since the phone will be mostly idle by the time Tegrak settings are applied.
As for settings...
I use the Interactive X governor. I prefer this governor for its simplicity and ability to ramp up to high CPU clock speeds quickly. I enable the governor by typeing "su" and "ix enable" in Terminal Emulator when on Imoseyon's 4.0 kernel.
I change the "scaling min" to 200Mhz to avoid instability when CPU usage ramps down quickly.
Currently at CPU Level 0 I am at 1265mv Core Voltage, 1100mV (unchanged) Internal Voltage, and 1200 Mhz Frequency.
I don't actually change other CPU Levels.
Lately I've been just keeping at eye on temps so I haven't achieved my desired clock speed of a relatively low-voltage 1.4Ghz to 1.5Ghz.
Overclocking is very dependent on the particular sample you get. Some of us have "Golden Chips" and some of us have duds.
Your CPU should be totally safe at temps around 130 degrees F, although I suspect that it could even take higher sustained temps well above that if it needed. I don't actually know, this is speculation.
I like to keep my temps low in general, I rarely crack 100F with my current settings (weather is cool here.)
Overclocking computers is one of my hobbies, and its fun to dive into the phone side of things. I haven't been able to find a whole lot of information regarding overclocking the Hummingbird processor. People have overclocked to 1.6Ghz. Stability tests are essential to improve the reliability of your overclock. Die hards will run the tests for 24 hours to weeks in the computer realm. At least with computers its better understood how the stability test actually works. I run 24 hours of Orthos blend mode (Prime95) on each core.
With phones, its hard to say if it will truly be stable.
I test for an hour on the phone with StabilityTest and call it good. Hopefully in the future more information will come to light regarding how to properly overclock.
Remember, the other side of the coin is underclocking and undervolting. If you drop your voltage, you should see a nice increaes in battery life. If you drop your clocks, then you can drop your voltage even more. If you get your phone dialed in to where there isn't much background apps sucking juice- a phone that is UV/UC'ed should have excellent battery life.
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
kvswim said:
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
xdadevnube said:
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
Click to expand...
Click to collapse
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
kvswim said:
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
xdadevnube said:
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
Click to expand...
Click to collapse
Probably because no one has taken the time to write one. Not exactly in high demand. I knew of one "guide" but the site has been down for quite some time.
Of course there are noobs guides but nothing quite in depth. I suppose people don't write them because there are obvious limits set by the kernel dev, and anything beyond that requires someone who obviously knows what they're doing, which defeats they purpose of a guide.
Sent from my GT-P1000 using xda premium
This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk
that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.
Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.
On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.
This is my third time typing this... (This website should really have an auto-save draft feature)
I recently installed the application "CPU Tuner" because I've always wanted to utilize my newly rooted phone. The phone is running Cyanogenmod 7.2 Stable, and currently overclocked at 1.5GHz. My main concern is overclocking my phone that high. Now, I didn't really choose that option, SetCPU automatically set it to that when it loaded a configuration. I'm a beginner to overclocking, and this is my first time doing it for anything. I've heard rumors of people melting their processors from overclocking it, so I want to know if it's okay if its overclocked to roughly twice the stock frequency of 800MHz. If it IS safe, then why isn't the phone automatically set to 1GHz to compare to it's twin, the Evo 4G? Or perhaps even 1.2GHz to surpass it? I would definitely be satisfied with 1.2GHz, but I wouldn't mind having 1.5GHz if it was stable and didn't drain the battery. On to the next question, would an OC this high cause instability and/or would it drain my battery? I only overclocked an hour ago, so I haven't experienced any problems whatsoever... yet. On to the profiles... I'd like some suggestions for improving my triggers. Right now, it set everything up to the highest frequency, but looking at the help, it said to not touch the frequency, but experiment with thresholds. In the Help, it doesn't tell you what the thresholds are, and what they do, and more importantly, how they work. It just shows that the highest is the most battery saving. I would have thought the lower the better, but... Anyway, if you could tell me, I'd be highly appreciated it. Finally, the battery temperature... It has an option to enable a setting to change profiles if the battery gets a certain temperature, but I'd like to know what would be considered "Overheating". I get paranoid when the battery temperature gets a little warm at around 36 Celsius... but the profile it switches to is supposed to really slow down the CPU to preserve battery, so I'd really rather not use it unless it's necessary. So, would 45 - 50 Celsius do, or should I set it a bit lower? My battery is 4000+ mV, if that'd help at all. If you know any sources that you can direct me to that would answer my questions, it'd be highly appreciated.
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
prboy1969 said:
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
Click to expand...
Click to collapse
Thanks for the response. It's pretty late, so I've bookmarked the link to read tomorrow. Alright, so 45 degrees Celsius should the maximum then. I've been thinking of switching over to SetCPU, since there are more comprehensive guides than for CPU Tuner (In which no one seems to have heard about), and it doesn't seem that the settings it set will be ideal for the long run. Although, before I switch over to SetCPU, I want to at least give it a shot. I'll change my settings so that the frequency decreases depending on battery level. Also, I don't have much but the basic governors and configurations on CPU Tuner, so I've never heard of Smartass V2 (Prior to skimming through the link you posted). Also, the battery came with it, I knew it seemed a bit different from most other batteries (From what I've seen in searches, most of them had around 2000), but I didn't know it meant that much.
The Governor settings available will depend on the Kernel, not on the CPU Controller. I've always been partial to SetCPU, but that's just me. I would again suggest doing a bit of reading, and experimentation to find your best settings. But defiantly the closer to normal the Battery temperature is the better. When the Battery heats up to much it will in most cases also drain faster. If you can post a Pic of the Battery I would really like to see it. I've never come across a 400mAh Battery for the Shift.
When I first rooted my shift 2 years ago I was very concerned of over-heating. I constantly checked the temperature. After a while I realized it is quite hard to over heat and cause damage, especially with the newest kernels the devs have put out. Just experiment with different settings and see what works best for your phone
Sent from my PG06100 using xda app-developers app
Hello,
I've a question regarding clockspeeds. Since yesterday i rooted my tab, as an early adaptor i experienced the lagging, heat failures etc. Since the JB update i've the feeling that the cpu doesn't run on max speed, also scaling the other cpu's is not as fast...
I downloaded several cpu monitoring apps, i found out my cpu never reaches 1.4Ghz. Max is 1,3Ghz, i don't know of thats for real or a bug in the monitoring code. But several apps have showed this, ex system tuner, also i found out that almost never the fourth cpu comes on. I'm not an excesif gamer, but for the test i played asphalt 7 and nfs shift.
Do you guys have an idea how to solve/tune? I already flashed the Vorbeth GPU OC (Thanks!:good but i wasn't able to find any more kernels or CPU mods.
To me its very very annoying that have a quad, but scaling very very conservative (I don't care about battery), i just want to ramp up and use all the cpu's hence i'm a multitasker.
Overall, i've the "feeling" that the heat issues are solved by using a very very conservative governer and not scaling max. Maybe i'm totally wrong, and i would be happy to hear that. Right now i feel kinda screwed.. by acer.
edit: Sorry for posting in general, i realize i've should post in QA
power saving level "balanced" is 1.3ghz, "High Performance" is 1.4ghz. It got introduced with an update. So your monitoring app is correct.
It could be possible to clock the A700 to 1.5ghz, but I wouldn't go higher since it's already getting hot enough on high CPU usage.
nex86 said:
power saving level "balanced" is 1.3ghz, "High Performance" is 1.4ghz. It got introduced with an update. So your monitoring app is correct.
It could be possible to clock the A700 to 1.5ghz, but I wouldn't go higher since it's already getting hot enough on high CPU usage.
Click to expand...
Click to collapse
Thanks, however i've always turned high performance on. I forgot to mention, but aslo during testing.