yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] wmromne:
AlaskaLinuxUser, Thank you so much for your work on the S4 T-Mobile ROM. I clean flashed the RR-N-v5.8.0-20170114-jfltexx-Unofficial ROM and GAPPS-Mini-7.1 on a s4 jfltetmo phone. This is a really nice ROM! I like the styling, features and performance. Cell reception, WiFi and Bluetooth all work great. Other than the video issue already identified, I am have two issues with the new ROM. First, the find time zone automatically is not working. If I select the time zone manually, it works. Second, I am having issues with the proximity sensor on calls. Previously, I had this issue with the RR Marshmallow ROM, and I had understood it was an issue with the CM13 build. Now, I am having the same problem with this new ROM. When I am in a call, the proximity sensor blacks the screen when the phone is near my head. When I lower the phone, the screen stays black, and I cannot access the touch screen. I did enable the power button to end the call, which is my work around. I am now wondering if I have a hardware problem. In any case, I look forward to your future builds. Thank you, again, for your commitment and dedication to this project.

Just a quick follow-up to my previous post. Apparently, the issue with the proximity sensor was a hardware issue. I had read some of the fixes regarding blowing air into the speaker grill, and I was a skeptic. I also thought it might damage my speaker, but I decided to try it. To my surprise, it fixed the problem. I used a low setting on my air compressor to gently blow a little air in the speaker grill for just a few seconds. Now, the proximity sensor is working correctly.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Wmromne,

Thanks for the kind words! This is my way of having fun, seeing things take shape and form, all the while learning new things and helping get more life and use out of older equipment (the s4 really isn't that old is it, though?).

I'm glad that you got your proximity sensor working, I have heard quite a few people with that same issue and correlating fix. It does seam rather odd, but by general consensus seams to be the best fix.

Thanks for the heads up about the time zones, I will take a look and see if I can track that down. Must have got lost in the switch from cm to lineageOS? Does anyone know if it worked on the previous version of this ROM? Thanks.
[T-Mobile Samsung Galaxy S 4] invisiblewave:
You can also just rename (or delete) that file if you want to stop the sound altogether, there's no need to replace it. First thing I do after updating, although I should point out I've only done it on TW roms.

This rom is excellent! My dd is a GS5, but I thought I'd give N a go on my old GS4. I only installed it a couple of hours ago, but I've yet to find any problems (haven't put a SIM card in yet!), and it's snappy as hell, at least as responsive as the GS5 running TW, and Google Assistant works perfectly! Nice work!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Praise God! Video Camera fixed, new release in the OP!

The OP has been updated with the latest and greatest video camera fix added in, thanks to [MENTION=5968293]side[/MENTION]! (Be sure to slap his thanks button!)

Multiple tests and it worked really well. I did have one time that it force closed the app, not while recording, but while switching between camera and video. Simply reopened the app and all was well!

Enjoy!
[T-Mobile Samsung Galaxy S 4] lngtrvl:
Nice ROM Alaskalinuuser thanks very much. I have only one problem, after flashing the 1/14 build I get WiFi errors try to use the hotspot. It worked fine on the original build.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Sorry to hear that. Tell you what, would you mind downloading the 1/23 build, as that is the latest version? I will try to test it tomorrow as well. Thanks!
[T-Mobile Samsung Galaxy S 4] lngtrvl:
I gave the 1/23 build a try with no luck, also tried the AOKP 1/15 build with the same results. I went back to the 12/15 build and everything is working fine again. I will keep looking into it.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Again, sorry to hear that you are having issues with it.

I just tried the WiFi hotspot from my JFLTETMO with OK3 modem and was able to successfully use the hotspot in secure WPA mode and in non secure mode. It hooked up on the first try and allowed me to browse the web from my Note Edge through the hotspot using the LTE signal on the S4.

I know that there have been issues in the past where it would not work if you had the WiFi on when you rebooted the phone (some persistent thing) perhaps you could turn your WiFi off, reboot the phone, then turn on the hotspot?

Did you do a dirty flash? Are you using a TMO or an XX phone? Which modem do you have installed? Did you install anything like xposed, systemless root, etc, etc,? (E.G., have you tried this with just the rom installed, before putting all of your programs in?) Remember, there is no such thing as random, only a pattern that we have not figured out yet.... :D

Hopefully we can get that figured out. It is hard to say though, it worked twice this morning here on my first attempt. Other users in the AOKP forum have mentioned problems with connecting before though, so it could be some issue with settings.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
That is good troubleshooting.

There-in lies the problem. I took a look at the AKLU kernel and I now know why. I will *hopefully* roll out some new kernel builds shortly....
[T-Mobile Samsung Galaxy S 4] Unidave199:
SU or no SU?

What a great and very elegant built! I thought I would have to get a Pixel to get Googly Assistant Love but now it is right here! Thank you so much!!!

I possible N00B Question:

Shouldn't SU be flashed in the initial install? I see the Kernel has ROOT access built in, but every other ROM required a SU flash. So, when I have tried the install and downloaded SU from the playstore, the binaries install but then I go into a bootloop when I reboot.

Is SU obsolete?

Dave
[T-Mobile Samsung Galaxy S 4] stanwebber:
I actually want some form of feedback when plugging/unplugging my charging cable as i turn off the battery notification light so this is the closest i can get to that in this rom.

one other thing to report: by accident i discovered the 'ok google' detection works on all screens when enabling the google assistant on this rom. i had this feature turned this off because i kept getting the 'retrain voice model' dialog on activation when i previously ran the AOKP nougat rom. i researched online and assumed this bug afflicted all non-pixel hardware so i gave up on it when switching over to this rom. i don't know if it works out of the box or a subsequent update to google play services makes it work, but i have full activation operation now without the retrain dialog, even on my lockscreen.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Dave,

Great question.

SU is certainly not obsolete! :D You just don't need it on this ROM, as you already have root permission built in and a control method for it.

Thanks for sharing, that is good to know! I am glad that you can now control that sound.
[T-Mobile Samsung Galaxy S 4] lngtrvl:
Life is good,

I tried the new kernel and the hot spot is hot. Thanks much Alaskalinuxuser.
[T-Mobile Samsung Galaxy S 4] kingwroth:
Hi I just have a small question: what does jfltetmo mean? I have the t-mobile variant (sgh m919), so it that just the same thing as jfltetmo? Also I have TWRP, but I have no idea where I got it from, but it does work. Not sure if it's related but just letting you know. I see most recent roms are for jfltetmo, so I would just like to be clarified on what it means. Thanks.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
No problem kingwroth, we were all new at this once!

Yes jfltetmo=sgh-m919.

It is important that your twrp is the correct twrp, though. Most likely it is, but you will know if you try to flash this ROM. If it flashes, you have the right twrp, if it does not flash, post the output that it tells you here, so someone can help you. :D

By the way, when you flash this, there is a small error that shows up about "log", that is okay.
[T-Mobile Samsung Galaxy S 4] Jason Maze:
Hotspot issue..

This rom is really good. Everything is working other than hotspot won't turn on, just gives an error message. Hotspot was working good on RR marshmallow. Any help would be great. TY
[T-Mobile Samsung Galaxy S 4] kingwroth:
Hi, thanks for the quick reply, but I also have another question. Am I able to ADB sideload this ROM? I don't have a microSD card right now, so I'm wondering if I can sideload the rom.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question, yes, you should be able to:

http://hackerspace.kinja.com/how-to-install-a-rom-via-sideload-1505153925
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the kind words.

One item to note, there were problems as mentioned in the previous posts about hotspots. These were resolved.

Please read through them and then download the latest version of the ROM and if desired, the latest version of the aklu kernel.
[T-Mobile Samsung Galaxy S 4] Yooshaw:
ALU -

I made the switch from your RR 6.0.1 build and am really liking it so far. Thanks for your hard work on this, I really appreciate it!

Also wanted to echo that I have the same time zone bug. At first it was correct, then jumped to UTC time. After a re-boot, the time zone will fix itself, only to revert back to UTC time a little later. Manually setting the time zone corrects it.
[T-Mobile Samsung Galaxy S 4] jets76:
Very excited to see this ROM. I need to know, the stock 4.4.2 has been rooted. Installed the latest TWRP. Can I just go ahead and flash this ROM after wiping? Is there any modem I need to upgrade? If so would you mind helping me out? I am trying to get over to my pals place to set this up for him tomorrow.

Thanks
[T-Mobile Samsung Galaxy S 4] red_five_1976:
I installed this on Tuesday, and it's great! It's smooth, stable, and bloody fast! I had been running RR 6.0.1 previously (the earlier one, not the one that AlaskaLinuxUser released after the original maintainer dropped it); it had never been screamingly fast, but lately it had been getting even slower. This ROM, though, is like a new phone. Nicely done, ALU!

I too have the timezone bug. I remember one of the 5.x ROMs I ran a while back had the same problem. The maintainer eventually fixed it, though. Hotspot is working fine, thankfully. I don't use it much, but I do on occasion.

I tried the AKLU kernel, but it went into a boot loop. However, I had installed it immediately after installing the ROM without booting it and letting the ROM finish setting up, so that might have had something to do with it.

Now to find a car charger that doesn't produce so much noise that it interferes with GPS lock.
[T-Mobile Samsung Galaxy S 4] mouassa bro:
Thank you so much bro
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
You are welcome, but a lot of the credit goes to the RR team, thanks for the kind words, though!

Thanks for the kind words! I have tested the kernel here, and it should work for you too. Be sure to make a backup first, and then give it another try.

Did you get this figured out? Let us know if you need some help! :D

Thanks for the kind words! Yes, I need to look at the time zone bug. It seems like it is working until either changing between cellular and WiFi, or between 3/4/LTE. As if it knew what it was, and doesn't check again, even though it forgot it already. A work in progress....
[T-Mobile Samsung Galaxy S 4] jets76:
Yes I flashed it straight up no problems works mint! :laugh::laugh::laugh:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great! Glad to hear it!
[T-Mobile Samsung Galaxy S 4] David X:
Hi, I really love this ROM but have only one problem. When I use Fongo to call, the recipient can not hear me, while I can hear them. Can anyone who is using Fongo please confirm if you have the similar problem? Thank you for your time in advance.
[T-Mobile Samsung Galaxy S 4] Guss35:
Hi guys, awesome ROM so far but I have an issue. My phone will not connect to 3g or 4g after installing the ROM, it will only connect to 2g. I don't know if maybe radio bands are changed in this ROM or not? Btw if it matters I'm on the Venezuelan cellphone company Movistar which uses 1900MHz(3g) and 1700/2100MHz(4g). Any recommendations to fix the problem?
[T-Mobile Samsung Galaxy S 4] Praetore:
Testing this out as my daily driver and it seems to be working fine! I haven't been able to update SuperSU, but I haven't run into any issues with root permissions so I think it's ok.

Also, since I have T-Mobile, is it normal to have it say 'Calling via T-Mobile' every time I make a call? I haven't noticed any changes but this is normal, right?
[T-Mobile Samsung Galaxy S 4] Yooshaw:
I'm having a similar problem using a messaging/VOIP/Video Call app (Kakao Talk). In my case, I can't hear, nor can the other party hear me when doing a VOIP call.

I got it to work by going to the Apps settings, click on settings, then on the "Assist & voice input," then changing the "Assist App" to None.

However, that seemed to fix VOIP calls, but Video calls have the same problem (neither party able to hear the other, but you can see the other).
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for posting! This may be a permission or firewall issue. Is this over cell data or on WiFi or both?

Thanks for the kind words! I will have to check on this. Which baseband are you using?

I use straight talk so I am not sure. Yes Nougat is still new, so there are a couple oddities about SuperSU, but the built in root permission works great. Great question though!

I noticed a lot of VoIP related issues for nougat in a Google search. Could I get a log from you after a silent phone call? Thanks! I can't fix it if I don't know what's broken. ;)

Thanks for posting everyone!
[T-Mobile Samsung Galaxy S 4] Guss35:
The baseband version is: M919UVUAMDL. I also attached a pic with the phone info. Thanks in advance
[T-Mobile Samsung Galaxy S 4] Yooshaw:
Can you help me on how to capture a log for you? Sorry, this is the first time I've flashed, so still a little new. Loving it though, thanks again!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Guss35,

Hmm, that should work, but that is an older modem and boot loader. You could do one of these two things:

#1. The quick way. Head to this thread and update your modem:

https://xdaforums.com/galaxy-s4-tmobile/general/foh3-modem-bin-mdl-bootloader-t3191094

#2. Upgrade your phone to a newer firmware, then reflash twrp and ROM.

Let us know if you need help with that.
[T-Mobile Samsung Galaxy S 4] Guss35:
From the link you gave me, should I flash the MDL or the non-MDL modem? Also, are there any benefits to upgrading to the newest firmware over updating the modem?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question.

You would need the modem, not the non-hlos file if you went this route.

The plus side to upgrading, in your specific case is the LTE signal. If you do the above without flashing all new firmware, your LTE may not work. If you upgrade all together, your LTE and modem and boot loader will all be the same, and should work better.

So in your case, I suggest upgrading completely first. However, flashing the modem zip from that thread only takes 2 minutes, so that is a quick option, to which you will have immediate results. But it is up to you.

Hope that helps!
[T-Mobile Samsung Galaxy S 4] David X:
Thank you for your reply. Can you please let me know where I can find Apps settings? Is it in the Fongo that I use, Kakao in your case? As I couldn't find "Assist & voice input" in neither Fongo nor android Setting.
[T-Mobile Samsung Galaxy S 4] mike85388:
Hi,

This is my first post on XDA, so I want to begin it all by thanking you, AKLU, and those who work with you for all the work you're doing here. I inherited an M919 that I've already flashed a couple ROMs on, and I've been flashing an S3 and two tablets as well. Good fun!

I just had a few high level questions that I'm slightly confused about. Sorry if I seem overly noobish.

1) I've seen mentions of RR Nougot being based in part on CM14 (now LOS) builds. However, a quick look at the LOS website doesn't show the jfltetmo. Even looking at the Cyanogenmod download list as it stood on Christmas only had CM13 builds for this device. So I'm wondering where LOS/CM 14 builds are coming from.

2) Are you aware of any plans to have jfltetmo be part of the official LOS lineup? I kind of ask that because once a device is officially supported, OTA updates are easy to do, as opposed to going out and manually downloading new ROMS..

3) I take it that firmware is completely different from the ROM. I've only been flashing ROMs, so I assume that my baseband is the same as it was when the phone was running stock. Do you recommend updating the firmware as a matter of normal process or only do it if there is a problem? I suppose the same question could apply to the kernel.

Again, I appreciate all your efforts that let us breathe new life into these (semi) old phones, and sorry again if these questions seem rather dumb.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hi Mike!

Thanks for the kind words.

There are dumb questions, but I find that they are few and far between when the person asking them is sincere.

So, in order:

#1. Cm is no more, so it will not have up to date official builds. Being based on cm/LoS simply means that the source code the RR team used is modified from that, rather than starting from scratch with AOSP, like SlimRoms, PA, or OmniRom do. Any LoS/CM builds for the S4 are being built by people (or teams of people) like me. So they are all unofficial builds.

#2. The only way that JFLTETMO can become official is a two part process. The first is a developer signs up to maintain that phone. This person has to meet several requirements, depending on the ROM. If the developer newts those requirements, then the ROM maintainers needed to accept that developer. Essentially, they want to make sure that the device is maintained so it will build every time from source, before making it official. As far as I know, either there is no qualified developer, or none have stepped forward to fill that job for our JFLTETMO.

#3a. To upgrade or not? Well, the easy answer? Is everything working that is supposed to work? Is your LTE reliable and fast? Of these are answered yes, then you could just keep using what you have. Is either of those questions are answered no, then I recommend that you upgrade your firmware. The biggest change is in the modem, and sometimes the newest modern will not work much (if at all) better in your area, depending on your local infrastructure.

#3b. Kernel: this is a matter of preference. My AKLU kernels tend to focus on better battery life, with very slight over clocking. There are not to many kernels to choose from for this phone now, so, you can use the "stock" cm kernel that I typically build the ROM with, or another kernel for additional features. If in doubt, or unsure what that does, I recommend that you stick with the stock cm one. It works good, but has no extra option.

I hope that helps! Let us know I'd you have more questions, they are always welcome here.
[T-Mobile Samsung Galaxy S 4] mike85388:
Excellent! That clears things up a lot!
[T-Mobile Samsung Galaxy S 4] darazor:
mike

Did you happen to see this thread from side?

https://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-lineageos-nightly-builds-t3530822

-D
[T-Mobile Samsung Galaxy S 4] mike85388:
Actually I hadn't, since I don't have that device. It was a very interesting read, and despite a few catty remarks here and there, was very enlightening. BTW, I had to remove the URL from your quote while posting this. As a new user, I can't post any replies that have links in them.

Thanks for the tip!
[T-Mobile Samsung Galaxy S 4] darazor:
mike

You said you have a S4 M919.

AKLU Rom on this thread will work on your device. If you look at post # 2 there are 8 screen shots the 5th one shows the device as GT-I9505 but is usable on a SGH-M919

The link that I showed you is also usable on a GT-I9505 and should be usable on your device.

Perhaps ALU can confirm this.

-D
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great point D, yes and no.

However, unless you edit the zip file, or install the jfltexx twrp, that ROM will not flash to our jfltetmo.

I borrowed a lot of work from the jfltexx devices to make these ROMs, but made a few edits so that they would flash on our phones.

But, if you edit the meta-inf folder of the zip, or flash jfltexx twrp, then yes, they will work on our phones.
[T-Mobile Samsung Galaxy S 4] borage12:
one small question

can i use this

￼RR-N-v5.8.1-20170210-jfltexx-Official.zip

have 5.8.0-20170114-jfltexx-unofficial
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Borage12,

You are welcome to try anything you want.

However, that ROM is only for the jfltexx. If you are using it on a JFLTETMO, then it will not flash unless you edit the zip or install the jfltexx twrp.

Hope that helps.
[T-Mobile Samsung Galaxy S 4] borage12:
seams to work lineage_jfltexx-userdebug 7.1.1 ...

But after 3 hrs of doing nothing , the battery is down to 70% , so going back to

5.8.0-20170123-jfltexx
[T-Mobile Samsung Galaxy S 4] Inferno9999:
Hi Alaska I recently installed the Nougat rom and I was enjoying it until I got into one of my favorite games (War Robots). At first I thought it could have been a heat issue, but I didn't feel the screen getting nearly as hot as I was used to on stock kitkat. I downloaded CPUtemp from the playstore and temps started off slow from around mid 40s to going no higher than mid 50s (Celsius). I then went even further into my investigation and downloaded Simple System Monitor. I enabled the GPU overlay to see my core clock and usage/load. When I got into the game I noticed my GPU clock was bouncing around 128mhz! That explains why I felt that the gaming performance was lacking. I am not sure what the problem could be since the temperature I was getting isn't bad at all for a snapdragon 600. Any suggestions?

---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------

I've taken an in game screenshot with the program overlays to better see what's happening. It might be a little difficult to make out, but the CPUtemp overlay is in the middle towards the top.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Inferno9999,

I'm glad that you are enjoying the ROM, but am sorry to hear that you are having trouble.

A couple of thoughts:

Which kernel are you using for that? The built in one or the AKLU kernel from the kernel thread?

Also, for the GPU, in kernel adiutor, which setting do you have the GPU set to for governor and max frequencies? Have you tried other choices for governor? For instance, to play your game, you may want to use performance governor to get the most power. It looks like you are set to ondemand from the constant up and down ramping.

If I recall, for that kernel there are only 3 working options for the GPUs governor. Power save, performance, and on demand. For heavy gaming I recommend the performance governor.

I also see the up and down of your CPU frequencies. During game play, you want a smooth chart. Which CPU governor are you using? Conservative or Lionheart may help with that. Performance governor would be the best, but the phone may get hot with that setting.

Generally speaking, my kernels are, by design, more battery friendly, and a bit less performance oriented.

I hope that helps.
[T-Mobile Samsung Galaxy S 4] Yooshaw:
I'm having a strange problem. I have two M919 S4s that I've flashed to this ROM with TWRP. My wife's phone is loosing mobile data connection. Seems to happen after returning to the house, and after the phone has connected to home WiFi.

There is no data connection, and when I go to APNs, the list is completely gone. I tried to manually save a new one, hit save, but it doesn't appear. Re-booting brings the APNs back and mobile data.

My phone is not exhibiting this behavior at all. Any ideas?