[Sprint Samsung Galaxy S III] mw86:
I can elaborate this is all true. The above is true but for various reasons. Truly at idle, IDLE 81mhz at 900mv will draw less power than 378/189 @ 900mv. Under load it reverses... It takes so long for 81mhz to finish the same task 189/378 takes that even though mv are same and 81mhz is lower it will keep cpu busy longer which seems to draw more power than quick up then down on mhz. Apparently mv has little to do vs mhz. A good thread i read points out 378 1200mv under load vs 1026mhz 1200mv under load the lower mhz will always draw less power until, UNTIL you reach the above scenario where 81mhz is calculating so slow it draws more than the slightly higher mhz available or when at idle the lowest mhz possible will draw less juice. One could say 81mhz is good for screen on idle as it draws least juice idle or barely loaded. If one can have governor scale fast enough underload 81mhz wouldn't not be a source of extra drain as it would not be underload on that mhz and idle ideally it would be. Prob also comes to 81mhz is more likely to cause a up and down step of mhz as at 81mhz hitting a cpu load threshold for the governor is very easy like even at 90 up threshold thats super easy to hit at 81mhz and its worse on very low sample rates as even slight bumps in load make cpu scale up and down sporadically.

Buddy your onto what a lot of us are... We wanted to run our phones like you had said your normal usage pattern is and we found if we want to stretch heavy usage over a day without plugging in we have no choice but to give the biggest effort to lowering how often our phone wakes up to supply us info readily available at all times of day. Its sad but we should be able to use them as uber smart phones but based on the radios we were given in these handsets we must work ever to optimize how and when data of any sort is synced. We can sit there and have 10 emails sync, twitter, Facebook, gdrive, Dropbox, box, live, skype, instagram and so much more but we will kill of stock battery in 4-6 hours max especially with staright screen time added in or even on and off checking the data and waking of the phone is what is killing it. Your doing so much better Slick Daddy configuring how you switched too. Some of us bought extended batteries to help allow us to go farther and get away with more data usage etc. Its a balance act and ypur off to an awesome start. You actually got fairly good battery before based on the extreme active usage you had before. Most of us take a few runs to get 5-20 more minutes per change and eventually we are at the most we can do and still use our phone for what its needed for. I didnt post my big run to act like i am flexking buddy :) I know you know that and the reason was to show the whole point... to get good battery we need to eradicate the biggest issue... Radio drain. So under active usage being very purposeful in when we turn on or use our radios we can extend our battery life as far as possible. Secondary is everything else in this thread.

Here is change log, bud what is your setup? Touchwiz, android version? I wlnt ask how you tuned or setup gov or max as your saying nothing changed but build prop you get lag. Ill try to track the lag with this info i can test and Gman etc.

Removed 4/21

prop "persist.gps.qmienabled" "true"

prop "persist.cne.bat.range.low.med" "30"

prop "persist.cne.bat.range.med.high" "60"

prop "persist.cne.loc.policy.op" "/system/etc/OperatorPolicy.xml"

prop "persist.cne.loc.policy.user" "/system/etc/UserPolicy.xml"

prop "persist.cne.bwbased.rat.sel" "false"

prop "persist.cne.snsr.based.rat.mgt" "false"

prop "persist.cne.bat.based.rat.mgt" "false"

prop "persist.cne.rat.acq.time.out" "30000"

prop "persist.cne.rat.acq.retry.tout" "0"

prop "persist.cne.feature" "0"

prop "persist.eons.enabled" "false"

prop "ro.ril.ecclist" "112,911,#911,*911"

prop "ro.config.multimode_cdma" "1"

prop "ro.ril.gprsclass" "34"

prop "ro.ril.hsxpa" "5"

prop "ro.sec.fle.encryption" "true"

prop "ro.hdcp2.rx" "tz"

#New Team K mods added 4/21

ro.media.dec.aud.wma.enabled=1

ro.media.dec.vid.wmv.enabled=1

ro.media.cam.preview.fps=0

ro.media.codec_priority_for_thumb=so

pm.sleep_mode=1

af.resampler.quality=255

persist.af.resampler.quality=255

dalvik.vm.verify-bytecode=false

ro.config.hw_fast_dormancy=1

persist.adb.notify=0

persist.sys.NV_FPSLIMIT=60

persist.sys.ui.hw=1

ro.PERCEPTIBLE_APP_MEM=4096

ro.HEAVY_WEIGHT_APP_MEM=4096

ro.SECONDARY_SERVER_MEM=6144

ro.BACKUP_APP_MEM=6144

ro.HIDDEN_APP_MEM=6144

ro.EMPTY_APP_MEM=8192

ro.hdmi.enable=true

dev.pm.gpu_samplingrate=1

ro.config.vc_call_vol_steps=7

ro.bluetooth.hfp.ver=1.6

ro.qualcomm.bt.hci_transport=smd

ro.bluetooth.request.master=true

ro.bluetooth.remote.autoconnect=true

debug.bt.discoverable_time=0

mmp.enable.3g2=true

ro.qualcomm.cabl=1

persist.fuse_sdcard=true

ro.com.google.apphider=off

debug.compbypass.enable=1

debug.hwui.render_dirty_regions=true

debug.enable.wl_log=0

ro.adb.qemud=1

ro.config.combined_signal=true

ro.hwui.text_cache_width=2048

#TK changes 4/21

prop "dalvik.vm.heapsize" "512m"

prop "dalvik.vm.heapgrowthlimit" "224m"

prop "lpa.decode" "true"

lpa.use-stagefright=true

media.stagefright.enable-fma2dp=true

dalvik.vm.heapminfree=512k

drm.service.enable=true

persist.hwc.mdpcomp.enable=true