yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Well, it probably goes without saying, but....

Google services for 5.0 is not compatible with 5.1,

You will need to start with a clean install to run 5.1 without many issues.

FYI

Do you know if there will be a change log put up for the 12.1 nightlies for jflteatt

or should we watch a different change log now?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
12.1 running great with a clean install. I don't seem to be having any problems with it at all! Very nice job FarmBoy!
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Well, all you should need for the clean install is to format /system before installing, particularly if you are using the PA GApps; That is all I needed to do, and a primary goal with 12.1 was to make it a drop-in replacement, with no need to wipe data when updating to it. If you are using the PA GApps 5.1 package, even formatting /system shouldn't be necessary, unless you are switching to a smaller version of the package - as long as you install 12.1 and then install GApps, all 5.0 existing GApps should be removed/replaced.

12.1 will not replace 12.0 in change logs, since it is a new branch - you will probably need to select 12.1, as soon as the option is available.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
The log for 12.0 only returns this:

err01: Device incorrect or not supported. Device may have been transitioned to CM12.1 nightlies.

and the nightlies automatically transitioned to 12.1 on my device.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
http://www.cmxlog.com/12.1/jflteatt/
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Changelog: http://www.cmxlog.com/12.1/jflteatt/

They removed the /12/jflteatt page, in case anyone goes looking..

Neeeeeeever mind.. My tapatalk didn't update until after I posted. Then I saw all of the replies. Oye.. (^.^)
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Updates not found

The CM updater on the phone, no longer finds updates

after the first 12.1 was found and updated to.

At this time the updates must be downloaded from the website
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
I've noticed since updating to 12.1 that I can't set up face lock anymore. I've confirmed I'm running the 5.1 version of TrustedFace, and have cleared its data, but it always crashes. Here is the crash report:

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/FaceLock/FaceLock.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]] couldn't find "libfacelock_jni.so"
at java.lang.Runtime.loadLibrary(Runtime.java:366)
at java.lang.System.loadLibrary(System.java:988)
at com.android.facelock.FaceLockUtil.<clinit>(FaceLockUtil.java:338)
at com.android.facelock.SetupFaceLock$SetupFaceLockFragment.onCreateView(SetupFaceLock.java:302)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.Activity.performStart(Activity.java:6005)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2319)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2418)
at android.app.ActivityThread.access$900(ActivityThread.java:154)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1321)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5293)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)

Looks like a simple matter of a missing .so file, but I may be oversimplifying it. I installed the 12.1 GApps referenced in the Cyanogenmod Wiki: http://wiki.cyanogenmod.org/w/Google_Apps
[AT&T Samsung Galaxy S 4 Original Android Developme] 78Staff:
Anyone still having cell cut out issues - seems like it's happening more and more for me. Currently on 4/26 and OC3 modem...getting ready to update to latest nightly, but if the cell issues continue I'll probably have to go back to CM11...
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
This is actually an issue with that GApps package. It apparently is either missing that library or is not installing it to the right place (should be in /system/lib). The PA GApps listed in the OP do contain the correct libraries (I checked that the zip contains it and that it is present on my device), but I can't guarantee that it will work because I don't use it. There is no "libfacelock_jni.so" in the standard build of CM 12.1, anywhere.
[AT&T Samsung Galaxy S 4 Original Android Developme] aguacateojos:
After updating to 12.1 I've experienced frequent shut downs. Pick up phone, start opening an app, BAM. Often this will even mean I can't boot my phone for twenty or thirty minutes... now, is this a sign of my device showing two years of age or a problem with the rom?
[AT&T Samsung Galaxy S 4 Original Android Developme] rogersa2k:
I did a clean install of CM 12.1 today and also flashed the OC3 modem. I noticed the cell cutouts like once an hour but thought maybe it was just me.

- Aaron
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
hmm, my phone seemed to cut out twice during a conversation with my daughter, It took about 30 seconds to get the voice back.

thats with the 05/02 build
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Well, that is definitely not normal, and not something that I am experiencing (nor others apparently, otherwise it would be all over this forum). I would double check the installed zips, make sure that you are using the GApps for the version you are installing (5.1, in this case), and probably do a reinstall with a /system format in the process (wipe out any artifacts that may be hanging around, causing problems). I'm assuming you are just using CM 12.1 with GApps, not flashing anything else.
[AT&T Samsung Galaxy S 4 Original Android Developme] 78Staff:
Mine is hanging up... I'll be talking, I'll hear a short ssshhhhh sound, then it hangs up on whoever I'm talking to. :(. Same occurs with 5.2 build and OC3 as well, which was a clean install, formated data, full wipe, etc. :(
[AT&T Samsung Galaxy S 4 Original Android Developme] bigal1542:
I'm still getting the signal drops too and I've tried every single modem in the modem thread for at least a day with the same issues of signal constantly dropping.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I must be lucky. I have been updating daily and have not had any signal drops in about 5 or 6 days. I have not changed from the Nl1 modem.
[AT&T Samsung Galaxy S 4 Original Android Developme] thesummoner101:
I'm on NJ4 with 4/29 nightly and no issues at all. I didn't have LTE right after installing, but was able to easily connect it and haven't had it drop since. No random reboots, Bluetooth works fine with my shower tunes, am able to make and receive calls.

I noticed lag when it activates the "Live Display" feature. It overlays a warmer tone film for easy night time reading. Reminds me of CM7 days, only now I have a faster device but slower interface... Lol
[AT&T Samsung Galaxy S 4 Original Android Developme] 78Staff:
Yeah same for me either model. I don't have time to **** around with it anymore, so back to CM11 for me for now...
[AT&T Samsung Galaxy S 4 Original Android Developme] ms.journie:
I remember reading somewhere unsure if it was in this post or not but does xposed work with this Rom?

Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] efasser:
Anyone else getting an System crash after updating to 05/13 nightly?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, I had to revert to yesterday's build. 5 / 13 would not run today.

LATER: The latest build, 5/14 is fixed and running like a champ... very nicely indeed!!!
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Checking

Are the builds after the 13th working properly now?

Anyone tried?

Edit: Thanks Op3nsrc -- Indeed I was blinded by relying on XDA to alert me for new posts,

so I failed to notice that 1weener had updated his post. DOH
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
[MENTION=4601021]1weener[/MENTION] updated his post about the 5/13 build. He said he went to the 5/14 build, and it's smooth. I updated last night and I agree. It's running great so far!
[AT&T Samsung Galaxy S 4 Original Android Developme] jpcdeux:
Anyone have a link to last cm12? I want 501 to use xposed...
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
4/26 nightly (last cm 12 / 5.0): http://get.cm/get/oHm

The cm 12 builds are all still accessible on the download page, too: https://download.cyanogenmod.org/?device=jflteatt

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] jpcdeux:
If you want a 404 error or a redirect to cm beta downloader yeah
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Crap. I must have d/led it right before they nixed it. I can upload it once I get to work. I have the 0426 nightly on my work computer.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] jpcdeux:
Thanks!!
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Cm12 - 20150426 nightly:

https://www.dropbox.com/s/jaraawsmw5a2oif/cm-12-20150426-NIGHTLY-jflteatt.zip

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] jpcdeux:
Thanks so much! Can't get my phone to take any LP Roms for some reason but I'll figure it out
[AT&T Samsung Galaxy S 4 Original Android Developme] wintermute66:
Does this rom have the option to unlink the ringer and notification volumes? I can't stand having them linked... Thx.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Yes. One setting I really like.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
Fingers crossed for this

I hope this fixes the weird issue of preferred network type not sticking to LTE.

http://review.cyanogenmod.org/#/c/98728/

Edit: I found this one too. If this does what it says, I'll be so happy because my SD card was always the home of my Ringtones and Notifications folders before Android 5.0.

http://review.cyanogenmod.org/#/c/98688/
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
The last nightly was the 18th.. This next one is looking to be a doozy, seeing the long list of "in the next nightly"!

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Imixsan:
Noup...the annoying lost of service is still there. If you change the network to 3G it seems to stick, the minute you go to LTE it starts dropping signal.

This looks like a pretty serious bug, how come that the guys at Cyanogen are not paying attention to it????

Regards.
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
The change hasn't been merged yet..... Have you tried it in your own build?
[AT&T Samsung Galaxy S 4 Original Android Developme] Imixsan:
No my friend, i'm a user not a builder...got no clue on how to do it.

I have also found another issue with this nightly. When using skype for video calling (dialing out only) the camera freezes after the first ring and few seconds after that the call window closes.

When I'm in a video call started by a third party there are no problems using the camera.

Any ideas?

Regards.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Nice Build

I'm just reporting that the 5/24 build is rock solid on my i337. Cell, Bluetooth, and GPS all working perfectly so far. :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Has anyone else had the camera blow up on them when they try taking a picture with the forward facing camera? Every time i try taking a picture while holding one of my kids, the camera app freezes, and then it can't find the hardware until I reboot the phone. Weird issue.. Stock ROMs don't have that issue, so I know it's not my phone.

--

Also, is there a way to enable CM Home on the trebuchet launcher? I try swiping to the left, but it bounces back. I've read, though, that there should be a Google Now alternative.
[AT&T Samsung Galaxy S 4 Original Android Developme] mzahs:
+1
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Camera

I switched to OpenCamera a while back,

the stock Camera froze constantly under many circumstances,

both front and back.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I've been using Google Camera, and the front camera freezes 90% of the time. I'll have to give Open Camera a try.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Starting with the 20150529 build there should be (not merged yet) a couple changes that solve most of the LTE and data connection issues on AT&T. There is an extra step you should take if you upgraded from CM 11 without wiping data or otherwise have restored APN data/settings from CM 11: using a root explorer or terminal, delete all "preferred-apn*.xml" files in "/data/data/com.android.providers.telephony/shared_prefs/" and reboot, or wipe data and make sure you don't restore APN data/settings later.

This fixes an issue where your phone is trying to use an (almost) random APN as default, rather than the one chosen as default, which is especially a problem when that APN doesn't support LTE or 4G connection (which also explains the timeout-like waits before data connections would come up - timeout on one APN before trying a "non-default" one).

Thanks to [MENTION=2044079]Nardholio[/MENTION] for finding and fixing this issue on the Galaxy S3 and then providing patches for the Galaxy S4 repos, and to [MENTION=629930]snakecharmer23[/MENTION] for seeing one of them and posting it here where it caught my attention.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Also, just noticed this today: [MENTION=2777334]TKruzze[/MENTION] and [MENTION=4544860]osm0sis[/MENTION] have started an official continuation of the PA GApps (now TK GApps) here.
[AT&T Samsung Galaxy S 4 Original Android Developme] Imixsan:
Hi,

I have been facing the following bugs:

1) Camera is unstable

2) Skype gets stuck after first ring when calling out on voice or video calls. When receiving the call it works fine. Tried re installing, tried older Skype version at no avail.

4) Viper4android needs a workaround for it to work. Need SElinux set to permissive and busybox installed.

5) Pattern block freaks out from time to time and shows several consecutive times immediately after unlocking.

6) keyboard shows up but does not write

Has anyone experienced these?

I'm always in the last nightly.

Regards
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
05/29 build

Well now,

that is quite a change in the app drawer......

They forced the vertical mode in trebuchet

it can be changed back to the normal horizontal view in trebuchet settings
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
Solid LTE signal now & no service drops. Many thanks to all responsible!
[AT&T Samsung Galaxy S 4 Original Android Developme] twangansta:
For #4, setting the SELinux to permissive is the only workaround I've found that worked. I'm guessing here but it's probably the way Lollipop handles things, and not sure if Viper4Android can be updated to fix this (it also hasn't been updated in a while to my knowledge).

All in all, a minor inconvenience.
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
I hadn't actually had any signal drops or LTE connection problems in a while, but I went ahead and followed the instructions here anyways. What I HAVE noticed for a while, though, is that when the phone first boots up, it says "No SIM card--Emergency Calls Only" for upwards of a minute before it changes to "AT&T--No service", and then a few seconds before it finally becomes just "AT&T". I thought this sounded like the APN timeout issue you were describing, but after deleting all of the files you mentioned and rebooting, it still behaves this way. Any ideas? Or anything I can try and capture to help? Thanks.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
That happens to be a different problem. One of the commits made (I think on May 31st) affected the phone service and how/when it comes up. Prior to that, the phone service would be successfully loaded before the UI was, and you would see regular phone service when the UI loaded. This problem that you're seeing is because the phone service still hasn't loaded, and then when it does finally load, it takes a few seconds to connect. Prior to the May 31st (or later) commits, you don't see this problem.
[AT&T Samsung Galaxy S 4 Original Android Developme] Rockman195:
Just a quick question, I'm coming from cm12 (android 5.0.2) and I'm wondering if this rom should be clean flashed or not. Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
A dirty flash is generally fine and recommended most of the time. If you have problems, try a clean flash before reporting them. As always, do a backup and you can just revert to that if there are any big problems.

Either way, you'll probably have to update your gapps when switching android versions.

Good luck.
[AT&T Samsung Galaxy S 4 Original Android Developme] Rockman195:
Ok thanks. It looks to me like gapps are the same for 5.0 and 5.1 or am I wrong?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, they're the same.
[AT&T Samsung Galaxy S 4 Original Android Developme] chrisc93:
Is anyone having trouble receiving sms with LTE enabled?

It seems that I can send texts fine, but I can't receive them on LTE. But once I switch to 3G all is well...
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I'm not having any problems with sms or mms, lte enabled and working well. Weird things could be going on though, what one person experiences may be different than someone else. I'm at&t and cm is working very well for me, best I've had on this phone. It's been the only thing holding me back from buying something else. Probably Nexus, not sure if I'll wait for the next one or go for the 6. Or neither. Decisions.
[AT&T Samsung Galaxy S 4 Original Android Developme] RK:
Everything was great for me except for Bluetooth share fc'ing. Unfortunately I am a heavy user of Bluetooth so not a daily driver for me yet..
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
The Bluetooth Share FCing is weird. I get it happening, too. It's not BT version related, and it's not related to if the device is connected to phone/media audio vs just phone audio. I can be on a call, end the call, and try to start another call right away, then Bluetooth Share FCes. I report it, when it happens.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Can I get a link to an UCUAMDL bootloader please! Thank you!
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Are you on MDB? You can't downgrade bootloader, if that's what you're trying to do.
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Thanks. It turns out that I am, indeed, on UCUAMDL (or, at least, that's what I get by running getprop ro.bootloader). So I'm in recovery (TWRP 2.8.4.0), and I was trying to flash the latest CM12.1 nightly, but it throws an error. Here's what it says: "This package is for device: jflteatt, jflte. this device is jgedlte." Now, how can I revert to ... whatever it should be in order to flash CM12.1? Is there a file I can edit in recovery, to restore the proper phone type?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
You really just need to change a couple lines in /system/build.prop. That's all I did, when I came from Dan's GPE lollipop ROM.

ro.build.product=jgedlte would get changed to: ro.build.product=jjflteatt

ro.product.device=jgedlte would get changed to: ro.product.device=jjflteatt
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Hmm, thanks. I already wiped my system. The only thing I can boot is in recovery. Can't find a system/build.prop in recovery. Other than restoring Dan's system, what else can I do?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Oh, boy.. Did you make a backup before you wiped /system and tried flashing cm12.1?

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Yes I did. I did a nandroid. Should I restore that? And if I do restore it, what do I do next?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Restore that first. That way, at least that way you have a phone that works. You have to have the phone on to edit build.prop.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Thank you. Will do. (Stupid question: What good is to to edit build.prop if I wipe the phone before flashing CM12.1?)

Edit: I also see a ro.product.name=jgedlteue line. Should I leave that untouched?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
That's true... If you wiped system, it shouldn't have mattered. post 18 had some info about that.

Sent from my TARDIS

---------- Post added at 06:14 PM ---------- Previous post was at 05:59 PM ----------

What recovery are you using?

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Well, I am stumped. I did a wipe as thorough as it gets (factory reset + format phone + custom delete (everything)). Could it be that the CM installation script recognizes the recovery as non-jflatt?

TWRP 2.8.4.0 downloaded using Flashify. Now, after modifying build.prop, I just installed a jflatt recovery, and I am getting ready to wipe it again, and flash CM12.1

Update: well, it looks like it is working! Replacing the jgedlte TWRP recovery with a jflteatt TWRP recovery did the trick!

Many thanks for the coaching!
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Did you download the jflteatt cm12.1 build, or a jflte build? Jflteatt split off from the unified jflte build.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Currently attempting to flash the latest nightly (20150618), using CM's native update app. Keep getting error message "E:Zip file is corrupt! E: Error installing zip file '/cache/recovery/block.map'." Tried downloading the update twice, same result. Could it be that the latest update file is bad?
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
E:Zip file is corrupt! E: Error installing zip file '/cache/recovery/block.map'

Same issue with today's nightly (20150619): Installs fine manually, but not using "/About phone/CyanogenMod updates." Methinks CM's Update app is broken on the i337. Can anyone confirm that updating using "/About phone/CyanogenMod updates" doesn't work?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
No, I cannot confirm that. But I can tell you that CyanDelta works perfectly.
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
http://goo.gl/ebydUX

CyanDelta may work fine. Manual installation works fine too. Have you tried installing using "/About phone/CyanogenMod updates"? What recovery do you have?
[AT&T Samsung Galaxy S 4 Original Android Developme] gho5t82:
I've had mixed results with cyan delta and the in house update app. Both had worked flawlessly until recently.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I'm using TWRP 2.8.4.0 and it works perfectly with installs, backups, and restores with all of the CM ROMS that I've tried.

I am not going to try something that apparently isn't working right t present. Instead, I suggest that you use CyanDelta to update since we know that it's working. It also uses just a small amount of the data, about 20MB, instead of having to download the entire ROM each time.