yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] dtriguero:
is twrp ur using for correct s4? Modem shouldn't stop boot sound or wifi/cell but not boot. Is device ext4 or f2fs? try full wipe system,data,cache sometimes things cause problems if something is incompatible left behind. Try see if will boot with out gapps flashed it should even without gapps u may have a bad gapps package. Do any other 6.0 roms boot.

Edit-also which bootloader are u on I'm not sure but I think the newer one may not allow a boot if permissive kernel so maybe the kernel. [MENTION=7026648]AlaskaLinuxUser[/MENTION] what are ur thoughts or knowledge about the bootloaders? didn't u flash to the newest at one point
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
We are missing something here. Perhaps we should start over. Dtriguero is on the right track.

Okay, what phone model do you have? Be specific.

Which version of modern/bootloader? Please be specific, the whole string.

After flashing back to stock 4.4.4, you do not need to flash cf-auto, just flash the twrp, I recommend 3.02, or even 2.8, Which specific version of twrp are you using?

Then, make your backup, do a full wipe, and flash the ROM, and only the ROM, no gapps. Do not wipe cache or davlik. reboot. Does the ROM load?

As for the kernel and boot loaders, well the wrong kernel will usually cause a failure before the splash screen (boot logo - the unicorn). The wrong modem will usually boot, but will not recognize the Sim card or other oddities.

Now, the boot loaders, those can be tricky, but in this case, I had used the old md's to the ok's, or is it oh? Now I have too look (too many phones). Either way, the nh7 should be fine, but there is no harm in updating. However, I am really inclined to believe that we are missing the obvious here, which is why I would like to request the above info.
[T-Mobile Samsung Galaxy S 4] BlueRomulan:
I flashed back to stock 4.4.4 and TWRP 3.02 with Odin. My wifi doesnt work anymore

Phone model: SGH-M919

Running version 4.4.4

Baseband: M919UVUFOK3

Kernel: 3.4.0-6281449 dpi@SWHD4319 #1

Build number: KTU84P.M919UVUFOK3

When in download mode, I see KNOX WARRANTY VOID: 0x1 and KNOX KERNEL LOCK: 0x0

No. I am stuck at the splash screen
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hmmmm... That looks fine. Do any other roms work when you flash them?
[T-Mobile Samsung Galaxy S 4] BlueRomulan:
No. I also tried your Resurrection Remix N 5.8.0 rom with the same results
[T-Mobile Samsung Galaxy S 4] dtriguero:
When flashed the 4.4.4 was it a full stock including aboot(bootloader) or modified to remove it trying to find out ur bootloader version. Ok3,mk2,nh7,mdb,mdl. As far as ur wifi sounds like ur using and old modem with newer bootloader there are two modem.bin and nohls.bin. Do u have sound cause one modem affects sound and other wifi but modems won't stop it from booting.

edit-In twrp did u wipe system as well or just factory reset. Also what twrp version meaning for what device there are difference in ones for T-Mobile, at&t, ect. they will boot but cause problems flashing correctly. Where did u obtain it official site or custom build
[T-Mobile Samsung Galaxy S 4] BlueRomulan:
I followed instructions on this thread https://xdaforums.com/showthread.php?t=2546016 and downloaded M919UVUFOK3_M919TMBFOK3_TMB. I do not think this contained a modified bootloader. Can you refer me to another DL source?

As for the modem, I do have sound. I was able to toggle wifi in the past after I flashed auto-CF on the stock rom. I didnt give this too much thought as I assumed that flashing a custom rom would fix this.
[T-Mobile Samsung Galaxy S 4] dtriguero:
What's in the tar file
[T-Mobile Samsung Galaxy S 4] BlueRomulan:
I wiped the system. I downloaded "twrp-3.0.2-0-jfltetmo.img.tar" here: https://dl.twrp.me/jfltetmo/

I extracted the zip and found two files. "M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5" and "SS_DL.dll"
[T-Mobile Samsung Galaxy S 4] dtriguero:
That tar is like a zip,rar type file look inside it what is listed also have u tried full wipe and just flashing the 6.0 rom without flashing gapps and seen if it booted sometimes a bad gapps package can mess things up. Are there any errors during the flash.

---------- Post added at 12:58 AM ---------- Previous post was at 12:49 AM ----------

So twrp shouldn't be a problem it's the right one. Sometimes but not often twrp messes up mounting system if would try full wipe again then reboot back into recovery it will say no os installed just continue then once rebooted manually monut system data and cache if aren't then try just flashing rom nothing else then reboot and see if boots if not attach ur recovery log u may need to copy after the flash before reboot its in /cache/recovery.log use twrp file manager and copy to sdcard before rebooting cause it will overwrite it next boot to recovery
[T-Mobile Samsung Galaxy S 4] HarveyWallbanger:
Hi I just recently installed this ROM. Love it!! I'm having trouble copying files from the phone internal storage to an external USB (otg). I can copy from ext USB (otg) but only to the download folder of internal phone storage. But not the other way around. Any advice would be helpful. Thank you.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
fadyrox,

This ROM will not allow itself to install on your phone. TWRP will say that your phone is not a JFLTETMO device. Sorry.
[T-Mobile Samsung Galaxy S 4] christoophat:
No, it doesn't , please read the OP to discover which phone this ROM is for (hint SGH-M919)
[T-Mobile Samsung Galaxy S 4] darazor:
After 1 week of use I would have to give this ROM an excellent as a grade. It is precisely what I was looking for in an "M" ROM. I suspect that if more people tried it they would feel the same. Looking forward to any future updates etc. Thanks for what must have been a lot of work. I may get around to trying Xposed on this but not sure I really need it.
[T-Mobile Samsung Galaxy S 4] christoophat:
installing now...
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the feedback!

These ROMs do take quite a bit of work. With my old laptop, each compile takes roughly 9-12 hours, so I adjust my codes/files/settings and try to run the compiler at night. I never realized how much time and effort devs put in! Now I am just thankful that God gives me the time and ability to work on it, and that I can give back to the community that has helped me since the old Motorola Flipside! I try to make a habit of hitting thanks on other devs ROMs, even if I didn't like their work, because it just might keep them working on our old phones, rather than moving onto something newer (don't worry, I'm not planning to move on anytime soon ;) ).

Just to let everyone know, here are a few things I am hoping to upgrade on this ROM. I have been adding alternative governors, such as YankActive, BioShock, Dance Dance, and Lionheart to my personal builds. I have not released anything yet as they are not stable yet (because of me, not because of the governors) or having compiler warnings and issues that I need to clean up first. Hopefully I can get the bugs ironed out and have those up sometime soon!
[T-Mobile Samsung Galaxy S 4] darazor:
I don't see a donate button. I would like to help support your eforts. Perhaps you could put one on.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
I really appreciate it, but I can't take any money for this. I do this for the learning experience and for fun!

If you would like to make a donation, would you consider making a donation for the homeless and hungry in Fairbanks, Alaska? A dollar can feed somebody for a day, five bucks can keep somebody off the streets and maybe even get them into a warm bed. I will never know if you did or didn't, and you don't have to post that here.

http://www.fairbanksrescuemission.org/give/

Or

https://stonesoupcafe.org/ways-to-help-2/donate-now/

Thanks.
[T-Mobile Samsung Galaxy S 4] darazor:
Update on the use of this really Great work. Just to see if I could, I installed Xposed zip then the Xposed APK. This in and of itself did not give any issues. So, I installed the Gravity Box module. This had one minor issue (though I did not try all options, too many and only wanted a few select). On Reboot, I would get a Gallery has stopped working notification but I found that if I waited a bit longer for everything to boot up then no stop working indication. Second issue, even with on screen nav buttons turned off in Rom control and gravity box they were on. I found that if I turned them on in both Settings and Gravity Box, set the color to white in Settings:Rom Control and the key color to black in Gravity Box and nav bar height set to minimum in gravity box then they were not an issue. The other modules I used were MinMinGuard, XPrivacy, XuiMod. Again, I did not use every option but those that I wanted worked. So, use will no doubt vary but Just a little update if anyone was interested.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for testing xposed! I know that is pretty important to some people.
[T-Mobile Samsung Galaxy S 4] christoophat:
Had high hopes for this ROM, but had the phone BT lockup when trying to receive a call in the car with Pandora streaming. The music stopped, but no further indication that a call was available, and I had to hard reboot phone to get it back. Giving the new release of JDCTeam's AOSP a whirl now...
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
No hard feelings, be sure to update the Bluetooth poll at the top of the thread.

EDIT: The Bluetooth does work, but you need to adjust a setting. For working Bluetooth see post #3 "Bluetooth Workaround".
[T-Mobile Samsung Galaxy S 4] khaoticking:
Flashed this on jflteaio with jfltexx twrp recovery works great so far can not comment on BT as I don't use it
[T-Mobile Samsung Galaxy S 4] darazor:
I meant to ask earlier. Is there a reason you use the older TWRP 2.8.7 vs the newer 3.0.2
[T-Mobile Samsung Galaxy S 4] khaoticking:
Unfortunately still has the BT issues bit its not a biggie for me because I rarely use BT
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
That is a great question. For which I have a perhaps less than great answer! :D

I tend to "stay behind" a bit for 2 reasons:

1. The latest is not always the greatest. As we see here in MM ROMs, there are Bluetooth issues. Granted that is not TWRP related, but often the latest and greatest builds of recoveries or ROMs can be buggier, so I tend to wait until the "dust" settles and the big fixes are already done.

2. Staying behind gives me greater testing scope. My phone is still on the MDL bootloader. I test the older modems too. So when people ask if it works on older setups, I have a ready answer. Some will only support their rom if you flash the latest, which is a legitimate request, as it keeps everyone up to date and on the same page, but I would like to know if it works on any setup, including older ones. You never know why someone may not be able to, or may not want to upgrade for some bizarre reason. (Not very likely though.)

Granted, T-Mobile didn't lock these bootloaders (until the S7, which they say is not their fault) but you never know..... So this may be a mute point.

Newer modems, however, are a good thing, but those are easily flashed for testing. I will likely update my TWRP eventually, but for now, it does everything I need it to do.

So you might say that I am endorsing TWRP 2.8.7 and newer.

Or I got too busy cooking up ROMs to upgrade my TWRP. Then again, I suppose I could have updated it faster than typing this post on my cell phone, so I'll let you be the judge of that. ;)

BTW: I had some trouble with my new kernel with BioShock governor. Still working on it. Compiling back and forth between this ROM and a few others (omnirom, liquid smooth, and slimroms 6, none of which have been cooperative lately).
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for perhaps the best answer I have ever had to an xda forum question.. FYI I too, am on MDL bootloader but OK3 modem.
[T-Mobile Samsung Galaxy S 4] ivoe:
Bluetooth car issues,

Been having setting close on me

Facebook abused my phone an totally killed the battery even tho I closed it several times

Purify app has saved my battery.

Just minor stuff after that

Apps closing/unable to start (fixes 2nd - 3rd time around)
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
To God be the glory! Some moderate success. I am still new at this modding thing, so it is taking me a bit to get this squared away. I managed to add the Lionheart kernel governor, but it is pretty choppy. The Lionheart governor is based on the conservative governor. I also have the source for the Wheatley governor, and I hope to add that as well.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
The Lionheart governor....

Unfortunately, when adding it in I broke the WiFi, so I DO NOT recommend this for daily use: https://www.mediafire.com/download/wac3678ry9gs0f7

I am posting here rather than updating the OP, because this version gained a choppy governor and lost WiFi, so it is not useful at this time. I am only putting it up if any wanted to check out the Lionheart governor for feedback purposes.
[T-Mobile Samsung Galaxy S 4] darazor:
I continue to use Xposed without any perceived problems. I have added appopsXposed for it's better permission management again without any apparent issues. If anyone else is using Xposed a heads up on module use might be helpful. Thanks. Appreciate your hard work with govenor but wil have to for go trying it as I need my phone to be fully functional.

---------- Post added at 02:29 PM ---------- Previous post was at 02:21 PM ----------

Forgot to ask this question. Not a request for action but informational only. Do you routinely update your builds with security fixes on a schedule or as you work on that particular area of the ROM. Thanks again for a really superior build.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question.

At present I do not have a "build schedule" for regular updates. My current plan is to update/sync the build when I add anything. I have re-synced the AOKP source code presently, but am having new problems with builds. AOKP JFLTETMO device trees are still stuck at LP5.1, so I use other rom trees to get good 6.0 material. The problem is that any changes when syncing can sometimes cause problems with the non-AOKP device trees I am using. At least, that is the best I can tell from what has been happening. I make lots of backups to try to enable "rolling back" if needed. I am currently compiling a couple of other roms, while working on this in between builds.
[T-Mobile Samsung Galaxy S 4] darazor:
I knew it wasn't an easy task. I, and I am sure others really, really appreciate the tremendous amount of effort that goes into this endeavor.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Well thanks! But most of the credit goes to the AOKP team! I just muddle through putting it on our phones. ;)
[T-Mobile Samsung Galaxy S 4] timz1313:
ROM

Rocks my. ..S4 ..m919..like ..S7..:o:silly::silly::laugh::laugh::laugh:
[T-Mobile Samsung Galaxy S 4] rephistorch:
I've been using this ROM on my phone and I love it, with one unfortunate exception. If you try using the hangouts dialer, your mic doesn't work (aka the person you are calling can't hear you). The mic works for all the other applications I've been testing.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Glad you like it!

Sorry to hear that it doesn't work in that app. Do you think you could take a logcat while attempting to use the app? Maybe then we can figure out how to fix it.

Also, for any interested... PAC-rom MM is up:

http://xdaforums.com/galaxy-s4-tmobile/development/rom-pac-rom-mm-t3400111
[T-Mobile Samsung Galaxy S 4] darazor:
I may be wrong but I believe that hangouts is VOIP. Also, I believe I read a blog note that stated the hangouts dialer was somewhat unreliable? Is there some setting that may need to be changed for it to work properly? Just a thought. Does Google voice work? It isn't VOIP.

You might also try changing the default dialer in hangouts.
[T-Mobile Samsung Galaxy S 4] redx64:
One issue I found with gapps not the rom is the dialer soft-reboots the phone everytime placing or receiving a call.

If you are getting this issue follow this quick workaround is to manually set the Phone/Dialer app as the default Phone App in Settings -> Apps -> enter image description here -> Default Apps -> Phone App.

Source: https://forum.cyanogenmod.org/topic/124381-dialer-crashes/?do=findComment&comment=590388
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Sorry to hear that you are having problems. I tested several gapps, but currently am using the opengapps arm 6.0 pico gapps, and I am not having that issue.

Are you using the built in dialer app? It would be great if you could pull a logcat when that happens so we can work on fixing it. Thanks.
[T-Mobile Samsung Galaxy S 4] redx64:
I used the open gapps 6.0 super and found this issue. However I fixed it based on the solution I gave above. Just wanted to share the solution, incase somebody else was facing the issue
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for sharing!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
New build is up!

New build is up and links are in the OP. Here is the change log:

20160619:

-Synced with AOKP source

-Edited default background

-Added "No Frills CPU" app to build

Mostly just want to keep the security patches up to date. No real change in use/configuration.

Edit:

I also fixed the mGerrit app. However, when you open it, it defaults to AICP's gerrit.
[T-Mobile Samsung Galaxy S 4] darazor:
Get a Zip signature fail error when trying to flash.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the response.

In TWRP, when you select "install" and then choose the package, but before you swipe, there is a little check box about center of the screen that says "Zip file signature verification." Is that checked, if so, un-check it. If you are still receiving the error, let me know and I will see if there was an upload problem. I did successfully install this on my phone, but pre-upload.

Please let me know. Thanks!
[T-Mobile Samsung Galaxy S 4] darazor:
Don't remember ticking that, must have hit by accident. Installed fine. Will let you know how things work.
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for this update. It's really great to have the latest security updates. It was a backup, dirty install and pico gapps, super SU, Xposed, AdAway, Nova Launcher. I find that everything is working as before. I haven't checked bluetooth. I will the next time I get in the car. I don't anticipate and issue since I've been trouble free all along. I do love this ROM.
[T-Mobile Samsung Galaxy S 4] darazor:
Update on Bluetooth. Continues to work fine on new build, tested on garmin today.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great! Thanks for putting that out there.

I am continuing the saga of kernel tweaking, and hope to have that up soon.

It is kind of like cooking. Add a little bit of this, a dash of that, and hope it doesn't flop! ;)

I have been blessed with some successful kernel builds, but am looking to get one that still enables all the features of the ROM to keep working (WiFi, Bluetooth, sound, etc.) We will see what happens!

EDIT: The Bluetooth does work, but you need to adjust a setting. For working Bluetooth see post #3 "Bluetooth Workaround".
[T-Mobile Samsung Galaxy S 4] darazor:
As always your work is greatly appreciated and I will add enjoyed. I seem to enjoy the tweaking as much as the functionality. Thanks!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
All,

New update to the OP. New build is up! There is no difference in the ROM, however, there are some changes in the kernel. If you wish to upgrade without re-doing all of your setup/apps, etc, you can just flash this kernel zip here (also in OP):

If you want to just use this kernel, here is the link for a flashable boot image:

http://www.mediafire.com/download/mkiz1745si6bm4p/aklu-lionheart-kernel-jfltetmo.zip

(It has been modified to flash on any JF variant. Use with caution! -First boot WiFi does not work, but reboot and it will work just fine after that.)

The first boot the WiFi does not work, but after a reboot it works every time there after! To God be the glory, the new kernel builds are working great!

Changes to the kernel include 2 new governors:

LionHeart - Lionheart is a conservative-based governor which is based on samsung's update3 source.

SmartMax - By default this is configured for battery saving, so this is NOT a gaming or benchmark governor! Additionally, to make it "snappy", smartmax has "touch poke". So input events from the touchscreen will boost the cpu for a specific time to a specific frequency. Developed by XDA user [MENTION=4683552]maxwen[/MENTION].

You can still choose ondemand, powersave, performance, conservative, interactive, and userspace, but this allows you to choose two "battery friendlier" options. SmartMax will help your battery the most, and LionHeart is a bit more performance oriented, but still conservative. Enjoy!
[T-Mobile Samsung Galaxy S 4] darazor:
Thanks for additional features. FYI wipe cache/Dalvik after flash and wifi worked on first boot. Mileage may vary but worked on my device.
[T-Mobile Samsung Galaxy S 4] darazor:
I notice that you use the OH3 modem/baseband is there a reason that you did not update to OK3. Seems OH3 came out in Sep 2015 and OK3 Jan 2016. I know you said you like to wait a bit before various updates but I thought I'd ask if there was a technical reason. Thanks
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
It works better for me in Alaska, seems the other modems drop out of LTE a lot here.
[T-Mobile Samsung Galaxy S 4] cirrus97:
Latest update, I discovered that if I connect my bt headset and try to make a call the call doesn't go thru the headset, in addition, the call doesn't hang up. It just sits there saying its hanging up, the only way to get out of that is to reboot.

Second new item is the system will reboot if I stay in instagram too long.

I tried to flash the new kernel and it says the zip file is corrupt.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Cirrus97,

Thanks for the feedback, it helps because I do not have a Bluetooth headset.

Questions:

1. You said this is an update, is this update with the 0623 Lionheart version, or the previous one?

2. I have flashed the kernel zip before I uploaded to media fire, so I will download and test from media fire tomorrow to make sure it isn't messed up.

3. What phone model, bootloader, etc.

4. Can you pull a logcat during the failure? Thanks.

For your info, I always leave the link to the previous build live in the OP just in case people don't like the new changes.

I am currently on the latest Lionheart version myself, an have had no issues, but I only have a Bluetooth key finder for a Bluetooth test object, so it is great to have feedback! Anyone else noticing similar problems?

EDIT: The Bluetooth does work, but you need to adjust a setting. For working Bluetooth see post #3 "Bluetooth Workaround".
[T-Mobile Samsung Galaxy S 4] EMcTx:
Just installed the ROM, seems very responsive so far. Bluetooth seems to be working for me, but I'm only using this phone as WiFi only, hooked up to a speaker, so I can't speak to phone calls.

The only problem I'm having is that I can't get the clear all button to toggle in the recents menu. It just stays gray. I really like clearing everything at once.Is there a secret to getting it to toggle on?

Apart from that, things are working great. I'll let you know more feedback after I've used this ROM for a few days.

Thanks again.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
EMcTx,

Glad you like the ROM. You are right, I just tried and couldn't toggle that on either, so I will have to look at that. I use Slim Recent which has that built in:

Now, if you use Slim Recent, you can clear all by "pinching" the top to the bottom with your thumb and pointer finger. That will clear everything from the recents.

Another option is the kill all button by enabling the task manager in the notification drawer settings for the ROM settings.

I can't get a screenshot of slim recents for some reason it doesn't capture with it open.

Hope that helps and enjoy the ROM!