yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
There has been major NE4 kernel commits since the last KT kernel. Those are major ones for any phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_kernel_samsung_d2,n,z

cm commits for d2 kernel. There definitely hasn't been that many. One does interest me though, because the msm_otg wakelock is kinda lame when you hit it and it drains your battery:

http://review.cyanogenmod.org/#/c/65080/

So I still vote for an update. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try

http://ktoonsez.jonathanjsimon.com/sgs3/ktweakershop/

That MSM is not a Merged commit. Failed QA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Err, what o_O It has been reverted

Edit: Points to this

http://review.cyanogenmod.org/#/c/65930/

Pretty sure it is in KT747, only kernel which gives me a msm_otg wakelock. Unless it's something else, then fml.

Edit 2: Guess ktoon would have needed to cherry pick it, which would have been surprising. Guess the quest to find the reason continues.

Edit 3: Checked, it ain't there. So indeed fml.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Oh I see. Good Point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Update for AOSP on its way :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Thanks man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log

1. Linux 3.4.90

2. Linux 3.4.91

3. Linux 3.4.92

4. Linux 3.4.93

5. Linux 3.4.94

6. Linux 3.4.95

7. Ramdisk sync with CM from 7/3/2014

8. All caught up to CM latest commits (June 28th)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
No tw love kt? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, look above for the update link for AOSP. Nothing to update for TW. :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Aww shucks lol, well thanks for a great kernel regardless I'll be waiting for some tw love when there is something to update lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Ktweaker crashes and won't open on quantum Carbon whereas it was working fine in the previous version. Anyone else have Ktweaker crashing upon opening?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Answer is the same as it has always been, delete ktweaker folder from internal sd card and start again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Sorry man, no I fully deleted the internal before flashing the rom. Doesn't work with carbon itself either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Deleted ktweaker folder in internal sd card, reflashed it, done the steps 3 times, still force closing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the aosp update.. Considering AT&T NE build is out, will we have an update.. The last TW kernel was based on the sprint build.. I have read that ne build has some kernel changes over nd8 release..

I know you have spent lot of time for making the sprint kernel working for our service. You have hacked the kernel to make the kernel working for our service. But if we can have kt kernel based on the AT&T build will be awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philliedbz:
Can grey scaling in power savings mode and ultra power savings mode be implemented in this kernel since i read in the international forums that grey scaling is in the kernel im on nd8 stockedrom port
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StunGod:
I'm wondering if anybody else is getting random reboots using this kernel with CM11? I did a clean install (wiped system, cache, dalvik, pretty much everything I could get at) by installing CM11 (the M8 build), then the latest AOSP version of this kernel (6/1) and gapps. Installed my apps from the play store instead of from backup, just in case.

I haven't applied any profiles via Ktweaker, and am open to suggestions. But what I'm seeing is that at random times the phone will reboot. There don't seem to be any consistent behaviors causing it - sometimes it's Facebook, maybe an incoming call, once when I opened the camera app, and I've glanced over at the phone while it's charging my desk and seen it the middle a reboot.

I haven't seen anybody else mention it in this thread, and CM was stable on its own. But for some reason it's behaving oddly for me.

I'll be happy to provide logs if somebody will tell me where to get them.

And by the way,I came to this kernel because of some serious thermal throttling issues with the default CM kernel. Not only have those problems gone away, but the phone is way more responsive now. What a huge improvement! Thanks to KT for some amazing work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's a newer version of the kernel, but no I haven't seen any reboot. Did you change any setting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StunGod:
Yeah,I updated to the new release today and there's no difference. And I've left all of the settings at default.

The new M8 release for CM is coming the next couple of days, so I'll probably do another full clean install and see where that ends up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
Dirty flash cm 11 and wipe cache and dalvic cache and reboot, go back into recovery after boot has completed wipe cache and dalvic cache flash latest kt kernel (AOSP) wipe cache and dalvic cache and fix permissions reboot should work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StunGod:
Thanks. I'll give that a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
What rom are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
PA latest

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Please explicitly grant Root to the Ktweaker App after force closing the app and wiping its data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Its not the folder the App should have Root Permissions. No Idea but ART Cache isn't controlled by TWRP Yet. So my guess is no it won't.

Switch to Dalvik before flashing Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Bump
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Remove the permission from inside the Superuser. Then Launch Ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There is none. You grant it when the program requesting root asks for it. What I believe Perseus means is to verify and delete the entry in your Superuser management app then open Ktweaker so it requests again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
It won't even create an entry. This is happening to a couple of us I see. Mine is from a fresh fully wiped install. I have everything backed on SD card so the internal is wiped as well.

That being said it won't even load.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What roms are you guys using and also what superuser?

Chainfire SuperSU?

Koush Superuser?

ChainsDD SuperUser?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
I'm using chain fire, carbon also tried it with quantum carbon.

It's also happening with PA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
Are you wiping internal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Yessir
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Well that's a bummer, I have no clue then. D:

Works super fine here heh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
What rom you got going pb?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
cm11 nightly, KT747 for the kernel at the moment, SuperSU by Chainfire. Everything works as it should regarding using KTweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
Just flashed the newest pa and now I'm getting the fc too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Just went from carbon to slim 4.4.4 and getting same FC. The list goes on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
FC with quantum rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Guys, there's no need to list all ROM you try that give you FC.

A logcat is all that can help here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Does touchwiz battery life seem horrid with this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Viper67857:
Nope, better than ever here with 4.4.2 and this kernel

Sent from my SAMSUNG-SGH-I747 running TMS3KK-1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
You're right here are the lc's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I'm on the road so it's hard to see on my phone but looks like u r getting xposed screwed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
I don't think that's the actual issue cuz I'm getting the fc and don't have closed installed I'll also get a log for you when I can
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Maybe the ktweaker fc happens if the ktweaker folder is empty. That's happens to me. I fix that because I have a folder backup of ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That would be better so I can see the error when I get back to town.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
I'll reflash and test it out. is everyone else on xposed ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Not me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No crash on latest CM11 nightlies, using ART though (so no Xposed).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
I have xposed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
And you are getting fc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Not now.. But when I update my phone to task650 last buil the fc happend. And when flash this kernel two time was same fc and check the ktweaker folder and is empty. Copy the folder backup I have and the fc gone.

For me the problem not is xposed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Flashing this onto Q5 and probably AOKP, will report back.

Sent via my Galaxy S3 (or 3 rather, it's more of a Frankenstein creation of the working parts)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Anybody around to test new ktweaker??????????

KTweaker Test AOSP kernel

http://goo.gl/esZH0j
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Can I hear a hell yes? [emoji7][emoji7]

Changelog?

Sent via my Galaxy S3 (or 3 rather, it's more of a Frankenstein creation of the working parts)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
I downloaded and tested work flawless very good. Thanks for the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, thought the change log was self expanatory :D :silly: :eek:

New ktweaker to see if the FC stops
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You were getting FC's on Ktweaker on the previous version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Nop no force close in my side. All good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Oh crap, was hoping you were one of the ones that was getting them on the previous version :(. Want to see if this got it or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
After I update my ROM I start have ktweaker force close but the problem was because the tweaker folder was empty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
And on todays, does the FC problem go away if you make the folder empty?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
What happen is for any reason when I update the task650 ROM the tweaker folder turn empty and I saved the content of all files in the folder on my sdcard and copy all files and the force close gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Anybody else test??? Also no need to report bad results without a logcat or its useless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Yes. Previous version fc'ed every time. No fcs with new version. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Awesome!!!!!!!!!!!! :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
Downloading now!

Works perfectly!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Confirmed works great. Thanks kt .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Tested the new Kernel. No issues of any color shape or form. Absolutely nothing but the Best work from our Favorite Developer!!!:good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The 2 apps are fighting for control. Please use either app not both.

Assuming you have removed Trickster mod, you can hit menu inside Ktweaker and hit load defaults. that will give you the Kernel's Own values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
I am getting google play fc and gapps fc with every 4.4.4 build. Did not happened with 4.4.3. I try to get logcat but without sucess.

I did multiple tests, always get the same problem.

Is it related to this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Likely related to your gapps... :silly:

http://xdaforums.com/showthread.php?t=2397942
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReekHavok:
The update worked flawlessly. I was never getting force close on anything. However the tweaker did not function.

Since the update the tweaker works awesome.

I'm running 4.4.4 SOKP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 7.10.2014

1. Updated KTweaker to stop FCing for certain people.

2. Same as yesterdays test so made it official.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
I am using that very same gapps packages and I get fcs... In all 4.4.4 roms, including quantum and aokp. Will download gapps once more and try again. Thanks for the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
My boy KT... didn't even flash 7/9 yet!

Sent via my Galaxy S3 (or 3 rather, it's more of a Frankenstein creation of the working parts)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you overclocking/undervolting? If any, don't do it, then see how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi when asking to yes or not hit yes all time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zetsui:
Ok so I have the Ktweaker kernel and the Task650 ROM. I have made sure in kernel settings for the ROM (Trickster) that none of the Rom's values are on boot. In Ktweaker I made an set all my values and saved a profile. It is under currentprofile.xml, but I cannot load it ;(, why? I can download one of the pre-made configurations to that directory and everything works fine. Also the values do not stick through reboot for my own ('would you like us to apply these values/vibration level?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Freeze/Disable Trickster Mod. Next wipe data to Ktweaker app. Reboot and then manually enter your changes in the Ktweaker app. Save those as a new profile. Make sure they are set to apply at boot. After another reboot, wait for 5 minutes (Yes 5 X 60 = 300 Seconds). Then open Ktweaker and check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davenrai:
How would I revert back to stock samsung 4.3 kernel from this?

I've flashed another kernel (other than samsung/kt) and the boot animation is still there. How can I get rid of it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aromig:
You could always just reflash whatever rom you're on. You would then have the kernel and animation that came with it.

Sent from my GS3 running CM11, via FapDaCock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zetsui:
Actually something I spent a damn near day going over yesterday (up 28 hours straight). Coming up from 4.1.2 for some weird reason all my default save settings files were stored in data/media instead of storage/emu/0 where ktweaker were looking for settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Wipe data to Ktweaker app. Or Hit Menu inside app and hit Restore Defaults. That'd give you app's default values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TylerMarshall256:
I'm using this on likewise I like everything but this kernel does not find my USB mouse hooked with my OTG cable. How to I get OTG to work? And if not does anyone know of a kernel that does?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
I had issues on Likewise LT getting my Computer to recognize my device at all. I had to boot to recovery, let drivers install, mount USB in mounts and storage, let drivers install, then boot to download mode, and let drivers install again. I unplugged my device, rebooted, then plugged my device in and my PC instantly recognized it. Might give it a try.

And make sure you don't have fast charge on. That will cause issues as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
what?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Guys this is a development thread. You've taken an entire page to post some bugs nobody else is having. Please fix it elsewhere.

Sent via my Galaxy S3 (or 3 rather, it's more of a Frankenstein creation of the working parts)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Lots of random reboots. It's not room specific. Would you be able to take a peek? Thanks :)

Last_kmsg in link

https://www.dropbox.com/s/1f1jh3xwlu8s5y7/last_kmsg.log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's not kernel related either. It's hardware related. Partition 15 problem from what I can see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Now I research more lol

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

Thanks dude
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sadly, yes thats what it appears to be, very very good analysis :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] killablack:
my playstore fc were caused by my theme; if you have a theme active it may be outdated or incompatible try disabling it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
Wifi not working for latest cm nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Seriously guys? This is a Dev thread, not a Mtl vs Toronto thread. (Btw I'm in Qc as well, doesn't make me an ass)

Reporting that wifi doesn't work is fine, a logcat would certainly be helpful if you want a fix though.

[MENTION=4311957]polobunny, Wheemer[/MENTION] Be respectful, issues happen on some devices while it doesn't on others. polo, you started helpful but didn't end up too good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draagyn:
Be nice, fellas.

When reporting an issue, it may be helpful to point out that something doesn't work 'for you'. Others may assume that it is broken for everyone. I think that is the root of all of this.

And remember, Canada is just America's hat.

But thank you very much for hockey!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Guys, if you must discuss CM, do so on THAT Thread. If its a issue with THIS Kernel then post a Logcat.

A Logcat or it didn't happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
from the moderator

To all in this thread post dev related issues or do not post........ easy......

Continue in off topic diatribe and infractions ...begin.......... thank you in advance

~~~ Oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moscow Desire:
[MENTION=4311957]polobunny[/MENTION] and [MENTION=4719948]Wheemer[/MENTION] , both of you "Knock It Off".

And yes, I see when it began.

Any more of this nonsense, and the Frosty gates will open and this I promise. If there's a violation of XDA rules, I expect to see a "Report Post", not some back and forth bickering that Moderation has to come clean up....

Clear?

Keep the thread on topic folks,

Thanks...

MD

UPDATE... now you have "2" Mods attention....:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Hey I'm getting a bootloop. Newest kk kernel.

Slimkat stable build 6

Should I install older kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try newer Slim or Older Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
OK, I like to stay on stable builds instead of weekly. Build 6 is newest stable slimkat. What version of the kernel do you recommend?

Thanks for your time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Usually one that is around the same release date as the ROM you're using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
KT747-AOSP-KK-ATT-07..>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Sorry I thought that was the newest. That's the one I'm expierencing boot loops with.

I'll try the one I have before that from June I guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you overclocking/undervolting/using a profile?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
New phone, fresh install of recovery, ROM, gapps.

---------- Post added at 01:12 PM ---------- Previous post was at 01:00 PM ----------

Quick question. How do I find older versions. I figured it would be in op, but I can't locate where.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
My Bad, try the one from June. KT747-AOSP-KK-ATT-06..>

http://ktoonsez.jonathanjsimon.com/sgs3/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Perfect! That's the same one I have on my SD card from before my old phone took a dip with me in The ocean lol.

Going to try it when I get back home in case I have to flash back to stock kernel. Or some unseen issue.

I love KT so much, his kernel has treated me very well for the past year. 7+h screen time. Hard to settle for less after u have the best.

I'll report back later, if it helps development at all. If it isn't needed all good!

Thanks again guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Don't flash any custom kernel on today's nightly, WiFi is broken after the flash.

[MENTION=4325945]ktoonsez[/MENTION] hope you update the kernel for addictive KT kernel users
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Wifi is broken with the stock kernel too, or at least it was for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
WiFi is working for me on stock kernel.. Try clean flash.. This is what I am using at the moment on my mobile
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Got better stuff to do than clean flash in the middle of the day, but thanks for the heads up anyway.

Edit: Oh and for the record [MENTION=4325945]ktoonsez[/MENTION], going moduleless is likely what broke it now that I checked the commits. Strange it was still broken after reflashing nightly w/o custom kernel. Must have been a derp.

http://review.cyanogenmod.org/#/c/68880/

http://review.cyanogenmod.org/#/c/68882/

http://review.cyanogenmod.org/#/c/68879/

http://review.cyanogenmod.org/#/c/61913/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Any way I can charge my phone while it's OFF with this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I believe it charges just fine, but doesn't show the animation. I might be wrong though, haven't tested extensively.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
No. Turns right back on. When plugging in and turning off, turns back on. Turning off then plugging in, turns on. Really a PITA when phones dies and won't charge cause it wants to constantly kick phone back on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I assure you that on cm11 0720 nightly with KT747 0703 kernel I can charge while off just fine. See picture.

Edit: Well, look at that. Perfectly timed it seems ha

http://review.cyanogenmod.org/#/c/68905/

Bootloader "issue", hence why I am not affected (not KK bootloader ha)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
442 touchwiz, sorry. I knew on cm11 it did