yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] outpost785:
Sorry if this has been ask but anyone have advanced calling working or toggles somewhere
[Verizon Galaxy Note 4 Android Development] Zacharee1:
No, and it's probably not going to happen.

Verizon's system is just too proprietary.
[Verizon Galaxy Note 4 Android Development] Jakib2:
do you have an aftermarket battery? https://www.amazon.com/gp/product/B00RRF385U/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1 This one gave me similar issues.
[Verizon Galaxy Note 4 Android Development] xflbret:
No, a Sumsung-branded battery. I'd love to blame the battery for all these headaches, but I am using the exact same battery in the Jasmine ROM...
[Verizon Galaxy Note 4 Android Development] Zdizzlerizzle:
Install Jasmine 7 with the provided TWRP backup, flash the partial firmware update, and let it fully boot into jasmine. Then clean flash cm and gapps. Flashing cm directly after the firmware is removing what you just flashed lol
[Verizon Galaxy Note 4 Android Development] xflbret:
That's exactly what I did in one of my attempts, attempt number 4 I believe.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
If you have an SD card, take it out and see if that helps.

I did actually have that shutdown issue you just described. It was when I was draining my battery. You say it works fine on JROM, but maybe it's a quirk with the CM kernel or something that occurs when your battery is bad. Buy an Anker and see if it fixes anything.
[Verizon Galaxy Note 4 Android Development] xflbret:
Anker?
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Anker battery. Much cheaper than OEM and arguably better.
[Verizon Galaxy Note 4 Android Development] rmc198501:
Just flashed over to 7/24 I'm liking it seems much smoother. I haven't tryed out GPS yet. I knew about the camera from trying out other builds so I knew to DL open camera. Only negative thing is the same issue I've had on tw ROMs is my clock time would change to hours ahead of the real time. I went into twrp and it got changed aswell so I put it back on my current time zone. I'll report back if it does it again
[Verizon Galaxy Note 4 Android Development] Rojikku:
I came from here, following the guide on the first page. http://xdaforums.com/note-4-verizon...ck-n910v-6-0-1-to-t3426905/page9#post67985717

My issue is posted near the end, but I'll explain it once more.

I run linux- to use Odin I run windows 10 in a virtual machine. The VM crashed when I was flashing the "Pateched" kernel after restoring Jasmine. The second and third time it failed, but Jasmine booted, so I assumed maybe the first one worked, and went along with the rest of the guide. However, I went to install XPossed as the guide says, and couldn't boot. Namely, it played the boot animation for a while, then the screen turned black, the phone vibrated once (short), and then was "bricked". I pulled the battery and it went back to being able to load Recovery and Download mode. I then did a bunch of wipes and installed CM and Gapps, worked fine. But I tried encryption and it did the same thing. Assuming encryption was at fault, I did it again, and didn't use encryption. I went to do a backup, went fine- tried to boot afterwards, same thing. Thus I assume I cannot start the phone after the first boot with CM.

I was told I had to install Jasmine and the Patched first, for drivers and such. So I went to do that again, to find I can't flash Pateched. I redownloaded it, but I have the same thing. It says "There is no PIT partition". I do not know what to do about this.

I wiped System/Data/Cache/Davlik, restored Jasmine (Which goes to system), and then wiped Cache/Davlik as the guide says. I then loaded up Odin, selected AP, selected Pateched, mounted my phone to the VM, the phone showed up in Odin, I hit start, and it said "There is no PIT partition". I believe that is everything. I suppose my foremost issue is I can't flash Pateched- and anything else can be temporarily assumed to be related to that.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Try looking that up. I think there's a way to restore, but I don't know how.
[Verizon Galaxy Note 4 Android Development] Rojikku:
I have no idea what you're asking. I also have no idea how to phrase my question (And thus successfully google it). I tried looking up the PIT thing, but honestly, none of the results sounded relevant. There was some stuff about the Odin version, but the guide uses the same one, which seems to be the latest- being 3.12.3. Most of them weren't even for the same phone. I have no idea what a "PIT" is, to begin with- but I assumed it was something that would be restored when I ran the Jasmine restore.

EDIT: I could try flashing FullFirmware again (Step 32), and then following the guide again from there, if that would give me back the PIT...But I have no idea what the PIT is, and it seems relatively risky to do that without someone giving me a "That might work".

EDIT 2: Further research indicates the PIT is very very important. Definitely waiting on confirmation.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Try looking up "ODIN error no pit partition"
[Verizon Galaxy Note 4 Android Development] Rojikku:
Ironically, that solved my issue. I saw someone mention "Make sure kies is closed"- and though I don't have kies installed, I let my phone try to install the software it wanted- and that autostarted a verizon thing, which caused my issue. That or running it as administrator fixed it, one of those. Now that I have the patch, I can consider that issue solved- and if I run into the CM not booting after reboot issue and find it's unrelated to this one, I'll post again on the thread.
[Verizon Galaxy Note 4 Android Development] Rojikku:
http://xdaforums.com/note-4-verizon/general/guide-step-step-stock-n910v-6-0-1-to-t3426905

Alright. I followed these instructions perfect up to step 56. I let my phone do its setup. I then rebooted my phone. This was just to test that I could. In short, I could not. It rebooted fine and all, but after playing the boot animation for a minute or so, the phone vibrated, I looked down, the screen is blank, and it does not respond to anything. Holding the power button does nothing. Holding the power and home button does nothing. Holding power, home, and a volume button does nothing. I know from experience if I take out the battery and unplug my charger, and then put them back in, it will let me go into recovery and download mode. However, my phone will not boot.

I imagine this has something to do with the ROM, though I won't swear by it, considering I never had to reboot when I was using Jasmine. I would prefer not to have to wipe my phone again, but I will do what needs be done. (Honestly, the setup process gets tedious after the fourth go around.)

Edit: I might mention I would love to google this, but I have no idea what to call it. Thus why there's a paragraph of description. Paragraphs of description aren't google-able.
[Verizon Galaxy Note 4 Android Development] happy2472:
why would anyone have to flash jasmine then a partial something or other and then CM ? I was trying to follow it all and it didn't make sense to me ... 7/24 is the latest build?
[Verizon Galaxy Note 4 Android Development] Rojikku:
2016-07-23 23:20 which is almost 7/24. According to whatever time my account is on, I presume. But I have the latest build, yes. As for the Jasmine, Partial, and then CM? I was told it had something to do with the drivers.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
You do not need to flash Jasmine at any point in the process of unlocking/upgrading the bootloader and installing this ROM.

The CPF3 partial firmware is important. A full flash of Jasmine is redundant.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
You don't have to flash Jasmine, but the partial firmware for CPF3 is recommended.

---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------

Do you have an SD card?
[Verizon Galaxy Note 4 Android Development] Rojikku:
I do have an SD card.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Try taking it out.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Unplug charger, remove SD card, remove battery, return battery, turn on phone, boot animation for roughly one minute, screen turns off, vibration of phone, returned to "brick"ish state.

I tried this before, I might add. But I couldn't be certain nothing changed, so I have tried it again, as indicated by the account written as it was happening.

Got any other ideas? I'll try them all.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Try flashing complete Stock MM? You can flash the Stock LL firmware afterward, which will keep you on the MM bootloader, and restart the upgrade process. You can't downgrade the bootloader, so you'll have to use the firmware without it.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Mercy. What's MM? What's LL? I have TWRP right now. I know what CM is. I know what stock is. I don't have any idea what Stock MM and Stock LL are.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Marshmallow? Lollipop?
[Verizon Galaxy Note 4 Android Development] jlavallee25:
I have experienced complete data and signal losses twice while on the phone.

I also have intermittent Bluetooth connectivity issues with my moto 360 and possibly my roadster

Battery seems to drain very quickly

Otherwise this is a rock solid build wish updated blobs would be released so most of my issues would be fixed
[Verizon Galaxy Note 4 Android Development] masterzoltar:
27th build works flawlessly for me. the only thing not working is all phone calls in call history show as unknown unless in my contacts.
[Verizon Galaxy Note 4 Android Development] jlavallee25:
Are you using Bluetooth? And what does your battery life look like?
[Verizon Galaxy Note 4 Android Development] gcounts:
On the 27th build, I've experienced data drops a couple of times, unknown caller except for those in contacts, battery is about the same as other cm13 builds, Bluetooth is stable for me, and g+ works. I dirty flashed, I'm running a cm13 theme, and I'm using gravity box. All in all its a solid build. Thank you hsbadr!
[Verizon Galaxy Note 4 Android Development] masterzoltar:
yes blue tooth good and battery is excellent. I started having issues today with proximity sensor not working during calls.
[Verizon Galaxy Note 4 Android Development] gcounts:
I have never had working proximity on any cm13 builds. I even tried the fix from the tmo side and that caused other issues.... I've learned to hold my phone a certain way until a fix comes along.
[Verizon Galaxy Note 4 Android Development] masterzoltar:
I guess it's speaker time.
[Verizon Galaxy Note 4 Android Development] hsbadr:
Happy New Year!

It's a new year and a new build has been added to DEVDB Downloads.
[Verizon Galaxy Note 4 Android Development] jared2876:
(1/2 build) The rom has been great for me but i am still getting data drops. Other then the data drops, this rom is really good and i like it. The data drops are showing up in a couple apps and when browsing the internet including chrome.
[Verizon Galaxy Note 4 Android Development] shaggyskunk:
Anyone having issues with SwiftKey or SwiftKey Beta running this Rom?

It started to be an issue with some of the more recent cm commits - SwiftKey Neural and Google & AOSP keyboards work fine.

Sent From My SM-N910W8 Running CMRemix 6.01
[Verizon Galaxy Note 4 Android Development] gcounts:
I haven't had a data drop yet...my GPS is working again, my proximity sensor still isn't working.....but thats about all that's wrong atm. I too like this ROM, and will stick with it.
[Verizon Galaxy Note 4 Android Development] jared2876:
Out of curiosity how have you been upgrading when roms come out. Have you been doing dirty flashes or clean?
[Verizon Galaxy Note 4 Android Development] gcounts:
I did clean installs until the 12-27 build, which I dirty flashed, and the 1-2 build I dirty flashed as well.
[Verizon Galaxy Note 4 Android Development] jared2876:
I'm just trying to pinpoint why everyone seems to be getting sable data connections but I'm not lol.
[Verizon Galaxy Note 4 Android Development] gcounts:
Yeah... It doesn't seem to matter for me...my data would go in and out but it seemed more prevalent in weak signal areas that I drive through.....it seems like other devices on cm13 are having the same issues as us....or worse.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Does anyone know if the TMO or ATT users are experiencing the data drop or is it just Verizon?
[Verizon Galaxy Note 4 Android Development] jlavallee25:
Thank you for the continued work!! I noticed that this build was 40mb larger then the last anything particular that added to the size?

I'm still experiencing data drops as well

I'm not seeing any issues on my end and it's my default keyboard.

---------- Post added at 09:02 PM ---------- Previous post was at 08:46 PM ----------

I'm also having problems with Bluetooth staying Connected to my watch.

My battery life seems awful with all of the cm builds I've tried

After about 5 hours with very limited use
[Verizon Galaxy Note 4 Android Development] DrPhant0m:
I've had issues with the phone freezing on a black screen... particularly overnight while charging on my wireless charging pad. This affected the 12/17 and 1/2 release so far. (12/17 was the first build I have tried) The 12/27 build did it within minutes of initially flashing the ROM, and then not again... but it was only a few days before I dirty-flashed the 1/2 release. I don't remember if the phone was plugged in at the time or not (in case it has anything to do with charging).

It happened this morning, so I pulled the battery and plugged it back in. When the phone booted, I was greeted with a notification that a bug report had been prepared, which I opted to email to myself. The bug report contained a screenshot (it was 100% black... which is important in its own way) and a text file containing 266,175 lines.

Does anyone here want/need to see the bug report? Or... is there a quick way to tell me what to look for to offer anything of use? If you view it in notepad, you'll go crazy. Use Notepad++ or similar to keep the intended formatting.

Quote me or PM me so that I'm sure to get notified.

Thanks
[Verizon Galaxy Note 4 Android Development] cursixx:
using this rom as my daily driver, over all its working and performs really well.

but

I'm having the same problem as DrPhant0m. This is with a clean install of 1/2 build. phone will freeze, vibrate and go to a black screen. requires a battery pull. it seems better on the 1/2 build. happening 2-3 times a day.

seems to be random for me. happened mostly while the phone isn't in use but has happened while using it too.

I've never been prompted about a bug report. i'm willing to send any logs etc you would need. just give me the details
[Verizon Galaxy Note 4 Android Development] jlavallee25:
I too experienced this today with the 1/2 build on a clean install. Does anyone have a link to the AICP build I can't seem to find it and my SD card died the other day with my backups.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Gotcha... I have the stuff from the thread I originally linked. So..

N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5

N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)

JasmineROM_v7.0_N910VVRU2CPF3.7z

N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z

Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)

UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)

Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)

That. I believe I downgraded the bootloader when going through the guide, considering it changed from having just "Yes" and "No" in the factory reset confirm, to having about ten "No" and one "Yes". There were also some minor font changes.

I can flash things if you'll guide me, but I can't form an image of what you want from me. I can flash stock something- though, if I may, why am I flashing stock? I did the whole "Get a developer CID" thing, and "Install TWRP"- what does flashing stock give me that I seem to be missing?

Edit: I kind of got distracted midway, but I honestly wanted clarification on if those were the right files, which order to do them in, and what effect I was looking for.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Go into Download Mode and flash that first file with ODIN. It'll overwrite everything on the phone, so make backups and move them off the internal storage. That'll put you on 5.1.1 but with the MM bootloader. Everything will work normally (and you'll even have split screen mod).

Root with KingoRoot (not KingRoot) desktop. KingoRoot desktop is a bit more stable in my experience, and KingRoot didn't work for me when I had to do this downgrade.

Do the unlocking process and get TWRP installed. Remember, your SD card will be formatted. You'll also have to remove it before you try to boot. Flash the second file (the hybrid firmware) with TWRP. Clear cache and shut down.

Go to the menu you get when you press all three buttons and do the factory reset. Boot into the hybrid firmware and root again. Do bootloader unlock again. TWRP will stay installed.

ADB push or copy all the other files to your phone.

Reboot to TWRP and wipe System, Data and both cache options. Leave Internal Storage and SD Card alone.

Flash CM, clear cache, then flash GApps and clear cache again. Also flash Xposed and, you guessed it, clear cache. Go into Download Mode and flash the PatchedKernel firmware.

Reboot into CM and set up. Hopefully, going full Stock and back to CM will fix anything that messed up.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Sorry, I'm stuck on "Flash the second file with TWRP". I thought it was a bit odd since I originally flashed it with odin- Being FullFirmware- but I tried it anyway. It doesn't show up despite it being in the Download folder...Presumably because it's the wrong file type. Am I missing something? Did you perhaps mean the third file, JasmineRom? Or is there some way to convert this file? Or maybe you meant to flash it via odin, and then flash TWRP again?

Edit: Wait, you could have also meant the partial firmware...The problem is "The second file" also has the word firmware in it, so I can't be sure of that either! I'm probably way overthinking this.

Edit2: Uh...So turns out maybe that step was important, because I skipped it, and...Well...It's very interesting. I have the cyanogenmod head and the...The little ring around it just keeps pulsing faster and faster, and now it's basically a strobe light. No idea why. I can't even begin to comprehend the reasoning behind this.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Flash CM again and reboot without changing anything else. Report back.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Aha! Optimizing app 8 of 16! I don't know if the gapps are still there or not. What do I do now?

Edit: Okay. Went through setup, since you didn't say anything.. It seemed to go fine. I didn't wait for it to download everything, then restarted it. Optimizing apps again. Dunno why...Hope it doesn't do this every time, but there's a decent change it won't- probably.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
They aren't still there. The problem was that you flashed the partial firmware over Cyanogenmod, which overwrote the kernel with one incompatible with this CM13.

If you wipe /system and flash CM13 and NANO open gapps again, you should get some smooth sailing.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Well, I can do that... Though I don't know if that will solve my original issue of the phone "bricking" after I reboot. Should I absolutely wipe /system and do that, or should I see if it's working okay as is? Because as far as I can tell I hage gapps- at least, it let me login to my google account...And I also have the play store.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
You should still do it. It's bad practice to flash a ROM over gapps. You might be fine, but play it safe.
[Verizon Galaxy Note 4 Android Development] Rojikku:
I appear to be able to reboot fine now. It seems to have a habit of doing "Android is starting... Starting apps" But my issues could be way worse. Though, if someone knows something about that, I'd be glad to hear. Still a small chance it's only doing it because of how fresh my install is.

I'll hopefully get everything working how I want it after a couple hours of tinkering with all the apps. Side question: What should I do for root? Like, SuperSU? Don't you generally use an app to manage what apps get root? What's considered the best right now? And if SuperSU, should I do the flash from TWRP for its binary, or what?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Enable root in developer options. Only use supersu if that doesn't work well for some reason
[Verizon Galaxy Note 4 Android Development] Rojikku:
I know about that- but if I like SuperSU better, should I flash the binary? Or should I just use the app as-is?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I've actually never tried SuperSU on CM13, so I'm not qualified beyond saying that you should stick with the stock root options unless you feel you need SuperSU
[Verizon Galaxy Note 4 Android Development] Rojikku:
Okay, thank you. Actually, it's doing the reboot thing again... I wonder if that's because I tried to use the superSU APK... Because it seemed to be working before I did that. Though I did do a couple other things.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
A clean flash of CM13 and nano gapps should be done to narrow the cause of the issue.
[Verizon Galaxy Note 4 Android Development] Rojikku:
Optimizing app 49 of 113... Obviously it doesn't remove my installed apps that easily. How fix? Otherwise I think my test is a bit biased.

EDIT: Okay...apparently all the apps I wasted time optimizing don't exist.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
That's perfectly standard. It has a very loose definition of "app", I'm sure.
[Verizon Galaxy Note 4 Android Development] Rojikku:
I see. I installed Nova Launcher and SuperSU. I rebooted several times, and it seems to work fine, which is strange. I'll see if I can't get the damned thing to reproduce my issue.

EDIT: AHAHAHA! I reproduced it! I uninstalled SuperSU, installed a theme, switched to the theme, enabled developer options, enabled root, and changed my hostname. ONE OF THOSE causes the issue. Now for more debugging.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Anecdotally, I think it's good practice to reboot after installing a theme. Just anecdotally, though.