[Sprint Samsung Galaxy S III] mw86:
Enable your normal minimum and max with all those vpltages applied and start using phone. I noticed if the cpu doesn't raise or lower to a frequency the voltage on that frequency stays same. If you lock on one its using the last voltage used when it switched to that speed and was locked. You apply voltage and voltage table reflects that. That we know and can test via terminal. Once scaling is renabled the frequency next to be run is running now on the updated voltage table. Now once it switches back to the mhz you were locked on its actually using the extremely low values. Play around from here and you will find if this stuff is stable. From there enable all frequencies you use and test scaling too most of the instability is found switching from frequency to frequency and voltage to voltage. 1000mhz full dual core load set to 700mV and actually using those mv is definitely not stable. Leave on demand governor and normal min and max so it scales and under full load that 1000mhz will crash at 700mv.

Spidey i did experiment today and noticed even using low brightness when possible... pretty low no data on not much phone drain, i turn data on and boom just a light post or two here i drop a ton of battery. I think 3g is taking more than our screens or cpu (when not overclocked extreme without undervolt). I haven't used 4g but 3g data seems to burn my battery percent up. Especially a update or two like you spidey. Wifi nowheres near the same draw.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 12:20 AM ---------- Previous post was at 12:16 AM ----------

I personally think you had a reboot from your extreme undervolt. Just my humble opinion. I tested all the same ranges and reboot is one of the most common of too low an undervolt.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 12:23 AM ---------- Previous post was at 12:20 AM ----------

See i am certain i am correct extreme undervolt is not stable. As soon as you see screen hit settings then apps then tab over to the right to all apps and go to ktweaker. Scroll and move quick i tested it works fast enough hit clear data and or even force stop and then clear data. Reboot done reset ktweaker

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------

There are many methods this is one of them, if others tried all else try this too.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------

Cache and dalvik wont hep but the rest can

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 12:32 AM ---------- Previous post was at 12:26 AM ----------

Another phenomenon related to the above is you can set min max to 1450mhz and all voltages below 1500mhz to 700mV and run test on stability or anything temps stay around same ranges just a bit down and is stable as the 700mv isnt running enable 700mv on 1500mhz or enable scaling by setting min to normal and max to that 1450mhz and both are unstable suddenly. Once that max frequency is set to 700mV it seems to in that scenario start using the 700mv immediately insread of needing to switch once to that frequency through scaling.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2