yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrFhenix:
ALOHA mr Koon

can you take a look at this solutions and port them or Add them to your Kernel

http://www.andronoticias.com/index.php?topic=1323.0

basically all the BAM DMUX molude mods will be amazing on your kernel

there is loads of DMUX WAkelocks ...

that will be the cherry on top
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Anyone else praying for a new kernel, considering Task's new release?

:angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Ohhh is that a kernel problem with the dmux? I saw a LOT of those in the kernel wakelock

Well if there is a fix... Let's fix it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrFhenix:
YEP apparently there is some BAM dMUX MODULE MODS that where implemented in some LG phones..

like Time outs and stop logging And stuff its implemented in the kernel

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Hey KT

I've been using your awesome kernels for past couple years since my S1 and hadn't done an update on my S3 since April or so of this year and I've always had amazing performance, oc'ability and uv'ing, etc but since then I just recently updated to a few of your newer versions and can no longer get the oc I use to.

I always have used 1809-1890 and could even use the max 2106 on occasion for certain thing. Would get occasional freeze, fc or reboot on the max but was practically fully stable on any oc' under the max even with some UV. But now I can't use anything above one step above stock (16xx)..if so it will freeze or reboot frequently. This is with no UV and tried some minor ov to see if that was needed but no luck.

Is this common with your latest kernels of the past couple of months? Any ideas?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
One thing that affects it is that ever since the changeover from 3.1 to 3.4, the math of the steps changed a little, you know, because math :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah, the math that Dr infernoo is referring to says that the old kernels were using incorrect math. When you were running 2106, your phone was actually running a couple of frequencies below that. My phone did the exact same as yours. I went from being able to OC to what I thought was 2106 to 1.6 like you. I didn't word all this very well. Sorry.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Any help would be greatly appreciated, because this kernel is awesome and i don't want to use any other.

Is anyone getting reboots? I've used 3 ROMs with the 8/31build and every rom reboots occasionally or reboots seconds after a reboot, but not for every reboot. I thought it was UV causing it but it is not. I follow the same procedure with any ROM, wipe/format all partitions multiple times(ocd lol) except the sd's.

I'm no amateur at flashing but here's the steps I take.

1.flash ROM

2.flash gapps

3.flash kernel

4.flash newest supersu (just recently started flashing this since I use viper4android, and it has to have it with 4.3)

5.reboot

6.wait 5-10 mins for everything to settle

7.Go through the initial setup and wait another 5 mins

8.reboot

Am I doing something wrong?

I'm running tasks newest AOKP build as of now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Flash the kernel AFTER you have flashed and successfully installed your ROM and Gapps. Also, after flashing the kernel, be sure to wipe cache and dalvik as well as fix permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Ahh oops forgot to add that I do wipe caches and fix permissions after flashing any kernel lol always.

The build before 8/31 I used almost the same procedure with slimbean and never had a reboot. But anyways I'm using twrp 2.5.0.0 right now (2.6 gave me errors when restoring backups) and with any ROM that I fix permissions it seems as if it does fix permissions but it does it so quick literally within 2 seconds? I remember it taking up to a min or 2. I see twrp has a new version out, 2.6.3.0 if i remeber correctly.

One more thing lol I flash slimbeans gapps with any rom i use, could that have any undesired effect? Sorry for all the questions but I've had this gs3 for less than a month now coming from a galaxy s blaze, things are a bit different. And i love how slimbean has the modded multi DPI play store.

Thanks for the help I didn't think to flash the kernel after getting the ROM all set up first. I'll try that out with the new twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
What he means is flash your ROM and gapps, boot and set up any apps or whatever you need, and then boot to recovery and flash the kernel. After that, wipe caches, fix permissions, and reboot :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Yeah i know what he meant sorry I just started taking adderall today per doctors orders and my mind is all over the place haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
Been using this kernel since 2012 on my Bell SGSIII on Task's AOKP 4.3 and got a random reboot just a few mins ago while updating apps in the play store. The kernel was flashed after installing and configuring the rom, which was after a full internal storage wipe. I'm running unmodified "a nightmare to remember" settings. I believe this was my first reboot on 4.3 so it's not a big deal but in thought I'd post the last kmsg anyway. Thanks for all your great work on making this wicked kernel for our aging device.

http://db.tt/D9sZSEc9

Sent from Task's AOKP on a Bell SGSIII using Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Is the link broken or is it just me? I get to the page but can't open the .txt file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
It was deleted. Check my thread in OP or under my name in Team Kernelizers' Box folder for the file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Are you running Balanced Bull or Nightmare to Remember?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Balanced Bull v3 on my S3 and Nightmare To Remember on my S4 but I tend to switch between the 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Cool. I'm running Balanced Bull v3 right now, but I haven't taken the five and modded my GSF yet. I just love my notifications too much :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
With proper management of wakelocks and such it's really not needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
What about that TK mod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Now that's a different story lol. I definitely makes some noticeable difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Sorry to be a pain, I just don't want to put the incorrect version on my device. Would the attached files from http://xdaforums.com/showthread.php?t=2291368 be the correct versions for an AT&T GS3 on 3.4 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
I'm sorry I'm not making much sense :) I'm just looking for the files/settings for Balanced Bull and Nightmare to Remember, not an older version of KT kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I edited my post before you could reply once I realized what you were referring to lol but again, the answer is yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
My flashing finger is getting itchy :D I'm loving this kernel, but hoping for another build soon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
About another month and the man himself will be back home for most of the rest of the year :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
I am surprised no one have mention this on the thread... but anyone else having the msm_otg wakelock bug? Its when you reboot your phone while the usb charge cord is plugged in. From everywhere I read it's a kernel issue. and I have this same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Read this post by [MENTION=5082757]LuigiBull23[/MENTION] he explains that happens

http://xdaforums.com/showthread.php?p=45654598

The #1 misfit

of my crew of misfits
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
just because one person thinks its not a bug, that doesn't mean it's not. google msm_otg wakelock and you have tons of people (only samsung people) having this issue and calling it a bug. Most of which points to the samsung's sources for the kernel.

Hope someone figures it out... hate to remember to reboot the phone while unplugged. Even worse, if the phone crashes and reboots while charging, you won't even know and when you do take it off the charger for the day of use, you end up with 4-5hours battery because the bug caused the msm_otg wakelock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Just because a whole bunch of people say it's a bug, doesn't necessarily mean it is one. This particular wakelock happens, and if you don't like it, either contribute to fixing it or work around it.

You're beginning to become annoying about it honestly. Considering that you spent a whole page whining about it over in the PA thread, there's no reason to come whining here too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
yep I am and will continue to follow up on this bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
I mean, if it's that present of a problem and it's on your mind enough to fill up two threads about it, then can't you remember not to reboot while plugged in?

Remember, people are doing this stuff for free. They have jobs and significant others/families that are a priority over fixing wakelocks. Patience is a virtue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
haha LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I reflashed AOKP, gapps, rebooted, set up everything including apps and some settings, rebooted. Flashed the kernel, cleared caches, Fix perms, reboot. Set ktweaker to my settings with no UV and no OC, rebooted, upon reboot I ran my own pegasusq cpu1 script and the phone froze for about 4 seconds then rebooted.

Kmsg: https://db.tt/RYS12eai

Dmesg: https://db.tt/VtRWoxqH
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Missing you Kt...(no homo)! :)

Task's rom is not the same without your kernel!

I know that real life takes time...hope seeing you back! Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
This kernel works perfectly on Task's 4.3 roms.

Sent from Task's AOKP on a Bell SGSIII using Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I can not get this kernel stable on tasks aokp. No matter what I do I get reboots all through out the day. I have been trying for the past 2 days to figure out what's going wrong :( I just flashed slim beans build 1 and flashed this kernel, set all settings within the rom, restored all my apps, undervolted, tried overclock, also I seen exit_only has some new builds to his killjoy flashed that also and everything works as it should...I don't get it. There's some kind of conflicting issue going on with this kernel and aokp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
I'm using the latest of Task rom and this kernel with KillJoy without any issues. I did have a lot of trouble just getting Task's 4.3 rom to install. Had to Odin back to the stock tw rom and then everything worked perfectly. I'm convinced that lots of rom, modem, and kernel flashes just leave crap behind no matter how many times you wipe the entire device when in recovery.... but that's just me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I believe your correct. After flashing so much the past couple days, somehow the lost+found folder in data multiplied and data was unmountable in twrp, I had to full format data including media then I was able to start flashing again. Luckiky twrp has a built in file manager so I could back up all my files from the internal. Very odd issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
***** important *****

***** IMPORTANT *****

LuigiBull23 has done some testing with some people that were having issues with Video playback with version with the GPU voltage control and found that everything is OK as long as you stick to multiples of 25. Anything smaller and not divisible by 25 will more than likely cause problems/reboots or out right ignoring the values by the GPU hardware itself. When he came to me with this info it immediately triggered my memory about my Nexus 10 device doing the same exact thing. So in conclusion, only do multiples of 25 when UVing the GPU. I will change KTweaker to do steps in multiples of 25 for the next release.

Hope this helps some of you people out there :good: :D. And be sure to thank LuigiBull23!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greogory:
Any chance you'll port your 4.3 kernel to the Nexus 7 Flo?

If not, I might try to cross compile your source to the Flo. May I PM you to ask for your experience about non-obvious gotchas to look out for?

Thanks,

Greg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
2 totally different phones man, its not something that can be ported, its taking Flo source code and merging in a butt load of code for all my features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The two best words I've read on XDA for weeks. :D :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
MALOF!!!!!!!!!!!!! :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
New release with task's build? :o lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Any chance of a sync with CM? There's been a lot of commits to the CM kernel since our last update.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Be patient. OP is probably busy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
The kernel is running great and soon enough there will be a kernel change when 4.4 kit Kat is released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrFhenix:
Just a question

Aloha mr Ktoon i am one Execibely Happy Slaves of your Kernel :) i just found something in my log after installing it and i wanted to ask...

i have this issue after installing your Kernel

https://bugzilla.redhat.com/show_bug.cgi?id=59278

i have this on my Log file

10-11 11:00:11.404 D/RIL_ATD ( 8637): gUartPath = dev/ttyHSL0

10-11 11:00:11.404 D/RIL_ATD ( 8637): UART ttyHSL0 is used by console

10-11 11:00:11.404 E/RIL_ATD ( 8637): Failed to init ATD

10-11 11:00:16.430 D/RIL_ATD ( 8638): gUartPath = dev/ttyHSL0

10-11 11:00:16.430 D/RIL_ATD ( 8638): UART ttyHSL0 is used by console

10-11 11:00:16.430 E/RIL_ATD ( 8638): Failed to init ATD

10-11 11:00:22.400 D/RIL_ATD ( 8673): gUartPath = dev/ttyHSL0

10-11 11:00:22.400 D/RIL_ATD ( 8673): UART ttyHSL0 is used by console

10-11 11:00:22.400 E/RIL_ATD ( 8673): Failed to init ATD

10-11 11:00:27.416 D/RIL_ATD ( 8677): gUartPath = dev/ttyHSL0

10-11 11:00:27.416 D/RIL_ATD ( 8677): UART ttyHSL0 is used by console

10-11 11:00:27.416 E/RIL_ATD ( 8677): Failed to init ATD

10-11 11:00:32.451 D/RIL_ATD ( 8684): gUartPath = dev/ttyHSL0

10-11 11:00:32.451 D/RIL_ATD ( 8684): UART ttyHSL0 is used by console

10-11 11:00:32.451 E/RIL_ATD ( 8684): Failed to init ATD

10-11 11:00:37.517 D/RIL_ATD ( 8686): gUartPath = dev/ttyHSL0

10-11 11:00:37.517 D/RIL_ATD ( 8686): UART ttyHSL0 is used by console

10-11 11:00:37.517 E/RIL_ATD ( 8686): Failed to init ATD

so if i do ETC/init.d/ATD fail to load or NOT FOUND

ATD and some similar issues refference

http://xdaforums.com/showthread.php?t=243921

am i missing a script ?? is there a way to Get it ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Restl3ss:
Problem

Okay so, I've flashed this kernel several times and my maximum clock speed is sticking at 1.5 ghz. I've done everything as the thread suggested. I'm using dandroid 4.7. I know it's not the tuning program because I ran benchmarks several times with the same results in all varied situations. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
sometimes this happens to me aswell, i dont know why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Did either of you even check on "enable OC steps" under General in Ktweaker?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Of course... sometimes I set the max cpu freqency to like 1.7Ghz and set the governor to performance and the cpu stays at 1.5Ghz. It will only got to 1.7 ghz if i set the min to 1.7Ghz. This happens sometimes, I havent really been overclocking lately to check if its still happening but it does happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
You must have some app, mod, or script interfering with your Max Mhz then. Be sure to check "lock frequencies" in Ktweaker to avoid this possibility. If not, then check in Extras > Battery Mhz Control and make sure you don't have any values in there that could limit your max cpu. Also, verify your Charging Max Mhz, which is also under Extras. Make sure you have "Selected Scaling max" as your selected option. The only other thing that can modify your max cpu are your Kthermal Control settings. If you are throttling then it will limit your cpu to what you have your Minimum Throttle Mhz set to, which is set at 918 by default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
I hope to see it for Android 4.3 soom. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
This kernel has been 4.3 compatible for some time now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Would anybody be able to tell me how to compile this kernel myself and merge the latest CM commits?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itzdustin:
stuck on the Ktoonsez boot screen. can still get into recovery but it just hangs. i followed instructions and have flashed my phones before and always ran into a hickup. so any help thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Bc of the post before yours, this happens to me as well. Wait for next version. IF there will be one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Sorry, apparently I can't read. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
So if you use this kernel (4.3 compatible) with the ROM vanir and try to use Google wallet, gw force closes upon typing in your pass code, not sure if it is a kernel or ROM issue, but it worked before flashing kernel, but have also use this kernel on other Roms with gw and it worked fine, so not too sure what's going on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Thats really a rom issue buddy I would believe

The #1 misfit

of my crew of misfits
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
That's kinda what I'm thinking too I just tried BMS kernel same out come, but flashed ROM stock kernel and it worked fine, I already posted in ROM thread so I shall leave to there to continue on.. Also as a note I wish I could use this kernel and not have this problem on this ROM. LOVE THIS KERNEL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Yea they need to edit the security package in the rom or its the knox app doing it had the same problem on the s4 buddy

The #1 misfit

of my crew of misfits
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Anybody have any advice on compiling this kernel from source? I'm particularly interested in merging the latest CM commits while I'm at it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I wish I had some wisdom to pass along but I would LOVE to see this come to fruition....this used to be the only kernel I used (Now using QuantumCore) but once kt747 is once again updated I will give it a shot....merging the recent CM kernel commits is most of the job, smashing the bugs that come about because of it is the rest.

You have my support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Here u go guys. This is almost 1000% caught up to CM and works with latest CM ROMs.

Tasteslikechicken verified it is working :D

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-ATT-10-16-2013.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Thank you thank you thank you...

---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------

Successfully flashed over slimrom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
What about PA?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
It should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Got a boot loop with PAC 10/15 release, (4.3.1) being the problem I assume.

Backpedaled to 10/01 PAC (4.3) which was a great release I find. Flashed the 10/16 kt kernel and its good to go!

Edit

Could have done a full wipe but went back to 10/01 for viper4android. All working so.

Thanks KT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
It's not 4.3.1. I'm using the 10/16 CM nightly(which is 4.3.1) and it's working fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Ditto with slimrom latest weekly, which is 4.3.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] winosxbuntu:
Your Saved Min/Maz Do Not Match Current, Apply your Min/Max

am new to kernels, it took me 3-5 months since i started rooting my SGS2, and now i own the AT&T SGS3 i747 and i did root it, also before i rooted i read, spent hours, days, weeks making sure that i knew what i was doing and getting myself into but after 3-6months of rooting its as easy as installing an app and using but am still scared of messing my phone completely and doesnt boot up

same thing happened with kernels but kernels are at the heart of your device, the brain you mess it up, you fck up your phone, bring it back you can but my point is, it took me longer to gut up and put a different kernel or replace my stock kernel with a custom kernel (KT747 by ktoonze, great epic kernel) am still scared and still an development with Kernels, custom roms are comfortable and ease of use

let me get to point for real now :laugh: so i install KT747 stock Touchwiz 4.1.2 clocked at 1.6GHz using Ktoonze settings and it works like a charm but ITS NOT STICKING ON THE 1.6GHZ MAX, it keeps changing/stays to 1.4Ghz but i want it to 1.6Ghz, i have checked on lock frequencies and Enable OC steps on general section (min 378, MAX 1.6GHz) followed everything on KT747 kernel forum for ATT SGS3 double, tripple, checked as many times, looked some threads to help me but it was a no help still having those problems

its keeps prompting me this (Your Saved Min/Maz Do Not Match Current, Apply your Min/Max) everytime i open, restarted, unchecked both and nothing helped to fix it

anyone can anwser or give suggestions to fix it, nothing is stupid or wrong plus am new to kernels idont wanna FCK UP MY PHONE

how do i fix?

am running Dandroid V4.7 stable 4.1.2, great battery life, unbloated, nice speeds but clocked at 1.3Ghz or less it cant play games well, lagging all the time and its not as smooth or fast as it is, since its touchwiz(underclocked) SO SLOW

---------- Post added at 05:56 PM ---------- Previous post was at 05:47 PM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Thank goodness for the new commits/updates... now I can enjoy V4A again. No more BEEP while screen off!

Now my question is... during Screen Off is it using only one CPU or both CPU on the I747?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm so excited...only thing stopping me from using your kernel was the fact it wasn't synced for a while. Flashing it with quantum right now!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Vyrus69:
Will the new kernel work on the T-Mobile variant, or should I wait for a version coming soon?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes it will. Flash away.