yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
(Edited due to errors from heavy multitasking... Fixing a crashed server too right now...)

I'm using the second cpu to keep it in frequency a little longer.

Its percentage based if I understand correctly, meaning the second CPU engages at that point in utilization in that step, so essentially cranking the hot plug up that high would shut the second CPU off and rely completely on CPU switching to handle load. Definitely kinder on battery if your phone can handle switching that much.

Ktoonservative originally (prior to latest) had the hot plug set to 65, up frequency set to 67, and did great on battery with stock settings. All I did there was open the margin up a bit since the governor is no longer stable at that setting.

Basically, what I started doing when I saw how unstable it was, was revert to the settings that worked great in prior iterations and start tweaking to get the CPU switching to match (as much as possible) previous behavior.

Since it SEEMS stable now, and I've only put it thru one full charge/discharge cycle, I'm going to leave it as is over the weekend. I'll probably start tweaking for battery Sunday or Monday.

Edit: I will however at that point start narrowing the gap between hotplug up and frequency up, probably by pushing hotplug to 73-74 like a higher version of the original ktweaker. I'm pretty sure that's where a big chunk of my battery drainage is coming from. I'm just not getting anywhere on stability vs battery right now and letting the install settle for a few cycles will eliminate a variable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Are you using any apps that chart CPU usage by load/MHz? I was using a couple of different ones to check this stuff out and turns out that it was causing reboots under load... the worst one was Cool Tool.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Nope, better battery stats and watching the frequency display in ktweaker. So, long term trending off of full charge vs immediate changes to frequency step. I track everything I put on this phone pretty carefully and if it gets unstable, the last thing on is the first thing off.

Usually I uninstall by means of restoring my last full (cache included) backup

I also edited my post I'm doing other things right now and confused myself, so the one you replied to doesn't say what I meant to say.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I don't know of that many of us having this problem with switching freqs to fast. I've read all posts here, which is probably why I can't remember if you said you were having this problem with other govs.. or even other kernels. Did you say it was just with KTs kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Edit: Not really having a problem. The pics I put up were to share my settings with the ppl that were still having a problem. I fixed it on my phone.

Only having issues on the latest release of ktoonservative. I dug that little tidbit about the frequency switching out of one of the links that people keep posting for the I/o governors explanation threads.

I don't use other kernels/governors. I've been using the latest current release of ktoonservative since I was on rooted stock.

I don't think many people would report on issues with the governor switching frequencies to often in a short time. Most people limit their bug reports to "it locked up/crashed/did stuff, plz fix". I'm just taking it upon myself to figure out exactly why, since the problem directly affected me.

Basically the pics I put up were me trying to help the people having stability issues by sharing settings that I have that work. Battery life is a tertiary concern for me. If I cared that much about it, I'd use a neutered tweak of conservative, accept the lag and call it a day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matthenson20:
Does anyone have a link for 10-31 release? The new does not play well with my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tnosz:
Go to page 612 OP posted links there for ICS and jellybean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I just wanted to say I am really enjoying this kernel (and ktoonsez's aokp ROM) and thanks to both I'm getting some insane battery life. 68% battery with 3.5 hours of on screen time!! I have an extended battery but 1 hour of screen time per 10% battery or thereabouts is phenomenal!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
What the flying ****. I have not once been able to get this kernel to run since the first build. I've done, literally, every possible thing to get it to work. Full wipes, different roms, dirty flashes, clean flashes, fixed permissions, clear all cashes, format system, etc. I'm on a TW JB rom, but I've tried the ics kernel as well. No luck thus far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Have you tried running his AOSP JB ROM with his AOKP JB kernel?:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
No, it didn't quite suit my needs. Odd because ktoonsez makes the best stuff around. I guess I'm just not an AOSP guy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
People have returned their phones because it wouldn't run this kernel. U just might be one of those unlucky few :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Wow! Still getting random reboots with this latest build what a pain in the ass, tw ics kernel, back to the 10/22 build I guess something I know gives me no reboots
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tutchthesky7:
Dual booting?

Is there anyway you could implement dual-booting in this kernel? much like siyah? that would literally be AMAZING
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Search is good - he already said that it would be more pain than it's worth with all the kernels he's supporting now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably not, that is waaaaaaaaaaay to much work for a hobby :D. My Siyah for the S2 took months to get that perfected by gk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
Kt, every time after bluetooth turns off the frequency slider doesn't reset back down to previous minimum . ie If min is set at 384 and bt min set at 810 even hours after bt turns off i go into ktweak and ktweak notifies that my values arent my suggested settings. If i hit no to reverting the sttings the slider is at 810. I tried wiping ktweak settings and re installing kernel to no prevail

---------- Post added at 11:08 AM ---------- Previous post was at 10:53 AM ----------

I forgot rom roolbox pro had access to kernel sruff. Cleared and uninstalled.. Will report back.

---------- Post added at 11:30 AM ---------- Previous post was at 11:08 AM ----------

Yeah.. Didn't work. Any other thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
OK. Yes I've searched but I still have one question. How do I kernel? :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What are you doing to disconnect? I only set it to return to 384 when the device sends disconnect message. Are you turning off bluetooth maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
Fortunately I'm getting a replacement soon. Hopefully that one works better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
There's many methods for that. can't think of any thing as a funny come back right now. If your on KT747 your already kerneling :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
It's colonel

---------- Post added at 06:11 PM ---------- Previous post was at 06:00 PM ----------

Anyone have a link for 10/31?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Your left shoulder hut!

"Lead me, follow me, or get out of my way. "
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
Forward march!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
Used the settings on the very first post here: http://xdaforums.com/showthread.php?t=1886233

I cannot go over 1809mhz. Anything over and it reboots on its own... would love to try 2106mhz... any ideas?

2106MHz - 1300mv

1998MHz - 1285mv

1890MHz - 1210mv

1809MHz - 1175mv

1728 MHz - 1130mV

1674 MHz - 1090mV

1512 MHz - 1080mV

1458 MHz - 1070mV

1404 MHz - 1050mV

1350 MHz - 1040mV

1296 MHz - 1025mV

1242 MHz - 995mV

1188 MHz - 975mV

1134 MHz - 950mV

1080 MHz - 945mV

1026 MHz - 930mV

972 MHz - 915mV

918 MHz - 910mV

864 MHz - 855mV

810 MHz - 850mV

756 MHz - 835mV

702 MHz - 820mV

648 MHz - 805mV

594 MHz - 835mV

540 MHz - 825mV

486 MHz - 805mV

384 MHz - 785mV

192 MHz - 760mV

144 MHz - 750mV

96 MHz - 745mV

Ktoonserative / noop

Touch Boosters = defaullt values

Screen Off Profile = 486 MHz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Rise the voltage of everything above 1809
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, +1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
damn my voltages are way lower with no issues 1809 is at 1140MV 1890 is 1170MV 1998 is 1195MV and 2106 is only 1250MV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
i tried the default settings for 1890 and it still crashes during benchmark tests... sometimes if i reset and let the settings load it still crashes.... I guess my phone cannot go over 1809? :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It probably cant, mine wont for over 1809, 1890 works sometimes but not even 50%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Maybe tour sgs3 will never take 1890, maybe you need to go above the stock voltages for steps above 1809
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
Id rather not overvolt.. that would defeat the purpose of saving battery right? :silly:

Its good to know that you guys will not go over 1809.. i thought maybe my phone was messed up.... Oh well.. its pretty quick as it is at 1809 anyway! Thanks guys! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Gonna run hot though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Not really, saving battery depends on governor adjustment and voltages. Since you undervolted every other steps by almost 100mv, over volting the over clock speexwouldnt make much of a difference battery wise. Its not like your phone was always at these steps. Plus, there's a lot of people who needs to up the stock voltages to get the over clocked steps to be stable.

Edit: you don't need to add 100mv you can go by 5mv at a time until its stable.it can indeed makes your phone runs hotter but if its the case you can judge by yourself if its worth it or not.

Reedit: if your willing to try, give me some feedback in my thread(were you got these settings) hope we can get this to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
OK hi all. New to sgs3 but not new to android, flashing blah blah blah

Curious... the swipe to wake isn't working for me. Why... I have it checked. I swipe left to right and nothing.

Thoughts? I did search up and didn't see anything suited to this issue. Thanks all!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
Are you in the right section? Looking at your post count, it doesn't seem like you own this phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tutchthesky7:
But but, that was incredible D:, . anyways, anyway you can put in a BLN mod like the S2? i know the s3 has the LED but i still loved the breathing effect from the s2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi Ktoonsez, I have a question. I was running cm10 and no matter what i did I couldnt get tethering to work on 4G (LTE), so I posted in your AOKP thread about it and they said that this issue was resolved in your ROM. Someone also replied saying that the issue was due to the kernel and not the ROM. Is it possible for you to include this fix into your kernel so that 4G tethering will work with cm10? I do enjoy some features in CM10 that aren't available in your ROM. I have like 6GB of data, so tethering would be nice. Thanks either way. Have a great night~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Tethering works with my newest 11/13 kernel, 10/31 did not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Im on dg stock tw rom 747 version and had some cam and video lag flash this kernel for the version I had and it fixed all my lags and the only tweak I did was set gov to power save..thanks for the kernel. The only thing I have is I saw in op was if you set kt conservite you would have to change the file name so you wont have battery drain thats only for that one setting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
I'm on CM10

I try to overclock but doesn't.

The slider is at 1809mhz but in parenthesis it stays at 1512mhz

I don't get why it won't work

?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Sorry. I should have been more specific. I was on cm10 running ur 11/13 kernel. Tethering worked only when I'm not on LTE (this issue only seems to plague Canadian phones). This is a separate issue from the one in your 10/31 kernel. This issue was on your aokp rom but was fixed according to posts from members in your thread. I'm now on your aokp rom, mostly everything is great but there are some features of cm10 that I miss like popup text msgs. Someone replied saying that this issue is a kernel issue rather than a rom issue, so I asking here if this fix can be applied to your kernel for cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Well since my kernel is identical when it comes to things like that, I highly doubt it, but you never know and I dont own the Canadian variant so I cannot test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
Wow. Apparently you cannot read my post. I said I have a sgs3 i747. Just Cuz I havent changed my sig yet doesn't mean I don't have the phone.

So my question remains.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It is not recommended to use it while you are NOT plugged in as it will drain battery at 2-4% an hour. Sometimes the phone gets a deep enough sleep to not see it on the first try, so its usually the 2nd or 3rd try depending on how fast you are swiping, but does work once you get the hang of it on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
What is the best CPU Governor and Scheduler combination for performance

Except for the performance governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I think you'll get different opinions but I say interactive/deadline
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
I've been getting my best with sio/lagfree 192-1512 and off screen at 486. And uv 192 to 594 mhz by 50mv.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EVOme:
Anyone have a link to the 10/31 JB kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
http://db.tt/nIzDPlBt - AOSP

http://db.tt/ISQY03T3 - TouchJizm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
Yes.. Basically, when I get into my car I have a "Pro Clip" that I put my phone into which is A/C powered, I then use a bluetooth power manager app that runs in the background and will connect/pair my BT device on A/C on. When I turn my car off, the A/C goes off and the app auto turns off the BT.. So maybe I will try setting the app so it doesn't disconnect BT on A/C off and then have a timeout feature for BT have 1 min of no pair.. or something like that :/ ..will report back, thanks.

---------- Post added at 03:18 PM ---------- Previous post was at 03:10 PM ----------

Another quick note, if I manually toggle BT on with no device to pair, and then manually toggle BT off, should it go back down to 384? because technically there would be no disconnect message from a BT device thus no info for Ktweaker to re-adjust min freq?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
I know this is sorta shunned on here, but do you have an estimate for your next release KT? I only ask because the last four clean flashes I have done are with your kernel and later that night you release a new one =p. So I'd normally do a clean flash today. Any plans on one tonight? Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Its not sorta shunned, its REALLY shunned. Never ask for an ETA, these great devs take time out of their day they could use to be doing other things, to create awesome works for the community, and for what? Some donations, that's all. And a few thanks. So that concludes my rant, think about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
The only reason I asked, is that I'm sorta curious if he is tonight. By any means, I am not asking for one today or even for a true ETA. I guess more lighthearted asking than really asking if that makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
My tests.. Summed up using BT min.

When in my car my phone stays paired and connected at all times.

Initial BT connection mhz adjust correctly and stick at selected value (810 in this case)

I receive or make phone call, 810 remains until phone call is terminated, once call terminates, BT min drops to default min although BT remains on and connected to car.

A new call does not adjust the min freq, only if i turn BT off then on again does the BT min re-adjust.

Also, when I connect BT to car as stated before, the min freq adjust correctly, if i do not receive a call and manually turn off BT the freq does not reduce to default however as KT implied if the pairing is disconnected prior to BT off then the freq does reduce to default.

I did this without using 3rd party app to get clearer results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This post above = ETA

ETA Means = Estimated Time of Arrival

ETA + XDA = Not cool ;)

"...but do you have an estimate for your next release KT?" is exactly what you stated. How is this not an ETA? It's absolutely an ETA. Please just be patient and take the releases as they come. Ktoonsez will update when he wants and when it's necessary. Just curious. But what would you be thinking there is to update as of right now? And why do you want one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, I will look at the phone call thing and see if there is an event for Bluetooth OFF to see if I can fix your situation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
But what does flashing a kernel have to do with a clean flash anyway? You can change kernels at will and they NEVER go onto a totally clean system anyway since they are replacing the kernel that came with the ROM that is already there. So you don't need an ETA... just flash the kernel when it comes out.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LaseOfFury:
When i flash this kernel, I loose any display past the bootloader (Frosty V4 Jellybean 4.1.1) The buttons light up and i hear sounds touching them but the screen stays black. I also tried it on the Bell JB Leak and had the same result
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
What kernel version did you install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LaseOfFury:
The one from the OP 11/13/2012 (Touchwiz Jellybean version) but then i tried the AOSP Jellybean for the hell of it and that didn't even give me button lights :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Search is a wonderful thing. This took me under 30 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LaseOfFury:
Thanks...i guess this is like posting a "Let Me Google That For You" link.. But after searching i just found someone else with the problem and i guess "after a couple pushes of the lock/power button you can get the screen to work" but not really a cause or solution or if that repeats itself or is just after first flash..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AOSP Screen ON issue test

Here is a test kernel for those that are getting the issue on AOSP where the screen doesnt want to turn on after it is sleeping. Report back what you see.

http://goo.gl/ygVxC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
Testing. Seems good. :thumbup:

Freshest nightly/kt747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
testing now KT..

don't know about everyone else but I could usually reproduce the black screen by cycling through the lock screen and turning screen right back off and then repeating at least 20 times..1 of the 20 times resulted in the black screen..just cycled through screen on/off 50 times and it did not hang once with new kernel..great work ktoonz :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Unfortunately I'm still getting the blank screen every so often.

I'm on ktoonservative and sio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloudyphiz:
I've been using the test kernel for 15 minutes or so, no problems yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Same here. Doesn't occur as often as it did before though. Using deadline and intellidemand.

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
Okay there is definitely a problem

It won't over clock!!!! Lol i t keeps just going up to 1512!! I move it to anything high...and it stays there then I exit and come back...and boom! 1512mhz max

I'm on CM10 Stable

11-13 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
What are you all using as your minimum frequency?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I think it has to do with performance in settings on cm10...even when its not enabled to run on boot..if you randomly open it from time to time it will not match your settings in ktweaker...I had the same problem with every kernel I tried on cm10..no issues on aokp..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
384

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Ah I was going to suggest moving up to 384 to see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
So far so good here on the black screen. Like another person said tho, not able to OC past 1512. I'm running The Collective ROM.

Knowing its just a test kernel tho......no worries. I'm sure KT will work it out before the official release.

Thanks bro. : )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nickovtyme:
Thought I'd share...this was my Speedtest right after I flashed kernel and tweaked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Just checked mine with Ktweaker and it allows me to set it all the way to 2100 MAX, i have mine set at 486MIN and 1890MAX. Do you have"enable OC steps" checked on?

Im running Task650 JB 11/18 Build.

I have set it at 486MIN because I have had the SOD issue and so far with that setting and on demand governer it hasnt happend.

Edit: here are screenies of Ktweaker and CPU Spy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
NVM.....mah bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
DELETE! im n00b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not sure whats wrong on your phone, but OC is fully enabled, no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Whats one letter, :D

I have been using it with no problem. I hope the AOSP agents dont come and get me while I sleep.

Ktoonsez, is it OK to use for AOKP? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Aosp=aokp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
And also AOCP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
AOKP is AOSP!

Sent from the Dank Device, aka my GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Does this Kernel support NTFS? It seems that my 64 GB does not read. Perhaps I must reformat it to Fat32...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
My test kernel supports NTFS, you'll have to do some searching, I think I put it out there on the same day as release, 11/13