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).
I am loving my Android experience so far coming from and iPhone 4. I am running LeeDroid and have been playing around a lot with SetCPU. At this time, I am not concerned about battery as of yet. I am asking this question in regard to optimal, blazing fast performance with minimal hiccups.
I have done Quadrant testing at various min/max CPU levels. I had excellent results at 1804 high 904 min. However I had to yank the battery after not being able to unlock the device.
For profiles, real basic, again I am not concerned about battery charge life ATM. I have it set to revert to stock performace (1036/245) if the battery temp reaches 100F.
With the screen locked, I have it set to 499/245. All of my settings are using the "ondemand".
I would like to know what an ideal minimum is for PERFORMANCE as well as ideal max (1804? Highest might not always be fastest?). I got amazing results with Quadrant full benchmark with settings of 1804/499. This also caused a lockup when trying to unlock the device though. Maybe because there was a conflict with my lockscreen max setting? I would think the app would put priority to the lock profile though.
Also, does this phone have a built in CPU temperature sensor that I could utilize with a CPU temp widget?
Thanks for reading my lengthy ramblings.
Ray
Not all Processors are created equal and therefore some can OC to 1900+ and some cant overclock at all. Most will be in between. Sounds like you are over doing it. I clock mine to about 1400 when charging. I have had it to 1700 without an issue at all, but I don't find a need to be faster then 1400. When screen is off I actually tell it to go to 250MHz. Sometimes its alittle slow to "wake". But it saves mucho battery. When just on battery I am running at about 1250. Been this way for about 3 weeks. Not an issue.
I have never had to yank my battery and quite frankly if I did I would never run it that high again. You are going to burn it up running it at that speed. Nothing over 1500 for extended periods. 1800+ for showing off maybe? But that's kinda dumb too.
I have not read about any built in temp thing so can't really answer that.
I don't know what kind of power hungry apps you guys are running, but I run mine underclocked to 906MHz. Snappy as ever.
either with setcpu or voltage control...would someone care to just explain how to use these apps.
I understand the governers, and I understand the min / max.
So If I bump that max up to 1400 or even 1600 and leave the minimum down...what exactly does that do?
If paired with on demand does it mean it will use as much processor as it needs to perform a task all the way up to the max of what I have it set to?
also, the thing that seems to confuse me mostly are the individual sliders you can adjust per frequency.
I know this is broad question, but I was just hoping someone wouldnt mind explaining this to me as best as possible...or at least dumb it down for me.
I have googled and searched, and really havent found clear answers to me personally to understand it.
thanks
I personally use voltage control extreme.
In regards to the individual sliders you speak of, I believe that those control how many volts the phone uses at each particular frequency. You don't want to turn the voltages down too low/high though because you can freeze your phone and have other problems.
I use the "conservative" governor and seem to get the best battery life with it.
By overclocking to 1400 or 1600 it allows for your phone to run applications, videos, etc. smoother, by using the remaining cpu capabilities of the phone's hardware. The drawbacks of overclocking are that it sucks the battery very quickly, it can cause the cpu to overheat, and can also decrease the life of the processor.
Hope that helps some!
So what is a safe top end? To run on a daily basis.
Sent from my SAMSUNG-SGH-I997 using XDA App
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App
Perpetrator said:
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App[/QUO
But doesn't overclocking cause the phone to heat up? I suppose it also depends on what temperature the phone is rated to safely run at too though doesn't it? Cause with increased temperatures I am pretty sure the processor's life could be impacted. But that is probably only if you overclock for a extended period of time.
I would suggest staying at 1.2 for daily use, but if you are doing something that requires a little more cpu you can just bump it up until you don't need it anymore.
Just my 2 cents worth.
Click to expand...
Click to collapse
I know that some ppl OC to 1.6 with ondemand gov and use that as a stable setting... others report problems, FCs, ... think it depends on individual phone.
Some stay at 1.4 to be cautious...
The UV section is where I hear a lot of dissenting opinion. Some say -100 across the board gives best battery/stability... others say voltage should be high toward 1600 and UV more as you approach lower frequencies... personally I find that a graduated setup is best but I am not an expert.
Just sayin' what I've read here.
I saw. 3 kernel.
Slightly. Uv
Midle. Uv
Extremely. Uv
What are the differences. Between. Those. ????
Sent from my myTouch_4G_Slide using xda premium
Saw that too - exciting!
UV is undervolt, which means running the device with less voltage (electricity). Uses less juice, battery lasts longer, and doesn't run as hot.
Depending on what you do with the device and how it's implemented the results could range from awesome battery savings without a reduction in performance to brownouts and having the processor work harder to get the same job done.
If you do a lot of processor intensive stuff ( resource heavy games, for example ) undervolting becomes a harder thing to take advantage of because the processor has to work harder when it gets maxed out.
The fact that tbalden lifted the artificially low 1.2 clock speed and bumped it up to it's rated 1.5 offsets that somewhat.
For most people undervolting is a godsend, because they don't miss that top % of maxed out processor performance.
Also, the greater range of speeds allows you to regulate the speeds of the device using apps (setcpu maybe) which can't set speeds outside of the range the kernel allows.
Tbalden got into what I was trying to before my crazy work schedule hit, and he is doing a whole lot for this device - now I'll be following the trail he's blazing instead of the other way around - win for the MT4GS community when people have time to make fun stuff like this for us to play with.
Haven't had the chance to read up on what he's done with it other then seeing it was there, so this is some general info to get you started with, there's a lot more to be said and I'm sure others will swing by and add to this description.
Sent from my Bulletproof_Doubleshot using xda premium
Slight is slightly undervolted, meaning it saves less on battery
Middle is around 5% undervolted, meaning around 5% saving in battery drainage
Extremely is 8%
Depending on the quality of your cpu material, it can work on your CPU well, or if it is made of a silicium chip that is less clean then your CPU will say voltage is too low, and phone might reboot. So depending on your device it may or may not work out.
UVing the cpu means no performance decrease. You should find out which kernel is best for your device. Safe is to go from Slight to Middle and then to Extreme if the Middle works out well. If you have reboots, fall back this way: Extreme --> Middle --> Slight
Also, if you dont want to use the Overclock frequency range, use SetCPU or an alternative cpu tool to cap it to your like.
Thanks guy. Now I understad why my phone s batt last longer . I flashed the extremely kernel . And I'm using an anker batt. And adding profiles with set cpu
And I noticed. My battery. Last way longer then before . Even though. I set the main profile of the set cpu to 1.5 hz max. 1.0 hz min. Wich makes the phone run as. My loptop. . Thank u developers
Sent from my myTouch_4G_Slide using xda premium
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