yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ktoonsez:
This version will only work with from TODAYS CM nightly (4/19) or newer

Change Log 4.19.2013

1. Linux 3.4.40

2. Linux 3.4.41

3. ROW scheduler updates

4. Update to date with CM and code aurora

5. Lots of Linux patches for SMP and some optimizations

6. More but no time........
[Verizon Samsung Galaxy S III] ddurandSGS3:
thanks for the update ktoonz.

ive been using your kernel since I started flashing and never realized how big of a role it played in my phones stability and performance. Ive been stuck on the stock CM kernel of a rom recently and it doenst even come close to comparing.

Thank you for the work that you do.
[Verizon Samsung Galaxy S III] Blaiser47:
Just flashed on latest slim build 4 and boots and runs great so far. May have even fixed my flickering issues. Thanks! :D
[Verizon Samsung Galaxy S III] mike216:
Don't flash 4-19 on liquid 4-16 or earlier. Wouldn't boot for me and my guess is liquid is not up to date yet? Very sad. It's all good sooner or later I'll be running it. That's all right, I thought 4-11 was perfect as is anyways.
[Verizon Samsung Galaxy S III] jlee08517:
in his post it says right in red to not flash the new kernel on anything older than cm nightly 4/19.
[Verizon Samsung Galaxy S III] mike216:
Yes it looks like I missed it. I'm sure many like myself wake up see something new and don't read thoroughly. It's not the first time I screwed myself by not following directions and unfortunately I'm sure it won't be the last
[Verizon Samsung Galaxy S III] tihsllub:
Well whatever you do don't try flashing a ROM with your buildprop changed. Bad bad bad bad things happen.

Sent from my.........
[Verizon Samsung Galaxy S III] Deliquified:
Like what? Your build prop gets overwritten..? Oh noes.
[Verizon Samsung Galaxy S III] tihsllub:
Ever used mobile Odin? If you change your build prop to install Google wallet. And you open mobile Odin with your build prop changed it will download the nexus add on automatically. And then when you try to flash. Bang hard brick.

Sent from my.........

---------- Post added at 01:16 PM ---------- Previous post was at 01:06 PM ----------

Is it me or does trinity colors clean up the colors? I notice that since I'm running this KT kernel I compared my phone with my girlfriends and her white colors are a bit yellowed while mine are well pure white.

Sent from my.........
[Verizon Samsung Galaxy S III] TheDriller:
That's why you should use recovery instead of mobile Odin. Mobile Odin was only useful on the e4gt now, not so much

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] Deliquified:
No i have not. I only use desktop odin. The reason it does this is because your build.prop changes from d2vzw(SIII) to the nexus code name (Toro?) It tricks Wallet into allowing it to install. The same occurs with mobile odin. It thinks you are a nexus, flashes software not meant for your phone, and you brick.

Morals of the story: Always read the OP thoroughly. The wallet thread states to ensure your build.prop is stock before flashing anything. Verify what you are flashing before flashing, and always make a backup.

Trinity colors fine tunes the colors to be more accurate. If you want to really see a difference, turn them on and go to settings > device > advanced > Galaxy S III Settings > mDNIe scenario and try out the video option.. Watch a video on YouTube and see the difference.
[Verizon Samsung Galaxy S III] dtowngs4g:
Same with carbon rom 1.6 it wouldn't even boot but Koontz 21913 flashes and boots.
[Verizon Samsung Galaxy S III] mike216:
Thanks for the response my friend. I should have read more thoroughly. The latest if only for CM10.1 based roms from 4-19 and on.
[Verizon Samsung Galaxy S III] Setco:
Running Carbon's 4/20 ROM with K747's newest 4/19 kernel. Clean flash. Running smooth. Good battery life so far.
[Verizon Samsung Galaxy S III] dtowngs4g:
I will try carbons nightly instead of 1.6.1! Love me sum carbon
[Verizon Samsung Galaxy S III] masri1987:
I've always had problems with carbon but will try it again.
[Verizon Samsung Galaxy S III] CraiaSoftware:
With the 3.14 version and earlier I was able to overclock to 2106. However, since 3.27 (and 4.11, 4.19) I can't go above 1809 without the phone crashing and rebooting.

What changed? Should I accept that it is capped at 1809 or is there some tweaks I can make to step it back up to 2106?
[Verizon Samsung Galaxy S III] tihsllub:
No I used maguro buildprop. Also it was a backup I restored. I saved it so I could restore wallet. And I open all my root apps to save grant/deny privileges after every flash. I used mobile Odin to clean flash/wipe my phone I was having issues with my framework.

Sent from my.........

---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------

And yes I knew what happened when I tried to flash. My screen when blank and I pulled my sd card and put it in my other s3 opened up my SD and noticed the modified build prop I saved after looking into it. Aka device name in about phone said galaxy nexus. My whole point is that I knew what I did and I'm just informing the masses.

Sent from my.........
[Verizon Samsung Galaxy S III] Blaiser47:
See kt kernel thread, all kernels had a calculation error so you weren't really clocking as high as you thought. Now it is correct and so when you go over 1800 something it can't handle it. However be assured it is still clocked as high as it was before, just now the numbers are correct.
[Verizon Samsung Galaxy S III] TheDriller:
Its been answered a dozen times... I'll save you the search though. There was a math error in the previous kernels so you weren't actually at 2.1GHz it was more like 1.7 or 1.8 but now its right and yes its sometimes possible to go that high but you need to over volt a whole bunch

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] tihsllub:
Hahahaha I how many times do I have to read about this? Do I have to put the answer as my tapatalk sig?

Sent from my......... no 2106 probably won't work anymore. their was a math error in the script for all the OC algorithms. so that means the old 2106 is roughly 1857. 1899 probably won't work either.
[Verizon Samsung Galaxy S III] dtowngs4g:
I tried and i keep getting reboots with the kernel. Uninstalled it. I really want to try it :(:confused:
[Verizon Samsung Galaxy S III] tihsllub:
I'm not sure any of the 3.4.4xxx kernels are meshing with carbons newest build. I think the baked in CM kernel is the only one.

Sent from my......... no 2106 probably won't work anymore. their was a math error in the script for all the OC algorithms. so that means the old 2106 is roughly 1857. 1899 probably won't work either.
[Verizon Samsung Galaxy S III] Aali1011:
Tried the newest build on the mastamoon 4/19 & 4/20 build with no success :( tried doing a clean install should dirty do the trick? Or is his build not fully up to date?
[Verizon Samsung Galaxy S III] brandoncarlson33:
New kernel works awesome on liquid 4/20 nightly thanks KT!!!!
[Verizon Samsung Galaxy S III] Stranger_84:
I tried it in slimroms build 4 and it worked ... Carbon roms rarely play nice with anything other then stock kernels ... Or at least I couldn't get em to work without issues
[Verizon Samsung Galaxy S III] Setco:
Did you do a clean flash?
[Verizon Samsung Galaxy S III] macman159:
Hey guys can someone help me understand in why my phone hates kt kernel? BTW this is touchwiz version. When I restart the phone, everything flickers, the symbols on the status bar go on and off, everything force closes. Does anyone have this problem and has solved the problem?
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Carbon 4/20 + KT 4/19 kickin' A on my phone. Battery life is noticeably better than previous Carbon nightly I was on (I forget what it was-- maybe 4/17?)
[Verizon Samsung Galaxy S III] tihsllub:
Um did you back you phone up first. Then factory reset. Flash ROM (if needed) flash kernel flash gapps then advanced restore data. Wipe cache/dalvik (just for good measure) fix permissions.

Sent from my.........
[Verizon Samsung Galaxy S III] axne1:
So far so good. Using 4-11-13 :D
[Verizon Samsung Galaxy S III] b1g.p0ppa:
I do backup, but I don't mess around with all that. Using TWRP I backup, wipe /system, queue up ROM then gapps then KT (in that order) and let all 3 flash, then wipe cache/dalvik and reboot. Works great unless its a non-bootable ROM in which case I restore from backup and wait till the next nightly drops.
[Verizon Samsung Galaxy S III] soapinmouth:
Getting random reboots galore with latest kernel and latest liquid nightly not sure which one is causing it, updated both at the same time.
[Verizon Samsung Galaxy S III] m-cat:
Hey,

I just flashed this on a jellybean TW ROM and ktweaker keeps crashing on me. The steps i took where to flash, clear caches, and fix permissions. Any thoughts?
[Verizon Samsung Galaxy S III] PsiPhiDan:
I wonder if there's much difference between liquid 4/16 + ktoonz 4/16 and liquid 4/20 + ktoonz 4/19?

Going to update today and find out! It's hard to imagine getting any better than this.
[Verizon Samsung Galaxy S III] axne1:
Can I run Ktoonz 4-19 with liquid? I got a black screen when I flashed it with Liquid nightlies 4/16.

EC Nationals

Wisconsin State Champs 2012
[Verizon Samsung Galaxy S III] Stranger_84:
Its very simple instructions ... 4-19 kernel is for all releases AFTER 4-19 only

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] tprophit:
Ok, that is working much better (75/80), sampling holding at 45000. Much lighter phone usage, and the late drop off coincides with most of the talk time. I would love to figure a way to preserve battery during talk time.

Also, at about 25%, changed my freq step based on the mod discussed in the other thread.
[Verizon Samsung Galaxy S III] masri1987:
was using liquid 4\16 with the 4\11 ktoons kernel, and battery drain was massive using row and ktoonservative

now using liquid 4/20 with 4\19 ktoons , battery drain is 'better' but not the greatest, but getting a lot of screen flicker as well that wasn't present on previous set up, also reporting this on liquid thread so you don't flame me lol
[Verizon Samsung Galaxy S III] Deliquified:
Sounds like you got a corrupt cache. Try this. Settings > Apps > All tab > KTweaker > force stop & clear data > Reboot to recovery > Reflash kernel > wipe cache and dalvik cache > fix permissions > reboot.

If this doesn't fix it, Reflash your rom & gapps in recovery, reboot, let everything load, back to recovery, flash kernel, wipe cache & dalvik cache, fix permissions, reboot.
[Verizon Samsung Galaxy S III] VinBertinelli:
Can anyone confirm that this works with the latest AOKP?
[Verizon Samsung Galaxy S III] juancaperez2000:
Wich latest? The Milestone? Nop, maybe if Bee or Hilber trow a really new one, yes
[Verizon Samsung Galaxy S III] VinBertinelli:
OK there should be an official nightly tonight, I guess I'll flash that and KT later on
[Verizon Samsung Galaxy S III] soapinmouth:
Ok I tried switching roms, wiping data, and switching governors and I'm still getting random reboots on the latest ktoon kernel.

Edit: I went from Latest liquid nightly to the latest carbon nightly.
[Verizon Samsung Galaxy S III] Hybridnoob:
Try latest CM - one that's known to work. I hear Carbon has problems.
[Verizon Samsung Galaxy S III] bgolden84:
I would even be up for some beta testing lol. Not trying to be pushy. Just loved the work you did n the sprint forums. And love the vzw kernel. Hell I've been running bmc 8/26 brick for a while. Every other aokp rom has some odd issues. And In my opinion it's the most stable. Xoomdevs stuff is pretty good to

---------- Post added at 12:46 AM ---------- Previous post was at 12:34 AM ----------

I gave up trying to compile from source after my son dumped his cup of milk on my laptop. Bad bad day. Lol.
[Verizon Samsung Galaxy S III] ktoonsez:
None of my kernels will work with TW-JB
[Verizon Samsung Galaxy S III] bgolden84:
Still don't think I could use a rom called jellywiz. Just sounds so wrong lol. Jk
[Verizon Samsung Galaxy S III] duarian:
Not sure if its synergy or what, but sometimes when switching governors my CPU 1 stays at the minimum refusing to go offline until I reboot. Not a huge deal. I am on R50 of synergy. Can't say for sure if its a synergy issue or not but either way just in case this happens to anyone else, try rebooting.
[Verizon Samsung Galaxy S III] jgrimberg1979:
Alright I tried using voltage control and attempted to fix the problem and still super laggy and hot. For now I can't mess with it anymore, spent a lot of time trying to figure this one out. Hopefully it gets worked out one way or another
[Verizon Samsung Galaxy S III] ktoonsez:
Voltage control wasnt a fix, I wanted to know what the maximum Mhz was set to when u had the super lag? Also, are u setting the "Lock Frequencies"?
[Verizon Samsung Galaxy S III] jgrimberg1979:
I had it set on different frequencies. I tested different ones and it was still laggy. Anywhere from 14k to 18k. Yes I had lock frequencies checked
[Verizon Samsung Galaxy S III] fr8cture:
Just flashed this about an hour ago so far so good!
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Why does system tuner always show my CPU 1 as offline no matter which governor I use? I am noticing a lot of stutters ever since I flashed this kernel and been using it this whole day and wondering if that's the cause of the problem. Could it be because I have CPU Sleeper (it turns off one of the cores when I lock the device) if one of the cores just won't turn on after I unlock my device?

Edit: I uninstalled CPU Sleeper, locked my device for a few and CPU 1 will not turn back on. It seems that if I switch governors it comes back online and then like 30 seconds after locking the device and unlocking CPU 1 is down.
[Verizon Samsung Galaxy S III] ktoonsez:
What governor? What ROM? What is your Min and Max Mhz?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I am using Synergy Nightly r67 with smartassv2 but really, this issue is happening with ondemand too so I'm guessing it's with every. And I'm using 2.1 ghz max and 384 min I've tried other max frequencies but it doesn't do anything. And yes I have OC locked in the ktweaker app. I'm wondering if his may be a rom issue.
[Verizon Samsung Galaxy S III] ktoonsez:
Im not seeing anything like that and I have used ktoonservative and ondemand on task's and I AOKP ROM. I use 192 - 1512 as Mhz and underclocked to 875 at 192Mhz.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Then I guess it may be a rom issue. I need to see if more people actually notice or have this problem on synergy rom. That's a bummer because there is no other rom out there as good as this TouchWiz-ICS wise IMO...
[Verizon Samsung Galaxy S III] Haro912:
Using the abyssplug governor on xoomdev aokp, latest, and my cores are coming on and going off alright over here.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] duarian:
Are you sure its not just staying offline while your watching it? CPU 1 will be offline most of the time to save power and only comes online when needed.

Try sending yourself a text and then quickly opening up system tuner and seeding if it pops back on. Or lock your screen at the CPU part of system tuner, and then unlock it to open back up to it. Just watching system tuner won't bring it online because your not doing anything CPU intensive
[Verizon Samsung Galaxy S III] schmaltzy:
I posted this a few pages back but never got a response. Sorry for the repost but I'm just looking for some answers!

I know what a kernel is and does, but that's about all I know. I just read up on the different governors and i/o schedulers, but I have a two part question:

1) What does the PEGASUSQ do? I thought I saw someone in another forum suggest using that governor but I'd like some more info on it if possible.

2) Which governor and i/o scheduler do you guys suggest using? I know a lot of it is personal preference, but I'm just looking for some suggestions.

Thanks!
[Verizon Samsung Galaxy S III] juancaperez2000:
Just guessing if someones are getting problems with ktweaker app, could we remove the app and manage the kernel either with setcpu o voltage control and get the same kernel privilegies or ktweaker is doing something really special thanks in advance
[Verizon Samsung Galaxy S III] epagib:
http://xdaforums.com/showthread.php?p=28647926

You can find description of Pegasus in link above.

I've read that for I/o schedulers: sio>noop>deadline in terms of performance.

Smartassv2 has been tested to be one of the top governors in term of performance. Most people pair it with noop.

I use Interactivex and sio. Has been great mix of performance and battery.

Sent from a SYNERGIZED GalaxySIII
[Verizon Samsung Galaxy S III] pdinphx:
I posted this in the Synergy ROM thread, although it probably belongs here.

Installed both 8-24 and 8-31 versions of Sammy yesterday, while running Synergy.r68.

Phone was laggy and extremely unstable. OC'ing to 2.1 guaranteed a hot boot, even with increased voltage, and twice the phone went into a slow boot loop.

I went thru ondemand, ktoonservative, badass, smartass v2 and a couple of others ... all with the same results.

I'm willing to go back and provide logcats, if that might help. Or anything else for that matter. This kernel option is very exciting ...
[Verizon Samsung Galaxy S III] MrBrady:
Running the TW kernel in Synergy. I don't see InteractiveX, but I do see Interactive. Which version of the kernel are you running?
[Verizon Samsung Galaxy S III] macman159:
Here are some pictures of what is happening. I flashed the new beans 15 build and same thing, I might give it a few minutes, but here is what happens. The screen just flickers and blacks out the phone, and also it seems as if it loads android again without restarting.
[Verizon Samsung Galaxy S III] Deliquified:
What you just described sounds like a hot reboot, which is usually a insufficient voltage issue. Check your settings. Have you tried this?: Settings > developer options > disable HW overlays. You must reenable it with each reboot.
[Verizon Samsung Galaxy S III] 6GDominator:
Hi,

Does this kernel has better battery life compare to Siyah Kernel?

Does this kernel support PA 3.15 which running on my Samsung Galaxy GT-I9300?

Thanks!
[Verizon Samsung Galaxy S III] Androideka5:
Is this not compatible with AOKP? I flashed build 6 and flashed the 3.4 kernel and it would black-screen on boot, but my soft keys would still light up
[Verizon Samsung Galaxy S III] pettigrew95:
Was running the lulzactive governor with ROW scheduler and was getting very random reboots occasionally. No UV'ing at all. I then switched to SmartassV2 and ROW scheduler and since so far so good.
[Verizon Samsung Galaxy S III] effendi9:
Use the 4/11 kernel for AOKP. 4/19 doesn't work.
[Verizon Samsung Galaxy S III] grislieber:
...um, yes it does.
[Verizon Samsung Galaxy S III] effendi9:
If it is AOKP Milestone 1, which I presumed he ran, it won't.

---------- Post added at 05:16 PM ---------- Previous post was at 05:14 PM ----------

Mr1 milestone 1, that is.
[Verizon Samsung Galaxy S III] mw86:
Try lower screen off max mhz in extras and dont hit disable during calls. This way over longer periods of time of phone call you only hit a certain max. If your not using one now how about set 918mhz as screen off max?
[Verizon Samsung Galaxy S III] tprophit:
Thanks. I've actually been using 378 as screen off max.....but have disable during calls enabled. Is that too low. especially if disable during calls is disabled?

Thank you.
[Verizon Samsung Galaxy S III] mw86:
Yes during calls your using full speed if necessary hence that quite difference in drain... 378 screen if max could effect things eventually. Im trying to be sure you dont go to low causing call issues. You can try 378 but i would recommend 486 at lowest and maybe 702-756 if you want to be lower than 918mhz. Basically make a few calls on different setting and see what helps seems to work without issue. If you can manage low than it should help battery drain. Keep radios off if you can that are not used.
[Verizon Samsung Galaxy S III] tprophit:
The lightbulb just went off.....

Since my batter MHz control is set to go to 1080 at 40%, and 810 at 25%, does it make sense to have screen off max also 810 so there is no conflict?

And by radios, I assume you mean location services/gps? I never ever use location services, and gps only when navigating.

Thank you.
[Verizon Samsung Galaxy S III] scorchedsky:
Something is weird with Wi-Fi in the 4/11 TW JB kernel.

At work, I have a really nasty, noisy wifi signal - stock kernel would hear chatter from who knows what devices. The app "Network Log" let me see all the traffic was kernel related, and coming to and from IP's on the network (I was 172.21.x.x, same as all traffic the kernel saw idling).

Since like October, I've been running ktoonsez' kernels and they completely get rid of this. This "dirty wifi" causes the download arrow to be constantly lit up, and it's UDP traffic from other devices on the network. All of ktoonsez' kernels got rid of this noise, up until the 4/11 version.

Did something change in the 4/11 kernels' wi-fi module that can explain this? Switching back to 4/4 gets rid of it. I'm not sure how you'd test it if you didn't have a dirty wifi network nearby...
[Verizon Samsung Galaxy S III] mw86:
Yes 810 is a good start :) just give it all a try in a phone call and see if your getting better battery. I dont remember if i mentioned but Noop is the most battery oriented scheduler.
[Verizon Samsung Galaxy S III] tprophit:
Thanks, yeah, I switched from row to noop about a week ago. No appreciable difference in performance; I'm slightly OC to 1674, and UC to 189. UV -50 except for 1674 and 1512, which are at stock voltages.

Using 4/11 carbon, I've heard 4/20 is better on battery....it's hard to get it dialed in with so many variables.

What do you think of UV-ing another 25?

Thank you, I'm learning a lot here...
[Verizon Samsung Galaxy S III] mw86:
Depending what voltage table was stock for you another - 25mv might be fine but i would not go further unless you want random issues... There is a point errors occur and no crashing making a poor user experience so goal is be sure your stable in anything you do. If i under volt to low and type on tapatalk my keyboard flips out till i get voltage fixed. Too many examples to list....
[Verizon Samsung Galaxy S III] ktoonsez:
Nothing has changed on wifi for months on TJ version so something must have changed in your network. Double checked my github and the last change was:

5 months ago

And the commit was

Make the unicast filter work with IPv6: from madmack
[Verizon Samsung Galaxy S III] brandoncarlson33:
i had mine o/c to 1809 u/v -50 and screen off is 81 for a while w/o issues but now using the pegasusq-zen.bin and am getting awesome battery life thanks to team kernelizers http://xdaforums.com/showthread.php?t=2144004
[Verizon Samsung Galaxy S III] tprophit:
I have the 'nominal' CPU. Will give it a try...

Thanks for all the help.
[Verizon Samsung Galaxy S III] macpro88:
I'm and idiot

I'll say it, I'm an idiot, I did not read the OP...

*sigh*

Flashed this Kernel, Liquid ROM 2.2, flashed the kernel for Linux 3.4 cause that's what I was running with Lean Kernel before...

...and I forgot to fix permissions...

and now the phone won't boot, and I CAN'T get into recovery. Don't know why. I can get into ODIN, but not recovery...

help anyone?

Thanks :o
[Verizon Samsung Galaxy S III] luis86dr:
Not fixing permissions wouldn't make you lose recovery. I would find the recovery image your using and flash it via Odin or terminal emulator.
[Verizon Samsung Galaxy S III] macpro88:
I tried flashing an ODIN package of TWRP and it still didn't work :(

I don't even get the blue "booting to recovery" text in the top left corner of the screen. Recovery is Power + Volume Down right??

And can I ask how to access the phone via terminal emulator if it can't boot?
[Verizon Samsung Galaxy S III] luis86dr:
Ahh, sorry thought you could still boot. I believe it's home + volume up + power for recovery.
[Verizon Samsung Galaxy S III] axne1:
EC Nationals

Wisconsin State Champs 2012