[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw)

[invisiblek]

IMPORTANT INFO:
-You must be on the VRUAMDK bootloader or you aren't going to be able to use this ROM. I'm sorry =(
(run this in a terminal to find out: getprop ro.bootloader )
-We have de-unified the Galaxy S4 line. This is for the Verizon variant (SCH-I545) only

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

Download Links

CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=jfltevzw&type=nightly
We have de-unified the Galaxy S4 line. Too many issues with having them all in one and a maintainer's nightmare. Look for jfltevzw builds now as opposed to the jflte builds you previously used.

Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps

The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S4 (jfltevzw), ROM for the Verizon Samsung Galaxy S 4

Contributors
invisiblek
Source Code: http://github.com/CyanogenMod

ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: VRUAMDK bootloader

Version Information
Status: Nightly

Created 2015-04-20
Last Updated 2015-04-19

 

[FernBch]

I guess I'll post first.

Up and running on 4/20 (flashed a few hours ago). So far I have noticed:

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.

The compass is not working properly. Orientation is slow to respond and is off by 180 degrees. This only happens when stationary. When viewing the sensors using Advanced Sensor Tester the magnetic sensor is showing some changes, the gyroscope sensor shows very little changes, and the orientation sensor shows one line out of three showing very little change. Don't know if it means anything.

Not sure if I am using the correct term here, but, 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.

Not sure if it is an Android 5.1 issue or not but I have had to reinstall several third party apps since going to CM12.1. Opening them results in a force close. If I navigate to the APK using root explorer, selecting it, and choosing install (to reinstall it) the app works correctly afterwards.

So far everything else seems to be working.

Logcat attached:

https://www.dropbox.com/s/khdo1uicmj8l7j8/Log_2015-04-20_14-07-16.txt?dl=0

 

[dansan382]

ran the 4/18 and 4/19 build. BT works, connects but won't stream anything. First my "Music" app was force closing every time it tried to play, it kept trying so it was a loop of force closes from it. I disabled the Music app, i then started getting bluetooth share has forced closed errors.

im flashing the 4/20 build but won't be able to test bluetooth playback to my car until tomorrow.

i also have the damn #in my status bar all day long. can't get rid of it, have no idea what its doing up there. even stays through reboots.

 

[FernBch]

Ok, I have come across another issue. I disconnected my Jabra BT earpiece earlier. Now it will not reconnect. BT has turned off and will not turn back on. Cycling airplane mode does not help.

Logcat:
https://www.dropbox.com/s/h86esc88wmth8pd/Log_2015-04-20_17-55-16.txt?dl=0

---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------

Ok, a reboot seems to have straightened BT out for now. It is on and I can connect my earpiece.

 

[gmp029]

BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message

Sent from my SCH-I545 using Tapatalk

 

[dansan382]

BT was not playing nicely with my car, tried rebooting with no change. BT would connect, but I would get a "Bluetooth share has stopped" message

Sent from my SCH-I545 using Tapatalk

get the same error. welcome to the club, looks like more bluetooth issues.

 

[FernBch]

get the same error. welcome to the club, looks like more bluetooth issues.

I actually expected it, happens after every version change.

 

[dansan382]

I actually expected it, happens after every version change.

yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.

I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol. i signed up for a motorola credit account, waiting for the account number to come in the mail and then ordering my 64GB nexus 6. my nano sim card came yesterday which I know verizon will give me a hard time activating. I also have a sim card cutter, some cases and a screen protector coming tomorrow so either way this is happening.

 

[vanberge]

yup, i didn't think it would be any better but was worth on a shot. can tell you on the 4/20 build it connects to my car (with a little convincing) but only recognizes the hands free profile. won't push any audio across. also turning on bluetooth is super buggy, it never really turns on and just switches the slider back to off.

I've heard euroskank builds have it working but i really dont want to full wipe my device again for the 3rd time in a week lol

I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.

So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me

 

[dansan382]

I was on skank's 12.1 build until 4.17 version and BT did not stream in my car at all. It would connect, then i'd go to play music and DoubleTwist would just keep skipping to the next song without playing any audio. Then BT would be wierd and wouldnt connect/reconnect after that until a reboot.

So far I'm seeing the same funcionality on this ROM so it seems like something with the 12.1 base to me

good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol

 

[FernBch]

good to know. there is a never ending battle with this phone on bluetooth, the compass and MMS lol

MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.

 

[dansan382]

MMS was the easy fix. I made a few APN edits and it has worked ever since. What I did is in either the official thread or euroskanks thread. BT they will eventually fix. The compass, as we all know all too well, is a whole different story.

Yea I followed your APN edits awhile back, still was hit or miss. the MMS would eventually come in but wasn't 100%. great roms though, i'm really liking lollipop

 

[phonedawg]

I started a bounty for the compass - http://forum.xda-developers.com/galaxy-s4-verizon/general/bounty-make-compass-cm-12-1-t3088991

 

[Otakulad]

Hello,

Thanks for you working on this ROM. My issue is I can't install it.

So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.

I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.

Thanks in advance.

 

[FernBch]

Hello,

Thanks for you working on this ROM. My issue is I can't install it.

So I was running JFLTE-GPE 5.0.1 for a while now by Danvdh. I noticed that at one point the Model Number changed to the GPE and device was jltegpe (or something like that). It didn't bother anything until I tried to install this ROM when I received an error in TWRP that I can't install the ROM because it is only for the jfltevzw. Does anyone know how to fix this issue. I am now running Hyperdrive and build.prop is back to jfltevzw but I am still getting the same error message in TWRP.

I am on the Verizon model of the S4 running MDK, loki'ed the bootloader, and installed TWRP.

Thanks in advance.

You may have to go back to stock first (either by nandroid restore or via Odin).

 

[Otakulad]

You may have to go back to stock first (either by nandroid restore or via Odin).

Thanks. I was thinking about that but since they are only nightlies and not everything is working, I'll wait.

 

[dansan382]

well its been fun boys..

just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol

 

[phonedawg]

well its been fun boys..

just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol

another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.

 

[FernBch]

well its been fun boys..

just got back from best buy with my unbranded nexus 6.. the GS4 was a great phone and a blast to use but these roms and their problems were driving me insane. enjoy the development, i'll probably keep an eye on whats going on. if anyone has a friend looking for an MDK bootloader GS4 on verizon let me know lol

Well, you'll be missed here but you gotta do what you gotta do......

I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]

Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.

 

[dansan382]

another one bites the dust - first rajones19 and now you. I might follow soon. Too bad considering the jfltexx variant has no issues.
I am test running a Nexus 6. Next weekend is the final return date. It is big but I am getting used to it. Let's see if I want to keep it.
My decision will also depend on Google's wireless network announcement. If it sounds good, I will return this Nexus 6 and buy one from the play store and leave Verizon.

Well, you'll be missed here but you gotta do what you gotta do......

I've talked jumpin ship before but I'll probably hang on till the bitter lonely end. I'm just hardheaded like that. [emoji14]

Seriously though, if I want decent coverage across my work area (10K sq miles in eastern AZ and western NM) Big Red is the only real choice. Who knows, maybe when I do decide on a new device it will be rootable and possibly even exploited.

well its time to move on, i really love the GS4 even more than my galaxy nexus but its been 2 years. I had this GS4 since launch date, actually had it 3 days early. she served me well and i honestly could have gone a little longer with it but I got tired of dealing with flashing stock roms on my phone just for certain key things not to work right. Got tired of having to explain to people when something didn't work it was because of custom software. Plus looking at my GS4 it just feels small now. Honestly would have preferred a 5.5inch phone but I dont see this thing being a problem once i get use to it. I'll probably keep the GS4 around as a mess around device so I'll probably still flash some roms with it. Don't think there is much of a demand in the resale space for a 2 year old phone like this. I've learned my lesson though, and I should have learned it from having a galaxy nexus but from now on out I'll only be using nexus devices.

I debated switching to T-Mobile and honestly I'm still very interested in doing so. Like others, coverage is a big concern and even though here in Southern PA (right outside of Philly) I get great T-Mobile coverage, I'm still worried about the one time to go somewhere that has 0 coverage. I drive back and forth to Long Island, NY where I'm originally from every few weeks and T-Mobile coverage is outstanding that entire trip so that would be nice. If I was still on the island I would switch in a heartbeat. Being in PA now, 75% of this state is a blackhole for T-Mobile coverage which very much worries me, even though I never really go that far. Maybe by the end of the year I might make the switch but for now I'm sticking with big red, unfortunately.