yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
I've ran into the issue with playstore apps downloading very slowly on wifi only quite a bit lately running 4.4.2 Roms. I have found that either with a reboot, or maybe 2. Or just Simply let the phone sit for several hours not trying the playstore at all, usually fixes the problem. Always has for me. It's like the system has to configure or adjust to something.

---------- Post added at 04:53 PM ---------- Previous post was at 04:28 PM ----------

Just thought I'd drop back in to report on the 4/2 kernel flash. I was mistaken about my apps being re-downloaded. The few apps that I had purchased, which disappeared when I flashed your update, would download and install, but showed only the little Android guy and the name of the app. Tried with my network and wifi, same results. I really think if I had formatted system, reflashed my nightly, then flashed your update, it probably would have worked. But instead I formatted system, flashed my nightly, flashed my gapps, rebooted and was able to download and install my apps again. So it's likely not my recovery. Rather something still not syncing with CM? Idk. Just thought I'd let you know. [MENTION=4325945]ktoonsez[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unknownyello:
Working with latest twrp 2.7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Flashed fine with twrp 2.7. Strange as it may sound, I lost some apps as well. All of them were paid user apps from playstore. When I try to redownload them, they come install as apps on SD and they FC when run.

Forgot to mention this is on CM 4/2 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Mine flashed fine and didn't remove any apps on 2.7.0.0. I'm running pa
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
What's strange is...for the past few months, I've only used BS and C-Rom. Anytime I've lost an app, its always been the same ones regardless if I used TWRP or CWM. Fortunately if I use another source to get those same apps/apks, they stick... until the next status 7 issue.

Sent using two ply for full wipes 'cause nobody likes skid marks from a dirty flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Flashed with twrp 2.7 couldn't fix permissions bit it flashed and optimized correctly. Working great so far. Flashed TV is morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unknownyello:
Had the same issues, but then I reflash the rom, making sure I delete system, and was able to fix permission the second time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
My banking app was removed... Play store won't open...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 04.03.2014

1. Update ramdisk to include updated selinux stuff from CM. This fixes paid apps issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
[MENTION=4325945]ktoonsez[/MENTION] not sure if you saw my comment yesterday about it but I was wondering if one day you could add intelliactive?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, its too embedded into the kernel its in, to reliant on other things I would need to merge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Anybody that was having paid app issue confirm its working for you too? I had 2 reports already from TMO guys that it is working now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I'm having issues flashing the 4/3 release in TWRP 2.7.0.0. I am getting an error updater binary in zip. I am running CM11 4/2 release. I have also tried redownloading.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
There was a 4/2 release. Try that. [MENTION=4325945]ktoonsez[/MENTION] must have had the CM Updater Binary in the 4/3 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nope, it is back to the way it always was before yesterdays test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
@peneoark, in that case make sure to get the post recent link KT has posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
TWRP latest - confirmed this one worked on d2att - no issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Unless he changed the target file in his link, I did download the latest kernel version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Twrp latest 4/3 working +1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NJD316:
Running great so far using latest CWM to flash on SlimKat 4.4.2 build 4.1 D2ATT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goombah88:
Tried the 4/3 release and I still get a status 7. I guess the stars aren't aligned in my favor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
CM11 4/3 nightly

TWRP 2.7

Flashed latest kernel. No issues and the paid apps install properly again. Thanks, KToonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s3lphctr1:
C-Rom 5.7

TWRP 2.7

Working great thanks

Sent from my ktooned c-rom i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
Not sure if this is resolved or not but did you wipe cache and dalvik cache?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] porkyhontas:
Unfortunately Sammy did a pretty shoddy job on 4.3. It's a miracle that any of the XDA TW developers and their ROMs (e.g., Wicked Sensations, MOAR, Project Wicked X) were even able to put a functional ROM together. As a matter of fact, these ROMs outperform Sammy's 4.3. Then you add in this kernel, and others, and you've got a mega powerhouse over Samsung.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goombah88:
Yep, I always wipe cache and dalvik cache after installing a kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
FWIW to those experiencing the "Blue LED" upon Boot, there may be a respite.

Since I updated to the unified CM code based Rom Slimkat version, this issue has disappeared.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goombah88:
I figured it was just a "new feature" of 4.4.2. Is it actually supposed to represent something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
No it does not mean anything. Its probably just a loss of Sync between two CM Commits in the Unified device tree.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I am switching roms. I am using d2att and would like to keep using your kernel. Any kitkat rom you could recommend that is compatible with your kernel. Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
There's Plenty of them. Try SlimKat, LiquidSmooth and so on. Don't go for PacMan or AOKP Those don't work with this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Blue led on boot fixed yet with newest kk kernel?

Not gonna bother updating till that's resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
An update to your ROM would resolve that issue. At least that's what removed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
I'm on slimkat 4.1 official. So if I update to 4.2 weekly it might solve the issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Go to the D2LTE unified Roll out 4.2 Weekly. Think that's what you meant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Yup. That's what I mean the new d2lte nightly. But the led still blinks after update. I'm running the 4 3 2014 build of kt747 newest for kk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Well that's the combo that cleared it for me. Perhaps you should do a clean install of both ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Those 2 dreaded words "clean install". Guess that's my last option.

Thanks for your assistance. I'll report back in a few days when I get time to clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Latest kernel 4/3 build is finally working great with task650 unified build 4/7.

LED turns on during boot then disappears when boot is finished.

All settings and changes stick on trixster mod and KTweaker after reboot.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
the blue led on boot is a feature not a bug..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
It is a bug.... How about reading back a page.

Where in settings does it set the led to blink 24/7 until u plugin a charger lol derp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
ive been running gummy rom for months.. was built in quite awhile ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
You might be mistaken man. Someone here in this thread confirmed this is a bug not a feature.

Edit. To clarify yes I know its supposed to blink during boot. But not continue to blink all day long.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
don't have time to dig thru the gummy thread but it's definitely a feature on that rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Who said anything about gummy ROM? Lol dude seriously read.

It most defiantly is not a feature to have the led blinking indefinitely.

---------- Post added at 10:19 AM ---------- Previous post was at 10:14 AM ----------

Clean install. Did the trick.

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The light is supposed to pulse on boot. The bug some people are talking about is when the light keeps blinking after the phone is completely booted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Absolutely spot on you both. More recent CM commits seems to have taken care of this issue. So those who experience this, should update their respective Roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Why does it take so long for the processor governor to settle down after reboot? Ktoonservative takes a good amount of time to settle down and stay at the minimum mhz. Unless I put it on powersave phone runs wide open and gets up to almost 50 degrees.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its the ROM loading all your media amoung other things. Nothing to do with a governor, kernel or ROM for that matter, they need to do startup stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
OK. Sometimes it can take an hour or so to settle. I wanted to make sure I wasn't missing something.

Temps are in centigrade in your app, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im going to take guess and say your are running a Touchjizz? Even with the jizzer ROM that is way excessive, AOSP settles in under 2 minutes and jizzer is usually 15-20 minutes but an hour is way messed up. So you either got a messed ROM or just need a good old fashion full wipe and start over fresh and see what happens with no apps installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Nope. Non-touchjizz. Quantum 3.66. This issue persisted after a clean wipe, fresh install. I was running an AOKP nightly and the phone started getting HOT all of a sudden. So I decided to get back to a ROM that I could use your kernel on. The weird thing is after a while and switching governors it will eventually behave. I am starting to think it might be hardware?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That does seem like hardware. But if it just started out of no where maybe your external SD has some corrupt data on it (or internal sd too I guess). An easy check could be removing the external SD while shut down and boot up without it to see if anything changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Good call. Sdcard was running at 30% and phone had only be rebooted an hour ago.

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

Well as usual. About an hour after reboot, she sits at 378 w/ 1 CPU on ktsvtv gov. Something is using the internal sdcard for an extended period of time. I killed media scanner and it didn't seem to affect sdcard usage. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Do you have any wakelock showing in BBS?

I got bad blocks on my internal memory, and every once in a while i'll get an mmc2 wakelock. A reboot will fix it, til it hits the bad block again, or til I fix it using fsck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
I'll see if I have a bad block issue. Thanks! Funny thing is, the reboot causes the issue and it only lasts for a short time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I would definitely check with BetterBatteryStats to see if an app/process is causing this (which is probably is, and thus slightly unrelated to kt haha)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scrawson:
PPP async

It would appear that the lack of PPP async support prevents Bluetooth DUN and maybe even PAN.

My system isn't set up to compile ARM kernels, is there any chance CONFIG_PPP_ASYNC and CONFIG_PPP_SYNC_TTY could be enabled?

It is my understanding that these are required for getting an internet connection through a Bluetooth phone/modem. Just to be clear, this is when the Android device has no connection, but another Bluetooth device does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What ROM r u using I don't need to do that on CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Is there a way to enable the advanced reboot? I have an Xposed module that used to enable reboot to recovery, etc. That module no longer works.

EDIT> I'm sorry. It DOES work. It's just I have two reboots now. One is the regular and the other is the one injected by the module. LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think you're in the wrong place, this is KT747 thread, kernel only. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
First of all, great kernel. I really love it and it works very well. However, there is one small issue. Maybe it's from the kernel or maybe it's not. When I use Pandora and multi-task on my phone, I get an incredible amount of lag. Has anyone had a similar issue and know of a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Have you tried different governors and schedulers? Also try enabling the oc steps even if you don't use them, they increase the thresholds of the proc...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
I tried all of those things but it didn't help. Also, it's not just Pandora but other streaming apps such as iHeartRadio as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
You may want to take a look at background programs, I run Play Music and iHeart... Do you have betterbatterystats installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
Yes I do. What should I look for?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
In my signature there is a link for Overclocking and Undervolting. It is expressly based around the settings of KTweaker. That's your reference guide if you will. Now there's a shorter way around your problem.

Please visit, This Ktweaker Shop Thread. You will notice in Post 5 that there are a lot of Pre-made Profiles listed. Pick one for your usage pattern. You can download them via the "Profiles and Scripts" option of the Ktweaker App. May I recommend "Balanced Bull" given your issue ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
Thanks a lot for pointing in the right direction. Most of these profiles, including balanced bull, make my phone unstable and restart itself. The only one I've found that is stable is the ktoonsez one. Is this normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Everyone's experience veries. That's why I had asked you to look at the link from my signature. That gives you a Starter Profile and how to make your own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
If my memory serves, almost all the profiles have undervolting to a fairly high extent. You may want to apply the profile then change it to stock voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Hey KT can we get an update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Honestly, I don't see the need for an update at the moment. Everything works perfectly ;)

If you really need something new to play with, you can extract "com.ktoonsez.KTweaker.apk" from the .zip of the S4 Kernel (Get it here) and copy it over your old KTweaker version located in /system/app

It works perfectly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
I flashed it a couple weeks ago over a new AOSPA build and bricked my phone for a bout 2 days before i could odin it back. Varies for everyone, be very very careful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Uh, flashed? You're supposed to extract the APK for the app then drop it in your system/app. Not flash a S4 kernel on your S3...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
No, No, lol i mean the 4/03 kernel. I don't care about the updated app, though it does look nicer :p I really doub't having put the updaet app would have stopped the bricking though if it would i'm going to feel really stupid..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It wouldn't fix it, I was just wondering if you flashed the S4 kernel. That would have explained the bootloop. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
haha thanks, no worries i should have clarified. I miss this kernel though, nothing compares :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
The new apk causes an FC. Tried clearing cache. No go. Just reflashed the kernel.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeff1981:
Worked fine for me I just replaced the apk and set permissions and then rebooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
Is there a solution for the fc when trying to set the lockscreen wallpaper? I tried searching (not very well since I'm on my phone) but nothing came up. Thanks I'm advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
That's a Rom issue if any. You should do a clean flash of your current Rom and this Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
There has been lots of kernel commits since last kt update. Check cm change log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Oh yes there are commits. [MENTION=4325945]ktoonsez[/MENTION]'s point is if they bring new functionality or bug fix,.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Check back one month kernel commit to get the answer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 05.07.2014

1. Kernel sync with CM

2. Ramdisk sync with CM

3. Linux 3.4.86

4. Linux 3.4.87

5. Linux 3.4.88

6. Linux 3.4.89
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Great update. No more FC or random reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You do realize that [MENTION=4325945]ktoonsez[/MENTION] does not have an S3. In addition he moved to Verizon from ATT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
i did not. thank you very much for the update ktoonsez. your kernels are very very good. (as if you didnt know). am using with Q 4.1 and has fixed multiple issues that i was having with Quantum. thank you again.

p.s. the user guide (by galaxyS3man30, i think it was )is especially helpful for us newbs. :)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glwilliams4:
Sorry if this was already covered, I did a search and found nothing. Does anyone else have an issue with very very low call volume? I flashed this kernel because my call volume was very low. Flashing this fixed it, but apparently if I switch from talking over bluetooth to talking via the handset during a call, the handset volume goes back down and never gets back up. Seems to be some bug when transferring audio from bluetooth to handset I suppose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Depend on your Rom and its bluetooth stack implementation. I know Liquidsmooth and SlimBean had such issues but later versions rectified it. Also check to see if the Rom allows you to control Volume boost for Calls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glwilliams4:
I'm running SlimKat and had the problem on that included kernel. I then flashed this, and it fixed it so I had assumed it was a kernel issue. Thanks for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try a Clean wipe and latest Weekly of the Rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
on my ROM, under settings ~ advanced options ~ device ~ sound ~ theres an option to click on 'extra gain in voice calls' . hope ya get it fixed.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Such is the case with Slimkat as well. It will work for him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
[MENTION=3639717]Perseus71[/MENTION]

What a great guy :D. Thanks for the continued help with the thread man :good: :highfive:. Hope everybody is enjoying the update :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You bet everyone is! :D You indeed are a sight for sore eyes. We know you don't have S3 or ATT but we all are really thankful to you for supporting us with your fantastic kernel. Thanks KToon :highfive:.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
You were absolutely correct, not a kernel issue but a Rom issue that was fixed on the latest cm nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
New kernel is running smooth for me so far. So happy because I was having issues with KT kernel before. Looks like I'm baaaaaaaccccckkkk!!!!

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Liquid Smooth 2.10 4.3 -> Any of the KT kernelse work?

I downloaded the AOSP JELLYBEAN 4.3 Linux 3.4 VERSIONS kernel, and installed on Liquid Smooth 2.10, which is supposedly an AOSP 4.3 ROM. But when booting, it locks up.

Anyone running a version of the KT kernel on Liquid Smooth 2.10? What specific version, or any links to it?

Many thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I have been using this kernel when LS had introduced 4.3 for the first time. I have been using KT747 since LS version 2.1 I do know it worked just fine. What you want to know is if that version 2.10 is really Android 4.3. Also do a clean flash and make sure to wipe Dalvik + Cache after flashing the kernel.

I have moved to SlimBean after Liquid version 2.9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
It's kinda funny. I searched back through this thread regarding this issue, I found a post I made quite a along time ago with this exact same problem, with same LS and same KT Kernel. I asked about it then and never got an answer.

If by clean flash, you do mean wipe everything, I'm not wanting the kernel bad enough to go through all that. I have a log of configed stuff and lots of apps installed. Actually, I had done a clean flash two days ago, including, of course, the wipe of Dalvik + Cache...although all the setup and apps is done now too.

Must be something with 2.10 that doesn't like this kernel then, given I've had same issues twice now when trying to load with this kernel.

I'll check out Slim Bean...I presume that is a kernel.

[EDIT]

It's not a kernel. As I was asking about a kernel, I had presumed a kernel was what you were suggestiong.

FYI...my phone doesn't like any of the 4.4.2 ROMS. I've tried 3. All too buggy for me (at least on my phone...I do think my refurb phone is a bit finicky...even 2.10 LS doesn't run as solid as on my previous phone).. Sigh...