yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Are you on the latest build? Are you on the BPA1 bootloader and modem? Have you changed any kernel settings? Are you using the latest gapps? Do the random shutdowns happen completely randomly, or only while actively using the device? Are you using a different kernel from the one included with the ROM? Are you using any Xposed modules? Have you flashed any additional zips apart from the ROM and gapps/Xposed?

---------- Post added at 06:29 PM ---------- Previous post was at 06:16 PM ----------

Have you tried JasmineROM 4.3 to see if your problems persist on that?
[Verizon Galaxy Note 4 Android Development] DeadRubberDucky:
I am on the BPA1 bootloader and modem, my kernel is 3.10.40-g031695 hsbadr@multiSystem #1, and im on the latest build, have not altered any kernel settings at all, and the shut downs happen if i put it on the charger at times, if im using it, and even when the screen is just off. it doesnt matter when it will just shut off whenever it pleases and i have to pull the battery to restart. I am using Xposed modules but this happened before i installed Xposed, and before i was on CM13 i tried Jasmine rom and that shut off way more than CM13 so when i went over to CM13 i wiped everything and started from scratch installing CM13.

And nvm my battery is having the gaps problems again even after opt
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I'm at a loss for what else to suggest at this point. [MENTION=5868929]hsbadr[/MENTION] do you have any thoughts you might be able to provide?
[Verizon Galaxy Note 4 Android Development] testsubject00001:
This isn't an answer but try booting into trwp then charging it. If it shuts off it's an issue with the hardware, if it's fine it's an issue with the rom.
[Verizon Galaxy Note 4 Android Development] DeadRubberDucky:
I will try this thank you sir
[Verizon Galaxy Note 4 Android Development] testsubject00001:
Np. I meant kernel or bootloader not rom. Sry been drinking a little.
[Verizon Galaxy Note 4 Android Development] DeadRubberDucky:
So a funny thing happened.

I rebooted into trwp and plugged in my phone and it charged just fine with no lag issues no freezing so trwp is fine there's no problem there.

But when I went to reboot it said that my system did not have a OS to boot and my internal storage seemed to not be there, there was zero internal storage. So i rebooted anyway and it started with the note 4 screen and then shut off. So I pulled the battery and restarted it and it booted right up into cm13 and everything.
[Verizon Galaxy Note 4 Android Development] DeadRubberDucky:
OK so I think I figured out my issue.

I had realized that I had flashed over the BPA1 modem AFTER I had already flashed over and installed CM13, so I did another factory reset and reinstalled CM13 after the phone was in the BPA1 modem and everything seems to be fine now.

Sounds kind of dumb but could that have been my issue?

*update*

OK nvm what I just said cause right after I posted this my phone shut off...meh seems to be running better though regardless.

Could Chrome be an issue with mm or cm13?
[Verizon Galaxy Note 4 Android Development] hsbadr:
[ROM] [6.0.1] CyanogenMod 13.0 [Jun 20, 2016]

I've added a new build to DEVDB Downloads. This build uses proprietary blobs and configs from the latest Android 6.0.1 Marshmallow (N910VVRU2CPD1). You need to be on Marshmallow firmware/modem and bootloader (check this!).

WiFI Calling is enabled (and all required blobs/services are included), but not tested. It may just work or cause issues. I guess you'll have to enable Advanced Calling and WiFi Calling on your Verizon account.

For fingerprint, it works perfect for me and I added many fingers. You may just need, at the end of fingerprint enrollment, to swipe quilckly one more time so that you get two "Done" messages.

Changes:

If you'd like to support this work, you may donate here. If you couldn't donate, you can definitely hit the THANKS button bellow :good:
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Thank you so much for all your continued work!

*Downloads build to test*

---------- Post added at 06:56 PM ---------- Previous post was at 06:26 PM ----------

Did a clean install with appropriate marshmallow firmware and 6/19 nano opengapps. Wiped cache/dalvik immediately after flashing and before boot. I was relentlessly attacked by countless crash popups for Google Play Services and some Android media process. After finishing Setup (with more crash notification popups all throughout the process), I continued receiving them until I unmounted my microSD card (could be a coincidence?). I was then unable to launch the Play Store (crashes of Google Play services, android.process.media, and Google Play Store), and decided to try another clean installation without my microSD in the device to see whether that changes anything.

---------- Post added at 07:36 PM ---------- Previous post was at 06:56 PM ----------

While I go through the setup, after a short while it takes me back to the language selection screen (the first screen of setup) and presents me with a toast informing me that an English (Canada) SIM has been detected. I'm using the Verizon SIM that came with this device, so that can't be right. CM Updater also apparently crashes after my data connection starts up.

---------- Post added at 07:45 PM ---------- Previous post was at 07:36 PM ----------

Is anybody else having trouble with the latest build? Anybody not having trouble?

---------- Post added at 08:06 PM ---------- Previous post was at 07:45 PM ----------

Installation without gapps still yields me Settings crashes during Setup, and CM Updater still crashes upon connecting to Wi-Fi.

Placing a phone call (again, no gapps installed) crashes the phone app many times, but weirdly I still seem to be connected to the call and can hear call audio (have only tried this by calling my own number and my GVoice number).

I actually think Settings just crashes at random* intervals.
[Verizon Galaxy Note 4 Android Development] dhplap:
Hello, just reporting my results so far. First I flashed the new modem successfully, but when I tried to reboot it would get to the lock screen but wouldn't unlock the phone. Tried that several times with no luck. Then I rebooted into recovery and still have twrp and tried to reboot from there with the same results. I'm just gonna flash the new rom and nano gapps to see what happens. I'll report back. If I did something incorrect could I please have some help. Thanks
[Verizon Galaxy Note 4 Android Development] Bicknasty:
One great thing I can say is that rear camera performance seems to be flawless*. Even HDR is working perfectly now without any crashes upon toggling it!

When using the front camera, everything works fine except that the metering doesn't seem to be doing anything, as if it's always using the darkest settings. No auto-exposure with the front camera. There's a similar lack of auto-exposure metering that seems to exist with video recording, on both the front and back cameras.

---------- Post added at 08:29 PM ---------- Previous post was at 08:27 PM ----------

Have you upgraded to the new CPD1 bootloader, or only to the new modem? You need both of them. It sounds like you're coming from an older build of CM, and upgrading to the new bootloader (iirc) requires that you go back to stock TW 5.1.1, so I assume you must have forgotten to upgrade and re-unlock your bootloader.
[Verizon Galaxy Note 4 Android Development] dhplap:
Hi thanks for your help, that's exactly what I did. I was on the 5/25 build and just flashed the modem. So am I still able to flash the BPA1 firmware now and start from scratch? If so do you know where I get the new bootloader? Thank you again.
[Verizon Galaxy Note 4 Android Development] vIgGeN7:
I am also having this issue.

Have not flashed new bootloader / only modem. 6.0.1 able to re unlock then using the same method as before to put your phone in dev?
[Verizon Galaxy Note 4 Android Development] civichater:
I have been running the latest build of Jasmine on new bootloader without issue, and I'm having the same multiple crashes after boot up
[Verizon Galaxy Note 4 Android Development] Bicknasty:
[MENTION=6987893]dhplap[/MENTION] and [MENTION=4855594]vlgGeN7[/MENTION] - You need to flash the full BPA1 stock firmware, re-unlock the bootloader as you did before, and then follow the remaining instructions in hsbadr's thread.

Once you've upgraded to and unlocked the marshmallow bootloader, you can flash TWRP via Odin and flash the latest CM13 build.

Be aware, in my testing it seems either that the build is very unstable or else I'm doing something horribly wrong.

---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------

Thanks for reporting your results. I'm also coming from the latest JasmineROM.

---------- Post added at 09:25 PM ---------- Previous post was at 09:06 PM ----------

Also, I've called other actual people and determined that calling any number can crash the Phone app, while still maintaining full apparent call functionality. The app crashes, but call audio still works on both ends of the call.
[Verizon Galaxy Note 4 Android Development] mbr007:
I did not have problem setting up with old build. But with new build for N910T/DOK2 Baseband, crushed on set up.
[Verizon Galaxy Note 4 Android Development] Asiangamers:
Confirm com.media bla blah crash also Google play crash as well... coming from jasmine rom :") did full clean :"(
[Verizon Galaxy Note 4 Android Development] dhplap:
Thanks Bicknasty. I flashed the stock restore bpa1 firmware but got a bootloop. Back on the 5/25 build now. I guess I should odin the official bpa1 firmware and start all over again. Could you tell me all of the problems you're having right now with the latest build? Thanks again for your help.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I think we need to use TouchWiz to enable WiFi calling. I'm going to try installing it in a Dual-Boot setup (if there's a safe ROM?). I'll enable it there and then test it in CM.

The Android instructions say an emergency address needs to be set up, and it doesn't look like it can be done from My Verizon: https://www.verizonwireless.com/support/wifi-calling-faqs/
[Verizon Galaxy Note 4 Android Development] Bicknasty:
All the problems I've encountered so far are detailed in my other posts on the previous page. The current build is just very, very unstable.
[Verizon Galaxy Note 4 Android Development] Asiangamers:
Hmm didn't see [MENTION=5868929]hsbadr[/MENTION] include this problem in OP....
[Verizon Galaxy Note 4 Android Development] dhplap:
Ok thank you again
[Verizon Galaxy Note 4 Android Development] Zacharee1:
You're lucky you can even get the phone to work with GApps, I tried 6/19 and 5/24 nano, and both of them gave me the Setup Wizard has stopped loop. Right now, I'm flashing the safe stock firmware so I can enable WiFi calling. I'm going to install CM13 with dual-boot afterward.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I wasn't lucky. I just spammed my way through dismissing the crash popups and eventually managed to complete the setup wizard after much frustration, which didn't end after the end of setup.
[Verizon Galaxy Note 4 Android Development] NJDEN:
I'm on firmware N910VVRU2CPD1 from this thread and I'm running the May 25 build. What I need to do in order to run the June 20 build is follow the directions in this thread to update the firmware? And upon updating the firmware I can simply clean flash the June 20 build?

I just want to make sure I'm following all this correctly before I go and flash the wrong thing.

---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------

edit,

actually never mind. I flashed N910VVRU2CPD1, but apparently I'm back on BPA1. Something got changed somewhere along the line here...
[Verizon Galaxy Note 4 Android Development] Bicknasty:
If you're sure you already have the CPD1 modem and bootloader, then all you'd need to do is flash this build in TWRP.

But I'd strongly recommend you wait for the next build to see if the myriad issues people are encountering are resolved. Now is not the time to move to a newer build.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
[MENTION=6485176]Bicknasty[/MENTION] I think I figured the SIM thing out. Make sure the language is English (United States). Once the Setup Wizard finishes, go to APN Settings. I noticed before that a StraightTalk APN was selected, so I selected VZWInternet instead. Now I've flashed CM again with Nano 6/21 before booting, which seems to be letting me go through the setup. I'll check the APN stuff again after.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Huh. How about that? I can verify that I do, in fact, have that problem.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I think I got the Media process ANR to go away too. Settings>>Apps>>Hamburger Menu>>Show System>>Media Storage>>Disable>>Force Stop>>Clear Data>>Enable.

It seems to have also fixed the Settings crash issue.

EDIT

I also cleared as much data as I could for each Google app, along with force stopping them. I'm not getting the random ANRs for them anymore, but I haven't tried opening the Play Store. I suspect, however, that the Media Storage crashes were the cause of everything.

EDIT AGAIN

I tried opening the Play Store. It crashed with an ANR, then the Media Storage ANR also came up. Weird.

I'm going to try the disable>>force stop>>enable method with the Google stuff.

---------- Post added at 04:14 AM ---------- Previous post was at 04:02 AM ----------

Nope. Play Store is still dead. I'm not sure what else I can try.

---------- Post added at 04:23 AM ---------- Previous post was at 04:14 AM ----------

I'm flashing JasmineROM in data-slot-1 to see if I can enable WiFi calling with it. I noticed something a little strange though. It says "OS Version: 6.0.1 Lollipop". Just a weird observation.

---------- Post added at 05:13 AM ---------- Previous post was at 04:23 AM ----------

JROM looks like it's hanging on activation.

---------- Post added at 05:47 AM ---------- Previous post was at 05:13 AM ----------

OK, I reflashed JROM, this time without the H-Vit kernel, and I got WiFi calling activated. I'm installing the Dual Boot Patcher app, then I'm going to go back to CM to test WiFi calling.

---------- Post added at 06:01 AM ---------- Previous post was at 05:47 AM ----------

After all that, I can't even test WiFi calling :p. If I turn on Airplane Mode, it wants me to turn it off. If I turn off the radio it thinks I'm in Airplane Mode.

---------- Post added at 06:05 AM ---------- Previous post was at 06:01 AM ----------

Yeah, this CM build is pretty buggy. The phone app crashes when I make a call, but still continues the call, like Bicknasty said. I still can't get the Google stuff to work. There are recurring ANRs.

---------- Post added at 06:30 AM ---------- Previous post was at 06:05 AM ----------

This completely fixed the Media Storage problem for me (I think): http://xdaforums.com/showthread.php?t=2760733

I can download files now. I did also add in disabling all the Google apps after Media Storage and Download manager, and then re-enabling them before turning GSync back on. I also cleared data.

---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------

I was hoping I would be able to use Aptoide to get apps instead of Google Play, but it force-closes too.
[Verizon Galaxy Note 4 Android Development] sulpher:
Same problems as Zach... but it seems to work fairly well without gapps. Manually added my contacts for now ;)
[Verizon Galaxy Note 4 Android Development] spy9000:
I'm getting consistent force closes as mentioned before. I made a backup before updating to this ROM and unlocking the new boot loader. Can we safely switch between backups if one backup contains the older boot loader/modem than what we are currently on?
[Verizon Galaxy Note 4 Android Development] sulpher:
yes you can switch, i just switched back to jasmine 6.0
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Jasmine 6.0 doesn't have the older bootloader
[Verizon Galaxy Note 4 Android Development] Zacharee1:
So Nano GApps doesn't work very well, but Pico just causes boot to hang.
[Verizon Galaxy Note 4 Android Development] sulpher:
Restoring a backup doesn't change your bootloader. If you want to revert you'll need to odin back to lollipop and reroot etc... if you flash a rom that worked on the lollipop bootloader without reverting you won't have working wifi.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I'm going to try with Full GApps next to see what happens and then maybe even (*gasp*) Stock (maybe replacing some of the system apps will help?), but I don't have much hope. I think we just need to wait for [MENTION=5868929]hsbadr[/MENTION] to release a fix.

For now, JasmineROM with DPI 500-520 works pretty well. UI Tuner from the Play Store can be used to individually reset any apps (except the Phone/Contacts app for some reason) that don't like the custom DPI.
[Verizon Galaxy Note 4 Android Development] spy9000:
I see, then we all just need to wait.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I get around the Phone issue by downloading the Google Phone apk.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
So I guess I should try flashing Stock then :p
[Verizon Galaxy Note 4 Android Development] Bicknasty:
To be clear, I was talking about on Jasmine
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Ohhh. Hmm. You install it as a system app?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Nah, just get the apk from Xda Labs and set it as default
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Hey it works! Thanks for the tip
[Verizon Galaxy Note 4 Android Development] dhplap:
So does the full cpd1 firmware have the modem included int it or do I have to flash that too? Thanks
[Verizon Galaxy Note 4 Android Development] Zacharee1:
The hybrid file in the bootloader unlock instructions does.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
It should include the modem. Flashing the modem over the full firmware shouldn't hurt anything though
[Verizon Galaxy Note 4 Android Development] dhplap:
Great . Thank you for your help
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I'm actually going to try flashing the Aroma GApps package. I'll list which apps I select when I post the outcome.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
The 06/20 build was very very broken. As someone who's used every build from 02/01 through 06/20, I promise you that this ROM usually presents a high level of usability and a respectable level of stability. The 06/20 build is the exception to that rule. The problems you've encountered have also been encountered by everyone else who properly installed the build.

The instability is understandable given that hsbadr is working to incorporate new firmware to resolve the major issues of previous builds and to implement wifi calling, and provide a greater degree of stability compared to the other builds from the past few months.

There is currently no functional build of CM13 that works fully on the unlocked CPD1 bootloader, but please stick around until hsbadr gets the next stable build out to us (and be sure to thank him when that happens)! When you've got a working build of this on your device, it runs like a dream. Don't let trying this out at the worst possible time ruin your outlook on Cyanogenmod. I promise you'll love it once the new issues are resolved (I doubt it'll be an especially long wait)!
[Verizon Galaxy Note 4 Android Development] syrenson:
Many thanks to JoshH100 and Bicknasty for your prompt and thoughtful replies. Also, many thanks to hsbadr for his/her hard work on making this ROM available to the community. Taking your feedback into account, would the May 25th build be a good choice for a stable experience that allows use of the more common features (i.e. calling, messaging, Google Apps (Google Voice for Voicemail in particular), Wifi (data, not calling), and browsing)? Or is there perhaps an even older build that would provide a more consistent experience? Thank you again for your time and consideration.

Edit: Also, would your recommend starting with Gapps nano or pico versus stock or should stock work fine on these older builds?

All the best
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Flashing Stock causes problems. Anything below that and you're good. If you use any build older than 6/20, you'll have to downgrade your bootloader and modem to use it.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I would very strongly recommend only using nano gapps, as it's the smallest package that provides all functionality that you can't get through the play store. Pico won't enable OK Google, and larger packages install too many things to system without necessity.

The 5/25 build was perfectly usable, but was prone to significant overheating during more intense usage. Its camera was also usable but not wholly stable, and prone to lag. You'll need to downgrade to the BPA1 bootloader and modem to use builds prior to 6/20.

There's a thread in the snapdragon development section of the generic Note 4 forum with instructions on kernel adiutor settings that can improve battery life and performance. I've found those settings virtually eliminated overheating issues on 5/25. I don't have a link but it should be fairly easy to find.

You also might want to delete NfcNci from /system/app, as there's a belief among many of us (myself included) that it's been a source of overheating on those earlier builds.

For a very stable experience, the 2/14 build is a good choice. As I remember, it doesn't have any heating issues or camera problems, but it lacks fingerprint support. That was the main reason I ditched it for the testing builds released in the months since.
[Verizon Galaxy Note 4 Android Development] syrenson:
Thanks again for the very informative replies. It sounds as if it may be in my best interest to wait until a debugged post-6/20 build is available. If the process of downgrading the bootloader and modem is as onerous as unlocking the original bootloader (and, in particular, if it risks possibly losing the unlocked status) I'd prefer to forego that exercise. This said, would someone mind pointing me to instructions on this if such exists?

For education sake, could someone also explain why a CM13 mod based on Adroid 6.0 requires an older bootloader than the one currently on my phone, which is running Android 5.1.1? That is, provided such an answer isn't too much of a chore. I am obviously still a bit green at this but I am looking to learn as much as possible. Thanks to everyone again for your time and assistance.

All the best
[Verizon Galaxy Note 4 Android Development] Bicknasty:
As long as you don't upgrade your bootloader to anything past the current CPD1 bootloader, you're safe in terms of future unlocking, as CPD1 can still be downgraded to BPA1, which is unlockable. The only risk would potentially be from ever using retail firmware after marshmallow CPD1. DO NOT do that.

If you're currently on the unlocked marshmallow bootloader, then you basically already know all you need to know about changing and unlocking bootloaders. To downgrade to BPA1, you just need to download the full BPA1 firmware and flash it through Odin, and do a full factory data reset in the stock recovery. Then you'll unlock the lollipop bootloader the same way you did before.

Basically, a ROM is built on a certain bootloader/modem for use with that firmware. For all builds before 6/20, BPA1 (5.1.1) was the most recent firmware, so they were built to be compatible with that. Now that the marshmallow stock firmware is available, hsbadr is trying to work toward compatibility with that firmware to enable newer features/drivers, and generally improve stability. So you'll get issues using a ROM with bootloader/modems they weren't built against
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I'm not sure.