[Sprint Samsung Galaxy S III] mikedavis120:
on the test build. having trouble getting cpu freq. to stick. Just stays at 1512mhz no matter what i try to get it to change. Was on moar rom im dl'ing hyperlight and odin style stock update. will give it a test on both of those and then update

update: Hyperlight runs way better that moar did with this kernel. I was able to get stable at 1.8mhz with a small ov but no increase in preformance so lowered back to 1782. smooth and no reboots/ bad behavior as of yet. Will play with it for a while while a download finishes. Want to do most of my testing on a 100% stock build

New update: On stock odexed mb1. I odined back to complete stock and then odin flasehd recovery and rooted. Sprint sent me the first update to mb1 and said there are no new updates even though we all know there is. So I used mobile odin to flash your kernel and start playing, I abused your test kernel and I mean I ran it for all it was worth. I managed to get it running stable @ 1944 mhz Performance/noop with 50mv OV on all steps above 1782 mhz. ran close to 50 linpack benchmarks on it and averaged 350 380 Mflop's with a best of 398.92 Mflop's. Quadrant yielded constant 6000+ scores and Root Stability recorded a multi thread Mflop score of 650. Single core 350+. Ran root scaling stability tests and completed 19 passes on both cores and 62 passes on ram with no errors. Above average battery life for the usage to I am quite impressed so far.

I could get it to run and function at as high as 2052 mhz with OV at +50mv from 1782 to 1944 mhz and +75 mv OV at clock speed 1998mhz and 2052mhz phone was not running any better than at 1944mhz and below so I ran 2 linpack runs one at 360 Mflops one at 371 Mflops. Quadrant caused the device to freeze and reboot on first try but second attempt yielded a score of 6200+. I tried to push 2052mhz to 1425mv and 2106mhz to 1450mv but phone would not handle it. Actually dropped the Mflops to around the low 200's and quadrant would freeze the phone and cause a reboot. Didn't run any stability tests on clock speeds higher 1944mhz as I knew they would fail.

Now I am switching modes and aiming for smooth operation and max battery life. I have undervolted all clocks below 1296mhz by -50 mv and have had no errors. I am now at 384min-1296max asswax/zen and running smooth as can be. I have not installed much for apps but I am running some apps that are usually somewhat battery intense. Ftpserver to my laptop is probably the biggest culprit, i try to keep it under controls by using nfc. I have a tag thats on the bottom of my laptop so if i set my phone near it it will start the ftp server and connect with windows and then sync everything thats below /storage to a backup directory. This usually ends up happening 2-3 times a day. Its nice to never lose sdcard contents even if you accidentally delete them. I am hoping to that the battery life the kernel displayed during my overclocking adventure will be even more pronounced at the lower clocks and voltage setup. I am monitoring the battery now as it charges. At 100% I will use adb to wipe the battery stats and then reboot and run it to 0 and see how well it does. Cpu spy is on and I hope to see alot of deep sleep.

As far as anything else. Thanks for keeping me busy on my day off. I was far from bored lol. Also if you can I would like to see a much lower min clock. And I would be in heaven if you could add smartass gov's to this when you get a chance. All in all I am impressed with it and can't wait to see whats to come.

Also to everyone else, don't follow my lead if you have access to this kernel. I know what im doing with overvolting and overclocking and I am willing to accept the risks. I would highly advise you not OC past 1782 and if you need to OV to get that speed stable then just back down to 1728mhz. There is no reason other than testing and utter craziness for your cpu to be that high. The angry birds don't go any farther