yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
That I know of, there are no hardware differences between jflteatt, jfltecan, and jfltetmo (I'm not an expert on this, so don't quote me); however, jflteatt has a locked bootloader and the other two don't, there are some firmware differences between at least jflteatt and jfltetmo, and jflteatt has an overlay built it that initially sets the APN to a certain AT&T APN.

Besides that, there currently is not a cm-12.0 branch on jfltecan, but the only differences between jflteatt and jfltetmo as it is are mostly device identifying strings, with the default APN and loki added on jflteatt. All GSM versions of jflte are using the same set of blobs.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
What do you have set as the APN? The APN I use is the "ATT Phone" APN, and I'm not having problems. MMS problems are often symptoms of APN problems in my experience thus far.

APN settings are in Settings->Wireless & Networks->More->Mobile Networks->Access Point Names, the bullet point on the right side marks the default one. If that doesn't work, you'll need to give me more information about your phone and how it is set up before I can do anything about it or give a better answer.

There are tests built into the flashing scripts that check to make sure your device/current ROM is jflte or jflteatt (for in-place upgrades).

The first suggestion I can offer is to wipe /system, since it will remove most traces of your previous ROM without affecting your data. If you still have that problem appearing, then your phone is identifying itself as jgedlte, and you're trying to use the wrong ROM (or you might have some recovery issues you need to fix first, but that is less likely, since your recovery obviously works). The full dirty flash is only supported if you are coming from a CM11 (jflte or jflteatt) or CM12 (jflteatt) install; you should be able to flash from your previous rom (if not CM11 or CM12 jflte/jflteatt) without doing a factory reset/wipe data, but I can't guarantee that it won't be needed.

The updater script checks to see that ro.product.device or ro.build.product are jflte or jflteatt, if neither of those properties is one of those values you will get the message "This package is for device: jflteatt,jflte; this device is ("ro.product.device")."
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Ya'll be careful regarding the alarm clock. My alarm failed to go off this morning.
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
I'll look at the APN settings and get back to you. I did notice that it works with the hangouts app but not the messenger app, if that helps at all.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
I have used 2 separate devices as alarm clocks ever since I stopped using a 'real' alarm clock that plugged into an outlet.

When your only alarm clock is run by a battery that barely lasts longer than 20 hours it's smart to have a little redundancy.
[AT&T Samsung Galaxy S 4 Original Android Developme] duckredbeard:
What nightly has been your best experience? And GApps also. I'm switching from a GPE ROM and have been impressed with the CM12 nightly on my Tab Pro 8.4. Eager to go with a CM12 on the GS4, so I'm looking for a "stable" nightly. GPS and Bluetooth are important.

I compel thee to opine.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I'm running the latest nightly, and the nano PA Gapps 2015-03-15 build. The androidfilehost link is still active. The latest nightly seems good. I haven't tested Bluetooth to see if it causes music to skip/get choppy. I know the 2015-03-14 cm12 nightly (I usually update weekly) had that issue.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
CM12 nightlys are stable and I don't have a problem with Bluetooth, GPS, or anything else for that matter. 3/17/15 was the last nightly I used because I went back to CM11 last week. CM12 is great, but CM11 is better for me at this point because it is so feature rich compared to CM12. I also had a couple of network drops on CM12, something I can live without... but may have been addressed in the latest nightlies. Can someone chime in on that?
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
For some reason I've always had problems with bluetooth with this rom. I always do a full wipe and install the newest nightly. I use bluetooth with my Honda and my beats headphones. Seems to have always been an issue for me. Any suggestions would be a huge help.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I don't know. I have a pair of bluetooth earphones from Newegg.com that just work. Music, calls, controls, it all works the way it is supposed to.

Also, I know this is counter to *flashing sense*, but I have NOT done a clean flash in ages. I don't even know how long. I flashed CM12 over CM11 and have updated using CyanDelta ever since. The only problem I have ever seen is an occasional network drop...

Most of the problems I read about seem to be after a clean flash... very strange.

Are you using this ROM with an ATT i337 phone?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I know the problem I have with Bluetooth is that about 10-15 seconds in to streaming music to my Jabra Freeway, or my mini jambox, the sound cuts out for a second, then comes back for a second, then cuts out again.

I'm running it on an att s4. I clean flashed only when I fresh installed cm12, coming from a GPE lollipop ROM. I did a full wipe. With successive nightlies, I've been dirty flashing.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Have you tried JetAudio?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
No. I've been using VLC. I'll give jetaudio and a few others a try.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] zxevik:
you sir are a god among men. this worked like a charm.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
I now keep a can in my desk at work and proactively blow out all the ports and earpiece every few months.

:good:
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Quick Bluetooth update, if I try to change songs while Bluetooth cuts in and out, regardless of media player (jetaudio, cm music player, vlc, it doesn't matter which), the app freezes (not FCs). Then I get "Unfortunately, Bluetooth Share has stopped". Afterwards, my phone disconnects and reconnects.

Looks like it's happening on different cm12 loads across multiple devices.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
What happens with CM11, does your Bluetooth work with it?
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Unfortunately for those of us that liked the PA GApps, TKruzze decided to take an extended, potentially unending break from providing GApps packages. They will be missed.
[AT&T Samsung Galaxy S 4 Original Android Developme] efasser:
I have no drops since last build of nighties, but my battery life is somewhere around or under awful. Hopefully new slim battery will help to solve the issue.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
12-20150325 -Nightly

As of the march 25th build,

the screen color problem is still there, where it sets the RGB values to 100% across the board on new installs.

To fix this, go into

Settings

Display&Lights

LiveDisplay

Color Calibration

and change the settings to something around 60%

50% leaves the screen too dark
[AT&T Samsung Galaxy S 4 Original Android Developme] Cusa:
Why haven't they fixed this yet? Do they not know about it?
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I did a clean install of 3/27 and everything was going well until I lost cell service again. I saw a couple commits r/t telephony and thought maybe it was fixed but not yet. When the service drops the preferred network is switching from LTE to 3G or back. Loving the ROM otherwise but I can't have that. Back to CM11, will keep watching for a fix.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Weird.. I'm not having cell issues. lte stays as my preferred network type, and lte works great.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
This Bluetooth Share thing is odd. My Jabra Freeway cuts out every second when playing music, then Bluetooth Share FCs. However, my Bluetooth mini pod speaker/speakerphone works fine..

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
i have problem with audio streaming on v2 BT devices, but v3 devices work good. i dont know if thats your case.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
That could be it, since the Freeway is v2.1. I wonder if the next nightly will help at all. Looking at the changelog (http://www.cmxlog.com/12/jflteatt/) it shows a bunch of bluetooth changes for the next nightly. Fingers crossed..
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
Yeaa i know, im waiting impatient for it!

Edit:

Still the same :(
[AT&T Samsung Galaxy S 4 Original Android Developme] Darmer Aldevaran:
Hi guys

Can I install this rom on my S4 i337m?

I'm noob with this phone
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
You sure can if you have a UCUAMDB or UCUAMDL bootloader and you've rooted your phone. If you have a different (updated) bootloader, you're out of luck. If your answer is "I don't know what that means" then you have some research and reading to do before visiting this thread again.

http://xdaforums.com/search.php?searchid=358021796

.
[AT&T Samsung Galaxy S 4 Original Android Developme] zirt57:
The MDB & MDL restrictions are for AT&T phones, not the Canadian I337M. We don't have safestrap. I'm on NK1 (Canadian I337M) and can use this rom.
[AT&T Samsung Galaxy S 4 Original Android Developme] ickensai:
I looked around to try to find any information on the CM ROM to see if this CM supports hmdi out and audio out when docked for the S4.

I am currently using my S4 as a mini smart player connected to my big screen. My s4 is currently connected to a samsung multimedia dock that has built in hdmi out and audio out.

when I had my S2, I lost these two functions when I moved over to CM ROM.
[AT&T Samsung Galaxy S 4 Original Android Developme] Armani G:
I have been installing clean nightly every week just to see what has been fixed. I am not using this phone as a daily I have a Nexus 6 for that but was thinking about giving this phone to my GF but the Camera seems to be freezing and then giving me a Camera error "can't connect to camera" especially with the Google Camera is everyone else having this issue? please let me know if I have done anything wrong and if their is a fix for this. Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] gho5t82:
Anyone else lose service all the time? Its getting pretty bad that i have to restart the phone in order to get cell service back
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
This rom is built for the AT&T Galaxy S4 (I337, not I337M). You will have to modify the install packages or have a modified recovery for this to work on an I337.

The reason there is not a version of CM 12 built for I337M is that there is no maintainer.

You can find other posts in this thread where modifying the install packages or getting a modified recovery are detailed.
[AT&T Samsung Galaxy S 4 Original Android Developme] s3nr1:
You can use Pacman nightly for the i377m it works really well, based on 5.0.2.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, I am dropping service about once a day... a reboot fixes it for another day. /but not good if you need your phone up at all times.
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
Likewise for me, I flash the current nightly every week or so but still lose service randomly. If it weren't for that I'd probably be on this ROM full time. I really like it but can't have the service drops.
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
I know it's a speed hit, but I dropped my preferred connection type from LTE to 3G and haven't had any more service loss issues. May work for you.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Perhaps it's been fixed. I've been on this ROM since my 4.4.4 GPS went out and can report that I have not dropped a signal since flashing the March 6th ROM a couple of days ago. Everything works now and seems to work very nicely. :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] mu3g:
Did you mean to say that you flashed the April 6th nightly of this ROM?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
wow... April already! Yes, April 6th. And I updated to the 8th yesterday. Still no signal drops. :D

Edit: Dropped signal over night again... :(
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
Signal Drops

I observe about 2 signal drops per week. It always happens when I turn my screen on and there is a nice empty triangle next to my wifi icon. Signal always comes back to normal within 10 or 15 seconds.

Is there a way I can monitor signal drops when the phone is in standby? I have a feeling it's happening a lot more often that just when I'm noticing it.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I hear ya. I would love to know when it goes out too since when mine goes it it doesn't come back until I do a soft reboot...
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
I flashed the new OC3 modem (baseband) this weekend. I'm hoping it helps. I'll post back in a few days with my observations.
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
There's a commit coming in the next nightly that I hope will fix the service drops. Not sure though, only guessing by it's description. Every time my signal drops I've noticed my preferred network type changes. I tried [MENTION=4293430]ninja_rancher[/MENTION] 's suggestion of changing preferred network to 3G and I don't think I've lost service since. The commit is a rewrite of preferred network type, no description beyond that. Fingers crossed... :cool:

Next nightly just went up, will see how it goes...
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I hope you're right about a fix soon. I always run 3G and I have drops every once in a while, but not every day at this point.
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I clean flashed 4/13 last night, no luck with network issues. LTE won't stick as preferred network, also had cell service drop 1st thing this morning.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Although I have had issues at my work location with bad lte reception.

I switched to LTE mode let it settle for a little bit and then rebooted the phone,

after the reboot the lte will stick...until another nightly is installed.

but if you don't reboot your phone after changing to LTE and you have any

type of issue on the phone, the next reboot will put you back to 3G.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
After a few days of being on the OC3 modem, I have observed only 1 signal drop. It was the day I flashed the modem. Since then I haven't seen any issues and my preferred network type has stayed as LTE.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
MMS problem

After installing the 4/16 nightly,

I can no longer receive or send pictures with the default mms apk.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
I guess it was a placebo effect. I had another drop today. As usual it was while I'm on WiFi and signal came back in 10 - 15 seconds.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
===================================================================

EDIT:::: I uninstalled ADBlock Plus...and after rebooting, my MMS is working Again

===================================================================

Catlog seems to be indicating that CM12 is returning that mmsc.mobile.att.net is an Unknown host????

22:11.059 I/Error (6019): 500 Server Error: Unknown host

04-19 12:22:11.059 I/ProxyService(6019): request done

04-19 12:22:11.059 E/Mms (6516): Url: http://mmsc.mobile.att.net

04-19 12:22:11.059 E/Mms (6516): HTTP error: Server Error

04-19 12:22:11.059 E/Mms (6516): java.io.IOException: HTTP error: Server Error

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296)

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:282)

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:183)

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:161)

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:115)

04-19 12:22:11.059 E/Mms (6516): at java.lang.Thread.run(Thread.java:818)

04-19 12:22:11.059 E/Mms (6516): Caused by: java.io.IOException: HTTP error: Server Error

04-19 12:22:11.059 E/Mms (6516): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:205)

04-19 12:22:11.059 E/Mms (6516): ... 4 more

04-19 12:22:11.059 E/Mms (6516): Delivery failed.

Full Catlog Here
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
Are the latest 12.1?
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Latest is 5.0.2
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
I haven't asked to get jflteatt pushed to 12.1 yet, although it could; I'm working through some issues on my device that suddenly appeared more recently, and also testing (trying to) a couple possible changes to see if they improve the service issues with LTE. I have been building 12.1 myself, and that is what I am running right now.

The issue some may have with what I'm testing is it could mean some problems for those flashing CM12 jflteatt onto jfltecan...
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I'm sure ready to give 12.1 a try...
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
Good luck with the service/LTE issues, it would be great if that got fixed. I just did a clean install of the jfltexx 12.1 nightly and it's excellent but I lost service several times in the 1st hour setting up & tweaking. Thanks for spending your time on this, we appreciate it. We're a quieter bunch here, more constructive & helpful, less whining & complaining. :laugh:
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Yeah, after some reading (mostly because of the problems I suddenly started having)...

I tried updating my non-hlos (apnhlos) partition wondering if it would help with some things, found (no surprise) that sound wasn't working, so I decided to try a build with the blobs from the OC3 release replacing those in the default repository. It compiled and booted, but I had Pandora FCs about every 3 seconds (Why Pandora? I only use you for about 2-3 hours on a random/rare basis...), sound still didn't work, and suddenly my phone was reporting an unknown IMEI. Bad me, I didn't have an EFS backup for this phone (not that it would have helped, since IMEI is stored in the modemst1/modemst2 partitions on the S4, as I later learned), so only solution I could see was re-installing stock MDL and re-rooting/etc. Come to find out in the end that it was a disagreement with something in the update or such, flashing an older update would have fixed it, but the problem still reappears suddenly now, after no issue for several hours... (I'll have to investigate this more over time.)

Anyway, I noticed what invisiblek had done with the jfltevzw blobs where he added a set of files to ensure sound would still work after updating non-hlos, and found that it worked and had a very quick connection to the network after changing the network mode to one that specifies LTE. I'm going to test that out a bit (and trying to make sure the IMEI issue isn't a software problem) before approving 12.1; if it works, it should make many people happy.

The reason that I would like to update the non-hlos is that it contains the firmware for the LTE radio (supposedly, I don't which file though, most appear to be security or sound related), while the baseband contains the firmware for the GSM and 3G technologies (at least that's my assumption, I'm probably wrong).
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
At least it sounds like you're having fun on the way (wishful thinking?)... anyway thanks for your diligence!
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
YES! THIS! It would be great to try something similar here!
[AT&T Samsung Galaxy S 4 Original Android Developme] bigal1542:
So are the LTE problems for all Lollipop Android? Limited to CM? Limited to the Galaxy S4? Limited to AT&T?

What problems with it are you guys seeing? Does it happen often?

Looking at trying out some new roms, but I'd like to see what's actually up with the LTE issue. Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
The problem is that when you enable LTE on the AT&T Galaxy S4 with CyanogenMod 12, the network connection drops out for a time and takes a long time to come back, and can be flaky, while if LTE is off, the cellular network connects to the network fairly easily and is pretty consistent.

I don't know if they are having similar problems with any of the other Galaxy S4 variants.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I've actually been having good luck with lte with the 0419 nightly with my i337. I don't usually keep lte enabled since where I live is kinda meh for lte. In in Lancaster, PA, for the weekend and lte/my signal has been rock solid so far.

I'm about due for an update (I usually update on weekends). We'll see how it works once I'm updated to the latest nightly..

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
CM12.1 nightlies are very close

http://review.cyanogenmod.org/#/c/96311/
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
This nightlies?? ;)

http://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-1-nightlies-qcom-t3088984

This thread is for CyanogenMod 12.1 builds for jfltexx
[AT&T Samsung Galaxy S 4 Original Android Developme] PhaedraCorruption:
FYI guys the GT-I9505 is EXACTLY the same as the SGH-I337

I have been running the GT-I9505 CM12.1 ROM on my SGH-I337 for awhile now and it's very stable.

I've heard of some people running into LTE problems with CM12.1 but for me, flashing the modem file(attached here) from I337MVLUGOC4 fixes that.

Mind you, the GT-I9500 is based off a completely different chip from the GT-I9505, so don't try flashing GT-I9500 ROMs
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
So, you are running the SGH-I337m Modem on your SGH-I337 without any problems with AT&T LTE in The USA?
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
12.1 was approved for jflteatt, jfltetmo, and jfltespr today. You should see nightlies starting tonight.
[AT&T Samsung Galaxy S 4 Original Android Developme] PhaedraCorruption:
Nope, sorry I should have stated I'm with Bell in Canada.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
I would not recommend anyone with SGH-I337 jflteatt use the Canadian modem. Stick with modems designed for your variant of the GS4.

---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------

Great to hear. I'm looking forward to getting a fresh start on 12.1 with a clean wipe. I'm hoping to download and update some time this weekend if I can squeeze it in.

Are you going to start a new thread or re-purpose this one?
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Going to stick with this thread.