yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Hey thanks for the info I under volted down 150 mV across the board and it seems to be working! I'm averaging about 38° so far which is a noticeable improvement. Also in running the newest nightly from PA which seems to be better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OmegaBlaze:
Awesome ass thread. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Glad to hear it! Just make sure it's stable! Otherwise you may think it's a Rom/kernel issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OmegaBlaze:
Just a quick in a nutshell question guys:

The entire goal of undervolting is to lower the voltages as MUCH AS POSSIBLE while keeping the frequencies as HIGH AS POSSIBLE, finding that sweet spot in the middle that is stable(Gives good battery & performance)??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Mostly just to bring the voltages down as far as is stable and thereby the operating temperature of the phone down to be as cool as possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yes. But realize that each frequency needs it's own custom tuned voltage. You don't have to keep the frequencies as high as possible per se. I'm underclocked and undervolted. It's all a matter of personal preference.

Everybody loves to talk about this magical sweet spot between battery life and performance. It doesn't exist. Either you will be disappointed with the battery life or disappointed with the performance. I choose to run a slower setup cause all I care is about battery life. I don't care if my apps take .5 seconds longer to launch.

You can have an undervolted perfectly stable fast good performing phone. Or you could have the phone at the same frequency with stock high and hot voltages. Both perform the same. One has better battery life and lower heat. But they perform the same.

A properly undervolted stable phone performs the same as stock voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OmegaBlaze:
I think that's were i'm messing up. I'm doing -50,-75, etc across the board.

Will undervolting and overclocking cancel each other out? I'm assuming undervolting and underclocking will always provide better battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Undervolting and over clocking are two separate things. Overclocking won't cancel the benefits of undervolting(less heat coming from the cpu and sometimes better battery life but you would need to drop the voltages a lot before noticing a real gain in battery life) like undervolting won't cancel the benefits of Overclocking ( if you did the whole stability test for each frequencies and you undervolted correctly like baconatorXVI explained above). And yes underclocking will give better battery life because each transistor on a chip dissipate power when it is switched. Increasing clock speed makE the transistors switch more quickly and transistors that are switched rapidly dissipate more power.

For digital circuits, dynamic power consumption = f*c*V^2

Where f=frequency, c= capacitance v= voltage. Note that the size of the chip also comes into play. This is a simple equation only for active power, it doesn't take the leakage power into account.

To be really accurate you would also need to consider the static power consumption due to leakage. So you would need to add V*I to the formula in which V is the voltage and I is the current flowing through the device. So it would look like this: f*c*V^2+(V*I).

This is only to give you an idea of how your cpu consumes power without digging into the details and more complex stuff that I have a hard time to explain in English since it isn't my native language.

Remember that your cpu isn't the only thing consuming power in your device so even if undervolting and underclocking reduce power consumption, they are not the only two things that will suddenly make your battery last 8 more hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OmegaBlaze:
Holy hell. Thanks alot for the detailed explanation.:good:

Underclocking & Undervolting will result in less power output.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Just out of curiosity what roms do you guys feel like you get the best battery life with this kernel? Or does it not really make difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
There's isn't a ''better'' answer here. It's 90% user (& software/app) dependent and 10% hardware.

That being said, you can get around the same battery life on almost every ROM messing with your settings, finding what works best for your device/needs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
IMO I find I get the best battery life on slim and aocp. Others will say the ROM doesn't matter...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Oh OK I was just wondering thanks for the opinions.

On another note does anyone else feel like the asswax script makes the battery really hot? I'm trying to figure out what the culprit is. It's fine (30°-40°) when I'm not doing anything but the minute I start doing stuff it spikes (40°-50°+) especially if I do anything involving the camera like hangouts or videos (I'm thinking this is normal though?) chrome kinda heats it up as well.

What apps should I use to get info to show you guys what is going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
I completely agree with you on the aocp one. I can pull 5 hours screen on in a full day so easily it's not even showing off. Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamo0132:
Ok what is the best setting for a gamer? (Dungeon hunter 4)

---------- Post added at 12:40 PM ---------- Previous post was at 12:00 PM ----------

When I reboot after i change governors to Ktoonservative my phone doesn't complete loading. What is causing my phone to do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Did you wipe cache and dalvic and fix permissions like the op said?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I haven't had the time to test rom's lately so I can't give a good answer. But I do remember slim gave me a significant bump in overall battery life compared to others
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Do you think that's because of all the dark themed apps they have?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
That's a factor also things like build.prop tweaks, init.d kernel tweaks things that affect performance like that. They will vary on different ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
It's quiet, too quiet. Where is everybody?!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oeusr:
Lurking ;)

But I agree, where is everybody? I like trying the different settings everyone comes up with haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Have you tried mine and Liltitiz's cpu1 scripting tom foolery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
+1 for trying the script! Noticeably increased my battery over other kernels and/or governor set ups
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oeusr:
Yes! I love it. I'm not sure if it's been updated/tweaked since I checked it out though. Or if there's additional scripts you guys use other than the cpu1 one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Has anyone come up with some tweaks for the scripts? I would like to try but I don't know where to start.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
These are my balanced settings for cpu1

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 486000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 50 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 1026000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 85> /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 200000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 1250 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Unless it's changed for you lately I had copied your settings into my script, gave you credit too in the file :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
I've been switching between kts may 29 build and most current. For some reason his may 29th yields twice the amount of battery life with the exact same settings on his current...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
These are my most recent settings, I don't think they're the same as you copied in your file. I got rid on some lags that occurred with my last settings but still keeping the same benefits for battery life. Note that these settings aren't for gaming or benchmark but for day to day lite usage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oeusr:
do you use any other tweaks, tasker profiles, or anything? How's it working for you? I get about 14-16 hours with 3-4 hours of screen on time with this and liquidsmooth 2.8. Thanks again for it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Yea im noticing the lack of lag especially in the keyboard (I use swift key) before it was having issues and now it's running snappy. Only thing left is to figure out how to really get that battery temp down my phone is still running kinda hot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Did you undervolt? I thought i suggested that to someone recently and gave a good rundown of how to do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Do the cpu1 modifications work if your primary governor hotplugs, or do they get reset when that happens?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Works great with hotpluging
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'm on mobile now but perhaps ten , 15 pages or so back I wrote a long in depth post explaining how to set up the script and make it run on boot. There was a picture of a cat so watch for that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dabberz:
I actually limit my hi-freq to 1080.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Hey I totally used your method. I use busybox installer now to run the script on Boot. I was more talking about where to start with editing the scripts themselves. I see all the settings and my eyes glaze over lol. Got any tips/things to read that could help me out?

Also I have been under volting but maybe I should try again to see how low I can get it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I posted this a few weeks ago. Check the link in the post

http://xdaforums.com/showthread.php?p=42688816
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I'm testing new asswax cpu1 setting aimed toward performance. I don't know how battery will be compared to stock interactive cpu1 but it should be better because it scales up less aggressively than interactive. performance/lag are as good as interactive though. I played some game without any lag and every test I did gave similar results than interactive.

Cpu1 settings:

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 1134000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 750 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 1809000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 90 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 55 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 75000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 75000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 378000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 500 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us

These are the ktoonservative settings I use for cpu0:

81-1809mhz

Boost cpu:1134

Down threshold: 70

Down threshold hotplug:55

Freq step:3

No 2nd cpu screen off:1

Sampling down factor:2

Sampling rate:25000

Sampling rate screen off:45000

Up threshold:88

Up threshold hotplug:93
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I think I remember what liltitiz wrote, i think it was pretty thorough.

I'll give my own quick paraphrase. Use root explorer(worth the purchase) to open the script with text editor, use copy pasta and paste everything in, or use my file http://db.tt/L6pLrDDs , it's a bit older with liltitiz's older asswax settings. So this could be good practice for deleting the old asswax settings and copying in some of liltitiz's new settings.

Echo means it's going to write the value to the location. Follow the file path to see what file is there. You can even use root explorer to edit the files if you want, such as cpu1 max.

Just go have fun. You can teach yourself a lot just by playing around. A backup beforehand never hurts :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oeusr:
Getting pretty decent results from light use and heavy use. On my light use day I got some random drop in battery life in the middle of the night that I just happened to wake up and see the 1% battery haha. Also I get random times where KTweaker pops up with "Your saved cpu governor adjustments do not match current, apply governor adjustments?" So I'll have to figure that out.

But loving liltitiz's latest cpu1 settings :good:

task650 aokp and ktoonsez's kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NellyWhads:
Hey guys, this may be the wrong place to ask this, but since the kernel community is huge here, I thought I'd go for it:

I have an issue with my s3, where no matter what kernel I flash, without any tweaking at all, I get visual anomalies (flashing squares around the loading circles, clock widget hands going haywire, PIE layout and color fill going bonkers, etc.). This happen with ANY kernel I flash, including KT747.

Does anyone have any idea as to how I can fix this? :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Maybe you had a bad gpu. One question with the stock kernel do you had any issue.

Please specify ROM, and what Kernels and release.

A dump file should help also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NellyWhads:
I didn't have any issues on stock kernel (I assume you mean stock TW). In fact, I don't have any issues with the CM kernels that are included in any of the modern AOSP based ROMs. Currently, I am running Jellybam 9.1.2, and the included kernel works flawlessly. As soon as I flash BMS, XOne, KT747, or any custom kernel, I get il the visual anomalies I mentioned. :/ I'm also 100% sure that this is not ROM issue because the same happened when air was running CM 10, CM 10.1, AOKP, PACMan, Carbon, and Slim.

PS. Noop brain fart but how do I get a dump file? (I am decently experienced in android modding, but not completely familiar with all the terms, debugging methods, etc.) :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
I would try this, go to Ktoonsez Kernel thread and use the provided kernel cleaner by matrb. It has link in red text stating if you need a permission fix/cache clean etc.

Kt747 thread OP

http://xdaforums.com/showpost.php?p=29426212&postcount=1

Direct link to kernel cleaner.

http://xdaforums.com/attachment.php?attachmentid=1319515&d=1347395869

Run the cleaner in recovery, then install the custom kernel and see if issues go away. Leftover files to a specific kernel can cause random issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I've seen some pretty awesome battery life with this kernel, but most of the really spectacular ones seem like people who don't use their phone much throughout the day.

Any suggestions for settings that provide the best battery life throughout the day, with moderate to heavy usage? I was running with a Hyperion 4200 mAh battery, but the back cover cracked, so I've had to go back to my stock one, and I'm struggling for battery life.

My settings now are:

81-1728 MHz

zen, 2500, 1, 300

ktoonservative, sampling_rate_screen_off 90000

-75 across the board

Screen Off Profile 486 MHz, noop

Sent from my NovaGen'd d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I would suggest :

81-1728 or 1809

Keep the scheduler that works best for you

Ktoonservative:

Boost cpu:1134

Down threshold: 70

Down threshold hotplug:55

Freq step:3

No 2nd cpu screen off:1

Sampling down factor:2

Sampling rate:25000

Sampling rate screen off:45000

Up threshold:88

Up threshold hotplug:93

And with any app that can run scripts( i prefer busybox installer) run this script to apply my asswax settings on your cpu1 instead of interactive.

Dropbox link: http://db.tt/YlJqAV52

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo 486000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 50 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 1026000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 85> /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 200000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 1250 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
How do I know if it worked?

Sent from my NovaGen'd d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Using a file explorer you browse to the location indicated by the script. By opening the files you can see if the settings were applied
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
if you use the smanager app to run the script you'll get a 0 or 1 output from the run.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
What?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
liltitiz and baconatorXVI I'm trying to use your script on a TW Rom. I can get it to run no issues by removing the line "interactive ideal idle frequency" . Which is no big to me. The thing is I cannot get the script to run without a Reboot, if I enable hotpluging. It was mentioned it works great with hotpluging. Did I miss a step somewhere ? TIA.

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nxoxe:
I will try the script hae a nice day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nxoxe:
I applied and works like a charm .....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
So I search around a little, but didn't see a solution to this. How do I keep the cpu1 settings to through the 2nd core shutting down? Am I missing something obvious here? Do I just have to time it correctly to set the governor for cpu1 and hope it sticks? I apologize for my ignorance here. First time messing around with the 2nd core.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
Check out the link below to the post by baconatorXVI. It will get you the info you need ;) .

http://xdaforums.com/showthread.php?p=41663912

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
I've got a script for cpu1 using conservative that is giving me pretty poor results. Asset tomorrow I'm going try on a different governor for cpu1.

Since liltitiz had narrowed it down to asswax I figured I'd try the other governors out and see what the deal is.

Lazy wasn't too bad, but there was definitely some room for improvement.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Just to remind users with trouble the key to this is even without script and doing it manually is set ktweaker to disable hotplugging in the governor. Apply the changes then you can enable hotplugging again and the second core would still be on the changed governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flak0:
I felt dangerous tonight and set Cpu1 via script to the Qualcomm governor msm-dcvs and it scaling on load quite nicely. Seems stable and goes offline quick. I am using [MENTION=4983878]castle_bravo[/MENTION] ktoonservative settings he posted.

Sent from my SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
I'm getting a ton of reboots while trying to run different scripts. will update later today
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chargen2:
Omega 9, TMO 747 latest kernel. Can't find a stop where I don't get unexpected reboots.

Tried loading defaults, clearing cache, reset permissions, different governers, etc

Anyone else encountering this? Had zero issues on latest versions of faux do o don't think it's my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
Try setting the Stock Voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chargen2:
Wouldn't that be done when I load defaults?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
In the Voltages yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chargen2:
Giving it a shot. Thanks for the info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yeah that would totally work. The goal is to ensure cpu1 is on while you tweak, otherwise your settings won't apply. You can either run a benchmark in the background which keeps both cpu's on or you can tell your scripting application to run at boot since both will be on. Or like mw86 says turn off hot plugging :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes. Turning hotplug off then back on after executing the script is probably the best route to take..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
Yes that is what I do. Disable hotpluging. Apply the cpu1 tweak. Check the settings are applied. Then enable hotpluging. But every enable hotpluging, the device will reboot.

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Try my method maybe? Wait are you on touchwiz? perhaps you need to remove some of the script if there's no file shown for those settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
Yes I'm on TW. That is what I believe is what is the major variable. Haven't run AOSP in forever. On TW, asswax governor does not have adjustments in KTweaker.

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flak0:
Agreed same behavior here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
I'm not sure which kernel you are on but the latest kt747 for touchwiz does in deed have adjustments for asswax
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
edit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
81-1728 or 1809 is that for the screen off profile max?

and after running the script do I need to enable on boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Those are the cpu min and max values. Don't set the script to run on boot until you've tested it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flak0:
Castle have u tried to tweak the standard ondemand for cpu1,also try msm-dcvs however no tunables there closed source by qualcomm

Sent from my SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prboy1969:
I'm on the 5/31 kernel. Yes you are correct. I misspoke. When I first input the settings all is good. But for some reason when I go back into KTweaker to check. It says there are no adjustments.

EDIT:

If I use the asswax governor for both cpu's I get no reboots.

TEAM MiK

MikROMs Since 3/13/11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Thanks my max is 1512 is that because of the governor or I just missed a step prior?

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
You have to enable Step OC in KTweaker.