[ROM] [7.1.1] [UNOFFICIAL] CyanogenMod 14.1 [Dec 25, 2016]

Would you prefer to add support for other variants/carriers?


  • Total voters
    476
Status
Not open for further replies.
Search This thread

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
Let me try this again. If this isn't what is needed, I'll gladly go get whatever else is.

There's no problem in your log.

GPS is working perfectly fine for me. However, if you'd like to tune it for yourself, you may edit the GPS configs (gps.conf, flp.conf, izat.conf, and sap.conf) in /system/etc. You can find different configs that you may test here.
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,712
16,023
IDK
@hsbadr
Here's a couple of logs.
I was experiencing freezing when opening the app drawer and also when switching WiFi off and on.. Gmail was also becoming non responsive. I got a popup for both Gmail and Nova Launcher asking me to Close - Wait or Report.

I'm not sure which log has both events captured.

Full Clean Flash - Factory Reset - Manually Wiped System - Data and Caches

Flashed Open Gapps Nano

https://drive.google.com/file/d/0B9TbnlZl-ugWUVRaakQwMTBBZU0/view?usp=drivesdk

https://drive.google.com/file/d/0B9TbnlZl-ugWV3ZNaGtpX0x4a0U/view?usp=drivesdk

Sent From My SM-N910W8 ??
 
  • Like
Reactions: javier72

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
@hsbadr
Here's a couple of logs.
I was experiencing freezing when opening the app drawer and also when switching WiFi off and on.. Gmail was also becoming non responsive. I got a popup for both Gmail and Nova Launcher asking me to Close - Wait or Report.

I'm not sure which log has both events captured.

Full Clean Flash - Factory Reset - Manually Wiped System - Data and Caches

Flashed Open Gapps Nano

https://drive.google.com/file/d/0B9TbnlZl-ugWUVRaakQwMTBBZU0/view?usp=drivesdk

https://drive.google.com/file/d/0B9TbnlZl-ugWV3ZNaGtpX0x4a0U/view?usp=drivesdk

A quick look shows that you've installed some 3rd-party apps that caused UI problems (maybe due to data restore?). For example, Beautiful Widgets (com.levelup.beautifulwidgets) and Nova Launcher (com.teslacoilsw.launcher) keep crashing.

In the other log, Google Chrome Beta (com.chrome.beta) crashes.

Test a clean flash with no 3rd-party apps! Then, install your apps one by one cleanly (no data restore). Finally, if you use TitaniumBackup, you could selectively restore the app data.

I didn't run into any freezing issues at all.
 
Last edited:

tchdud3

Member
Jun 26, 2010
14
5
There's no problem in your log.

GPS is working perfectly fine for me. However, if you'd like to tune it for yourself, you may edit the GPS configs (gps.conf, flp.conf, izat.conf, and sap.conf) in /system/etc. You can find different configs that you may test here.

With that, if I were to re-install 11/26 (working GPS), copy those files to my ext_sd, re-install 11/15, overwrite 11/15's files with those from 11/26, should that work?

I have no idea what all else goes into those files and do not want to negate other changes you might have made, but if all I need is a specific config from one of those files, happy to do the re-installs to run it down and report back for other Tmo users.
 

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
With that, if I were to re-install 11/26 (working GPS), copy those files to my ext_sd, re-install 11/15, overwrite 11/15's files with those from 11/26, should that work?

I have no idea what all else goes into those files and do not want to negate other changes you might have made, but if all I need is a specific config from one of those files, happy to do the re-installs to run it down and report back for other Tmo users.

Yes, if 11/26 works for you, you can use the GPS configs on 12/15.
 

seriosbrad

Senior Member
Sep 2, 2010
489
237
Alberta
GPS also not working reliably for me on the 910W8. GPS worked once yesterday, with Google Maps, to my destination; on the way back it wouldn't lock on at all. This log is from today, it wouldn't get a good lock period.
 

Attachments

  • Log_2016-12-15_12-57-58.zip
    199.6 KB · Views: 19

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
GPS also not working reliably for me on the 910W8. GPS worked once yesterday, with Google Maps, to my destination; on the way back it wouldn't lock on at all. This log is from today, it wouldn't get a good lock period.

Did it work better for you on any previous build? If so, try to replace the GPS configs from that build or from your stock ROM. Make backup!
 

seriosbrad

Senior Member
Sep 2, 2010
489
237
Alberta
Did it work better for you on any previous build? If so, try to replace the GPS configs from that build or from your stock ROM. Make backup!

I honestly don't remember about any 11/26 build GPS issues. I took your advice and copied those GPS config files from my stock ROM (DPK1 Firmware for the N910W8) and just went for a drive. Worked pretty much flawlessly! I've attached them as a .zip if you are curious.

Google Maps even prompted me to do this, which I've never seen before.
 

Attachments

  • N910W8VLS1DPK1_GPS.zip
    12.5 KB · Views: 100
Last edited:
  • Like
Reactions: razholio

tchdud3

Member
Jun 26, 2010
14
5
Yes, if 11/26 works for you, you can use the GPS configs on 12/15.

Wiped, restored 11/26, confirmed GPS working, archived FLP,GPS,izat & SAP, wiped, installed 12/15, tested GPS (not working, as expected), replaced cfg files, rebooted, no GPS.

Any other suggestions?
 

Attachments

  • report_2016-12-15_181053.zip
    5.4 KB · Views: 19

the Doctor

Retired Senior Moderator
Dec 15, 2011
4,588
4,525
In the TARDIS
NOTICE: If your posts are missing, it's because they were considered off-topic here in the development thread and have been moved to the Q&A/discussion thread.

Before posting here, make sure you've read the first three posts and understand what you're reading. Repeat offenders will receive infractions as off-topic posting is against XDA's forum rules.

Sent from a government computer using my sonic screwdriver
 
Last edited:

wgrant

Senior Member
Sep 23, 2011
1,546
522
Using latest build 12/15 on sprint. Unable to send SMS. Started with no data/MMS which got resolved but now I have no SMS and I'm assuming calls (nobody ever calls so that's not an issue). Data is working and so are MMS. Attached is a log of me trying to send a text and it eventually failing.

http://cloud.tapatalk.com/s/58545bca2adc6/sms.txt

Hopefully I did that correct, never taken a log before.

Sent from my SM-N910P using Tapatalk
 
Last edited:

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
Using latest build 12/15 on sprint. Unable to send SMS. Started with no data/MMS which got resolved but now I have no SMS and I'm assuming calls (nobody ever calls so that's not an issue). Data is working and so are MMS. Attached is a log of me trying to send a text and it eventually failing.

http://cloud.tapatalk.com/s/58545bca2adc6/sms.txt

Hopefully I did that correct, never taken a log before.

It isn't a ROM issue. You likely need RIL blobs from Sprint ROM. Try to replace the folliwing files (set correct permissions or use adb push in recovery):
Code:
/system/bin/rild
/system/lib/libril.so
 

wgrant

Senior Member
Sep 23, 2011
1,546
522
It isn't a ROM issue. You likely need RIL blobs from Sprint ROM. Try to replace the folliwing files (set correct permissions or use adb push in recovery):
Code:
/system/bin/rild
/system/lib/libril.so
From stock ROM or another aosp/cm based ROM?

Sent from my SM-N910P using Tapatalk
 

wgrant

Senior Member
Sep 23, 2011
1,546
522
From the latest stock firmware that you should be already running.
Excellent, will grab them and give it a go. Thank you

OK so that caused me to lose radio altogether, had to reflash the ROM. I have discovered in this process that if I force the phone to CDMA texts work but my network lists as Verizon instead of Sprint. When I go back to LTE it shows Sprint but no SMS anymore. Also noticed that when on CDMA only I get "carrier settings" at the bottom. Attached a couple screenshots to explain. If this is better suited for the q&a please move it mod, just seemed related to my previous log post.

a1c247079aa790c9b5cee931cd1c4de7.jpg

9bd94a367034238111e1d27804c0deba.jpg

6d5749b74b5162662294aea14a9c3f43.jpg

a29fa223f7cb40695736a5c4e47a39fa.jpg


Sent from my SM-N910P using Tapatalk
 
Last edited by a moderator:

StayingSober

Senior Member
Apr 30, 2013
58
51
Western NY
SM-N910V, CPF3, running latest build 12/15, clean flashed with latest Nano GApps. A lot of improvements since the previous builds! One issue I noticed still occurring is the random zoom/crop during video playback (mostly only HD videos) in Facebook, sometimes YouTube, etc. To elaborate a little further, when watching a video, it will play fine but randomly crop the video to only show the top left corner of the video and continue to play. If you close the video and open it back up, it will play just fine.

@hsbadr I captured some logs when it occurred. I briefly parsed through the logs and couldn't find the issue occurring, but I can definitely say it occurred between timestamps 20:45:55 & 20:46:08 in the logs. Just for safe measure, I included roughly 30 seconds prior to when the error happened. If you need any other info or additional logs just let me know.

As always, thank you for all of your hard work and dedication!
 

Attachments

  • zoom.txt
    175.1 KB · Views: 35
Last edited:

hsbadr

Inactive Recognized Developer
May 18, 2014
3,930
22,401
Excellent, will grab them and give it a go. Thank you

OK so that caused me to lose radio altogether, had to reflash the ROM. I have discovered in this process that if I force the phone to CDMA texts work but my network lists as Verizon instead of Sprint. When I go back to LTE it shows Sprint but no SMS anymore. Also noticed that when on CDMA only I get "carrier settings" at the bottom. Attached a couple screenshots to explain. If this is better suited for the q&a please move it mod, just seemed related to my previous log post.

a1c247079aa790c9b5cee931cd1c4de7.jpg

9bd94a367034238111e1d27804c0deba.jpg

6d5749b74b5162662294aea14a9c3f43.jpg

a29fa223f7cb40695736a5c4e47a39fa.jpg

There's no such issues on the main CDMA variant (VZW) nor the other GSM variants.

A few things to test:
  • Make sure that your device is listed as trltespr in the build.prop:
    Code:
    ro.product.device=trltespr
    Reboot and select CDMA network!
  • Try 11/26 kernel by flashing boot.img over 12/15 ROM!
  • Re-add the following file from 11/26 (in recovery):
    Code:
    /system/framework/qti-telephony-common.jar
    This may cause MMS issues though.

SM-N910V, CPF3, running latest build 12/15, clean flashed with latest Nano GApps. A lot of improvements since the previous builds! One issue I noticed still occurring is the random zoom/crop during video playback (mostly only HD videos) in Facebook, sometimes YouTube, etc. To elaborate a little further, when watching a video, it will play fine but randomly crop the video to only show the top left corner of the video and continue to play. If you close the video and open it back up, it will play just fine.

@hsbadr I captured some logs when it occurred. I briefly parsed through the logs and couldn't find the issue occurring, but I can definitely say it occurred between timestamps 20:45:55 & 20:46:08 in the logs. Just for safe measure, I included roughly 30 seconds prior to when the error happened. If you need any other info or additional logs just let me know.

As always, thank you for all of your hard work and dedication!

I don't run into these issues, but I'll look into it.
 

abraha2d

Senior Member
May 15, 2016
227
129
Atlanta, GA
i9100
Verizon LG G2
@hsbadr I've also been experiencing the "video zooming in" issue that @StayingSober has. The video embedded on the following website does it at the 10 second mark without fail:

http://www.consumerreports.org/cro/...smart-door-lock-may-outwit-burglars/index.htm

I tried this with both the embedded android webview (the blue one that pops up when you click on a search result from the Google search app), and with Chrome. Happens in both.

I'll see if I can get a logcat.
MOD EDIT: Next time refrain from posting until you have the logcat or post it in the discussion/Q&A thread.

EDIT: This time it was at the 20 second mark... Same video. Maybe it only happens at 10 second intervals? I wasn't in full screen this time, though...

I can't find where MatLog saves the logs. I have it, though. Just need to find it.

Sent from my Samsung Pixel XL using XDA Labs
 
Last edited by a moderator:

abraha2d

Senior Member
May 15, 2016
227
129
Atlanta, GA
i9100
Verizon LG G2
Got the log for the video zooming issue. It's attached.

Turns out MatLog saves logs under a directory called catlog on the internal SD card...

Sent from my Samsung Pixel XL using XDA Labs
 

Attachments

  • 2016-12-19-00-01-28.txt
    329.1 KB · Views: 17
Last edited:
  • Like
Reactions: razholio
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 346


    Disclaimer:
    Code:
    /*
     *
     * Your warranty is now void.
     *
     * I am 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 me for messing up your device, I will laugh at you.
     *
     */

    Tags:
    To avoid confusion with the OFFICIAL CyanogenMod build tags that include Nightly/Developement (every 24 hours, experimental, newest features, unstable) and Snapshot/Release (every 1-2 months, suitable for daily use, devices signed-off by maintainers for inclusion), these UNOFFICIAL builds have three tags:
    • STABLE: include tested changes and confirmed bug fixes;
      are suitable for daily use.
    • TESTING: include experimental changes to be evaluated and to possibly fix some issues;
      may be used as daily driver only if they don't break functionality or introduce new issues.
    • VZW-ONLY: same as TESTING builds, but support Verizon variant (VZW SM-N910V) only.

    Changelog:
    For the latest changes and bug fixes, check the 2nd post!

    Status:
    This ROM supports all Snapdragon variants, especially US variants (Verizon / VZW SM-N910V, T-Mobile/TMO SM-N910T, Sprint / SPR SM-N910P, and US Cellular / USC SM-N910R4) and Canadian variant (SM-N910W8). This is only possible because I made major changes to the kernel, init, and frameworks/telephony overlays. Moreoever, the vendor proprietary blobs for VZW variant support both CDMA and GSM networks. So, the device name/model and related properties will reflect the VZW base/blobs.

    Check the ROM status in the 3rd post!

    Kernel:
    For stability, this ROM uses ~pure Samsung source code for the kernel with carefully cherry-picked commits from CAF MSM 3.10 source code for APQ8084. A few patches are merged to implement some CMHW features. Moreover, driver updates are integrated from the latest Samsung releases.

    I'm also contributing to this kernel repo that will be shipped in some builds for extra features.

    instructions:
    • Hit THANKS
    • Make backup
    • Do a full factory reset
      You should wipe the system partition!
    • Flash ROM + Gapps ARM 7.1
      Gapps nano package is recommended!
    • Enjoy!
    Only for international variants (SM-N910F/G):
    >>> Flash RIL/QMI fix from the 3rd post, before flashing Gapps.

    Notes:
    • Clean flash (wipe system/data/cache/dalvik) is required.
    • You need to install nano Gapps for ARM SDK 25 (Android 7.1.1 Nougat) .
    • You may also need to set default Apps and grant special access/permissions.
      In Settings/Apps, click the Settings icon and select "Show system" from the 3-dot menu, as needed.
    • Make sure that your preferred APNs are selected in Settings/Cellular networks.

    Downloads:

    Support:
    A voluntary work consumes resources and more importantly time!

    If you'd like to support the development, you may donate here:
    • It's fine to just click THANKS or enjoy without saying anything.
    • A donation is to show appreciation of the work I have done already.
    • A donation is not by any means in expectation of future work.
    • A donation doesn't entitle for preferred/private support/requests.
    • A donation is meant as a gift - always appreciated, never required.

    If you couldn't donate, you can hit THANKS :good:​

    XDA:DevDB Information
    CyanogenMod 14.1, ROM for the Verizon Samsung Galaxy Note 4

    Contributors
    hsbadr
    Source Code: https://github.com/CyanogenMod

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: N910VVRU2CPJ2
    Based On: CyanogenMod

    Version Information
    Status: Stable
    Current Stable Version: 14.1-20161225
    Stable Release Date: 2016-12-25

    Created 2016-11-06
    Last Updated 2016-12-25
    215
    Changelog

    Green dates are for STABLE builds, blue dates are for TESTING builds, and red dates are for VZW-ONLY builds. To learn more about build tags, check OP!

    You may find a WIP section on top, for what to expect in the coming build. You could vote for a newer build by hitting THANKS to the announcement post of the latest build. For more details, check ROM status in the 3rd post!

    All builds include the upstream CyanogenMod changes.


    END OF DEVELOPMENT


    25.12.2016:
    • Cleaned up and updated audio configs
    • Disabled ERI operator string for non-VZW variants
    • Enabled TTY mode in Telecomm service
    • Increased gain for camcorder microphone
    • Increased gain for other mixer paths
    • Made time daemon MLS trusted subject
    • Restored contexts for directories during init
    • Set proper WiFi and bluetooth power configs
    • Updated operator info for CDMA variants
    • Updated SELinux policy and addressed denials

    23.12.2016:
    • Added missing camera parameters
    • Addressed SELinux denials
    • Created missing init directories
    • Enabled gesture settings
    • Falling back to L3 by removing liboemcrypto
    • Re-enabled fingerprint wake-and-unlock
    • Updated init and kernel ramdisk
    • Updated RIL SHIM library

    20.12.2016:
    • Cleaned up and updated media codecs
    • Created missing log directories
    • Defined actions to be executed during/after boot
    • Disabled camera CPP duplication
    • Disabled nonexistent media decoders
    • Disabled unsupported Qualcomm's flags
    • Enabled telephony IPv6 capability
    • Enabled the setgid bit on directories created by init
    • Fixed nandroid restores due to telephony data
    • GPS: Added android_runtime dependency
    • GPS: Cleaned up and updated GPS/location configs
    • GPS: Fixed missing Samsung sec-GPS configs
    • GPS: Fixed "Use of memory after it is freed" warning
    • Handled framebuffer hint for Ambient Display
    • Reverted "Allow Flashlight service to use wakelock"
    • Moved camera service to run on late start
    • Set appropriate permissions for time data
    • Toned down VM BMS logging level
    • Tuned system properties for graphics performance
    • Updated camera parameters and sysfs permissions
    • Updated and cleaned up SHIM libraries
    • Updated audio features and board flags
    • Updated graphics framebuffers permissions
    • Updated kernel cmdline for debugging
    • Updated QMUX daemon socket permissions
    • Updated Qualcomm's time services
    • Updated SELinux policy and addressed denials
    • Used the default number of surface buffers

    15.12.2016:
    • Addressed SELinux denials
    • Allowed Flashlight service to use wakelock
    • Built OMX libraries from source code
    • Cleaned up media codecs from white spaces
    • Disabled fingerprint wake-and-unlock
    • Enabled Qualcomm's DivX video decoders
    • Enabled Qualcomm's MPEG video decoders
    • Fixed fingerprint/home wake conflict
    • Fixed Google Home app crashing
    • Fixed Google Fit app crashing
    • Fixed graphics and media configs
    • Moved qcamerasvr service to main class
    • Re-configured radio access family
    • Reduced bootanimation resolution to speed up boot
    • Restricted ERI for CDMA carriers
    • Updated init services GIDs
    • Updated media codecs and profiles
    • Updated/Restored trlteRIL java class

    13.12.2016:
    • Added support for Substratum theme engine
    • Added system properties for Perf
    • Allowed all display rotation angles
    • Allowed interfaces to get v6 address for tethering
    • Cleaned up and organized system properties
    • Cleaned up and updated kernel ramdisk
    • Cleaned up CellBroadcastReceiver overlays
    • Cleaned up framework base overlays
    • Cleaned up SELinux contexts and escaped '.' character
    • Configured VSYNC phase offsets
    • Created Telephony Provider symlinks for legacy RIL
    • CyanogenMod 14.1 (Android 7.1.1 Nougat)
    • Disabled bluetooth by default
    • Disabled Qualcomm's location stack
    • Enabled extended video features
    • Enabled install non-market apps by default
    • Enabled IPv4 defrag and rpfilter support
    • Enabled IPv6 defrag and rpfilter support
    • Enabled PCM audio offload by default
    • Enabled SAP sensors for GPS use
    • Fixed MMS sending failure
    • Fixed offline charging animation
    • Fixed unknown phone number
    • Fixed unknown network / operator
    • Fixed Widevine DRM SHIM library
    • Forced reading operator-string from ERI XML
    • Increased maximum readahead to 512 KB
    • Increased media volume to 30 steps
    • Increased voice call volume to 15 steps
    • Moved ERI configuration files to CarrierConfig
    • Moved time_daemon service to main class
    • Removed duplicated system properties
    • Removed obsolete system properties
    • Removed old-apns-conf.xml APN list
    • Removed QTI telephony extension
    • Removed TelephonyProvider APN overlays
    • Removed unneeded Contacts overlays
    • Removed unneeded Keyguard overlays
    • Removed unneeded Messaging overlays
    • Removed unneeded Telephony overlays
    • Restored Samsung proprietary boot classes
    • Restored Graphics/HWC system properties
    • Reverted the custom bootanimation
    • Set correct permissions for tombstones
    • Set device provisioned by default
    • Set P2P preferred channel list
    • Set SELinux label for wifiloader service
    • Switched to CM charger libhealthd
    • Switched to unified LED capabilities overlay
    • Use 3 surface buffers to avoid timing issues
    • Used alternate ERI XML via init
    • Used HTTPS for GPS/XTRA2 download
    • Updated blobs (MMB29M.N910VVRU2CPJ2)
    • Updated all GPS/location configs
    • Updated and unified MMS configs
    • Updated build info from N910VVRU2CPJ2
    • Updated CarrierConfig overlay for all variants
    • Updated consumer IR HAL
    • Updated charging thresholds in uW
    • Updated doze and ambient display configs
    • Updated eMBMS configuration parameters
    • Updated media codecs and profiles
    • Updated Qualcomm's Adreno GPU drivers
    • Updated IMS/VoLTE proprietary blobs
    • Updated IMS/VoLTE system properties
    • Updated NFCEE access for Android 7.x Nougat
    • Updated servcies GIDs and SELinux labels
    • Updated SELinux policy and addressed denials
    • Updated system properties for audio
    • Updated system properties for media
    • Updated thermal-engine SHIM library
    • Updated vibrator/vibetonz sysfs permissions

    26.11.2016:
    • Enabled proximity check on screen wake
    • Enabled suspend when screen is off due to proximity
    • Increased the maximum size for MMS message
    • Reset MMS user agent string and profile URL
    • Updated AAPT/DPI configs and system properties
    • Updated security configs for Android 7.x Nougat
    • Updated SELinux and addressed denials
    • kernel: Addressed eMMC 5.0 spec violation
    • kernel: Disabled MSM DMA test module
    • kernel: Updated filesystem drivers
    • kernel: Updated EXT4 driver
    • kernel: Updated ecryptFS driver
    • kernel: Updated sdcardFS driver
    • kernel: Updated MSM camera driver
    • kernel: Updated MSM GPU driver
    • kernel: Updated MSM IPA driver
    • kernel: Updated MSM SoC sound codecs
    • kernel: Updated MSM SoC sound driver
    • kernel: Updated network drivers
    • kernel: Updated QSEECOM driver
    • kernel: Updated Qualcomm SoC driver
    • kernel: Updates from the latest source code

    25.11.2016:
    • Added custom telephony plugin
    • Added support for trltedt (SM-N910G)
    • Cleaned up CarrierConfig overlays
    • Cleaned up framework and boot class path
    • Customized telephony network values
    • Ported updates from Pixel XL images
    • Re-added custom bootanimation
    • Updated Android filesystem config
    • Updated ramdisk services groups
    • Updated SELinux policy and addressed denials
    • Updated SELinux rules for camera
    • Updated SELinux rules for CMHW/vibrator

    21.11.2016:
    • Disabled Samsung MTP
    • Fixed unexpected app crashes
    • Updated CarrierConfig overlays
    • Updated telephony overlays
    • Updated vendor proprietary blobs

    19.11.2016:
    • Fixed first/clean boot issues
    • Fixed media/Youtube audio issues
    • Fixed speaker and mic for voice calls
    • Optimized and cleaned up kernel ramdisk
    • Removed unused CM NFC feature
    • Reverted the custom bootanimation
    • Updated SELinux rules for the kernel
    • Updated filesystem mount options
    • Updated filesystem manager flags
    • Updated firmware GID and mount masks

    18.11.2016:
    • Added support for all Snapdragon variants
    • Added fs_config support for custom binary
    • Added custom permissions for pm, camera, and IMS
    • Applied a fix for emergency calls
    • Enabled reschedule/delay service restarts
    • Restored audio configs from Touchwiz
    • Updated media codecs for Nougat
    • Updated media profiles for Nougat
    • Updated RIL java class for Nougat
    • Updated WiFi configs for Nougat
    • Updated SELinux and addressed denials
    • Updated SELinux rules for media hacks
    • Used set_prop to replace deprecated rules
    • Custom bootanimation by @Creeper36

    14.11.2016:
    • Enabled audio features
    • Enabled Cell Broadcast settings
    • Enabled VoLTE bools
    • Hacked media for legacy blobs
    • Unified build for all variants
    • Updated SELinux policy

    13.11.2016:
    • Addressed SELinux denials
    • Fixed some errors/exceptions
    • Updated proprietary blobs

    12.11.2016:
    • Addressed SELinux denials
    • Fixed Widevine DRM
    • Restored audio effects
    • Updated media codecs
    • Updated bluetooth overlays
    • Updated telephony overlays

    10.11.2016:
    • Preliminary support for other variants
    • Updated audio configs
    • Updated bluetooth configs
    • Updated SELinux policy
    • Updated kernel source code
    • November security patches

    06.11.2016:
    • CyanogenMod 14.1 (Android 7.1 Nougat)
    [/QUOTE]
    187
    ROM Status

    Release Date:
    No ETA, but you could vote for a newer build by hitting THANKS to the announcement post of the latest build.

    END OF DEVELOPMENT


    Supported Variants:
    This ROM fully support US variants:
    • Verizon / VZW (SM-N910V)
    • T-Mobile / TMO (SM-N910T)
    • Sprint / SPR (SM-N910P)
    • US Cellular / USC (SM-N910R4)
    and
    • Canadian variant (SM-N910W8)
    International Snapdragon variants (SM-N910F and SM-N910G) need RIL/QMI fix. This can be done by flashing blobs from the latest firmware (cm-14.1-trltexx-fix_v3.zip) before flashing Gapps.


    Nandroid Backup/Restore:
    To fix nandroid restores (No SIM and Phone FCs) due to TelephonyProvider data/symlinks for using legacy RIL blobs on newer versions of Android 7.x+, you may wipe TelephonyProvider data by flashing this ZIP directly after restore and before rebooting to system.


    Required Firmware:
    The latest Android 6.0.1 Marshmallow firmware is required for all variants. Check your device/variant forum for firmware upgrade!

    VZW-ONLY:
    ROM Firmware Required: N910VVRU2CPJ2

    If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:

    This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2.


    Bug Reports:
    All bug reports should be posted here. I'll ignore the posts that don't include appropriate logs. Unfortunately, I don't have the time to respond to the PMs.


    Q&A:
    There's a linked thread for Q&A, general discussions, and pre-/post-installation chat. Please keep this thread clean and post there all your personal issues that are not related to the development such as Xposed, themes, extra mods, other stuff, ... etc.

    This thread is only for development, including bug reports with logs. All other topics should be moved to the new thread.

    Thank you for collaboration! That's how users could contribute to the development.
    144
    [ROM] [7.1.1] CyanogenMod 14.1 [Dec 13, 2016]

    I've added a new STABLE build to DEVDB Downloads.

    The ratio of THANKS to DOWNLOADs measures user appreciation and votes for development.

    Notes:
    • Clean flash (wipe system/data/cache/dalvik) is required.
    • You may also need to set default Apps and grant special access/permissions.
      In Settings/Apps, click the Settings icon and select "Show system" from the 3-dot menu, as needed.
    • Make sure that your preferred APNs are selected in Settings/Cellular networks.

    Read OP for general information and installation instructions! Changelog is in the 2nd post and ROM status including the required firmware is in the 3rd post.
    127
    [ROM] [7.1.1] CyanogenMod 14.1 [Dec 15, 2016]

    I've added a new STABLE build to DEVDB Downloads.

    The ratio of THANKS to DOWNLOADs measures user appreciation and votes for development.

    Some of you have down-rated the ROM, especially the Q&A thread. If you do appreciate this work and don't like the threads to get closed, please leave a 5-star rating to both threads! Only bug reports with logs belong to this development thread while all other topics and questions should be posted there.

    Read OP for general information and installation instructions/notes! Changelog is in the 2nd post and ROM status including the required firmware is in the 3rd post.