Related
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.
http://www.tomsguide.com/us/overclock-android-device,review-1762.html#xtor=RSS-998
Opinions from people who really know? I can't imagine that overclocking increases battery life.
It doesn't. At least from my understanding. In fact as I understand it running at higher clock speeds would decrease your battery life no? I usually under clock, so...
Sent from my SGH-I777 using xda premium
The theory is that overclocking allows you to complete processes quicker, which in turn allows the processor to go back to a idle/deep sleep faster. In practice it doesn't really work that way though.
ryude said:
The theory is that overclocking allows you to complete processes quicker, which in turn allows the processor to go back to a idle/deep sleep faster. In practice it doesn't really work that way though.
Click to expand...
Click to collapse
doesn't the increase in voltage also come into effect?
They did talk a little about undervolting to increase battery life. Personally I don't worry about it. I'm not using my phone to sort out heavy algorithims at the moment, so running how it does is fast enough for what I use it at. Just found the article interesting.
K Rich said:
doesn't the increase in voltage also come into effect?
Click to expand...
Click to collapse
They say the undervolting on lower clocks should balance out the higher voltage on overclocks.
stalked_r/t said:
They did talk a little about undervolting to increase battery life. Personally I don't worry about it. I'm not using my phone to sort out heavy algorithims at the moment, so running how it does is fast enough for what I use it at. Just found the article interesting.
Click to expand...
Click to collapse
Undervolting rarely makes a difference on mobile SoC's, but on the desktop/laptop CPUs you can really save a ton of power with undervolting and underclocking.
Why to overclock and understand it?
Here is a good reason to know what you are doing..
and the battery avg's lasting at least through the day, but most of the time, I have a charger near me...
EDITED: because it won't accept my screenshots HTML Probably cause I have n00b status on this account name.
AnTuTu Benchmark v.2.8
Total Score: 7446
RAM: 1201
CPU Int: 2264
CPU Float: 1767
2D: 295
3D: 1148
Database: 450
SD W 11.8MB 118
SD R >50MB 203
1600mhz
2012-05-23 18:17
You can view this SN here: Screenshot
Fluxi Kernel/My own OOM settings/AOKP/my own XXTweaker settings
The article says its not the actual overclocking that is saving battery life. When you put SetCPU on your phone not only can you overlock but you can underclock and set different voltages. I'm not 100% sure how the voltages play into it but you can set the processor to run at really low speeds during certain acts ei. when the screen is off, or any other time you don't necessarily need alot of power. That's and I changed all the voltages (I got them from a post where the guy knew what he was doing and tested them). I get almost 2 days moderate browsing, apps and text. If I talk alot or use my hotspot I only get 1.5 days. It is a little time consuming to get everything just right but when you do you really see it.
icyhandlz said:
The article says its not the actual overclocking that is saving battery life. When you put SetCPU on your phone not only can you overlock but you can underclock and set different voltages.
Click to expand...
Click to collapse
This isn't a SetCpu feature there are other programs that can do this as well. It just so happens SetCpu has it built into the program. I bought SetCpu back in my Atrix days and loved it so it does work great for a simple tuning program.
Sent from my SGH-I777 using Tapatalk 2
Many of the kernels these days have their own tweaks and mod apps as well
Sent from my SGII AOKP Fluxi i777 running Beastmode OOM using Xparent Sky Blue Tapatalk 2
I'm running a kernerl and a custom ROM that allows me to underclock and overclock.
I tried it out both ways and the battery lasted for almost the same amount as on the stock option. As I tend to play games a lot on my phone, the underclocking ran into some issues with stuttering and sometimes force close of a couple of games.
Personally, I've never been a big fan of either .
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts