yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
It prevents other apps, such as setcpu or similar, to change the frequency of the CPU. At least that's what I think it does..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Fully charge your phone, set it up so that everything is shut down when screen is off( sync, mobile data, WiFi), use your phone sparingly and get 30-40 hours on that charge. OR use you phone as intended, charge every night and enjoy your "pocket computer that makes phone calls". Seriously with your set up you should be able to day a full day with 4-5 hours screen on unless you have widgets on every home screen and forced full time lte connection. I think most users are getting this unless they are full oc. If you can get up in the morning, use your phone how you want and make it to bedtime on a charge I really don't see the problem. Only tip I can give is keep the screen as dim as possible, that's your biggest battery eater. Think about it 45 hours with screen on at 3 hours is only 1 hour of use per day, not much actual use in my opinion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soul4rent:
I'm sure it's not the same for every device but if I UV too much I get shorter battery life with alot of excess heat without the tale tale signs that I've gone too far like screen flicker.

I read somewhere that if it's uv'd too low on a certain step when it loads up the cpu it throws an error or bogs the cpu down with recalculations then moves to the next step up depending on the governor. I took that to mean that even if my UV is stable at low loads on the first few steps, when I load the cpu with a task that could be completed at a medium load on 486mhz it will still ramp up till it's stable which might be over 1ghz running a much higher voltage than 486 stock voltage which completely defeats the purpose of UV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
the way I look at it is..if you can get a full day..for example take the phone off the charger at 6-7am and use it like your supposed to..off and on all day..texts..net..phone..email..cam..and can get home that night with still 30-50%..I am happy with that..I mean what's the point in having a phone as nice as the s3..if your only gonna use it for a total of three hours over 2-3 days..seems like a waste..don't get me wrong I like good battery life just as much as the next guy..but i also would like to use the phone I pay so much for each month..not just look at it while its sleeping..to see how long I can make the battery last lol..no offense to any of the hardcore battery fanatics intended :D

edit..I also should add that I have zero problems making it home at night with 30-50% battery left under the above conditions..I use the piss out of my phone all day..this kernel ensures that I no longer need to carry a charger with me everywhere I go..

I use..sio and interactive..96mhz and 1624mhz..minus 40mv on all frequencies..vibration=75..everything else is unchanged
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
I am even more confused than you are. First off, I am total noob to CPU tweaking. So first stupid question: Where and how do I set "Vibe"? I replicated everything that you have here and my phone went crazy. It was totally unusable. Flickering all the time and apps just constantly crashed. So now I am back to Frosty JB v2 on Rogers GS3 with Ktoonservative and Deadline set in KTweaker.

If I get even 18hrs of moderate to light usage with 20% or so left to plug it in at night I would be a happy camper. Thanks for any help you guys can offer.

PS: I have already gone through almost all the settings and tweaks that I have come across on the web to extend the battery life. I don't play games and I watch a few youtube videos every once in a while. Basically I only use it to browse the net or WhatsApp when I have some downtime waiting for something or someone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ztmike:
Does setcpu not work with this kernel?

Just noticed in OP it says to use a app called KTweaker but gives no mention to where you actually get this app? Checked play store and its not on there..

Never mind..it was downloaded with the kernel lol.

But one last question..does this automatically over clock the GPU? Don't see any options for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
"Vibe" is vibration intensity. It's in Extras in KTweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It auto installs when you flash the kernel, Look in your app drawer, its called KTweaker, there is also a widget. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ztmike:
Yea I figured it out after messing with it..I reedited that post with one last question though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I wish I could make you a widget. I would keep you on my home screen. ;) :highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No GPU OC, it was removed since it provided NO gains at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AMLO! DITtO!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ztmike:
Thanks for the reply. Running good so far at max over clock on Tasks 10/16 ROM build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
ktoonsez : is this the same Kernel that is on AOKP? like if i flashed AOKP , do i need to flash this as well if i want your Kernel? if not which Kernel comes with AOKP?

Cheers,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
We use the stock CM10 kernel for the ROM, you will have to flash my kernel right after flashing the ROM each time :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrygooch:
Is this fact? It could explain why my battery life is lower than it used to be. My phone can uv very low. Perhaps there is a point it's to low yet not low enough to cause screen flicker and random reboots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You need to see what is eating your battery like that. Sometimes Maps or the Media Scanner can be at blame, but really any app can start polling relentlessly and wreck havoc with your battey. Get Better Battery Stats and CPU Spy to see if your phone is sleeping properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Is there any way to tell what clock you were at when you crash? I had my first crash in a day or two and don't want to bump the voltage on all of the clocks. Even something for future crashes would be awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Future crashes?!

Ktoonsez could totally strap a flux capacitor to his C6.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Cooltool in the play store can help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Yeah, so like if my phone crashes again, I can just look at a log and see what clock it was at when it happened.

This is great for when I am using the phone, but this time the phone was just sitting on my desk and I wasn't looking at it. I am looking for more of a log for when I start the phone back up. Sorta like when StabilityTest crashes, it gives info on the crash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iKidRobot:
i'm coming from a stock kernel and i'm really new to UVing and OVing. any tips for better battery life but not sacrificing too much on performance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
See the third post on the first page

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Check out better battery stats. It tracks things like that. I have noticed that when I get too carried away on uv, my midrange frequencies are utilized more and it will show a lot more usage on 1134mhz, my top step. Turning my voltages up (not by much either) almost completely stopped my top step usage.

I think the phenomenon exists but (on my phone at least) its in the very narrow margin between "hopelessly unstable" and "I can do what I want"

I also set freq_step to 1 and my up_threshold for 90, which seems to work really well up until I hit that narrow window, then it crashes like a mother.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fizzer82:
Two things to consider here.

First, power consumption is a function of both voltage and clock. The common formula I've found is: P=CV^2f. Where P is power (watts) C is capacitance (let's call that a constant for the sake of argument) V is voltage, and f is frequency. So, voltage has a greater effect, but say 96mhz @ 900mv will use less power than 486mhz @ 900mv.

That alone would indicate that the lowest speed would be the best min value. Your our other statement about completing tasks is also valid, but no so much for the min setting as the processor will scale to meet demand (as we know controlled by the governor). It is a consideration however for your max screen off setting. It you set that too low, you could have background tasks chewing up more battery as the tasks take longer to complete and keep the cpu out of deep sleep for longer. The proper setting there will be determined by what you phone does while the screen is off. If it's set too high and you run a governor that does not step down quickly enough, you will be consuming more power than necessary. If set too low and you have processor intensive background tasks, you will be consuming more power by the cpu staying out of deep sleep for longer than necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soul4rent:
That's pretty much how my phone acts. This is -125mv across the board another -5mv and the lowest step with any significant use is above 810. In theory that means trying to save that 5mv actually cost me 100mv.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
This one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancaperez2000:
never mind
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Under general click enable oc steps, and watch the magic
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] csjesse:
stupid question.. but for underclocking only, is it recommended to Enable OC steps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
Been getting bad battery life with this kernel and I wanted to try out a new one. Do I just install the new kernel over this one? or do I need to wipe this kernel first somehow? Im runnining LiquidSmooth JB on my S3.. please help! Its not booting right now after installing LeanKernel over Ktoonsez kernel on JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Good info

Any idea if CPU chip manufacturers optimize the chip to be idle at stock min (384)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not sure what it could be, personally my phone wont even boot with LeanKernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
Really? I've been getting amazin battery life (13+ hours with heavy use on 4G for 8hours). What are your kernel settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I don't think it matters. I think it's just based on what you set the CPU speed as.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
I agree, sounds like you're seeing almost the exact results I am. I initially went - 150, and wound up settling in at - 135 before everything started to really click. At - 150 I was seeing a lot of 1135 usage, at 135, I was seeing mostly 92, with a heavy dose of 144
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hiquin:
So ktoonsez, any chance of a TouchWiz version of 10/16? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I will be building all versions tomo or Saturday using the "super crazy fast" flags. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeromechrome1:
Ktoonsez any chance of a version of your amazing kernel for Drewgaren's TW JB ROM? Would be very much appreciated by thousands of us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Hell yeah! Is that the secret version I'm running from Saturday or will it be updated?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
I was running it at 1134mhz and applied the standard voltage settings that come stock with the kernel settings. I was using this on AOKP rom and my first problem was that the ktweaker app wasnt applying my settings at reboot. I finally got the settings to stick. I used it for about 2 weeks and I wanted to try out a different Kernel, though im pretty sure Id be coming back to this kernel eventually. When I installed the other other kernel, my phone refused to boot to the home screen. I had to restore a nandroid backup..

---------- Post added at 06:13 AM ---------- Previous post was at 06:11 AM ----------

Yah thats the problem Im facing now. I was able to run leanKernel a few weeks back, but thats because I installed it right after I updated my rom. I then installed your kernel and things worked fine, but now Im trying to go back to leankernel for a few days but the phone wont boot at all. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Lean, CM10 and KT kernel have all changed around the 15th and will not boot with a ROM built before the 14th. Check ROM dates, you may need to load an old kernel from before the 15th, or one of the lastest kernels if using a ROM built after the 15th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
home button wake delay

Sometimes the phone does not wake from sleep when using home button. I'm running 10/16 and Ktoonsez latest kernel (3.0.46-KT747-g1324643), Lock frequencies enabled, ktoonservative/cfq, no U/V

Keep up the great work - 9MF37243Y3681942X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man :good:, ya its a known issue with AOSP, it happens on all kernels (stock and custom). Its getting better but still isnt 100%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkeaver:
Try deadline gov with ktoonservative. I had the same issue and it cleared it up. Haven't had it since. Might be a coincidence but ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Ok Ktoonsez, this is just absurd!!! I wanted to tweak my UV some more. Thought I'd start with my Max (1728) and work my way down from my current UV steps... sure no problem, first two OC steps undervolted another -5mv (1075mv @ 1728 Mhz) and -10mv (1060mv @ 1674 Mhz) respectively (@ -10mv & -15mv, I got reboots with Stability Test). Then I got to the stock 1512 MHz step.... yeah, I've been testing this step for almost the last 2 hours!!! I started at my previous UV step of 1060mv, with a classic stability test (yes, I have my min & max set to 1512) every -5mv. It got to the point that I switched to -10mv at a time....

I'm at freaking 940mv on 1512MHz

, and just completed a 15 min stability test, and a bench mark test, with no reboots!!!! :good::good::good::good::good:

I was just trying to find a semi-stable mv vaule for each step, and then do a multi-hour scaling test to really test it out... I'll be lucky if I even get to that today. I am having to recharge my phone, b/c I ran it down from 95% - 5% just testing the 1512 Mhz step, and I'm not even finished. Holy hell man, this kernel is FREAKING AMAZING!!!!!!!

Will post my full UV table once (if???) I ever get it finished. :p

Stay tuned....

Oh, btw, I'm running AOKP 10/16 & your corresponding 10/16 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
And...I hate you...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lokesh1699:
what software do u run stability tests on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You can get some from the market... dont know names...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lokesh1699:
okay..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
I second that lol :what:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Lol... I use get this... "stability test"...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
LOL i looked it up saw it... but I don't need it... my phones rock solid...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vineet381:
Hi,

I am really new to this as its only 2 days since I got my s3, I m on AOKP latest (10.16) ROM and want to try this kernel, which version should I flash..is its "AOSP JB on or after 10.14" ? Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
The AOSP JB... latest version... there a 10/16 I believe...

---------- Post added at 03:08 PM ---------- Previous post was at 03:06 PM ----------

Here's 10/16.... It's not in the OP... It's posted some pages back...

http://www.mediafire.com/?y3rymjlozs5h5t0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jde984:
Actually that is the one posted in op ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
sho is... thx for pointing that out...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
This is my results so far today with everything off except data and using my previous posted voltage settings. Seems pretty low to me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
looks bad... have u flashed recently? do u have better battery stats to check for wakelocks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
Im on 10/16 aokp + 10/16 k747... this screen is from earlier today... you definitely should try other settings in ktweaker + you have something waking your phone up for long period of time... as Quasimodem already said check what's waking your phone with better battery stats

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
mind sharing ur settings? I'm using the ones posted by Swiftks-dawg...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
i'm using this setup

---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------

those settings were good on 9/13 aokp+k747 ... can't imagine how much undervolting it can get more with the new 10/16 :D after my battery cycle on those settings i'll try switz voltage table if he post it :D sounds great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Just set those thanks man... here's swiftks UV... not much different from yours...:

http://xdaforums.com/showpost.php?p=32806960&postcount=5212
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
I'll have to try that I think I'm on so kntoonservative with similar voltage settings with my max screen off set at 486

---------- Post added at 01:03 AM ---------- Previous post was at 12:54 AM ----------

I posted my voltage and CPU setting awhile back but I'll try what you said and report back

---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------

This is exactly what I was using when I posted the pictures
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
I was talking about those Swiftks's settings & voltage table :D sounds awesome

http://xdaforums.com/showpost.php?p=33012257&postcount=5490

also keep in mind you are using your DATA connection 100% of the time.... huge battery hog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Stupid question but how do I get that down
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
System settings > Data Usage > On-Off switch

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Before I list me updated settings, I'm gonna start with a quick question to KT... Are we sure that all frequencies within the stock values (486 Mhz - 1512 Mhz) are actually applying the undervolt settings?

I'm not trying to be rude or question your great work, as I know very little about making/compiling kernels, but my UV for the upper threshold of stock (1512 Mhz), just kept going down and down... it got the point where I was testing like 820mv on 1512 Mhz, with no crashes. However, the under clock (96 Mhz - 384 Mhz) and over clock frequencies (1674 Mhz - 1728 Mhz) have very clear thresholds for my phone, and will reboot fairly easily if I cross them. Maybe the kernel is just that awesome, and I happen to luck out with a killer phone. But I would encourage others to mess with their UV settings within the stock frequencies, to see if they are experiencing what I am. I haven't tried let, but I'm fairly certain I could have set all my stock frequencies to 800mv and have been just fine. Since I am using 26 of the 30 provided frequencies, I spaced them out a bit, just for neatness sakes... don't really see a point of running 18 frequencies at the same voltage, kind of defeats the purpose, if their all drawing the same amount of power. :silly:

That being said, here is what I am currently running with 0 problems thus far. I tested these settings with Stability Test, using the scaling test (currently over a hour so far). *See pic below.

If you are going to try these UV settings, please make sure to disable set at boot; less you get stuck in a bootloop.

ROM: AOKP 10/16

Kernel: KT747 AOSP JB 10/16

Min: 96 Mhz

Max: 1728 Mhz

I/O Scheduler: deadline (stock values)

CPU Governor: ktoonservative (stock values)

Touch Boosters: stock values

Screen Off Profile: 486000

Vibration Strength: 90

Voltages:

1728 Mhz = 1080mv (had to raise it back to my previous settings, the only crash I got was at this value)

1674 Mhz = 1060mv

1512 Mhz = 970mv (could have eaisly been 800mv, but I had to leave room for the other frequencies ;) )

1458 Mhz = 960mv

1404 Mhz = 950mv

1350 Mhz = 940mv

1296 Mhz = 930mv

1242 Mhz = 920mv

1188 Mhz = 910mv

1134 Mhz = 900mv

1080 Mhz = 890mv

1026 Mhz = 880mv

972 Mhz = 870mv

918 Mhz = 860mv

864 Mhz = 850mv

810 Mhz = 840mv

810 Mhz = 840mv

756 Mhz = 830mv

702 Mhz = 820mv

648 Mhz = 810mv

594 Mhz = 800mv

540 Mhz = 790mv

486 Mhz = 780mv

384 Mhz = 770mv

192 Mhz = 760mv

144 Mhz = 750mv

96 Mhz = 740mv

If you try these and are getting a crash, I'd suspect it's most likely the lower underclock, or high overclock values.... but what do I know. :o

Hope this helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Great work. Yes they are applying for sure (stock steps are actually 384-1512). It is a table that applies the voltage per step in a loop so there is not room for error and my phone reboot if I mess with any of the higher steps (1134-1512). Again, great job :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psloan:
Thanks Swiftks. I gave yours a shot. i am running stock tw rom. As soon as I tried to run the facebook app, my phone rebooted. rebooted again right away after the crash. I had to go in and add +25mv across the board to get the phone to boot and run facebook again. will tweak from there.

--pat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Use Friendcaster... Better app with less permissions. :p

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwahchees:
Bug:

On Paranoid Android ROM 2.22 (10/13) running Pre 10/14 KT747 Kernel, the cpu cores go all wacky. Sometimes the second core maxes out and stays there. It doesn't work like the first core would with the incrementally going up the scale to hit target freq. This is on Ktoonservative.

Hate it :C could you please explain why this is happening :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Are you uv, if you are you may be to low
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Pardon me, please what is the name of the app that tells me what clock speed I was on when the phone reboots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Stability Test, but that's only if you're running it when it crashes (i.e. you're doing a stability test).

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lohanchien:
Looks like you have background processes coming on when your screen is off and taking a long time to complete. Doesn't look like you are hitting deep sleep. Increase your max mhz for screen off to 1026 and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
So just shut my data off? I still need to be able to receive calls and what not. I heard of an app awhile back that was supposed to kill all programs so the phone would sleep way more
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Calls and non-MMS texts will work normally.