yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
It's best to flash a new kernel only after booting with the stock kernel.

Try following your own steps up to and including #5, then 'Reboot System' and set everything up how you like it (on the stock kernel).

Then:

1) Reboot Recovery

2) Flash Kernel

3) Wipe cache + Dalvik

4) Fix permissions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
There is about 100 pages full of various combinations and settings to enjoy here:

http://xdaforums.com/showthread.php?t=1886233
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
The thing with battery life it depends on what the user is running in the background which includes GPS, Syncing, Wi-Fi and most importantly third party apps etc. Ktoonsez settings works perfectly on my phone but it might not work for you because like I said it depends on the user ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Totally agree, and to add: the guy that asked the original question would probably get killer results out of installing better battery stats, letting it run for a few days, then taking the results to a thread on q@a that discusses bbs, wakelocks, and other eaters of batteries.

(not trying to troll or be insulting, my suggestion is what I did to get my battery consumption under control. Kt's settings work great, but one rogue app with a couple wakelocks will screw the pooch)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Yup exactly my point you are totally right so when somebody comments on battery life I be like blah blah blah! LoL :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mikehud1984:
Well I still wasn't able to get it working. I'm guessing its because I just got this SIII which I've read somewhere that they have changed internal hardware a bit from the SIII's at launch. I originally got the SIII at launch then my gf broke her SII so I gave her my SIII and went and bought another one for myself. Well on this newer version the CPU is revision 4 where on the one I originally bought was revision 0. I'm guessing once Samsung realized the phones were selling themselves rapidly they decided well let's grow our profits by making them slightly cheaper with lower powered yet same spec'd cpu assuming nobody would notice. Guess I'll have to try and trade with my gf lol yeah right haha.

---------- Post added at 09:18 AM ---------- Previous post was at 09:09 AM ----------

I never had a problem with any ROM or kernel I threw at my original SIII and that includes OC. This one however doesn't seem to like anything other than stock (rooted of course) it even gets pretty warm running just stock no OC so I guess it's at it's limit already and can't be tweaked. Just got a P.O.S version I guess. Anyway I do at least want to thank you all for any help I received and of course to all the devs, I love you guys (no homo) lol. No but really you make Android so much more fun to mess with by giving us all lots of added functionality and extra goodies as well as unlocking the sheer horsepower of all these great devices. Without all of you Android would never be the same. I eventually want to become a dev myself if there are any tips or courses you recommend to get started I'd really appreciate the info. Again thank you for everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ac3theone:
Is there a version of this kernel for 4.1.1? I'm on stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes. Its in the OP. Its 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
I'm still getting an off and on issue with BT music. I found settings that keep my phone from rebooting, but there are still times it cuts out for a moment...like a bad phone call. Anyone else have this issue or a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Same here, bluetooth is kinda funky.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jazenf:
Just downloaded this kernel just wanted to learn more about the swipe 2 wake feature. I'm on the slim ROM is does that feature work for this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.17.2013

1. Couple little Linux patches

2. Fixed Bluetooth issue, where certain people could NOT connect to there device

3. Thats it..........

ENJOY!!!!!!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
VZW?? Did you upload the wrong one? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just fixed it :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Sweet! Your awesome thanks man for the update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
It still says vzw for the aosp 3.4 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated: Huuuuuuuge Update

SAMMY VERION: Download CWM flashable zip kernel

http://www.mediafire.com/?ysnm27vfwowtai2

AOSP VERION: Download CWM flashable zip kernel

http://www.mediafire.com/?rup6oa9z5am160b

Change Log for 7/19

•The long awaited Voltage Interface

•Underclock step at 192mhz

•Pegasusq tweeks

•smartass2:tweaking for responsiveness and battery life

•deadline-iosched.c: tweak deadline for flash devices

•arm: Allow CPU-supported unaligned accesses

•mm.h: increase readahead value from 128kb to 1024kb

•compiler optimizations

•sched: clock wrap bug in 2.6.35-stable kills scheduling

•sched/fair: Improve the ->group_imb logic

•mm, oom: fix potential killing of thread that is disabled from oom killing

•fifo: Do not restart open() if it already found a partner

•block: fix infinite loop in __getblk_slow

•cpufreq: Import latest cpufreq_interactive driver from Google

•wakelock: (tungstwenty's implementation) plus lots of other additions

•bcmdhd: Change packet filter settings to block multicast
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Well I am on Rogers and all frequencies are sticking as specified by voltage control. I didn't realize i747m GS3s were considered different if not AT&T?

But then again we all live in igloos, don't we :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
wow...when the vacation is over you really get back to it! If I only had an SG3 to give this a whirl... l8r
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Dam, new update, no time to charge up from 15% battery, look out spare battery here I come lol :D

Thanks great stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Is this going to be compatible with cm 10 yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Havent had time to look at it, will be soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Adb remount D: for sammy no one answers le question lol

im on my phone. expect terrible typos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Forgot about u, it should be but not sure since I run my AOKP:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Just tested its a nogo QQ

im on my phone. expect terrible typos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Wow, nice update. Something strange though...In both ROM Control settings and in SetCPU, SmartassV2 is not a choice to select from as governor. Wondering if I should reflash or if you see this too. I see that there are smartass tweaks in the changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Don't see it in Voltage Control either - and it was defaulted to 1890 max (not a problem, I just set it back to 1512, just for information).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Always do the following AFTER installing the kernel:

1. Clear cache

2. Clear dalvik

3. Fix Permissions

The govs/schedulers are missing from the AOSP version, I changed defconfigs and forgot to add them back in. Ill get them in in a little bit and post up:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Nice. I'm running cm10. I can't wait to run your kernel on it :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chipstien:
So voltages are showing up backwards in SetCPU. Showing default voltages as 1300mv for 192hz and 825mv for 1892hz. Just making assumptions that these are not the correct values.....

Sent from my GSIII running AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No big shock here, since that program has not cooperated with this phone at ALL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chipstien:
OK.... switching to VC now. :-D

Sent from my GSIII running AOKP.

Edit..... all good under the control of VC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
what's regarded as a safe general use undervolt level i can use ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
On Sammy version it too defaults to 1890 (easily changed in VC). So far running great! I know many use Ondemand and noop, but what's a good combo to use with Smartass?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
Anyone start toying with undervolt values on Sammy version? If so what and to where have you adjusted?

Currently running on demand/noop and all seems well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
you need to make one for the jellybean CM10!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
toons, you updated the new post, but not the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I dont know what the crap is going on in XDA, the post from last page is definitely fixed, and just tried to change the OP again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Looks like you got it that time. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Gah! Figures you go and update just after I clean flash a new ROM. Damn you toons!

J/K buddy! Nothing but love for ya man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Hands off...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Hell no!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
LOL!! KT's ''Thanks'' in the OP.

Think he may be doin something right? ;) Bout to flash 5/17 on the newest Pacman.

Appreciate ya bro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
You think, I know. LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
80K798332R727362V

Once again, not much but sent u and task equal amounts. Thanks again for all ur work. Hopefully the s4 will be paid off eventually even though again I don't even plan on getting one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks bro, always appreciate it :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Anyone have an issue when turning off Bluetooth it hangs at "turning off bluetooth" and pings cpu at 100%? Reboot is the only fox for me. On cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Do a force stop on Bluetooth Share, clear data+cache for Bluetooth Share, then reboot before turning BT back on. Fixes it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
A simple reboot fixes it. Why do a force stop and clear data and cache when in the end you're rebooting anyway. I found that if you turn BT off before turning your BT device off it won't hang. i.e if you connect your phone to your car with Bluetooth turn Bluetooth off on your phone before you turn your car off.

Good question, I believe there was as I see a TouchWiz ICS version and a TouchWiz Jelly Bean 4.1 version. I'm not sure but its possible the TouchWiz 4.1 is 4.1.1 but I'd wait for a response from ktoonez before flashing. Why are you still on 4.1 anyway? Just curious.

And that's probably only the AT&T thread.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ac3theone:
I'm using the 4.1.2 TouchWiz version,so far so good. I'm still on 4.1 cause I can't seem to find a stable stock version. All the 4.2.2 roms I try are very buggy for me. Do you have any 4.2.2 rom suggestions? It doesn't matter what features it has I just want something stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Is it possible for a custom kernel to affect something like the LTE toggle in CM10.1?

I am using the correct pta APN settings for my AT&T i747, but toggling LTE on and off doesn't seem to do anything anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats all controlled by the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Okay, good to know. Thanks for the prompt response.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Check you PM inbox.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Generally, only one or the other is needed. Either rebooting or force stopping Bluetooth Share both fix the issue, at least until the next time one shuts off BT with a device connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Did I have it backwards? Turn the car off then turn of Bluetooth? I don't use it often and I know one way or the other works.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
cpu1 needs to be fooled around with, I need more people to test

Gentlemen,

I have written a massive post in the KT747 thread for a pretty neat method for tuning our phones, more specifically tuning cpu1.

I put a lot of time in testing, and writing this, I'd really appreciate it if you could go check it out and perhaps test the method out or provide advice and feedback. I've even linked a cat picture so now there's nothing holding you back.

http://xdaforums.com/showpost.php?p=41663912&postcount=1102

here ya go, I've spent a lot of time working on this and i'm open to criticism or ideas or changes so please let me know what you think, but it's probably best to keep discussion in that thread.

Thanks for being such a fun community of developers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Interesting... I know about ktweaker only tweaking cpu0 but didnt know it would leave it running at almost max freq when cpu0 is at low freq. Since hotplugging means cpu1 would be off till cpu0 gets some load. Anyways.. It would be awesome if we can tweak cpu1 with ktweaker:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
[MENTION=374416]Bacon[/MENTION] Wouldn't that turn your phone into a lagosaurus Rex?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I'm getting constant reboots every 10-15 mins on the latest version of this in combination with the latest task AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I believe the way that works is to turn off or disconnect any Bluetooth devices, then turn off Bluetooth on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's because of incompatibilities between the ROM and kernel. You gotta stick with Tasks for the time being.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
just in case check your bootloader version using Root Checker (the one with the blue Android as icon) I didnt try using ics bootloader with the newer cm builds on the s3 but back when i had froyo bootloader on galaxy s i would get reboots every 5-10 minutes till i updated to gingerbread bootloader.

Edit: unless you meant cm added something again that makes ktoons kernel incompatible with latest task
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
cpu1 still gets turned off by hotpluggin which is good. my logic was keep cpu1 at a lower frequency, yet still let it bounce up under heavier loads to keep things smooth.

bassically my phone is now a galaxy nexus, more or less a 1.2ghz dual core.

The game is tweaking it till you don't have too much lag and not too much cpu spikes.

hehe well that depends on how you tweak it. right now asswax is my governor for cpu1 and 1080mhz with ktoonservative and 1296mhz on cpu0. For me some apps have a small amount of lag, but it's barely noticeable. you can tune it to however you want. you can make it laggy or super fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
How's battery life
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Well I'm kicking myself for not taking a screen shot from when I was in Kansas with great cell reception!

I had like 18+ hours on battery weigh like 30-40 % left and maybe something around two hours screen time.

I can't exactly recall what it was but for me overall, battery life has been improved from what I've seen.

Battery life is so subjective though. For me things have improved but it's totally possible it won't be beneficial for others

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Bacon, I've a feeling we're not in Kansas anymore. :cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
My new thread is up for previous builds on this fantastic kernel (ALL supported models!)

Check it out here and let me know what you think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Wow, great work man. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Not to crap on the party, but why do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Read the OP in the thread and there you'll have your answer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Because awesome. That's why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Just for fun I went to the op and now I want to curse and die cause the freaking blue and red text ontop of black xda app background is like daggers to my poor eyes.

I think you've done a good job with the list, will you be including the experimental test builds? Oh and also you do know that Dropbox has a daily download limit right?

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Thanks. I will be including all builds, including test builds.

I'm aware of the daily download limit. My current limit is 200GB per day. That was all I could offer at the time of my post. I will eventually be moving over to Mediafire but until then everyone should be set for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
things are perfect KT. enjoy your holiday pal. nice and quiet in here :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beefgoat:
KT has been busy with his GS 4 kernel. He put out a release for it just yesterday. Now, I feel as though I should buy one myself. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I didn't even realize. Guess this will be goodbye here, I'm getting one tomorrow then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
He doesn't abandon people - he's good that way :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
+1 he is going to be doing the s3 n s4 he still has both devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Wasn't worried about that. Might as well get one for 200 on an upgrade and sell this since him and task made the move.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I hope his GS4 kernel will work on the GS4 Google Edition. I'll get that if anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
He did? <- Straight from task's sig :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Had issues using Waze today. Flashed back to Cm kernel and the issue went away. Was getting major lag and corrupted graphic updates. Was plugged in with fast charge on... Maybe that didn't help. I'll do more testing and report back

Envoyé depuis mon Samsung Galaxy S3 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Reboot, that happened to me a while ago and that fixed it. YMMV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Already tried that. Didn't fix it for me. Well it did for 2 minutes or so... Heh.

Tried clearing data and cache in Waze too.. Didnt help.

I'll try again with KT tomorrow, with default settings and no fast charge and report back if the issue persists. Perhaps with a logcat

Envoyé depuis mon Samsung Galaxy S3 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Try upping your voltages as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidDude24:
Flashed this kernel and phone boots but rom wont boot?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
What ROM? Which kernel? More information please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Check for the correct version - that's what you get when you download the wrong one (or get a bad download). Restore your nandroid and try again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Can you please be more specific? what ROM and version, which kernel build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys, and yes I will be still building this one too :) :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I've been waiting oh so patiently for the next build :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Has there been any major kernel changes from CM in past week or so? On latest nightlies is it still decent to flash latest KT(5/17)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You should be good to go, no updates on any Qcom kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yayy. I've been on 5/17 CM with the 5/17 kernel and it's been amazingly stable so I haven't been updating.

Only problem I have with my phone right now is that the battery life sucks when I'm in a low service area. Which for me is work all day. Even connected to WiFi, it struggles to maintain a cell connection, I end up with like 50% left by midday. When at home or wandering around the city on LTE (and sometimes WiFi), I'm down to 30% by midnight after being unplugged since 8AM. Not spectacular, but it's pretty much constant use, so I'm pleased. :highfive: Good job toons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
What about task's 5/21 rom? Something changed the latest release the we can't use your kernel. Or is that not correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
It works fine bro. You're the only one to report this as far as I'm aware. With that said we can only assume that the 5/17 build isn't working due to something more than likely on your end. If more users can confirm this then that's a different story but you're the only one since Task's 21st release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
It doesn't work for me either. Constant reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I think he meant he can't boot the phone at all. Is that what you're referring to also?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
For me it's working perfect with task 5/21 Rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Exactly. I've heard Nothing but good things. Not sure what's going on with the guys above but it does sound user related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I had two random reboots today. Does this author want a cat log or the last_kmsg file? Only happened while connected to blue tooth. Thanks

LiquidSmooth & KT747 Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Last_kmsg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Wrong jb bootloader maybe? Since Task's 17.05 LK3 is needed...

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
If that were the case then the ROM's installation script would fail and based on the info I got they were able to boot just fine. I could be wrong but just doesn't add up.

---------- Post added at 10:33 PM ---------- Previous post was at 10:29 PM ----------

More info is needed regardless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Yes but that one line can be removed in the update script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
Ktoonsez, can I use your ktweaker app on my nexus4 to control kernel? NOT your kernel, I'm not dumb. Just your app. Obviously I'm using a nexus4 kernel. Thank you.