yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes. It's important we do our best in making sure nearly no one misses this. The more sources the better :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
No issues on the official aokp nightly thanks toonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fendulon:
Wish I'd seen the requests. This build is running just as fine any other. Run it a bit longer to get a true gauge but on PacMan it is running awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
http://db.tt/3rvjq9I4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Also, here is a direct link to the latest build. The folder is every version I've ever downloaded :)

http://db.tt/gLrogYZx

---------- Post added at 07:51 PM ---------- Previous post was at 07:50 PM ----------

Ktoonz, are you building a kernel for the Google Edition S4? Or will your existing code run on that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Already have it stored within my own archive but thanks anyways for this. Appreciate the generosity in sharing. Much respect bro :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If anybody has a server I can use for builds PM me, not drop box, never had much luck. Looks like my mediafire account is shut down. Too many downloads. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
FWIW, You could try Copy.com.

20G storage for free. IDK how much traffic it allows, though, but file size is no issue...

https://Copy.com?r=8jLy2a
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I'm out right now, but I have to see how much bandwidth I have on all my servers. If I can accommodate you I absolutely will.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
I see ppl posting pastes of a tw 6-26 release that the download link wasn't working for I don't see it in the thread that's supposed to have all builds either. Anyone have the tw 6-26 release or am I tripping balls? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Kts media fire account is shutdown right now to many downloads on it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Hasn't been posted yet because of the file host issues. I will update OP to my thread once the TW one comes available here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I tried to PM you, not sure if you got those messages. PM me for hosting info. I've got you all hooked up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Ktoonsez, what is the MD5 sum of the 6/26 release? I just want to verify it before fetching it from someone else's host.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
He's at work right now he is working nights atm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Here is the md5sum of the copy I downloaded that works perfect:

78a5f00ab90944279254cc8eb38d60c2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

BIG HUGE thanks to "MSgtSimon" for leting me store the file on his website server. Go thank him RIGHT NOW!!!!!!!!!!!!!!!!!! We now have a home for the files :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
ktoonsez, I just sent you a PM for another back-up if needed, as I work for Weebly.com and they have no bandwidth restrictions at all for file sharing or downloads.

And latest of your kernel is running great! No issues to report.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Glad to see hosting has been provided kudos. I see the aosp update up now. Was there a tw one as well or was 5-31 the latest release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
5-31 is latest for TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
ktoonsez, I can also offer a backup mirror too...

I have a 4GB storing space that I pay for... by I only use a small amount for a pictures gallery and my email address.

I would have to check with my web hosting support team to see if they allow that kind of traffic... but since it's unmetered, I don't think there will be any kind of problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidFiend76:
New updated kernel is working great on my S3 ktoonzes. Thanks bro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iosmonster:
When playing music, only plays on right side of headphones, other than that great kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
I also am getting this. Only seems to be in play music though. And a clear of cache and data has seemed to fix it at least temporarily...

EDIT: Scratch that Pocket Casts also was not working. Flash back to 6/8 fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I have no problem with the play music on the newest kernel. thats odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
sorry i should have also mentioned i'm on cm 10.1.0 stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Great. A release comes out and it's while I'm waiting for a replacement phone and using the s2. Why toons? Why?!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
for at least the past month, there has been a bug in CM code that caused the phone to reboot when taking a picture with a third party app from the front camera.

this has been tested by me and some other users... this bug is present when using nearly very third party app with the front camera.

Yesterday, this bug has been fixed in the latest release of RootBox rom (4.1). With this rom, the front camera is working fine.

With the same rom, but with KT747 kernel, I'm still getting the same problem... so it looks like to be a kernel bug.

A bug report has been filed on jira for cyanogenmod (https://jira.cyanogenmod.org/browse/CYAN-1504)... but no one answered/commented except me. This bug was also reported to the cyanogemod thread on xda... and no developer acknowledge that someone was working on this.

So I'm writing here today hopping that someone will catch this bug and fix it for good.

If you need a catlog and last_kmsg, you can find one here : https://www.dropbox.com/sh/ovy2odfyoyv2km7/7n77aU4BGU

it's not with the most recent kernel... not even sure if it was with KT747 installed. But it was captured when I had the front camera problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
restart

hey Ktoonsez,

Thanks for updating the kernel. Its been running well, just had a random restart again when waking up the phone. It appears like it decided to reboot all on its own - not quite sure why though. Running your settings with Tasks latest AOKP.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Lol. Bandwidth utilization went from ~1MB per day to almost 1GB just today. Unlimited bandwidth FTW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
According to your last_kmsg, your phone rebooted because there was an error mounting /data. I was wondering, how long had your phone been on when it rebooted? According to your last_kmsg, it rebooted at 9 seconds after boot, which suggests it actually rebooted twice, and your last_kmsg is from the second reboot. Either way, the specific cause of the reboot was a failure to open the journal for /dev/blk/mmcblk0p15, which is the data partition. If your phone booted back up fine after that error, I wouldn't worry too much about it, since that means the error was just a fluke, possibly caused by back-to-back random reboots, and the EXT4 driver was able to recreate the journal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
Great summary - thanks so much! Should I be worried about the data partition? I always clean wipe between Tasks AOKP updates. Or do you think KT's kernel isn't cooperating too much with my phone?

I appreciate your insight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL :D :p :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
I wouldn't worry too much about it, to be honest. It seems like your phone experienced a random reboot, which messed up the journal for data. As it attempted to boot, it detected the borked journal, panicked, and rebooted a second time, after which the damaged journal was recreated. As long as there weren't any pending writes in the journal, your data filesystem should be fine. If there were pending writes, then the changed data would be lost, but the filesystem should still be intact. I guess what I am saying is, if there are no errors in your data, such as missing or corrupt apps or information, then you should be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
So how has everybody's download speed been from MSgtSimon's server? Just curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Faster than light! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dark_intel:
I'm getting quite a few random reboots just doing normal things. Dolphin, Handcent, google now. log says kernel panic? Not sure whats going on, was working fine yesterday. On Slimbean. Also using Kernel 6/8 because audio out only plays right side on newest release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joe772:
When using headphones, I'm only getting sound out of the right earbud. Common bug? Any fix? Other than that, amazing as usual.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I'm on PA running the latest and audio plays fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Audio perfect on Tasks latest and toonz 6/26. Maybe it's a ROM issue .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
You're right man. That seems to be more of an AOSP issue than a kernel issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illmatic24:
I had a weird audio issue where the volume in Play Music would stay maxed out. This 6/26 update fixed it. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andyx1985:
Small donation for your awesome work. Receipt Number: 0935-8823-7826-6978

Thanks for all the work toy put into the sgs3 kernel. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dark_intel:
Figured out my problem. Setcpu was setting all voltages under 540mhz to 0. Wouldn't allow editing so I use just kt now.

Xda I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
SetCPU shows some jacked up voltages on my phone too, but as long as you don't modify them in SetCPU or check "Set at boot" it should be fine...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
If you are running the current build revert to 6-8-2013 build. I could get music to play through both channels on Google Play by hitting the song 2 or 3 times and then it would play through both channels. So, I knew it was software related and every other music app played normally.

So far so good on the older one without the newer CM stuff added. That seems to be the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yotorogo:
I'm running the tw 4.1.2 kernel, with the hyperdrive s3 rom. My problem is that when I go to ktweaker and I try to overclock it, it doesnt go past 1458 even though min and max are set to 2106
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
What governor are you using? The cpu will only scale according to what parameters are set within that specific governor. When OC do you receive the toast notification saying Ktweaker has been granted superuser permissions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yotorogo:
I am using performance as a govenor and yes I get the toast sayong that permission has been granted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I see Lagfree lol but anyways I would suggest downloading the Kernel again then use the Kernel Cleaner from the OP and reflash the Kernel following my recommended steps. It MIGHT have been a bad Flash or just another kernel tweaking app conflicting with Ktweaker.

1) Backup current Ktweaker settings

2) Go into Settengs > Apps > Ktweaker

3) Clear cache and data then force stop

4) {Optional} Open any root browser, navigate to /system/app/ and delete Ktweaker apk

5) {Optional} Clear all superuser logs

6) Reboot Recovery

7) Flash kernel

8) Wipe cache/dalvik

9) Fix permissions

10) Reboot

Clean ROM installs only require steps 6-10 but I'm sure you already know this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yotorogo:
I followed your instructions step-by-step but when I open ktweaker I have the same problem. I feel like I should try using the Aosp kernel but there is no 4.1.2 version for that atleast none that I can find
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try a FULL wipe (system, data, cache, dalvik cache) of the ROM then once you've booted the phone follow steps 6-10 steps. Don't restore any data until you've tested Ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yotorogo:
Thankx a bunch it works now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Hitting that Thanks button would greatly be appreciated :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
You can try underwear kernel, just search in the forum for the task 650 AOKP ROM in the first post you can find only the kernel of the ROM. But for me the KT kernel has many more options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredrick1213:
Does this not work on MIUI v5? I get stuck in a boot loop whenever I flash this over MIUI
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It works with AOSP based ROMs only.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Somethings wrong with KThermal. In "Minimum Throttle Mhz", the lowest I can go is 81000. When I go to "Voltages" it shows the lowest frequency I have is 81 Mhz. Is this an error?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Nothing wrong there at all.

81000 Mhz = 81 Mhz

That's just how the system reads it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
To be more specific, the list offers frequencies in kHz and your selection is converted to MHz.

While we're on the subject...

Throughout KTweaker, megahertz is incorrectly abbreviated as "Mhz". In fact, it should be "MHz".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Actually, 81000 kHz = 81MHz. Otherwise it doesn't make any sense :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes. This is true lol. However I was referring to it as how it is displayed on the phone for our fellow user to understand that what may be displayed under "voltages" is no different than what is displayed under "Kthermal Control". From a general perspective, yes, 81,000 kHz does = 81 MHz. Thanks for the clarification :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Incorrect.

81000 kHz == 81 MHz

81000 kHz != 81 mHz

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
100% correct. Thanks for clarifying :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I would never recommend using the performance governor... it keeps it locked at the highest frequency, highest voltage, highest heat. You run the risk of harming your phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liquidraven:
LuigiBull23

Is the latest june 26th VZW build up on your DB link? i cant find it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes it is bro. You probably looked under the TW folder and the 6/26 build was an AOSP release ONLY so its located under that folder. If you're looking for TW, 5/31 is the most recent one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liquidraven:
thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Noticed on a recent car ride that I also have the issue of sound only coming through the right channel. I think it's specific to this kernel, but I haven't had a chance to test it yet with another one.

I'm on CM10.1 stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mirrored:
On the latest TW kernel and I'm trying to copy ktoonsez settings. In general -> governor adjustments, he set his boost_cpu to 1134 but the only boost options I have are boost_2nd_core_on_button and boost_turn_on_2nd_core. Which one is correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
I think you need to be on a CM* nightly later than stable for KT latest to work. Ask around for an older build, sorry I don't have it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
KT's settings are on the AOSP version. The TW version options are a little different. If I'm not mistaken, on TW you have to set the boost speed under Extras, but its been a while since I was on TW, so I may be wrong on where the boost speed options are.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
KTweaker fc's on Task's latest 7-2 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Where do I get the nightlies for this?

Or do you mean a CM nightly rather than stable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
He meant CM nightly, KT doesn't release nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
He meant a CM nightly. I think your issue is ROM related because my sound is great on Tasks 6/24 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Runnin on task latest as well, Ktweaker didn't FC for me. Did you dirty flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
KT uses the same ROM. I think clearing app data for Ktweaker or a full wipe will resolve his FCs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
May have replied to the wrong person, I don't have any problems with Ktweaker :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I was adding the suggestion of clearing ktweaker app data to your suggestion of a full wipe.

Edit: also be sure to have fixed permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
:eek: My fault guys! I applied a 2nd cpu script as a ktweaker settings backup! No wonder it force closed. Got it all fixed now and it seems to be running fine.

Thanks for confirming it was just me. That's what I get for updating too early in the morning!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
It would be awesome if KT could add the nanolunch governor to this kernel. I get fantastic battery life with that governor. Any thoughts KT?

HAPPY 4TH OF JULY!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Which kernel have that governor as of now?

Edit: Got it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
I just noticed recently that my GPS flickers as I'm moving is there a setting for the GPS that I should be using? I don't have anything to GPS set Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Try disabling hardware overlay in developper settings, from the rom, not the kernel.

Envoyé depuis mon SAMSUNG-SGH-I747 en utilisant Tapatalk 4 Beta
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Im runnig synergy rom whats good settings to use for this kernel so I dont get battery drain? :beer::beer::beer::beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mranonymous333:
Can we not under volt anymore? I could have sworn this kernel let you do that. Guess I'm missing something. Back to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
KTweeker app that is installed with the kernel has all the settings u need to tweek it, including undervolting.

Ktoonzes seems to be busy right now with the SGS4. Hope he hasnt abandoned us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
He hasnt abandoned yall i promise theres just nothing to update everyone with thats all 4.2.2 is coming to yall soon then there willl be more updates for everyone to enjoy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Why the default response of back to stock? Back to stock kernel or stock un rooted?

I've been undervolting since about day one and I'm about -140mv on my top step
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
Thread lightly cleaned.

No more childish and/or troll comments or you will get the infraction message next.

Keep all posts, and PMs respectful.

Now, lets get back to development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
The gs4 kernel is much newer and is probably less stable than the gs3 kernel, which is why it requires constant updating.. Hes said himself that he will continue to support the gs3.

So no reason to worry :thumbup: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I'm getting itchy... It's been 13 days! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Common flash addict withdrawal symptom. This is normal. Stay strong brother :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Tell me about it lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
I've got the flash fever too!

I've also got the ChangeLog-Itis!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegreatscott:
Hello everybody,

I have a question I'm hoping you guys could help me with.

I'd like to flash this kernel to my phone, but each time I try, I get assaulted with force closes on boot, then get bootlooped until I restore a backup.

Flash procedure: wipe cache, dalvik, flash kernel , wipe cache and dalvik, fix permissions, reboot.

I used to use the this kernel on my phone, but I had to switch my phone for another one under warranty. This new phone doesn't seem to like this kernel.

Furthermore, this phone doesn't seem to like 3rd party kernels, period. I've only been able to get leankernel working on it, as well as whichever kernel comes packaged with whatever ROM I flash.

Does anybody have an explanation, and/or some suggestions for me to try?

I miss this kernel, and I've heard only good things about the more recent versions.

Thank you all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
What ROM are you running? It sounds like you may be flashing the wrong version for your ROM. There is a TW and a CM/AOSP version. Make sure you're getting the right one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
Does anyone know if I can run this on hellfire rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegreatscott:
Thanks for getting back to me.

I'm definitely aware of the difference.. I'm very certain that I'm using the aosp , 3.4 variation of the kernel.

My phone boot normally, and by 5 minutes in I'll be caught in bootloop hell.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Why not? It's an AOSP ROM so that should give you a clue on which version you should grab.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Are you able to get a last_kmsg after it starts boot looping? If you can get a last_kmsg, I can take a look and see if I can find anything.

There are numerous guides on XDA, and else where on the internet, that can walk you through getting a last_kmsg. If you need help with the last_kmsg, send me a pm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
No updates = sad panda
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegreatscott:
I managed to snag one before the phone went down. I glanced through it, but it looks like a different language to me.

Thank you for taking the time to check this out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
18 days... Hnnnggg :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Unfortunately, it looks like your phone is one of the unlucky ones that just can't handle KT's kernel. Specifically, it seems the biggest issue is with your GPU. There were a lot of errors in the GPU, which finally caused the frame buffer to quit syncing, making the pmic force the system to shut down.

I wish I could tell you a way to fix the issue, but it seems that your phone is just unable to handle this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegreatscott:
Weeeaaaaaaaak.

OK my man. Thanks again for your time.

If anybody has any suggestions I could try to make it work, please let me know.