yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Ibuprophen:
It's a bit of a challenge via text, i'll try my best to explain a few things to keep in mind...

The Unofficial Builds, for this specific device, were signed released by lead developer of this devices LineageOS Team (Invisiblek).

The Official builds were reviewed, signed and approved for release by the LineageOS Group Team Leader (there's a few of them who overseas their prospective team groups).

Going from an Unofficial build to an Official build (and vice versa), by default, should be known that a clean install should be performed.

With that stated, many individuals perform what is called a "Dirty Flash" that should only be done when updating an Unofficial build with an updated Unofficial build OR an Official Build with an updated Official build. This also involves other actions too (IE... Re-Flashing the SuperSU and, an encouraged, Updated GApps package).

Though, I do agree with the painstaking process this this is but, it is something that needs to be remembered as a standard of practice.

Other's have performed different variations and may have been successful in doing them but, that only applies on a case by case basis. For example, though, I have a d2vzw device and have had some issues (as well as others) with the LOS14.1, there are those who also has the same device haven't had any issues with it.

I hope i explained this okay.

I wish you the best of luck!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**
[Verizon Samsung Galaxy S 4] HowardZ:
Is it safe to

1. use LineageOS 14.1, and

2. encrypt the device in the settings, and

3. use TWRP to install LineageOS updates to the encrypted phone?

I ask because a few years ago there were problems with TWRP recognizing the encryption.
[Verizon Samsung Galaxy S 4] Ibuprophen:
On March 8th TWRP released version 3.1.0-0 for the jfltevzw here:

https://dl.twrp.me/jfltevzw/

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Verizon Samsung Galaxy S 4] HowardZ:
Ibuprophen,

I know you try to be a very helpful person here, and I appreciate it.

But you could have just said you never tried encrypting your S4 phone and you just plain don't know the answer.

Instead you just told me where to get the UNLOKI version of TWRP that I already LOKI'd and put on my phone.

To encrypt the S4 and discover there is no way to update CyanogenMod/LineageOS means wiping everything - even the internal storage. Only the SD card can be spared (and best to remove it to be safest). It's really a super pain in the butt to undo the encryption.

So either someone says - Yeah I tried it and TWRP still does not support LineageOS's encryption. Or - Yes I tried it and TWRP installs updates just fine.

To say nothing because you don't know the answer - is perfectly acceptable.
[Verizon Samsung Galaxy S 4] Ibuprophen:
No disrespect at all but, nowhere in my text did it state anything that the official release was or was not Loki'd...

All i stated was that the official TWRP was released and the link.

If any misunderstanding has resulted in my response then I truly and deeply apologize for this.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[Verizon Samsung Galaxy S 4] Daeo:
I am very curious to run this ROM in some shape or form. I currently run the Hyperdrive 20 and the BT connection constantly drops and is the only reason i want to switch. Does anyone know a CM that has stable bluetooth with gapps package i can flash over? I tried to flash this rom and a long list of gapps packages and everytime i loaded into the rom gapps would force crash constantly.
[Verizon Samsung Galaxy S 4] dansan382:
bluetooth "works"....... if you plan on using it to stream music from you might not have too much luck. I haven't tested phone calls via bluetooth but music playing did not work. was using 4/18, 4/18 and 4/20 builds, all three suffered from the same problem. would connect to my car but wouldnt stream music. bluetooth share error kept popping up
[Verizon Samsung Galaxy S 4] Daeo:
Ya this is exactly my problem and i have come to the point where i will either find an older working version of CM running on 4.4 or wait this to be fixed. I don't want to purchase a new phone yet as i am waiting for the new note so im kind of in a crappy place. Bought a new car and now my media cuts out constantly and stutters :(
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 4/23 this morning, other than the normal issues I reported earlier (compass etc) seems good.
[Verizon Samsung Galaxy S 4] thedoman:
This is the third 12.1 rom that has had problems with exchange services force closing for me. is there a fix for this?
[Verizon Samsung Galaxy S 4] FernBch:
Not that I am aware of. Since everyone uses CM as a base the issue most likely will remain until the base is fixed.

Have you tried euroskanks builds?
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 4/26 earlier. Preliminary assessment shows the following:

New issue:

CMupdater is borked. Actually noticed it a week ago but I figured it could be related to the migration to 12.1. Finally created a JIRA report.

Unchanged issues:

As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it. JIRA regression created - no progress shown on it.

The issue where individual SMS messages are marked as unread when a particular recipient is also part of a group MMS is still present. Could swear I have created a bug report for this, even when on CM11 - can't find it.

Surprise!! The compass is not working properly. Created a bug report for this on CM11. It is actually marked as Resolved. Ha!

{insert sarcastic comment here} lol

This issue seems to be fixed, will test more when brighter light is available (snowed this morning & still cloudy):

Adaptive brightness does not seem to be responding well and overall the lower brightness setting of the display seem to be too dark. In an outdoor environment any brightness setting below 50% is pretty much unusable and the brightness when in direct light doesn't increase enough. (May not have described that correctly).

BT seems good with a Jabra earpiece. I have yet to test it with something like music play over Ford's Sync and vehicle BT. Will test later.
[Verizon Samsung Galaxy S 4] thedoman:
E mail app (exchange service) force closing on the last few builds. Anyone else have this or know a fix? Thanks
[Verizon Samsung Galaxy S 4] musicfreak190:
Hey all is the latest nightly, Android 5.1.1 ?
[Verizon Samsung Galaxy S 4] vanberge:
Yeah the last couple bills have been
[Verizon Samsung Galaxy S 4] FernBch:
Noticed a couple things with the 4/26 build.

You cannot edit the "owner" profile. Message says contact doesn't exist.

There is a considerable lag when waking the device before the screen lights up.
[Verizon Samsung Galaxy S 4] musicfreak190:
The owner profile thing has been an issue since CM12.1 started.

And about the lag that stinks.. Anyone else seeing that?

Was going to do a clean flash tonight.

---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------

I have no issues with Exchange crashing.. That's weird..
[Verizon Samsung Galaxy S 4] FernBch:
I clean flashed last night. I noticed when I flashed 4/26 it screwed with some of my system apps. BBS was no longer installed. I did a cache/davlik wipe and when I restarted it was only optimizing 150 apps when it should have been 172. I just factory reset and clean flashed 4/26 and Gapps. Other than what has been an issue (compass, etc) it seems fairly good.

I do have one question, though. I keep getting "message not sent" notices as soon as I open the stock messaging app. I have figured out sometime over the last month or so one of the nightlies changes something in my messaging database. If I delete the database I don't have the message. I really don't want to delete my entire SMS/MMS history. I'm curious if I can go through the database and delete an entry (or two) and rid of the unsent message that causing this. Discarding it and completing it does nothing.
[Verizon Samsung Galaxy S 4] indolent:
Anyone else have issues with the file manager? I can't figure out how to move a file. The only options I see are "copy selection here," or, "move selection here." Of course the move selection here button just causes an error since it's trying to move a file to the folder it is already in. Also, the actions menu is completely different depending on whether you long press a file or you check the box next to the file and tap the 3 dots button.

Also, the capacitive button backlight setting is back to not saving after a reboot.

edit to add, I did a clean flash of the 4/20 built, and dirty flashed the 4/26 update.

---------- Post added at 05:36 PM ---------- Previous post was at 05:33 PM ----------

I still have the 4-16 version downloaded on my phone. I can upload it somewhere if you haven't found it yet.
[Verizon Samsung Galaxy S 4] checho408:
It would be awesome if you could do that i haven't found a working link.
[Verizon Samsung Galaxy S 4] indolent:
What's a preferred file host? I haven't shared a file in a while.
[Verizon Samsung Galaxy S 4] checho408:
Google drive is fine
[Verizon Samsung Galaxy S 4] indolent:
Here you go. http://goo.gl/pMK56k
[Verizon Samsung Galaxy S 4] snakecharmer23:
compass fix

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

I really hope this finds its way to the other jf devices.

Edit: I re-read the commit message and I think the VZW calibration will apply to all jf devices.

Yay.
[Verizon Samsung Galaxy S 4] checho408:
Thanks :) really appreciate it.
[Verizon Samsung Galaxy S 4] FernBch:
I just read the notes on this one. It applies to the jf kernel for VZW models for CM12.1, CM12.0, and CM11!

He had commented back in January that the kernel wasn't initiating something to do with the magnetic sensor properly. It just may be a little more than coincidence that the issue appeared when the kernel had the major change that it did almost a year ago.

I also will not say that our developers and maintainer don't do a good job, as that would not be true.

Just the same I'm going to take a wait and see approach. At least it has been merged so it's a start at minimum.

Edit:

Well, I have applied the commit to my S4.

And.......

And......

Wait for it.......

My compass really seems to be working as it should!!!!!!! It's not sluggish. It's not wonky. It's not off by 180 degrees! And all my third party apps that rely on the compass are also reporting the proper orientation and are no longer off by 180 degrees!!!!!!

Thank You invisiblek! This one item now makes this ROM the ROM off choice.
[Verizon Samsung Galaxy S 4] FernBch:
Oh, just noticed, unless I didn't read it properly, the compass commit did not make the 4/28 nightly.
[Verizon Samsung Galaxy S 4] jackburnt:
Wonderful to hear! I think I'll upgrade from 12 once the nightlies pan out.

Thanks for your reviews!
[Verizon Samsung Galaxy S 4] berndt_toast:
Yep, it sure did (4/28 nightly).

http://www.cmxlog.com/12.1/jfltevzw/
[Verizon Samsung Galaxy S 4] vanberge:
So who do I paypal $25 to? Haha
[Verizon Samsung Galaxy S 4] .Ejekt:
Huzzah! And of the other issues you posted about? Thinking about climbing aboard the 12.1 train sometime this week.
[Verizon Samsung Galaxy S 4] FernBch:
invisivlek, the info you seek is in the bounty thread!

Flashed 4/28 earlier. Preliminary assessment shows the following:

CMupdater:

CMupdater is borked. Actually noticed it a week ago but I figured it could be related to the migration to 12.1. Finally created a JIRA report.

MMS/SMS:

As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it. JIRA regression created - no progress shown on it.

The issue where individual SMS messages are marked as unread when a particular recipient is also part of a group MMS is still present. Could swear I have created a bug report for this, even when on CM11 - can't find it.

Compass:

Surprise!! The compass is working for me!!!!!! Oh Happy Day!!!!!!!!!

Adaptive Brightness:

This issue seems to be fixed, will test more when brighter light is available:

Adaptive brightness does not seem to be responding well and overall the lower brightness setting of the display seem to be too dark. In an outdoor environment any brightness setting below 50% is pretty much unusable and the brightness when in direct light doesn't increase enough. (May not have described that correctly).

Bluetooth:

BT seems good with a Jabra earpiece. I have yet to test it with something like music play over Ford's Sync and vehicle BT.

For me it is a daily driver and has been. I know some have had issues with BT and streaming audio but I use it very seldom so it hasn't been an issue for me.

---------- Post added at 11:57 AM ---------- Previous post was at 11:54 AM ----------

Edit:

I have also seen reports of exchange services force closing but I don't use it and can't comment.

The migration to CM12.1 has also broken the ability to edit the owner profile. Attempts to do so just says "contact doesn't exist".
[Verizon Samsung Galaxy S 4] FernBch:
Almost forgot. There is still considerable lag when waking the device from deep sleep.
[Verizon Samsung Galaxy S 4] vanberge:
I paid him my contribution - thanks!
[Verizon Samsung Galaxy S 4] gmp029:
I installed 4/28, but compass still doesn't work. I tried initializing with moving the phone along a figure 8 and also by rotating across the three axes. Any ideas?
[Verizon Samsung Galaxy S 4] FernBch:
Clean install or dirty? I applied the patch to 4/26 (got there through a few dirties) and I clean flashed 4/28 and it worked after both installs. The only thing I noticed was the initial GPS lock seemed to take forever but has been spot on ever since. I used GPS Status & Toolbox for me first lock and calibration. Calibration was done by rotating the phone a couple times around each axis.
[Verizon Samsung Galaxy S 4] indolent:
I still have issues with bluetooth streaming in my car. Google play music and the cyanogenmod music app both refuse to play any music stored on my phone at all while connected to bluetooth. If I turn off bluetooth, they both play fine through the phone speaker.

Pandora streaming works for a while, then just stops streaming, even though it says it is. The only fix is to reboot.
[Verizon Samsung Galaxy S 4] FernBch:
That pretty much sums up the current BT issue. It affects all CM based ROMs. If you can capture a logcat and post a link it may help.
[Verizon Samsung Galaxy S 4] cawpin:
The only problem I've noticed with 4-28 is that screen/pixel scaling seems to have had some slight change. This causes a widget I use, Battery Life, to display correctly. The settings screen is scaled completely wrong. It was fine on the previous nightly I was on, 4-24.

Edit:

I can confirm that Exchange support is borked. The standard Email app seems to not even support it anymore and Exchange is in the Gmail app. I do not like this at all.
[Verizon Samsung Galaxy S 4] .Ejekt:
I guess I'll wait patiently on 4/19 :3
[Verizon Samsung Galaxy S 4] Jon8RFC:
Compass / Magnetometer certainly seems to be fixed! Thank you, Invisiblek!!

I did a clean install of 4/29 nightly (I don't do factory resets, I always wipe system/cache/data/dalvik instead), let GPS orient itself (important for Azimuth), did a few figure-8 calibrations, and Google Sky works just as it should, like my OEM S4 and my OEM HTC DroidDNA! Thank you, Dan!
[Verizon Samsung Galaxy S 4] goblygoop:
I don't know if its helpful, but I know how to make my audio streaming work correctly. I just listened to iheart radio for 30min straight. For me, when i connect to my N/AC router, the audio will nose dive every 5 minutes or so depending on how much internet surfing I'm doing. If I switch to my G network, I don't have any problems. BTW..its streaming to my moto s9hd's. Hope it helps
[Verizon Samsung Galaxy S 4] FernBch:
Try it over Bluetooth connected to a car such as Ford Sync.

---------- Post added at 11:30 PM ---------- Previous post was at 11:27 PM ----------

I have noticed a new BT issue today. I use a Jabra earbud. Today it started working for only one or two calls. After that people could hear me when using it but I couldn't hear them. It worked properly after a reboot but only for a call or two.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 4/30. So far I have noticed that the lag that was present when waking from deep sleep seems much better.
[Verizon Samsung Galaxy S 4] jareddlc:
BT audio not working

im on 4/29 and cannot play bt audio in my car.
[Verizon Samsung Galaxy S 4] .Ejekt:
Came from 4/19 to 4/29. Haven't tested GPS or BT yet. No lag or MMS issues thus far.
[Verizon Samsung Galaxy S 4] Ridwan Majid:
Instructions

Hey guys just read the post and am super excited. I'm wondering however where I can find instructions to install Cyanogenmod ROM. Thanks
[Verizon Samsung Galaxy S 4] FernBch:
Compass and GPS are great. Invisiblek fixed the compass two builds ago!!
[Verizon Samsung Galaxy S 4] FernBch:
I noticed something with WiFi today. I got a Jetpack and set it up to connect with my phone (it has unlimited data). If I choose to not broadcast the SSID I can't connected to it even though it is a saved network. Any other WiFi device I use will connect to it when the SSID is not broadcasted but the S4 on CM12.1 won't.

Anyone have a workaround or is this a known bug?

---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------

Also noticed that editing the owner profile is no longer borked.
[Verizon Samsung Galaxy S 4] goblygoop:
Sorry, my infiniti only has hands free, no streaming audio. I have a logitech bluetooth to RCA adaptor in the car, but the phone still sees it as headphones and streams correctly.
[Verizon Samsung Galaxy S 4] FernBch:
Running 5/2 now. I've noticed the CMupdater is partially fixed. I can download the updates but the changelog is still not viewable.

---------- Post added at 12:06 PM ---------- Previous post was at 11:08 AM ----------

I finally figured out the "could not send message" error I was getting as soon as I opened Messaging.

Using SQLite Editor I opened Phone/Messaging Storage, then opened mmssms.db. Inside the "PDU" enty I noticed one line had a zero in the read column and all other listings had a one there. I deleted that line only. Now when I open Messaging I no longer get that error.

What was happening was I would get a notification pop up every time I opened messaging saying "this message could not be sent". Opening the message would give a blank, unaddressed message and choosing discard from the menu did nothing but exit messaging.
[Verizon Samsung Galaxy S 4] Cameron_S:
I'm on the 5-1-15 built and Bluetooth seems to have been fixed. Worked flawlessly yesterday and today with my moto 360 and audio streaming / calls in the car.
[Verizon Samsung Galaxy S 4] FernBch:
Figured I'd post this status report.

CMupdater: Download now works, changelog still not viewable.

MMS/SMS:

Found solution myself:

As soon as you open the stock messaging app a notification appears saying a message could not be sent. Choosing "Discard" from the menu of the unsent message does not discard it.

Still looking into this one:

The issue where individual SMS messages are marked as unread when a particular recipient is also part of a group MMS is still present.

Bluetooth:

I have yet to test it with something like music play over Ford's Sync and vehicle BT.

I have also seen reports of exchange services force closing but I don't use it and can't comment.

Fixed:

The migration to CM12.1 has also broken the ability to edit the owner profile. Attempts to do so just says "contact doesn't exist".

Looks like the major outstanding issues are streaming audio over BT to vehicle and exchange services. Once these are sorted out CM will be totally awesome. Their getting closer......
[Verizon Samsung Galaxy S 4] FernBch:
Guess I spoke too soon about CMupdater. Had to download 5/3 through the browser.
[Verizon Samsung Galaxy S 4] natec003:
How's BT been acting? I go through streaks where it seems to work OK... That's the only thing that's keeping me from using this rom
[Verizon Samsung Galaxy S 4] Cameron_S:
Its been working great. I had nearly given up on the ROM because BT is really important to me. I figured I would try the 5-1-15 build and have been pleased. Have not seen a BT share force close for the past 3 days.
[Verizon Samsung Galaxy S 4] FernBch:
That's good to hear. I'll have to test it with Ford Sync.

Does anyone know if Exchange Services are still an issue?
[Verizon Samsung Galaxy S 4] FernBch:
I have a new one for everyone.

Today I used my phone enough that the battery died. After I got it charged enough to restart it I have a major issue. All apps that I have installed as a system app either FC or are no longer installed. For some reason /system is corrupted and I had to start fresh.

Anyone else see anything like this? This is not acceptable and I will be looking for another ROM, even if it means going back to TW.
[Verizon Samsung Galaxy S 4] jareddlc:
BT working in my car now with 5-03
[Verizon Samsung Galaxy S 4] FernBch:
Just for S&G's, I ran the battery down again. After a fresh, clean install of everything I was able to repeat the issue that surfaced earlier today. Third party system apps either FC or are reported as "not installed" after a forced shutdown due to a low battery. I hate to say it but in seven years I have never seen the reliability of CyanogenMod be so bad. Whatever has changed it definitely is not for the better.

For some time now it seemed as if I was one of the few flashing each new nightly and posting up an assessment report and/or fixes/workarounds when I could. It just seems like over the last few weeks things have really gone downhill stability wise. Fixes for issues are getting slower and slower to come along and it just makes it difficult to use as DD anymore.

That said, it is with a heavy heart that I must say farewell to CyanogenMod for the short term at least. I'll follow along for a while and keep up to date on updates and commits. Who knows, maybe CM will improve again and be my ROM of choice.

I would like to say Thank You do the developers who do what they do because without them CM for the SCH-I545 would have disappeared some time ago.

Farewell for now everyone......

[emoji22]
[Verizon Samsung Galaxy S 4] indolent:
Interesting. I was just thinking the opposite. With the compass and bluetooth seemingly fixed, I think it is worthy of a dd for most people again.

I do agree that fixes are getting slower and slower, but what other options do we have? Mind if I ask what you are planning on moving on to?
[Verizon Samsung Galaxy S 4] FernBch:
Haven't made up my mind yet. Most AOSP are CM based and I really don't want to go back to a TW ROM. For now I'm still running CM12.1, though. Before I make the big leap off into the deep end I want to test a few things out then look at other ROMs. After all that I'll decide. Who knows, maybe it will just be a rant on my part and I may find out I'm actually better off staying put. I guess it all boils down to how much "tinkering" I'm willing to accept. CM has had some issues but most are either minor to deal with or not too hard to work around. Whatever it is that is screwing with my system is a bit of a PITA and I am not fond of having to reinstall things frequently for them to work.
[Verizon Samsung Galaxy S 4] mangalo2004:
I've never been a fan of TW at all, but I put the latest version of my wife's phone yesterday and it's not as bad as the 4.4 version. It's definitely better than it used to be.
[Verizon Samsung Galaxy S 4] musicfreak190:
Something that is driving me nuts. I will randomly look at my phone after the screen being off for a while and I will notice Wifi disconnected me and then it connects back up when I unlock it...

WTF Verizon CM12.1 Conspiracy. LOL