yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Is there anything else at all that could be setting that simply by opening the app? Do you use set cpu, system tuner, rom toolbox or just about anything like those? I use romtoolbox but i stay away from the cpu section.

I use CWM recovery but im sure twrp works but it never did the following right for me so i stick to CWM.

You could try this. Having the backup set in ktweaker go to settings/apps/all apps/ktweaker/ force stop then clear data.

Reboot to recovery, clear dalvik cache, clear cache, mount all partitions available in mounts/formatting option section (dont format anything stay away from factory reset) now with system/data/cache/sd card/external sd card mounted go back to advanced in cwm recovery and hit fix permissions. Once done which may take a bit, select reboot phone.

Once fully booted dont enter anything just make sure everything started, go to Ktweaker hit restore settings, hit apply hut okay on all of those. Hit restore backup a second time and again apply everything that comes up (a second time since ive found sometimes the order settings restore that some don't apply so after initial restore the second restore makes sure all the saved settings applied)

Now make sure it says restore settings at boot immediately and exit ktweaker. Enter nothing, reboot and see what happens at boot. Using like cool tool see if you are now using the right mhz at boot. If so go ahead and now enter ktweaker and reconfirm all settings are as you had set and yes use lock frequency option.

I hope after all that it works. Otherwise in my opinion there is still another app causing the issue. Good luck i hope it helps.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
So far I like it. They kept moving forward with every albums and they are all good in their way. Plus, the cover of atlas makes a real nice background :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
I've been playing around that last week or so and I've been able to get some respectable battery life out of my phone running on the stock battery. I'm basically running liltiziz PegasusQ / Noop settings with a bit more undervolting.

Max - 2106 Mhz

Min - 192 Mhz

Screen off - 384

PegasusQ / Noop with liltiziz governor settings

And of course the aforementioned undervolting.

The phones goes into a nice deep sleep and uses very minimal power but wakes up perfectly.

There's about 45 min of streaming video, an hour or so of web browsing, 20 min of games, lots of twitter, FB, and Flipboard. I was mostly on Wifi, but there was some LTE / HSPA+ time in there which usually kills my battery due to poor LTE service in my area. The 4 hours of screen time was split pretty evenly over the entire 15 hours. overall I'm pretty happy. It gets me from when I get up until I go to bed! What more do I need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I've been using 700 mv @1458 for probably over a month now through all the kernel versions. Switching PA PK and skim bean.

And yes, that means I've rebooted with the apply settings checked.

I did lots of extensive testing awhile ago...

The only thing that convinced me was a steady 10 degree Celsius difference cpu temperature between stock voltage and 700mv while running benchmarking for long periods of time under equal conditions. It was seriously a lot cooler.

I've dug through the system files to the location in the screen shot, this is what I've seen. It's been that way for a long time now.

I don't know how else to test this...

Edit: argh it's not uploading the screenshots...

It's under /sys/devices/system/cpu/cpu0/cpufreq/uv-mv table....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The settings definitely apply. I hadn't really investigated any further, but I did test some absurdly low voltages myself.

I didn't think the settings were actually having much measurable effect, since the Trepn graphs you and liltitiz posted didn't show much if any change to current. 10 degrees Celsius is quite a difference.

I keep trying to puzzle out what's going on, but I've still got no idea. As far as stability, I have no idea. I suspect Trepn isn't reading accurately. I watched your video again, and it looked like current might have increased when you bumped voltage up, but readings appear to be capped around 130uA.

It's way to late to wrap my head around this. Need sleep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Yes the temp drop definitely means the volts are applying then. As for 1458 fully stable at 700mV it doesn't seem likely. I gave Decimalman a test in theory for 1000mhz @ 700mV. He performed it and didn't even fully run the test and ut crashed immediately. So his also applied correctly. If you perform similar its not guaranteed but likely it will crash at 1458@700mv. Decimalman has a very low voltage table and seems atleast a little more likely to be fully stable. I understand you tested, how is it that you tested for stability?

Antutu bench passes on every one of our handsets at stock, can you pass a full run on all your frequencies? As in test with your max if that passes drop your max to next lowest mhz and rerun the test. Stock every frequency even 96mhz passes.

So i wasn't saying everyone's volts weren't applying just those whom 700mV worked for every speed. Like yours with temp drop proves it applied, but then the only question is how stable is it?

I respect everyone's opinion and i accept fact. This is only a suggestion. Feel free to look into it or not.

I almost question how well that app is monitoring the power levels.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'm about to leave class and start my hw due at noon, no testing for this morning...Lol

Don't forget that current is much different than voltage. Current is the amount of charge, voltage is the ability to move that given amount of charge. I gave an analogy earlier explaining the difference. Sorry I don't have the time to dig it out. It's quite a few pages back...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Oh c'mon, playing with your phone is much more important than school. :p

Current != voltage, but Ohm's law says V=IR, so unless resistance is changing dramatically, it's safe to assume that current will change accordingly. In theory, anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
CPU are way more complexe than this. Considering we are talking about mV mA and mohm, its is note than possible that the resistance is dramatically changing. You have to consider heat, length of the circuit, circumference of the conductor and the frequencies. You also have to consider that this is not a simple electrical circuit. There's a bunch of resistance along the way and they are not all acting the same. Believe me that if it was that easy we would have come up with an answer a while ago :p

I ran several test I tried to figure out the maths out of it and couldn't come up with a constant value, which would've been the case if the resistance wasn't changing. Since I was working with MV and mA I had no choice but to ran test till the battery drains out to get numbers that actually means something. And so far I still can't say for sure if its applying or not but I'm running 700mv for 1134 to 1458 MHz and I did see difference in temperature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Absolutely. However, I would think the fundamental relationship would still generally hold when considered at a really large scale, whether or not the math remains accurate.

I'll give this some thought. Of course you guys have been working on it for ages, so you've got quite a head start.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Hey bro to be fair i just read the entire thread. Conclusion i am going to test what you and lilitz have done too. Ill get back to you later on it. I see niw how you guys are doing it and i think thats the key. As other i saw same thing. Using 96-2106mhz at an undervolt like that even just on 96mhz crashes on mine. So to be fair and see whats fact for myself i will test it like you two. You deserve that after the work you put in. I hadnt seen the work till i read the whole thread now.

One thing you should change in your testing though. Battery temp may be a small indicator but cpu temp is better see pic here. System Tuner and Temp Monitor can read sg3 actual cpu temp. Ranges for cpu are 70f-200F around 195-200F phone shuts off :) tested 2106mhz thoroughly myself on stock volts and some lower ones.

You know it almost seems if lower frequency use higher volts it uses mv instead if the higher frequency uses lower mv. Perhaps the answer is hidden in qualcomms own governor. Remember how if frequency drops then goes up it uses it doesn't drop to the lower mv unless it was going from low to high not high to low frequency. I know thats not how our governor runs but what if S4 has some issue like that. Then the 1458 would be using the mv next down from there? I have no clue till i start testing like you guys. Be back later.

Im going to try 2106 min max after 1458 and see how both do when no other frequency is used and how low i can get it. But difference for me is i am going to apply volts at boot to be sure they were set. I dont think when we hit apply without reboot that it applies to the cpu yet. If the files being used how can it be written to? I think its necessary to reboot with the set volts because in past i could set any mv any frequency and same thing you guys see happened but i rebooted and it crashed at boot before. Leads me to believe at the time you guys hit apply its not using those still. I want to see myself so be back tonight after much tinkering. If the lot of us keep tinkering one of us is bound to have a breakthrough. C u later tonight.

Check for cpu temp differences instead. Example antutu 2106mhz 1350mv 185-195f depending if was idle before test. 2106mhz 1290mv about 160-185 F under the antutu run.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
i'll do my best to test, but i just got my bluetooth mouse in the mail, along with hdmi out. so i think i'll be busy :P

oh and i always always use cpu temps. i'm using system tuner, they have a notification bar widget deal. it's an add on. but it's easier than switcching back and forth between the apps.

also don't forget that when you switch away from apps like stability test(while benchmarking/heat testing) you will be using the gpu which adds more heat, as well as the lcd will be generating heat. so if you do heat testing stay on one app, use the notification drawer with system tuner for the cpu temps.

just keep being consistent! oh and i've found the voltages apply immediately. right off the bat. i can see almost instant temp changes when i switch the voltages from low to high.

i think the behaviour you were experiencing was very heavy cpu load while booting and it was probably not stable enough. that's probably why it crashed and rebooted. when i do voltage testing i always uncheck the set on boot button so it doesn't get in an annoying reboot loop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Well yes i know about reboot loop and i know how to fix it no prob. I also know about switching apps when testing, i think you didn't look at pic careful. Temp Monitor like System Tuner shows temp in notification drawer too. See its in green says 109. So we are on the same page on all this that means. Ill get back to you then since you wont have time for testing.

What happens if you set all stock mv right, set 1458 and 1400mhz to 700mV and test. Does it still stay stable? Ill look into it later. Ill be as consistent as possible.

Please someone where do I buy or download Trepn profiler app like you guys. Please and thank you. I monitor temp change at 1/2sec refresh rate. In the app is realtime reporting but i dont sit in Temp Monitor while testing. I think the cpu can't report temp much faster than a second to 1 1/2 anyway. Sounds like you monitor and test just like me. Ill let you know what i find if it differs any from your findings or if there is anything to add to it.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The only APK I see at the moment is attached to this post. Hopefully it's the same one we're using, since the new version available from Qualcomm doesn't seem to read any power information off my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TylerL520:
I ended up just reflashing everything and starting over because I couldn't figure it out, it's working fine now. Thanks again for all the help, I appreciate it.

When I was overclocked my phone was running really hot fairly quickly so I turned off overclocking thinking that was causing it and just undervolted with the max at 1512mhz, but it's still getting hot quick. Is that normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] awaisuk:
liltitiz, what governor are you running these days thats good on the battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
After trying out a bunch of settings posted here, I found that I wasn't completely happy with the performance on my phone, so I went with something different:

KTweaker test #2

UV: Subtract 25mV from all steps None (testing to see if I still get hot reboots in apps)

Min: 96MHz; Max 1512MHz

I/O Scheduler: deadline (default settings)

CPU Governor: pegasusq

cpu_down_rate:20

cpu_up_rate:10

down_differential:5

freq_for_responsiveness:384000

freq_step:20 freq_step:25

hotplug_freq_1_1:550000

hotplug_freq_2_0:400000

hotplug_rq_1_1:300

hotplug_rq_2_0:200

ignore_nice_load:0

io_is_busy:1

sampling_down_factor:2

sampling_rate:40000

sampling_rate_min:10000

up_threshold:80 up_threshold:75

up_threshold_at_min_freq:65 up_threshold_at_min_freq:60

Touch Booster 1st: 756MHz 648MHz; 2nd: 540MHz 810MHz

Screen Off Profile MHz: 486MHz 384MHz

I've only been running this for a couple of hours, but things seem very smooth and CPU Spy is showing acceptable results so far. I played some HD games and experienced no lag while the CPU sat at 384MHz. Watching 1080p hi10p video with FLAC audio also kept the CPU at 384MHz, and listening to music with the screen off kept the CPU at 96MHz.

Edit: I switched the first and second touchbooster settings (now 540MHz and 756MHz) and seemed to get even better results with the same performance.

Edit: Updated settings with my current configuration. Battery life seems good so far. The only issue I'm having is the black screen wake issue, but I think this is tied to the min frequency, so it's a tradeoff I guess. The min frequency also causes the CRT screen off animation to sometimes play at a low framerate. If there was a way to set different minimum frequencies for different screen states, that would probably solve the issue.

Edit: Still running these settings, although without any UV now as I've gotten a couple of reboots in apps. I flashed Task's 12/2 AOKP update and I haven't had a black screen wake issue since. The CRT animation still lags occasionally, but not as much as before, and my battery life has still been great (16.5 hours unplugged with 4 hours of screen on time, heavy use).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
I don't know if it's my battery but being at 1.8mhz and undervolted I get horrible battery life these days. I don't know if it's my Hyperion battery but it seems like it gets worse every few days or so. 2 hours of screen time and my battery is at 70%
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Setcpu can accomplish this, I use it on my n7. Not sure if it will work in conjunction with ktweaker tho.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Perhaps check for wake locks. I know my brightness makes my battery temp go up a lot if its up high.

If on Jelly Bean Touchwiz check for qosmgr running your cpu too much.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
I'll probably give that a try. Hopefully there won't be a conflict.

My first battery rundown results with those settings, heavier than normal usage:

4% remaining, 12 hours off the charger, 3 hours of screen on time, over 3 hours of phone calls. Included phone stuff, web browsing over HSPA+ and wifi, gaming, autosync of widgets and 2 Google accounts, and lots of messing around with the phone. Much better than I was getting before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
If I'm reading this correctly (the strike tags aren't parsing on tapatalk) any particular reason the second touch booster higher than the first?

Doesn't the second touch booster kick in immediately after the first? So wouldn't having the first one higher result in better performance at no cost?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
I'm going to be honest: I'm not sure how the touch boosters work in relation to each other. All I noticed was that I didn't see any performance decrease from having the first touch booster lower and CPU Spy seemed to show more desirable state times with this setup. Could definitely be a fluke, but I haven't noticed any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Apocalypse487:
Don't use them together. Settings don't stick and it creates problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] awaisuk:
I am using these settings on stock ICS rooted, but screen is flashing sometimes.

What do I need to increase to stop the screen flashing? Because the voltages are not that low..only 25 uv each step..so that should not be causing it right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
The UV is probably the cause. Some phones can't handle any undervolting. Keep raising until you don't have flicker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
Something is gotta be up here... This battery is getting worse daily... Hyperion battery... Look at these stats.... Horrible!!

Undervolted and at 1512... Usually im on 1800mhz but for testing purpose I went to 1512 today...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
What governor are you using? Try some settings posted in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Hmm. Does anyone know if the black screen issues started with a specific kernel or release, or were they always just there? I'd gladly roll back to an older kernel if it fixed this one issue. Today I got 16 hours unplugged with 4 hours of screen on time, auto-brightness, autosync, web browsing, gaming, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Apocalypse487:
If you mean when you unlock the device? I think that is a safety feature for butt users. I find it annoying because I never butt dial.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
It is not a safety feature for butt dialer lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
Can we get some more. Txt files of your setups? Love trying different settings.

Freshest nightly/kt747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
It is currently noop/intetactive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Interactive isn't great for battery life. Try ktoonservative or ondemand
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
I tried those as well... Still the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Apocalypse487:
It would make sense if it was lol. So it's just annoying without butt dialer support :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
Interactive is just fine for battery life thank you.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
That doesn't prove anything. Let's see your on screen time :/

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Ive been testing a lot. I can also place 384-1500mhz at 700mV and not crash in testing. I am looking for a way to prove my theory but u believe after a certain amount of mv the volt table can say 700mV but is using closer to stock maybe 25-50mv less. I tested with temps and like was told posts back all stock volt 384-1500mhz, 1458@700mv and tested then tested at stock and every - 25mv down and you get to a lower temp then you do at 700mV. Eventually temps start going back up. It seems if i lower all other mv around the frequency it doesn't matter but if you make sure all mv at lower mhz are no higher than that frequency mv it can continue to drop. Now i also did same at forst and lock min to max at 1458. You can do it on any frequency. According to temps well before you hit 700mV temps go back up. The story changes if you set a proper min max to allow scaling when frequency changes are introduced it shows really if a mv is stable even more.

The undervolt can be possible into 700mV at lower frequency possibly like sone are using but even 1000mhz is not stable on 700mV.

Its a placebo effect the 700mV. I can set min max to 1458@700mv and all the table from 384-1500mhz at 700mV and run the benches at 1458 and pass. Temps are close to stock volt seems it forces a volt closer to a small undervolt. We get farther making a ladder effect on the volts, small to medium drops of mv per drop in mhz.

Stability test even shows there is not as much a temp difference on 700mV as a -50/ - 250mv undervolt.

Like Ktoonsez couldn't understand why some phones were doing this its bevause set proper all the phones are unstable at a true 350-500mv undervolt. Some frequency especially overclocked or underclocked ranges cant take much more than 25-50mv for some accross board others 75-150mv.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lexxa83:
Uv -125 across the board
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Nice lexxa - 125mv is awesome and a nice setup accross the board. So your min is 800mv right? Nice.

Paranoid Galaxy S3 on Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
<edit> this is also my latest with sio/interactive and -100 across the board.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lexxa83:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ser_98:
what's the best settings for cm10 for best battery life ?

i'm using ondemand governor and it's pretty good but I was wondering If I could to something to get even better battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yes, you could try some of the settings posted in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
You could try this thread too

http://xdaforums.com/showthread.php?t=2032956

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lonz358:
Stock battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
What were your governor adjustments
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lonz358:
Didn't change anything there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Why are you using on demand for screen off governor instead of keeping ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
This is a good idea to use Ktoonservative on screen on and off. Plus if you use two separate ones its going to use stock governor settings.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lonz358:
I have no idea, but its working well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Personally my phone take less battery with ktoonservative or abyssplug on idle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lonz358:
I changed it now... Will see how it goes