yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] stang5litre:
No problem at all. Thanks for doing that for me. I love your rom solid( I didn't notice it was missing till i got another call yesterday and was like hummm. lol). I know you were taking a break i hope you get your much needed rest. Thanks again for all your hard work :):good:

Didn't think i would like the blacked out theme turned out i love it lol.

Is there anyway to swap calls beside that button? if so i can use that and would save you the time to swap that out.

Thanks for the Rom Jrkruse !!! And you support is top notch.
[Verizon Samsung Galaxy S 4] Shockz:
I am a little confused with the difference between this rom and the one in your "[ROM][TW 4.4.2 KitKat XXUFNDG for MDK] Updated 5-19-14" thread. What is the difference or which one is better/newer? Thanks and sorry for the possible silly question. :p
[Verizon Samsung Galaxy S 4] tkacer:
NC5 is the official vzw 4.4 release, whereas the other thread you referenced is built off the latest international 4.4 release (it's always changing). If you want the latest and greatest release, go with the int'l - might be a little more buggy but jrkruse does a great job getting those compatible with the vzw platform.
[Verizon Samsung Galaxy S 4] Shockz:
Ohh, I see now. I was confused by this:

VZW_NC5_AROMA_4_29_30.zip Aroma Installer Choose what to Install

I545_VRUFNC2_AROMA_4_18_14.zip Aroma Installer Choose what to Install

I545VRUFNC2_4_17_14.zip Full Stock Installs Everything

I saw the first one with VZW and the other ones were i545 so I thought those were INT because I didn't actually really look at them until now. xD
[Verizon Samsung Galaxy S 4] tkacer:
Yep - the NC2 was the leaked pre NC5 release for vzw.
[Verizon Samsung Galaxy S 4] stang5litre:
Kernel

Is this the other Kernel everyone is talking about? "talexop_Kernel_i9505_NB8_v2.5" If so any benefit from switching from KT to that? Thanks

Just trying to see what people are having the most success with. Battery life etc. Might swap back to the NC2 Radio as i have seen some post about getting better signal. Thanks in advance. :)
[Verizon Samsung Galaxy S 4] bryantjopplin:
From the home screen hit menu button, then edit, then home screen settings. Or just delete lol
[Verizon Samsung Galaxy S 4] jrkruse:
I have another thread that I update with the latest International Builds. I mod the roms so they work on verizon I keep this thread with only Verizon released roms. NC2 was released as a leaked version. NC5 is the official release from Verizon My International thread can be found HERE if you want the latest International Build.
[Verizon Samsung Galaxy S 4] gadget!:
Unfortunately...

I can no longer enjoy your work :)

I bricked my S4 and had to send it in to be jtag repaired and it came back with NC5 bootloader...

I did manage to Odin back to NC2 then back to NC5 rooted so I can flash roms but only safestrap compatible.

Please... Make a safestrap compatible rom :cool:

Or... If anyone wants a mint 32gb S4 rooted with NC5 I would be willing to trade for an MDK S4 with some dollars to boot. LOL

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] Redflea:
So sad, sorry to hear that!
[Verizon Samsung Galaxy S 4] downhillvinnie:
how do you change the kernel...Just loaded and no wifi
[Verizon Samsung Galaxy S 4] jrkruse:
Sorry to here that. Someone probably did the old swaparoo and got themselves a MDK bootloader board.

I need to read through the threads and see what it will take. I will get one working for SS.
[Verizon Samsung Galaxy S 4] gadget!:
Well I just bought me another 32gb MDK S4 on eBay...

Can't handle not having control of my phone!

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] sirlantzz:
Update from 4.4.2 from 4.2.2

I originally rooted my stock 4.2.2 and stayed on it, until recently (3 days ago to be precise), and tried one of the 4.3 roms. Felt it was too buggy for every day use so went back to my rooted stock. Then I saw today the post for 4.4.2 stock rooted and read almost all the treads. Found a few good things and everywhere I read, wipe wipe wipe. I said to myself, "let's see if I can brick a GS4! I've done a HTCG1, why not an GS4?" So I installed over all my stuff.

4-8 minutes later, after the install, it did an 'optimize app upgrade' of some sort. Then BAMN! Phone came on, all settings were the same, wallpaper the same, icons on screens in the same place, text messages still there, phone log, everything the same! So not sure if anyone else has tried it, but yep, it works! If you don't hear back from me, it stayed stable and I didn't kill myself after 3 days:)
[Verizon Samsung Galaxy S 4] jrkruse:
I hope that it works out
[Verizon Samsung Galaxy S 4] jrkruse:
You flashed this rom and have no wifi? Are you mdk bootloader or SS?
[Verizon Samsung Galaxy S 4] gadget!:
I do too :D

I've been so spoiled, I've loved my 32gb MDK S4. The best phone I've ever had so I think it was the only thing to do.

I bricked it doing something that was totally my fault.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] downhillvinnie:
SS
[Verizon Samsung Galaxy S 4] Zmnypit:
This is not a SS rom.
[Verizon Samsung Galaxy S 4] stang5litre:
Not safe strap

This Rom is for MDK builds only.
[Verizon Samsung Galaxy S 4] bryantjopplin:
BTW everyone, don't delete shealth on the fnc5 with the s5 add ons. Disabled rotation on mine and reinstall would not fix it. I just froze it
[Verizon Samsung Galaxy S 4] Scorp123:
I seem to have lost my tether ability. I have no idea what I changed. Is there anything I can flash or try to fix this and re-enable wifi tethering?
[Verizon Samsung Galaxy S 4] gadget!:
OK, I have to throw in my 2 cents worth.

I have this rom flashed on an NC2 build and it is working perfectly!

Read on...

Since I bricked my MDK phone I have been forced to become up close and personal with safestrap and 4.4.

I have read until my eyes hurt!

Here is what I have found so far.

As near as I can tell safestrap in not Completely working on any Verizon S4 with 4.4 bootloader.

You can install the SS AT&T beta and it will get you into safestrap recovery but you can't flash a rom in a ROM slot...

I have tried 3 times! It will go through the motions and it appears to be flashing but when you reboot it goes into whatever rom you have in the stock slot, with bits and pieces of the rom you just flashed.

That being said here is what I did.

I followed Surges Downgrade / Upgrade thread to a tee with one exception, I flashed this rom in the stock slot!

I flashed the rom first then without rebooting I flashed the updated SuperSU from the link in Surges thread.

Then since the SS thread had modules for everything up to MK2 (nothing above) I pulled the library files from a working 4.4.2 rom and made my own flashable zip.

I have wifi good signal and everything I have tried is working great.

Big thanks to Surge, now I have a rooted NC5 rom on an NC2 bootloader.

This is my experience, I would imagine it should work for a anyone else as well.

To test things, I have successfully flashed 2 other roms in the stock slot after a full wipe. And I have made 2 full backups and restored back and forth between the two with no issues.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] Surge1223:
good find! [MENTION=1949695]jrkruse[/MENTION] let me know what 4.4.2 SS compatible roms you've made so I can add them to the OP of the NC5 upgrade w/root thread!
[Verizon Samsung Galaxy S 4] guyver2077:
Thanks. It looks like ill have to wrap myself around safestrap as well. Im so upset because i was on MDK.. I flashed this build, booted up fine, but then never recovered after a reboot. Couldn't even get into recovery. I panicked and flashed a MK2 tar via Odin... so now im screwed with it.
[Verizon Samsung Galaxy S 4] mpiccirillo2006:
Phone Calls - Screen Goes Black

I just installed this Rom and it works awesome....

My only issue is that as soon as a call comes in, and then you answer, the screen goes Black and never comes back.. So you end up having to press the HOME button to get the phone so you can end the call.

You can never pull the phone away from your ear and see the screen, you have to press HOME..

Any thoughts?
[Verizon Samsung Galaxy S 4] gadget!:
I'm using this rom and I don't have that problem.

Sent from a Galaxy S4... Far far away
[Verizon Samsung Galaxy S 4] Scorp123:
I also had this happen, but only one time. I don't make many phone calls though and I haven't tested it I'm a few days
[Verizon Samsung Galaxy S 4] bryantjopplin:
Guys that don't want the record button on the phone can change it via xposed framework and wanam module.
[Verizon Samsung Galaxy S 4] mrsean:
Last night, I did a full wipe and reflash. I also flashed the Talexop kernel and loki-doki. Next, I booted up the phone, enabled pin lock and rebooted. Upon reboot, I was easily able to swipe pass the lock screen before pin lock engaged just like before. BTW, password lock in affected in the exact same way. Finally, I did a MD5 check on the rom and verified that the file downloaded correctly.

I'm surprised that nobody else is still seeing this behavior. I thought pin lock was fairly popular. I am going to find another rom to try out.
[Verizon Samsung Galaxy S 4] thedoman:
You could always get the developer version ($$$$$$) I picked up an mdk on ebay.
[Verizon Samsung Galaxy S 4] Redflea:
That's just bizarre...I'm no longer running this ROM, switched to Jkruse's NE5 international ROM, but on both I've had no PIN issues on boot.

I'm at a loss to explain your PIN lock issues. Good luck.
[Verizon Samsung Galaxy S 4] igacek:
Is anyone noticing weird issues with the keyboard/screen flashing at times? When I'm on apps like Reddit Sync and others that use the keyboard, the keyboard will flicker in and out, and makes it hard to type. I'm using SwiftKey. Seems to happen with other keyboards at times too.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yes I have as well, I think it's the kernel. I changed some settings and it started doing the same but a little worse, set defaults and rebooted and still some issues every once in a while.
[Verizon Samsung Galaxy S 4] jdfrye:
I also noticed this to. i thought it might be Last Pass overlay keyboard. but maybe its within the ROM.

Are you two running Last Pass?
[Verizon Samsung Galaxy S 4] igacek:
I am not using LastPass, no.
[Verizon Samsung Galaxy S 4] bryantjopplin:
What is last pass?
[Verizon Samsung Galaxy S 4] jdfrye:
Password manager
[Verizon Samsung Galaxy S 4] storm81456:
I've got the flickering keyboard too. I use Swype. Only seems to happen when typing in certain apps.
[Verizon Samsung Galaxy S 4] ckarrow2:
Bump! Fantastic Rom!
[Verizon Samsung Galaxy S 4] crossen0:
Am I the only one week experiences stutter when hitting the back button while in a conversation in messaging? It lags and I have to hit multiple times before it backs out.
[Verizon Samsung Galaxy S 4] stang5litre:
No mine is running great. No lag issues here. Did you have that issue as soon as you installed? Or just started happening?
[Verizon Samsung Galaxy S 4] crossen0:
Immediately upon restoring messages with SMS Backup & Restore. It happens intermittently - but on every TW rom I install. I only restored roughly 2000 messages and it never happens on aosp roms, even when I restore say 10k messages like I have in the past.
[Verizon Samsung Galaxy S 4] jpen:
Running great so far. Only problem I am having is when listening to music, it skips every so often. Only happens when the screen is off and listening to the music.
[Verizon Samsung Galaxy S 4] mochamoo:
That is the KT kernel. Go into ktweaker and change the disable_media_hotplug from 0 to 1.
[Verizon Samsung Galaxy S 4] jpen:
Um, I actually never messed with ktweaker. I searched all over and cant find disable_media_hotplug. I am most likely missing it somewhere....
[Verizon Samsung Galaxy S 4] mochamoo:
It is under Main Settings -CPU settings-Governor adjustments

Here is the main thread for the kernel and ktweaker app:

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

This is the thread for all the profiles/scripts for the kernel:

http://xdaforums.com/showthread.php?t=2393708
[Verizon Samsung Galaxy S 4] flipper44:
Love the ROM but two nagging issues

Very often I will make a call, I never hear the phone actually connect or ring, the other person receives the call and I don't hear them. I can keep retrying but the same thing happens.

I listen to allot of Audiobooks using MortPlayer for Audiobooks..and I send it to my Jabbra Handsfree via bluetooth and it FM transmits to the radio. It seems like this issue only happens after I have listened to an Audiobook.

Second issue:

I get a random reboot once and awhile(which I don't mind), but the thing I don't like is that I sometimes will wake up in the morning after charging my Phone and the Phone will be completely Unresponsive. I have to Long Press the Power button Several Different times until Finally it will reboot.

Has Anyone Else had these issues?
[Verizon Samsung Galaxy S 4] bryantjopplin:
The call issue here as well, with the screen fluttering and a random reboot every once in a while. Completely clean install.
[Verizon Samsung Galaxy S 4] trmiv:
I've had the call issue as well. I rebooted and it worked after that, and hasn't returned yet. I don't make a ton of outgoing calls though so who knows.
[Verizon Samsung Galaxy S 4] mochamoo:
I get the SOD (2nd issue) in the mornings once in a while. This is not good because it means the alarm doesn't go off ;) I can usually fix it by messing around with the KT settings in ktweaker. Can't say for sure what fixes it, consequently it happens again when I change kernels or profiles. I think increasing the voltage across the board helps. Not very scientific I know. I try to stick with a profile/script that works. Operative word is *try* :)

I tried the talexop kernel for a while. It was pretty stable but my phone ran hot and battery drain increased quite a bit while I was using it. As far as I know you can't tweak the kernel with something like trickster or ktweaker. I may give it another try.
[Verizon Samsung Galaxy S 4] Velocifero:
Talexop kernel doesn't prevent SOD. Happened to me yesterday using it.
[Verizon Samsung Galaxy S 4] 32BitWhore:
I raised min clock to 3xxMHz (sorry don't remember the exact right now, but it doesn't matter) and haven't had the issue since. I only had it once or twice on 189MHz min so this could be entirely unrelated. I generally leave the ktweaker settings alone on my S4 especially on this build as it runs well regardless. Default ktweaker settings seem to be acceptably quick and stable for me, and gives me a full days use with about 40-50% battery at the end of the day.
[Verizon Samsung Galaxy S 4] Velocifero:
Cool, thanks. I'll give that a try if I get SOD again.
[Verizon Samsung Galaxy S 4] mochamoo:
My best friend has a completely stock, unrooted, locked bootloader S4 on kitkat and it had an SOD yesterday as well. Ended up having to pull the battery to get it going again.
[Verizon Samsung Galaxy S 4] Velocifero:
So you're saying it's hopeless to try and find a ROM that doesn't have SOD? :crying:
[Verizon Samsung Galaxy S 4] mochamoo:
Guess you could say that. I think that he has seen this a couple of times since Kitkat rolled out. I see it more with kt kernel than talexop.
[Verizon Samsung Galaxy S 4] bryantjopplin:
No I have yet to have any on three different kit Kat touchwiz roms. Perfectly stable for me in every aspect.
[Verizon Samsung Galaxy S 4] Velocifero:
Dang. I've tried many different KK TW ROMs and kernels and it's happened every time so far. I've factory wiped each time too. I haven't tried Hyperdrive or Echoe long enough to assess them yet, though.
[Verizon Samsung Galaxy S 4] meazz1:
Does this rom work with Safestrap 3.72 on VZW?
[Verizon Samsung Galaxy S 4] mochamoo:
Which radio? I am using nc5 radio. Imagine that is also what is on my friends completely stock s4 too.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yes nc5 radio. Only issue I have seen is with SwiftKey keyboard I have some screen stutter every once in a while when it first opens up.
[Verizon Samsung Galaxy S 4] mettee:
Something weird, if anyone else has this I'm curious. If I'm plugged in to charge and the phone is off it will not boot. I have to unplug the charger then power up. Anyone else?
[Verizon Samsung Galaxy S 4] Zmnypit:
Is there any KTtweaks that can be done to stop the over heating during tethering?
[Verizon Samsung Galaxy S 4] calebcabob:
verizon visual voicemail

Does Verizon VISUAL VOICEMAIL work?

Can someone try it out if they don't mind leaving some feedback?:highfive:
[Verizon Samsung Galaxy S 4] stang5litre:
Its not in the Rom and you cant use the apk file as it still will not install. BUT. There is a fix for it. I found it on my desktop will post link for you. As soon as I get home
[Verizon Samsung Galaxy S 4] calebcabob:
Cool, I am curious! I've gotten it to work in most 4.3 ROMs. I'd love to know what else is out there though! Thanks a lot!
[Verizon Samsung Galaxy S 4] Zmnypit:
I found something with the overheating issue some of use are experiencing

http://xdaforums.com/showthread.php?t=2674928
[Verizon Samsung Galaxy S 4] Scorp123:
Have you tested this??
[Verizon Samsung Galaxy S 4] Redflea:
Just installed it, don't game so I don't expect it to have much effect on my phone.
[Verizon Samsung Galaxy S 4] stang5litre:
Sorry took me a minute try this out ?

http://xdaforums.com/showthread.php?t=2768874
[Verizon Samsung Galaxy S 4] calebcabob:
Did that work for you?
[Verizon Samsung Galaxy S 4] reggie cheeks:
Months ago I know but that is dope. Thanks!
[Verizon Samsung Galaxy S 4] mochamoo:
I am thinking that I will just go back to a 4.3 backup. Even stock Kitkat phone has sod issues. My friend is kind of upset with his right now.

Gonna go old school... Yup.
[Verizon Samsung Galaxy S 4] mb27:
Is there anything I can install or flash to enable long pressing the menu button to kill the active window? I know with wanam xposed I can enable long pressing the back button to kill the active window, but that conflicts with using multi-window.

Thanks.

Edit: Never mind. Gravitybox has this setting.
[Verizon Samsung Galaxy S 4] ljcorsa:
+1
[Verizon Samsung Galaxy S 4] stang5litre:
Yes just follow the instructions and it worked for me at least . Hope this helps ☺
[Verizon Samsung Galaxy S 4] calebcabob:
Don't forget to thank the one who posted that thread:)
[Verizon Samsung Galaxy S 4] Zmnypit:
Running it since Friday and haven't had any over heating issues. Knock on wood
[Verizon Samsung Galaxy S 4] stang5litre:
Didn't realize you were the one that found this fix lmfao face palm lol

Thanks again
[Verizon Samsung Galaxy S 4] calebcabob:
Oh, no problem. Haha. I'm glad to hear it worked for you!
[Verizon Samsung Galaxy S 4] Velocifero:
Awesome! You're welcome :)
[Verizon Samsung Galaxy S 4] dark_overload:
Random Battery Drain / Crash / Reboot

My fault for posting this in the wrong thread. I have too many tabs open. THIS is the thread for the ROM I am on: NC5. I've deleted my post in the other thread and attached the log file to THIS post.

I keep having these random "reboots" that a few people have spoken of. It starts out with a process (usually "Android System") consuming 100% of one or more cores. During this process I can only assume that a TON of logcat entries are being created because CatLog just sits there until the crash/reboot, as does the logcat export tool within KTweaker.

I have attached a dmesg log of the time up until, including, and after the soft-reboot. The text file has CRLF newlines. I hope this helps.

This has been happening with the KT-SGS4-KK4.4-TW-VZW-04.28.2014 kernel that is built into this rom and now I can confirm that it still happens after upgrading to the KT-SGS4-KK4.4-TW-VZW-05.28.2014 kernel.

I have had my phone connected to the Android Debug Monitor for most of the day now and it is not going to be disconnected until I catch a crash. I'll keep THIS thread posted with the results. ;)
[Verizon Samsung Galaxy S 4] dark_overload:
Fatal exception in "android.ui"

Just happened again. Interestingly enough (and this is the first time) the Samsung keyboard was stuck on-screen and wouldn't go away until UI death. I have a nice logcat from the entire incident.

Hey jrkruse, I should tell you that aside from this I think you've made an awesome system. Once we solve this issue I'd like to try the aforementioned VVM trick. You or anyone else who had a hand in the creation of this system should please feel free to PM me. I'd be happy to help debug.

It seems truly random. Every time I think I know what causes it, I can never accurately reproduce it. But I am going to supervise everything this puppy does from now on. :laugh:
[Verizon Samsung Galaxy S 4] heath2805:
I had that happen too multiple times. I just use Google keyboard from playstore and problem solved. It has no lag like Sammy's keyboard anyway and its free...all good
[Verizon Samsung Galaxy S 4] Zmnypit:
Got the cooling down message again last night browsing reddit. Seems like the leaked version of this rom did not have this problem.
[Verizon Samsung Galaxy S 4] flipper44:
I am having the once a day (at least) reboot as well...Long Use of Bluetooth and Audiobooks Will force it after about 2 hrs, if it doesn't force the reboot, it makes calling impossible or answering calls have no voice, even after Ive shut bluetooth down.
[Verizon Samsung Galaxy S 4] dark_overload:
Hey flipper; I noticed that you mentioned long use of BT. Just out of curiosity are you using a wearable (i.e. Samsung Gear) device over BT link?
[Verizon Samsung Galaxy S 4] flipper44:
[/COLOR]Hands free FM transmitter
[Verizon Samsung Galaxy S 4] dark_overload:
I wonder if BT is the cause. I'll do some more testing. Is there any way you can save a logcat from when it happens to you?
[Verizon Samsung Galaxy S 4] 318sugarhill:
I get it about once a day... And I was under the belief that wifi caused it.... Until it happened today at work... No wifi at work. No Bluetooth for me. I wear a fitbit but I only turn on Bluetooth to sync it and I usually just sync with my Nexus 7. For me it happens when the phone is idle in my pocket for a longboat time
[Verizon Samsung Galaxy S 4] bryantjopplin:
It's not this rom guys, almost every thread with 4.4 touchwiz for the s4 all seem to have the same issue. Personally I have only had one reboot from two weeks of use, no freezes, excellent battery, only some weird screen flashing when swiftkey keyboard opens up for about 1 second and it's periodically. Hope you guys find the issue
[Verizon Samsung Galaxy S 4] dark_overload:
I have seen the IME flicker you speak of, though it never seemed to cause problems. I have also seen other threads talk about similar problems, but without a correlation between log entries across these different systems one can only assume there is a connection. I haven't heard of any issues like this on the OFFICIAL system, so something in these custom builds is causing it.

The good news is that since this system is modified as little as possible, I cannot think of a better candidate for tracking down the cause. I really hope we can solve this too. I have always liked ROMs that are as close to stock as possible.
[Verizon Samsung Galaxy S 4] Surge1223:
The issue is not rom related most likely. I havent seen one person using SS complain about this, so one could assume the cause would be kernel related (the symptoms even sound kernel related) in which case logcat will not help you much, instead you should investigate kmsg.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Me? If so I wasn't really worried about it as it doesn't do it too much and doesn't affect me. Lol. But just out of curiosity sake what kmsg command would give me enough detail to see or is it just kmsg?
[Verizon Samsung Galaxy S 4] heath2805:
I agree with Surge. Most reboots or lock ups are usually kernel related issues.Voltage/CPU could need adjusted. All devices act differently to kernels. I found KT kernel to run the best for me. His 6-09 update is working great.