yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] BrianAllred:
No scripts, but I'd changed the minimum CPU frequency to the lowest possible on this kernel and I'd switched the GPU governor from simple to ondemand. I'll switch them back and see what happens.
[Verizon Samsung Galaxy S III] rockingondrums:
I played earlier and it just lagged once. I went to home screen and back, it was fine. I just played again and it lagged to a stop, so I went to home then accidentally cleared recents.
[Verizon Samsung Galaxy S III] d1ez3:
Does anyone else experience lag when turning on the screen with this kernel? It always takes more than a full second to turn the screen on after pressing the button for me
[Verizon Samsung Galaxy S III] kinnerful:
Yes for me. Bumping the voltage up from the default values may help.
[Verizon Samsung Galaxy S III] rijujeevan:
Which kernel is compatible for liquid smooth 3.0??

3.0.y or 3.4.y
[Verizon Samsung Galaxy S III] Droid316:
3.4y.
[Verizon Samsung Galaxy S III] BrianAllred:
Memory leak looks to still be present. Candy Crush crashes after anywhere from 10 to 20 minutes.
[Verizon Samsung Galaxy S III] Droid316:
Anyone try this kernel on eclipse rom and lose data?
[Verizon Samsung Galaxy S III] BrianAllred:
GideonX recommends flashing ROM + GApps + Kernel when flashing this kernel because the data loss is a known issue. I personally only flash ROM and kernel and it seems to work fine for me.
[Verizon Samsung Galaxy S III] Droid316:
Ok I flashed Rom gapps then rebooted then went back into recovery then flashed kernel.I'll do this now, thanks for the help.
[Verizon Samsung Galaxy S III] BrianAllred:
Yeah, it needs to be all during the same recovery session, before the reboot. Sorry, should've mentioned that.
[Verizon Samsung Galaxy S III] donnyp1:
How did that work?
[Verizon Samsung Galaxy S III] Droid316:
Not good lol.Lost data.But found out you have to flash Rom then gapps then the kernel all in one session then everything is hunky dory.Running eclipse build 5.1 with bms kernel and killjoy script.
[Verizon Samsung Galaxy S III] GideonX:
That's what my instructions say to do on the download page, lol.

Maybe I should make the red text blink and add music or something.
[Verizon Samsung Galaxy S III] Droid316:
Lol oops my bag.
[Verizon Samsung Galaxy S III] samsgun357:
Hey Gideon, why is it that flashing this kernel without flashing ROM etc in same session is causing the loss of imei?

Its not a big deal but just curious as to why this would happen on the latest kernel build but not the previous.

Thanks for such an awesome kernel BTW!

In Hoc Signo Vinces
[Verizon Samsung Galaxy S III] wwonka69:
This should solve your issues. It did for me.

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

Lol make it big red and flashing and people will still miss it.
[Verizon Samsung Galaxy S III] miguel11691:
Which version do I use for the cm 10.1.3 rc2
[Verizon Samsung Galaxy S III] JRJ442:
You need the 7/30 build or earlier. D2 devices are all 3.4 kernel versions now. So just go to the OP, click on the latest 3.4 version link. Once there, all the way at the bottom you see something about older builds.
[Verizon Samsung Galaxy S III] fussgeist:
Flashed the new LiquidSmooth 3.0, updated Gapps, and the BMS (3.4.y)

Had the issue of no mobile.

Followed the directions to relash in one recovery everything and in order.

Did this a few times and still do not have mobile data.

On the about phone status screen, it has no known network, out of service, unknown phone number, and the MEDI and IMEI are unknown.

Been flashing ROMs and some kernels for years now and never ran into this.

Help?
[Verizon Samsung Galaxy S III] GideonX:
Flash liquid and gapps, reboot to homescreen and see if imei returns.

If so, reboot into recovery and then flash liquid, gapps, BMS in a row. Now see if it's there.
[Verizon Samsung Galaxy S III] indyssee:
On newest Slim weekly, I couldn't play videos through browser (tried multiple) and the same video downloaded basically couldn't play through MX browser. I flashed Lean kernel and now they're playing fine.

Anybody else having issues with video? I haven't changed any kernel settings except changed to interactive/row.
[Verizon Samsung Galaxy S III] GideonX:
Which site?

I just tried liveleak on the stock browser in Slim 1.2, played just fine for me.
[Verizon Samsung Galaxy S III] indyssee:
IGN
[Verizon Samsung Galaxy S III] GideonX:
Works fine for me.
[Verizon Samsung Galaxy S III] indyssee:
Damn... I'm not sure, then. Thanks for testing it out. I'll try again after work.
[Verizon Samsung Galaxy S III] fussgeist:
flashing just liquid and gapps and everything is normal, same as when I flashed a recovery image before to get back.

Flashed liquid, gapps, then BMS; no mobile.

Also tried this pattern:

flash ROM, gapps. reboot (mobile fine).

flash BMS, mobile gone.

flash ROM, gapps, BMS together, mobile still gone.

rather annoying as I've had horrible battery useage on liquid 3.0 and everyone is raving about BMS kernel with it.
[Verizon Samsung Galaxy S III] jsdecker10:
I'm also on the new "Unofficial" Liquid 3.0 and BMS 3.4y and everything flashed correctly the first time AND everything has been working just fine(*knock on wood*) since Day-1 of being on Liquid 3.0/BMS 3.4y . I don't understand why you're having such a hard time with this...I really don't get it. Hmmmmm.... you mentioned your different flashing "methods," but I didn't notice any mention of how/what you wiped before you began flashing. Maybe that has something to do with your issue you're experiencing? Are you on CWM or TWRP? What exactly are you wiping, and in what specific order? I know you said you've been flashing roms and kernels for years, so I assume that you most certainly know what you're doing here, but everyone forgets things and/or makes silly little mistakes from time to time!! I know I sure do! lol
[Verizon Samsung Galaxy S III] twistedillutions:
Strange the issues

Try factory reset then flashed rom gaaps and bms

Ive done flashed rom gaaps then bms separate and it was good..if 3.0 not working well then go with 2.9 official
[Verizon Samsung Galaxy S III] fussgeist:
CWM.

I did a full wipe through recovery on the first install of 3.0, but haven't on reinstalls since, probably worth trying that.

But with the issues I've been getting, thinking I'll just downgrade till 3.0 is official (and runs well on my device).
[Verizon Samsung Galaxy S III] juancaperez2000:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw [2013-02-20]

Did you tweak some governor on this release? Thanks for this
[Verizon Samsung Galaxy S III] d1ez3:
Does nothing need to be wiped flashing this kernel from a different kernel? Is there a wipe built into the flash?
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw [2013-02-20]

No gov tweaks with this release.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw [2013-02-20]

Nothing needs to be wiped.

Any kernel thread that suggests you do so before flashing a kernel is regurgitating a bad habit. Wiping your cache or dalvik has no affect on your boot.img.

Roms on the other hand, are a different story.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] d1ez3:
interesting, thank you.
[Verizon Samsung Galaxy S III] ITR218:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw [2013-02-20]

Working nice so far on Liquid Smooth JB v2.1 4.2.2! Thanks
[Verizon Samsung Galaxy S III] GideonX:
Here's a build for d2usc (US Cellular) 2013-02-23 - http://goo.gl/J13fJ

I'll release both vzw and usc versions in this thread, thx.
[Verizon Samsung Galaxy S III] petermac88:
Just flashed this Kernel with PAC-Man v20.0.0. I will update after 24 hours of use, so far so good though! =)
[Verizon Samsung Galaxy S III] kidruk:
Great work my man .. Been bouncing around on kernals and I must say I really do like this running on Rootbox. I do have a quick question though; is fast charge already enabled of do I have to set a command in terminal emulator?
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

You'll need to toggle it via terminal or use an app to do it.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] kidruk:
Sounds good. Whats the command via terminal? or is there an easier method to toggle it?:highfive:
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Load trickstermod from the play store. It'll let you edit some other settings as well.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] kidruk:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

No doubt .. Appreciate it my man!
[Verizon Samsung Galaxy S III] petermac88:
Hey Gideon, quick question, what CPU Governor Control should I be running or what do you recommend running.
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

I'm currently running smartass2/row, pretty decent so far. Try them all :)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] kidruk:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Smartass2/row seems to be the combo not giving me random reboots .. Are you over over clocked at all?
[Verizon Samsung Galaxy S III] GideonX:
Actually, majority of the time I'm running underclocked at 1 or 1.2Ghz. If you are getting random reboots, try bumping up the voltage a tiny bit. My undervolting may just be too low.
[Verizon Samsung Galaxy S III] bnmohler:
great kernal so far. i have it on liquid smooth RC1 and no stability issues yet. I saw it said CM wpa/wpa2 tether "testing" in OP. I can confirm it not working for me but if i do none tether seems fine. I wasnt sure if testing meant you were testing in house or you merged it into your latest build and wanted to know if anyone had luck with it working or not.

Great work!
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

The tether security fix was cherry picked and included. It's working for me on mastamoon's cm kang. Of course, it's not official so it appears some have it working, some can't.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] cvsolidx17:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Battery drain while the screen is on is a little high however my phone deep sleeps excellently with this kernel. I'm using the smartassv2/row combo, underclocked to 1.2ghz. Any suggestions/tweaks? Running it on the latest CarbonRom btw
[Verizon Samsung Galaxy S III] jsdecker10:
So you wiped system, cache, and dalvik, correct? Then flashed the ROM first, then the newest 4.3 gapps, then finally the 3.4 BMS Kernel last...? ...all in the same recovery session, before rebooting for the FIRST TIME?
[Verizon Samsung Galaxy S III] fussgeist:
wiped sys, cache, dalvik

flashed ROM and gapps.

everything was fine but thought I'd try BMS for better battery life.

flashed BMS, reboot, got the expected data loss.

flashed ROM, gapps, BMS all together. still data loss and no imei, phone state, number.

went back to a recovery (v2.7)

I don't think I did a wipe here.

flashed ROM, gapps, BMS together; same result.

I need to try wiping and flashing everything at once.
[Verizon Samsung Galaxy S III] airmaxx23:
I just flashed this on the unofficial 10.2 9/25 build and lost data.

Edit: I tried installing everything at once and still no data, it's actually causing my phone to reboot after about 2 minutes.
[Verizon Samsung Galaxy S III] fussgeist:
tried wipe and flash all together, still no mobile anything. Think I've exhausted all my attempts.

Looks like there's something in LS 3.0 does not like BMS for certain devices.

Going to v2.9 for now and might give BMS a try there and certainly after the official 3.0 comes out.
[Verizon Samsung Galaxy S III] airmaxx23:
I went through about every way possible to flash this and still end up with no data with CM10.2.
[Verizon Samsung Galaxy S III] GideonX:
People with data issues that won't resolve itself, give this zip a try. Let me know if it works better.

goo.gl/2C9851
[Verizon Samsung Galaxy S III] airmaxx23:
That brought back data but as soon as my screen timed out I couldn't get the screen to come on and now it won't boot past the boot animation.

Edit: I tried dirty flashing CM10.2 with GAPPS and then the kernel all at once and I still can't get past the boot animation. Restoring a backup now.
[Verizon Samsung Galaxy S III] mcp770:
Noticed a few roms are having issues with apn data not restoring after flash which isn't a kernel issue. There is a apn backup restore app in the play store. On a rom with everything working backup apn data. Then switch to the new rom sign in with wifi get the app and restore the apn info. Works like a charm.

Note, you have to make the apn app a system app with titanium or move it manually for it to work right.
[Verizon Samsung Galaxy S III] Bamdroid:
Go into settings, mobile network, CDMA and select RUIM/SIM. There's a chance NV was automatically selected since your IMEI/mobile network says unknown. If it said "0" then it would be a lost IMEI. See if that fixes it.
[Verizon Samsung Galaxy S III] xbiker321:
Just installed this over my Eclipse 5.1 and KT747 kernel. Installed fine and didn't lose data.

I however just did a clean install because I wanted to. So far it's running great :)
[Verizon Samsung Galaxy S III] tyler.frost92:
How does this ROM compare to Eclipse 5.1 (what I'm running now)
[Verizon Samsung Galaxy S III] meandg5:
This isn't a ROM its a kernel.
[Verizon Samsung Galaxy S III] samsgun357:
I'm having issues if I go to 182mhz and turn the screen off it requires a battery pull. Also seemed to be getting random reboots if I over clock, even at 1622mhz. It seems to run fine at stock clock speeds. On slim 1.4 with latest BMS. I've never really had issues over clocking even at 1900mhz, don't know why its causing problems now.

Official Team Pipe Me production!
[Verizon Samsung Galaxy S III] GideonX:
That low clock speed may not work with your phone then.

I assume 1900 wasn't on BMS, since that slot isn't in my cpu table. Link me to what you were using and I'll check.
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-09-29 - http://www.droidhype.com/kernel/34
[Verizon Samsung Galaxy S III] gadgetguy08:
IMEI did NOT disappear when I flashed BMS only. Yeah! Thanks!

:thumbup:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
There's big red print stating what to do right on the download page and its been there for the last three updates at least.

Edit: My bad holmes, I misread and thought it said "IMEI did disappear." It gets tiring seeing others post that.
[Verizon Samsung Galaxy S III] gadgetguy08:
No worries. I should have made it clearer, so I edited it a bit. :)
[Verizon Samsung Galaxy S III] tyler.frost92:
Lol whoops. Reading too many threads at once has its consequences
[Verizon Samsung Galaxy S III] samsgun357:
I tried those speeds on lean or faux kernel on TW and 4.2.2 builds. Not a big deal really. I finding that at 1512mhz this phone runs just fine handling everyday tasks, better battery life too. Going to test the latest build on min and max clicks speeds though.

*edit* I tried over clocking, even at 1566mhz I'm getting random reboots, constantly. Using slim 1.4 and latest BMS kernel.

Official Team Pipe Me production!
[Verizon Samsung Galaxy S III] samsgun357:
I'm testing lean kernel now. So far I've been able to go to 1780mhz without issue. I love BMS kernel, battery life is awesome but I can't adjust my clock speeds at all with it.

Official Team Pipe Me production!
[Verizon Samsung Galaxy S III] GideonX:
What voltage is being applied to that slot?
[Verizon Samsung Galaxy S III] samsgun357:
I mistyped earlier, its 1728mhz [MENTION=1539587]1275[/MENTION]

Official Team Pipe Me production!
[Verizon Samsung Galaxy S III] GideonX:
Stock BMS is 1300 at that slot. Did you UV?
[Verizon Samsung Galaxy S III] samsgun357:
No I didn't, this is on lean kernel latest stable build.

Official Team Pipe Me production!
[Verizon Samsung Galaxy S III] silver04v:
How do we know which rom version we are running. I'm on AOKP 8/20 build. Where do I find this information?
[Verizon Samsung Galaxy S III] dpeeps74:
In settings > about phone. Your kernel should either be a 3.0.xx or 3.4.xx version

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] OMG_VTEC:
whats the last 4.2.2 build for bms? havent made the jump up to 4.3 yet

thanks
[Verizon Samsung Galaxy S III] GideonX:
7/30 Build
[Verizon Samsung Galaxy S III] Dearborn1977:
Lol what are you waiting for!?!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm sure you're already aware but 09/29 BMS is working fantastic on Slim Bean 1.6 weekly!
[Verizon Samsung Galaxy S III] Droid316:
That it is.

™ Sent From My Slimrom 4.3 Rom Running BMS Kernel With Killjoy Script Powered By 7000MAH Of Battery Power™
[Verizon Samsung Galaxy S III] OMG_VTEC:
you know, i looked for the builds and went to source for the kernel. when i finally went to the actual download place i saw that was an easy one...

sorry...lol
[Verizon Samsung Galaxy S III] krwdre:
Sorry guys wrong section :(
[Verizon Samsung Galaxy S III] srs731:
Just to make sure, this will work with PAC-ROM 4.3.1 correct?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I want to say yes because this has been working fine for me on the latest Slim Bean build 1.8 which is 4.3.1. Different rom obviously but there's a few of us using this successfully.
[Verizon Samsung Galaxy S III] GideonX:
I've only tested on slim weekly 1.8, which is 4.3.1. Works fine for me.
[Verizon Samsung Galaxy S III] srs731:
Thanks for responding, for others to know, it does not boot.
[Verizon Samsung Galaxy S III] GideonX:
What doesn't boot? Slim? Pac?
[Verizon Samsung Galaxy S III] srs731:
Sorry should have been more specific, I personally couldn't get it to boot on PAC-AIO Nightly 10/12. 4.3.1 Maybe I just had bad luck, and someone else could chime in.
[Verizon Samsung Galaxy S III] GideonX:
Boot looping or just doesn't boot at all?
[Verizon Samsung Galaxy S III] srs731:
Damn I really slacking here aren't I. Boot looping, I get past the Splash screen, just nothing more. Stuck on "insert coin, game over"
[Verizon Samsung Galaxy S III] GideonX:
Hang on, trying something.
[Verizon Samsung Galaxy S III] GideonX:
Want to try this test build out? http://goo.gl/39RGNN
[Verizon Samsung Galaxy S III] srs731:
Beautiful! Thank you. All is well on my S3 again :)
[Verizon Samsung Galaxy S III] GideonX:
Super. I'll fix up a few things and push a new build out tomorrow. Enjoy.
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-10-16 - http://www.droidhype.com/kernel/34/

This one is mostly a maintenance build, nothing really new aside from fixing the 4.3.1 pac-man problem.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Working fine over here with SB 1.8. just as the prior version was. Yes, I updated for the sake of updating lol
[Verizon Samsung Galaxy S III] GideonX:
I like your style.
[Verizon Samsung Galaxy S III] flyestAC:
If it's good enough for Gideon and Snoop it's good enough for me. :thumbup:

Booted and running just fine on Slim 1.8 for me as well.
[Verizon Samsung Galaxy S III] herooftimeloz:
The latest versions aren't working with the new CM 10.2 nightlies (I'm using mastamoon's version) :(
[Verizon Samsung Galaxy S III] GideonX:
Can anyone else confirm this?
[Verizon Samsung Galaxy S III] AdMire:
Yeah, I get some com.phone force close when I try and flash it. (Running same ROM as Heroo)
[Verizon Samsung Galaxy S III] GideonX:
And you guys have followed these instructions in mastamoon's OP?
[Verizon Samsung Galaxy S III] AdMire:
I don't get the com.android.phone force close until I flash the BMS kernel. The way I read that is if you flash HIS build alone, flash that link and it will clear the databases. I flash his nightly fine, no force closing; once I flash the kernel, I get the com.android.phone force close. Should I flash his nightly, BMS, then that link all in the same go? I haven't tried that.
[Verizon Samsung Galaxy S III] GideonX:
Give it a try, all it does is clear the db, which may be what you need.
[Verizon Samsung Galaxy S III] herooftimeloz:
Yup, I tried two instances, with and without flashing that file. In each case it led to com.phone FCing
[Verizon Samsung Galaxy S III] AdMire:
Same as above, just tried myself.
[Verizon Samsung Galaxy S III] GideonX:
You guys have a zip of mastamoon's build before 10/15 you can try? I got a feeling one of these cherry picks he's got in there is causing the FC.
[Verizon Samsung Galaxy S III] AdMire:
I do not, although with that said, the first time this happened to me was I believe 10/10.
[Verizon Samsung Galaxy S III] mikejr83:
It seems to be happening on a few different kernels. It does it with my unofficial KT747 kernel. I came here to see if it was fixed in BMS. I have to see if the latest LK is doing it.

I talked with masta about it today and we couldn't come up with any quick solutions.

GideonX, what commit(s) did you use to fix the PAC problem? I'm having the same issue on my unofficial kernel.
[Verizon Samsung Galaxy S III] SomeGuyDude:
Running like a champion on Carbon. So I'm happy.
[Verizon Samsung Galaxy S III] rhamorsky:
is good like hell for me on liquidsmooth 2.10:laugh:
[Verizon Samsung Galaxy S III] GideonX:
I think what fixed it was merging in some changes from the pac ramdisk. I wish roms would leave the ramdisk alone...
[Verizon Samsung Galaxy S III] hallstevenson:
But what if they need to do something for their built in kernel?
[Verizon Samsung Galaxy S III] GideonX:
I may just go the anykernel route and not worry about this anymore.
[Verizon Samsung Galaxy S III] hallstevenson:
The anykernel method is ingenious ! I vote in favor of you doing that (I'm always careful "telling" someone else how to do something).
[Verizon Samsung Galaxy S III] hallstevenson:
Would you suggest this new kernel for ALL v4.3.1 ROMs or just these certain ones ? notta updated his Paranoid Android build (port ?) to 4.3.1 as well as various, recent CM updates, etc.
[Verizon Samsung Galaxy S III] GideonX:
Should be fine for most 4.3.1 roms.

Only one I know not working right is mastamoon's cm, not sure about that one yet.
[Verizon Samsung Galaxy S III] ITR218:
Newest kernal working on Dirty Unicorns 4.3.1 ..
[Verizon Samsung Galaxy S III] hallstevenson:
Seems to be okay on notta's Paranoid Android (latest RC2) build.
[Verizon Samsung Galaxy S III] hallstevenson:
Okay, I may have ran into a minor issue.... On the way into work, I made a phone call and on speakerphone, with the volume all the way to the max, it was way, way too quiet. Once I got to work, I re-flashed [UNOFFICIAL ROM] [AOSPA] PARANOIDANDROID 3.99-RC2 (OCT17) | 4.3.1 Linaro 4.7.4 O3 and made another call and it seems louder. Granted, I wasn't in my car where there's more noise.

I do know that volume levels can be controlled or set by the kernel so I'm just wondering if this is the case.
[Verizon Samsung Galaxy S III] GideonX:
You can tweak the sound output via Trickster.
[Verizon Samsung Galaxy S III] GideonX:
Just read this in mastamoon's thread. Did you flash the db deleter before flashing gapps or after? It seems you need to do it before flashing gapps to get rid of the phone fc.
[Verizon Samsung Galaxy S III] Reborn627:
I can confirm that running the db deleter before gapps still causes the "unfortuantely com.android.phone has stopped worked" error to occur when flashing this kernel as the last step. This is the order that I just attempted.

1-Wipe system, dalvik & cache

2-Flash Mastamoon's unofficial Rom, DB Deleter, gapps (8-20-2013 version) & GideonX's BMS

3-wipe dalvik

4-reboot system

Once the device came back after rebuilding the dalvik it errors persistently.

Just thought you'd like to know.

Pecae,

Ray
[Verizon Samsung Galaxy S III] mikejr83:
It seems that any custom kernel is having issues with ROMs using the qcril commits (mastamoon's). I haven't tried LK yet but I'm guessing that it will have the same problem.
[Verizon Samsung Galaxy S III] hallstevenson:
Doesn't appear to be available in the free version. Are you referring to the paid version ?
[Verizon Samsung Galaxy S III] GideonX:
Yup, looks to be.
[Verizon Samsung Galaxy S III] GideonX:
I believe you are right, paid has it.