[Q] SetCPU won't allow me to slow below 172800 - AT&T Samsung Galaxy S II Skyrocket SGH-I727

I installed the newest faux kernel, along with a stock ROM and the new UCLA radio. Seems to run fine. My main reason for putting on the FAUX kernel was battery life, as it's a scalable kernel.
So I downloaded SetCPU so I can take advantage of the under-clocking without using scripts. I chose on-demand, and it sets the high to 1728 and low to 192. My understanding is that a stock Skyrocket is runs at about 1.5. It runs nice and fast stock, so I tried to put the slider down to 1516, but it jumps back up to 1728.
Why will it not let me take advantage of maximum underclocking?

Bump.......

Related

Overcloking

Is anyone else having an issue with custom kernels? My Tbolt only seems to run on the stock kernel/voltage. When I flash an oc kernel sometimes it will load and then freeze the system.
Sent from my ADR6400L using XDA App
All phones are NOT created equally. Your phone may just not be able to handle it while others could.
I realize every cpu used is not the same and can't handle being overclocked to the max, but come on, I can't overclock it at all without it freezing shortly after the Rom starting. Don't you think that's a little out of the ordinary?
Sent from my rooted Tbolt.
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Yeah that does sound kinda sketchy. Which kernels have you tried? Have you tried running one that wasn't undervolted? I've heard people having issues with the UV kernels.
Wkd1 said:
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Click to expand...
Click to collapse
I know what you mean. I had the 1.2 GHz uv kernel from adrenalyne and the phone ran like crap. What's the point of over clocking if real world results are worse. Smart-Ass would stutter while it was ramping up and gun bros ran like crap until I reverted back to the stock kernel.
I'm hoping somebody makes an OC kernel that isn't under volted.
Sent from my HTC Thunderbolt using Tapatalk.
I'm running Imoseyon's version 3 of the lean kernal, 1.4 ghz, undervolted. it seems much faster and more responsive, and has yet to cause me any problems. Right now I'm running on 20 hours off the charger with 45% battery life left (extended battery, so assuming stock would last around 9 hours).
The only kernel that works for me is adrenaline's 2.6.32.21 battery is life kernel. I've tried his other kernels, imoseyon's lean kernels, and a few others all with the same result of freezing up the Tbolt.
Sent from my rooted Tbolt.
Have you tried adrenalynes newest kernel? I'm using version 4 right now with no problems.
Yeah, another vote for Adrenalyne's kernels here.
I'm running the version 4c, and it's flawless on my phone. (4b locked up at higher speeds.) But the other tweaks he threw in there kick ass. Louder audio, faster charging and, I think, most significant, a potential fix for the GPS issues a lot of people are experiencing. Granted, mine was not too bad -- I could usually get a lock within a minute or two, but now it's locking in under ten seconds.
Can't quite comment on the battery life yet, but it's probably pretty damn good, especially with a minimal overclock or even staying at 1Ghz.
Running one of Ziggy's...so far so good...
I ran Drod's 1.5 kernel with no problems overclocking. When I switched over to Ziggy's or Adrynalyne's overclock kernels, I am unable to overclock with out my phone freezing and going into constant boot loops. Kinda weird but I have no real need to OC so I just went with Adrynalyne's stock kernel and been fine ever since.

[Q] Is this okay for me to do?

First off:
Rom:
Virus rom RC1B3
Kernel:
1.8ghz bolted BFS uv kernel
if you overclock, your battery life is less. more power = more usage
so, in theory, if you underclock, less power = less usage..
when I'm at work, I barely use my phone. Maybe to text or a call here and there..
So I wanted to improve my battery life as much as I could,,, I have SetCPU and I have the minimum at 350mhz and the maximum at 650 using the smartass governor when not in use.. Since this is underclocking, the battery life has improved drastically,, though is it safe? I don't see any reason why not, just though I'd like some input on it.
Yeah, you're fine. With the Smart-Ass governor you don't really need to underclock. It's called smart-ass for a reason. It will only use as much is needed. So when your phones screen is off not running any tasks, the governor will underclock itself.
Another thing to add is if you are using SetCPU, then you really do not need to set up any profiles that would underclock the phone if you are using smartass.

Has your oc or uv capability decreased?

Did any of you used to be able to OC and/or UV with no problems, even at 1500MHz, but now are unable to get the same performance out of your g2x?
Mine did. When I first started flashing on this phone, I was able to run oc/uv kernals at 1500MHz, and even uv the lower end an additional -50 beyond what the kernal is already undervolted at...and run back to back smartbenches with no problems...but now, any attempt to uv leads me to forced reboots, and any attempt to clock higher than 1200 does the same. I've tried every rom and kernal on this site. I wonder if I damaged my phone with the high oc early on.

[Q] - Overclocked kernels - What's the point ?

I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.

pros and cons OC/UV

about time for me to change roms again. i know there are many with this option, but have never chose to pursue that option due to lack of understanding benefits. always seemed to get satisfactory battery life out of phone, but could it be better? i have noticed different speeds on my phone with different roms but is this something that can speed up and keep the smooooth in my phone?
just thought i would get some feedback of the advantages and disadvantages of overclocking and undervolting.
will it harm my infuse?
what are good settings?
what exactly would the OC or UV each do?
if i run a search on this, i know i am going to get the phone book and just figured i would get a more specific answer directly as opposed to piecing little bits together and still not being confident in what my interpretation would be.
everyone in the infuse community always seems to have the answers and dont steer the dullards such as myself in the wrong direction.
you guys are the MAN, and well, you women.....your the woman i reckon
captemo said:
will it harm my infuse?
Click to expand...
Click to collapse
No, so significant damage can be done with overclocking. Alhought if you set your ghz too high your phone might become unresponsive, overheat and/or auto reboot your device. This is normal if your on GB and some ICS roms. Don't see it much on JB becuase the some kernels dont support it. Just be sure to play with your settings and MAKE SURE SET ON BOOT IS DISABLED or else your phone will be stuck in a bootloop when overclocked beyond stable settings.
captemo said:
what are good settings?
Click to expand...
Click to collapse
I usually stick with 1400 ghz because 1600 ghz[max] drains battery too quickly for not much of performance boost and 1600 is considered unstable on most GB and ICS roms. As for CPU governor Id stick with ONDEMAND.
captemo said:
what exactly would the OC or UV each do?
Click to expand...
Click to collapse
OC is over clocking your processor to a higher ghz for better perofmance and under volting is drawing less energy
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Garen21 said:
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1420742
I used to under volt a lot to get better battery life. But it seemed to make a couple apps hang now and then.
I am now on Scotts PA JellyBean ROM. Battery life is very good for me stock with this. So I have left under volt to stock settings.
Normally I'll run on smartassV2 governer. With NOOP i/o. And 100mhz - 1400mhz.. just for a little extra boost.
When I know I'll be playing a game or multitasking, I'll boost it to 1600mhz.
Overall stock settings run amazing, both battery life and performance, on Scott's PA JB and CM10.
After doing some reading, I believe I can get better results from using the above settings. It all depends on what your personal goal is.
The biggest concern you should have when overclocking is mentioned above. Boot loop, just make sure you test it for a while with set on boot un checked.
Undervolting you can go to low and also boot loop, so same applies here... leave set on boot un checked. All phones are different on what settings they run best at. Just gotta play around and see what works for you.
A good rule of thumb for under voting... go down 25mv at a time and test it out... keep going down 25mv until you get a problem or boot loop and then go back.. then you'll know your max.
You can safely under volt more on the lower frequencies than you can the higher ones. Personally I never undervolted more than 100mv across the board. And when I did, I usually kept it around -50mv.
Sent from my SGH-I997 using xda app-developers app
not for infuse but a good reference for ocuv. explains what they do
http://forum.xda-developers.com/showthread.php?t=1827635
Sent from my GT-I9300 using xda premium
This is the best guide I've found covering kernel and system tuning - CPU parameters, governors, schedulers, init.d, loadable modules, etc. It's for the SGS2 (i9000) and some of the governors/schedulers are not available on the Infuse, but much of this is applicable to our phone:
http://forum.xda-developers.com/showthread.php?t=1369817
As for OC/UV, as long as you stay away from the "Performance" governor (this runs the phone at max freq all the time), and undervolting below -75 to -100 you generally will be safe. As phones are different, it is important to test in gradual steps to ensure your phone will be reliable. Use a good CPU manager, like SetCPU, Antutu, or Voltage Control. Make sure you enable the "revert to stock" feature so that you can boot recovery and turn off any bad OC/UV. As noted above, do not check the enable on boot setting until you are certain you have a good config.
The decision to OC should take into account how you use the phone. If your phone is asleep more than 80% of the time on average, you can probably run an OC config and still have overall good battery life (i.e. lasting an entire day with nightly recharges). If you use your phone for music playback or something else that prevents it from sleeping, OC may not be for you. If you run CPU intensive games, it is better to disable UV settings while OCed.
Use CPU Spy to keep an eye on your time at each freq state (and sleep). Use the default battery stats and graph to monitor which apps are consuming the most battery. Use apps like Better Battery Stats, Android Assistant and Watchdog for more detailed monitoring of what is keeping the phone awake and which apps/processes are top cpu resource consumers. With this information you can identify problem apps and decide whether you should remove them from your phone.
From the "unintended functionality" side of the house, there are certain tweaks that will cause your phone to run at max freq ... mucking around with phone properties in build.prop can lead to runaway rild process problems (usually shows up as unusually high "Dialer" in the standard battery stats list and a phone that is warm or hot to the touch). Some of the tweak scripts in adrenaline and tbolt can cause similar problems. There is a known bug in the infuse network drivers that shows up as much higher than normal Android OS battery usage. This can usually be corrected (short term fix) by toggling Flight/Airplane mode off/on. Running the stock UCLB3 GB kernel also seems to minimize this issue (assuming you are running a GB ROM), but flash with caution as you will need to disable voodoo lagfix first. (You will also lose CWM recovery, OC/UV capability, and be on the slower stock file system setup).
I have done a fair amount of experimenting including lots of time on conservative governor with Fmax=1600 and never had any problem that I attributed to OC'ing.
In contrast I did find a limit on UVing. I just updated my thread with my experience on uv here:
http://forum.xda-developers.com/showthread.php?p=32552571#post32552571
The bottom line is that for MY phone, the following works fine:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Some other links with others' experience suggestions about UV'ing for Infuse:
Hozw low is your undervolt?
http://forum.xda-developers.com/showthread.php?t=1693689&highlight=kernel
[Q] Recommended SetCPU settings?
http://forum.xda-developers.com/showthread.php?t=1292836&highlight=setcpu
You’ll note the last thread has comments from Entropy’s settings.
Also Zen and qkster gave advice in the first thread (my thread).
All three guys very well respected and worth listening to.
Entropy mentioned you can uv the higher frequencies more than the lower (different than what was posted earlier in this thread). I don’t know for sure but I’d lean toward Entropy’s advice on that matter.
I think all in all somewhere between 50 and 100 is the max you can expect to undervolt.
What can be achieved varies with phone as stated by many.
You are welcome to experiment with slowly decreasing. That's what I did.
But in the benefit of hindsight, the process of slowly decreasing is tedious. And going beyond the limit was a little scarey for me. Could've been worse if the phone crapped out at a critical time during "experimenting". Like almost everything related to battery life, the results (how much benefit) seem y subjective (difficult to measure quantitatively). Most people say they don’t notice a dramatic difference with UV. If you want to get the low hanging fruit without a lot effort, you might just try 50 down. That's what I'd do if I had to do it all over again.
By the way, setcpu can be set up to provide a failsafe escape route even if you go overboard. There is a zip file that will toggle the setcpu settings off when launched from CWM. You just have to put the zip file on your sd card before you start tweaking. See "safe mode" in the setcpu documentation.
started to wonder at first whether i would get any responses after 218 views and nothing, but i knew the community would come through as they always do. all the regulars as usual regulars ( Zen, Quickster and others) are always eager to help. i think you have all provided me with the valuable info i requested.
thank you much party people

Categories

Resources