yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] swizard210:
It's not stupid at all! In fact, I actually did NOT have root turned on in the developer options. So thanks!

Unfortunately though, I just did it, and then restarted my phone, but still it showed the same problem. I even again re-flashed the SDK Arm and reinstalled the apk, and restarted afterwards, but again, that didn't work either. =(

This is the Xposed Error Log:

04-26 09:26:18.582 I/Xposed ( 427): -----------------

04-26 09:26:18.582 I/Xposed ( 427): Starting Xposed version 82, compiled for SDK 23

04-26 09:26:18.582 I/Xposed ( 427): Device: SM-N910V (samsung), Android version 6.0.1 (SDK 23)

04-26 09:26:18.582 I/Xposed ( 427): ROM: Android 6.0.1 Marshmallow N910VVRU2BPA1

04-26 09:26:18.582 I/Xposed ( 427): Build fingerprint: Verizon/trltevzw/trltevzw:5.1.1/LMY47X/N910VVRU2BPA1:user/release-keys

04-26 09:26:18.582 I/Xposed ( 427): Platform: armeabi-v7a, 32-bit binary, system server: yes

04-26 09:26:18.582 I/Xposed ( 427): SELinux enabled: yes, enforcing: no

04-26 09:26:21.488 E/Xposed ( 427): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
[Verizon Galaxy Note 4 Android Development] dynamix911:
2/1 is stable but the camera is bad has trouble focusing and it's super grainy doesn't take good pics. Is there anything I can do to improve the camera ? Or it is what it is until it gets updated
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I'm not experiencing that with my camera. You can try a different camera from the Play Store.
[Verizon Galaxy Note 4 Android Development] kerfex:
The SPen

First go to the play store and download the program called CM Spen Add-on. The purchase S pen command. http://www.emandt.net/Android/SPenCommand/Website/
[Verizon Galaxy Note 4 Android Development] swizard210:
As per some other threads, I went and deleted the /data/data/de.robv.android.xposed.installer/conf/disabled file, but like 80% of the time I try to restart my phone, it just gets stuck on the CM Logo Loading screen. And then 10% of time it gets past it and goes to "Optimizing Apps" which literally takes like 45 minutes to an hour to get past. And the last 10% of the time, it actually just go right into the actual home screen. So from all of these tries, that file stayed deleted and Xposed worked ONCE. Every other time, I either never make it to the home screen, or after the "Optimizing Apps" thing, the /data/data/de.robv.android.xposed.installer/conf/disabled file comes back, and I get the same error in Xposed.

Am I doing something wrong? I'll hard reset/wipe and start over, but I want to make sure EVERYTHING is done exactly right to reproduce a successful outcome, since I've tried deleting and re-flashing everything multiple times now and I keep having the same problem. =(

Please help! Thanks!
[Verizon Galaxy Note 4 Android Development] hsbadr:
[ROM] [6.0.1] CyanogenMod 13.0 [Apr 26, 2016]

I've added a new

testing

build to DEVDB Downloads.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
What's new?

Edit:

And welcome back!
[Verizon Galaxy Note 4 Android Development] hsbadr:
It includes upstream CyanogenMod changes since last build (Mar 31 - Apr 26), device-specific updates (kernel tweaks and under the hood changes), and possible fixes for the reported issues.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Hopefully a possible fix for the camera issues? I'm downloading the new build now; will flash and see how things go. Appreciate the work you do!
[Verizon Galaxy Note 4 Android Development] hsbadr:
Yes, Camera/video recording issues have been fixed. You need to post meaningful logs via logcat or any other utilities if you run into any issues!
[Verizon Galaxy Note 4 Android Development] Bicknasty:
One thing I immediately notice is that that's (edit: by far) the fastest boot (from Samsung logo to end of boot animation) I've yet seen from any of these builds, having tried 2/1, 2/14, 3/23, 3/29, and 3/31. Feeling good about performance.
[Verizon Galaxy Note 4 Android Development] dynamix911:
How is the camera/video? When i was on 2-1 build it worked but the picture was very grainy and had issues with focusing. It did a better job in the daylight but the picture quality seemed a bit off.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Haven't had the ability to do much proper testing. Video recording after a minute or so of testing seems to function properly. Using the camera flash, it seems to keep the flash on, fails to take a picture, and requires me to close the camera app to fix the issue. Picture-taking seems to be generally finicky, but not grainy. I've had a camera-caused forced reboot on this build, but not while connected to usb charger, so make of that what you will.

---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------

On further testing, the CM camera app is pretty grainy compared to the Google Camera (installed when flashing OpenGApps). So far Google Camera seems pretty stable for stills, and only CM camera has actually forced reboots for me.

---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------

And it seems that the Google Camera fails to connect to the camera when attempting to capture video. So basically it looks like Google Camera is good for still capture and non-functional for video, while the reverse is true of the CM camera.

---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------

Soft-rebooted after clearing Google Camera app data, and now I can record video (but not at UHD, only at 1080p) in that app. Camera flash functions properly in Google Camera.

Note that when I describe what I've done in testing the camera, it is to provide context and not an attempt to provide a user guide. I basically have the sense that one should not use the CM camera app with this build.
[Verizon Galaxy Note 4 Android Development] dynamix911:
Thanks your your input what you describe is what i was experiencing in the 2-1 build.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
update: Google Camera can force a reboot still. Took a picture while HDR was on, flash off, and 3-second timer. Will take a look into logcatting to see if I can actually capture logs from one of these events when they occur.

edit: on a different note, still getting the system process stopped responding popup on boot. It still seems to be meaningless.
[Verizon Galaxy Note 4 Android Development] douger1957:
Crap. I just got 2/1 loaded up and it seems to be stable. I'm not sure I want to go back to flashing ten ROMS a week like the old days. :p

If it fixes the frying of SD cards when trying to format for internal it might be worth it.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I don't think you're missing much by staying on 2/1 build. I've stayed on the 2/1 build, it's fast, stable, and everything works.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
If you're set up on 2/1, I don't think you should consider upgrading to any build that hsbadr doesn't label as stable.

---------- Post added at 04:07 PM ---------- Previous post was at 03:57 PM ----------

I ran a logcat leading up to a camera-related forced reboot. What's the best way to post the log?
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
What's the difference between a "testing" build and a "nightly" ? Is one 'more stable' than the other? Or are they same?
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
A testing build has not been "tested" enough to be determined to be "stable". There may be major/minor "bugs" in a testing build.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
So is it the same thing as "Nightly" in terms of stability?
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I don't know how much testing goes into a nightly, so, not sure.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Is 2/1 a Nightly or Stable release? If it's Nightly, I might as well just give the new build a chance.
[Verizon Galaxy Note 4 Android Development] dynamix911:
Pastebin and then post it on here from the pastebin link i would assume.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I think hsbadr has labeled it stable.
[Verizon Galaxy Note 4 Android Development] ct_tec313:
Has anyone successfully used the fingerprint to log in to any apps tried to find the setting so i can use it with chase bank to no avail

any help would be much appreciated
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Here's what logcat gave me leading into a camera-forced-reboot.

http://pastebin.com/Zcur8bVv
[Verizon Galaxy Note 4 Android Development] sportytony:
please delete post as there has been no help. But I believe I figured it out. Donating anyway as this has always been a go to rom over the years confirmation 0M628403YP437651V
[Verizon Galaxy Note 4 Android Development] HORIZONx720:
The newest build fixed the battery drain issue I was having so definitely a good job OP just one problem is the camera likes to crash when using flash most of the time. Going to do some testing with open camera and google camera later today so will report back.
[Verizon Galaxy Note 4 Android Development] cylamanae:
A few things are missing on the new build unless I have a bad download no pull down settings and not getting notifications other than that a solid ROM
[Verizon Galaxy Note 4 Android Development] Cauterized:
I had no issues with camera flash on the new build but I am experiencing the no notifications and no quick settings bug (clean flashed the ROM twice) Phone also was overheating right away, got up to 100f before I decided to go back to 2/14
[Verizon Galaxy Note 4 Android Development] NJDEN:
So far the 2016-04-26 ROM has worked really well for me, but with a few issues.

Camera Flash - Both image and video taking are fine; however, whenever flash is involved it becomes significantly less stable.

Recents & Volume Button (Buttons to either side of home) - Both of these buttons continue to deliver haptic feedback when pressed if the phone is locked and display is off. They do not light up, only cause the phone to vibrate. As of this moment the buttons only allow feedback for a few seconds after a screen lock which is strange... I could have sworn they remained active indefinitely after a screen lock when I went to bed last night. If it is only for a few seconds then this issue becomes much less annoying, but still slightly annoying.

I'm not real concerned about the flash, but I would like to know if anyone else is experiencing the issue with the buttons remaining active (even for a brief period). Is that normal for everyone on this build, or just something I'm experiencing?
[Verizon Galaxy Note 4 Android Development] kerfex:
Which Build? I have great battery

OK, I think the issues everyone is having is because the did not take the OTA updates and are are trying to root and update and patch all kinds of modems, etc. I took all of the OTA updates along the life of the phone and did my root and dev conversion from the factory BPA1 . First try off the bat no problem. I also do not use the latest TWRP, I found the 2.8.7.0 build to be the most stable for our phones. OK that being said:

I use the CM-13 - 02/14/2016 build. I have Xposed installed and that is the regular Xposed for ASOP. I use the 80 build framework as the newest 82 build is buggy and does not work with the latest Google Play Services. After getting Xpsoed installed I set up Greenify. That alone with the built in DOZE and I get outstanding battery life.

Yes it does, the kernel is the kernel in the build. :) I have not tried the multi system kernel because I do not want muti-system. The only other kernel I have knowledge of is the Sprint kernel. I'll stick with the one compiled for our phones. So the one in the ROM. So the most stable kernel I have found is the 02/14/2016 build's kernel. Then you said you get bad battery life and I described what I use in order to get great battery life. Hence the Xposed framework 80 build along with grennify and you'll have good battery life.
[Verizon Galaxy Note 4 Android Development] happy2472:
I'm not sure if you were referring to me with what you said because nothing you said is related to my issue and or question??
[Verizon Galaxy Note 4 Android Development] kerfex:
Don't use 82

The 82 framework is buggy, use the 80 build. Works perfect.

---------- Post added at 03:12 PM ---------- Previous post was at 02:46 PM ----------

Yes it does, the kernel is the kernel in the build. :) I have not tried the multi system kernel because I do not want muti-system. The only other kernel I have knowledge of is the Sprint kernel. I'll stick with the one compiled for our phones. So the one in the ROM. So the most stable kernel I have found is the 02/14/2016 build's kernel. Then you said you get bad battery life and I described what I use in order to get great battery life. Hence the Xposed framework 80 build along with grennify and you'll have good battery life.
[Verizon Galaxy Note 4 Android Development] nbock01:
Question, what is the DPI setting (default) in this rom?
[Verizon Galaxy Note 4 Android Development] happy2472:
Well my friend I apologize then ... also I want to try the new update to this ROM but currently I'm using Kyubi and I'm more then happy it's an amazing ROM. .. if I get bored I'll make a TWRP backup and flash the update. Thank you for the advice.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Sorry for the noob semi-off topic question, but is there a quick/easy way to back up all of my apps between different ROM flashes? With TWRP and/or Titanium Backup Pro? Please either explain or link me to a thread or page or video. Thanks. I need to revert to another build but had enough problems trying to get Tapatalk to work correctly and I don't really want to lose my settings for that app amongst others.
[Verizon Galaxy Note 4 Android Development] kerfex:
No Need to apologize

No need to apologize my friend! The Kyubi ROM is excellent! Enjoy! I just really missed CM, so I am playing with that for now.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I hate to tell you this but there is no sure-fire method/app of backing up apps and data that will be perfectly restored on a new/different ROM. Backing up is easy...any number of choices to do that. The problem most often is using that backup on a different ROM. That usually always has issues. It's a PIA, but fresh install of apps in a newly flashed ROM is always best.
[Verizon Galaxy Note 4 Android Development] happy2472:
I found if you use titanium backup ... when you restore anything in red is NOT compatible. TWRP is the same if you restore apps set for 5.1.1 and put it 6.0 it I think will cause issues. I could be wrong.
[Verizon Galaxy Note 4 Android Development] mising:
Yes, mine stay active for about 3-4 seconds after the screen turns of as well. Does not seem to affect anything though.

Actually, it keeps doing it in my pocket at random times as well.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Thanks for the reply. Based on what I've seen from various replies, I'm thinking the 2/1 build you'd mentioned still seems like a better bet than the latest 4/26 download. Would you agree? I haven't tested either and I don't know if you've tested 4/26 yet.

Can I get multiple builds running at once and basically have the ability to multi-boot? Is that was Multi-System does?
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I've run/tried EVERY build and always go back to the 2/1 build. That's what I'm on now. Find a build that runs good for you and stick with it until a build is released that is considered an upgrade or one that offers capability that you want and don't currently have. Don't "chase" every build that is released, you can't keep up.

No, you cannot multi/dual boot.
[Verizon Galaxy Note 4 Android Development] colbyrainey:
Just flashed 4/26 build and it seems to be a huge improvement over anything else I've tried so far.
[Verizon Galaxy Note 4 Android Development] NickSaul:
Have you had a chance to test out Bluetooth, GPS, and the fingerprint scanner on the 4/26 build?
[Verizon Galaxy Note 4 Android Development] pacovilla182:
I've tried bluetooth, GPS and fingerprint. Bluetooth seems to be quite better than stock. I sync my Pebble and bluetooth helmet without any issues. GPS seems to run fine, Google Now nows where I am and Maps works normally. Fingerprint seems to recognize and store, well, your fingerprints, but still not able to use them to unlock the screen.

Besides the haptic feedback on the buttons when locking the screen and the fact that I can't find any working port of Samsung camera everything else works ok IMO. Does anyone one of a good replacement of the camera that records 60fps?

Thanks!
[Verizon Galaxy Note 4 Android Development] NickSaul:
Thanks for the info! I think I'll download it now.

With regards to a camera app that records 60fps, I tried out lgCamera, which has a lot of options, one of them being the framerate, which includes 30, 60, 90, and even 120fps. Unfortunately, when I selected 60fps and tried to take a video, it crashed.
[Verizon Galaxy Note 4 Android Development] dynamix911:
I'm waiting for a good camera before I make the switch back to daily driver. Thanks for the feedback.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
[MENTION=4513158]jpcalhoun[/MENTION] I installed 2/1, the gapps (via TWRP) and the BOK3 modem (via ODIN), booted it up and started re-installing apps, as I was doing that, I noticed that my phone ran hot and shut down. I turned it off for awhile, it cooled down, it heated up again and shut down. I did exactly as you said, did an FDR and did the cache wipes you said to do. How can I fix this issue?
[Verizon Galaxy Note 4 Android Development] jjosph:
I noticed that if you don't install the gapps fingerprint lock works. I tried using the aroma gapps package and didn't realize it didn't install anything so when it loaded I was able to unlock with my fingerprint. However I restored and reflected and used the micro gapps package and that installed and I lost fingerprint unlock
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Its difficult to determine exactly what is causing the heating problem. Try this: Go into recovery and clear cache and delvik cache. Power off the phone an remove the battery. Wait about 30 seconds, replace the battery and power the phone on. If the phone is not over heating continue to install your apps. If the phone is still over heating then I'd do a factory reset, full wipe, and start over. That's what I'd do. You may choose to do something different.
[Verizon Galaxy Note 4 Android Development] jacampb2:
Thank you so much for this! This seems to be a pretty rare issue, but I had the exact same thing happen when I tried to change my "internal" formated 128gb to portable. Black screen and no response. Had to battery pull and then it would bootloop the samsung logo. Pull the card and it boots fine. I searched for a few hours and either it's not described as I/we did, or it is quite uncommon. My card brand was a 128gb transcend if that matters.

I never thought to try to boot to TWRP during the logo bootloop. I just tried a moment ago and had no problem getting into recovery. I will add that TWRP refused to mount the card for me, showing it as 0mb. I went to wipe-->advanced-->selected extSDcard and wiped and it formatted it, mounted it and booted just fine. On successful boot I just set the card up for portable storage. It seems the adopted/internal storage is still not very robust from what I am reading.

Thank you!

Jason Campbell
[Verizon Galaxy Note 4 Android Development] douger1957:
I think the problem is that once you've set the card up as internal, it's encrypted. The only way to use it again is to wipe it in recovery or do a diskpart clean.

I'd turn handstands if I could get my card to mount as internal. Maybe when I get home, I'll try a wipe and format in recovery.
[Verizon Galaxy Note 4 Android Development] chadwick359:
I also appear to be in this boat. Did a clean flash, pushed open gapps after rom was in place but before 1st boot, don't seem to be getting notification entries (but am getting sounds) and I'm unable to access quick settings in the statusbar.

I feel like there would be more folks mentioning this than just cylamanae if it were widespread, can I confirm that this doesn't seem to be hitting anybody but us?

Also, my capacitive keys are throwing haptic feedback with screen off per NJDEN's post, but their backlights are turning off with screen as expected.

Clarification: this is referring to the 4/26 build.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
I think the delvik cache/cache clearing and battery pull took care of the problem. Thanks. I'll post back after a few days when I've had a chance to use this and feel it out.

Sorry if I've asked this before, not sure if I have, but when I originally converted from Retail to Developer, I was told to flash a kernel to stop my phone from bootlooping. This was prior to upgrading to CM13. This post referred me to a kernel download (see second link posted). It stated 5.1.1 in the filename, and SM-N910P (not SM-N910V). I didn't catch this earlier, but it still worked, and my phone still reported that it was a SM-N910V. Has this been wiped out/overridden by CM 13? Sorry, a lot of this stuff is new to me and I don't quite know how it all fits together. Reason I'm asking, is because the kernel that I flashed, there's a version for it to support the ZeroLemon battery (here), which is linked to on that page as well. Will this all play nice together?
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
It's hard to tell the kernel that was referenced and it really doesn't make much difference. You have the kernel you need when you flashed CM. It might support Zerobattery or it might not. Install Zerobattery and see[emoji1]
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Yeah it doesn't support it. Same problem I had since day 1, 1% takes forever to drain. So I take it that you're saying that the kernel I flashed was overriden by CM13.

Is there a way in CM 13 to view (and maybe edit if necessary) your battery capacity? I know there is in the Note5 port ROM.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
CM came with its own kernel, probably different than the one you reference, so yes it was over written. I don't think you can edit your battery capacity. You can flash the kernel you referenced and see how CM responds. If you have issues then re-flash CM.
[Verizon Galaxy Note 4 Android Development] shadeau:
Easy way to multiboot/try other builds

So I've tried a bunch of different builds and ultimately settled on the 2/14 build (there was some reason I liked it more than the 2/1 build), but I still can't get my car to connect to CM13 with voice. Reading around that could just be a CM13 problem. I also can't get GPS to work quickly enough in any build past 2/14 to work for maps and the like.

My solution to trying out new builds, and still having stock features for when I need them, is to dual boot. And yes, you can:).

I found this article: http://xdaforums.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211

and used it to get a working dual boot system on my Verizon Note 4. The OP is outdated so if you just download the first apk and watch the video in post 18 you can save yourself some reading time.

I have JasmineROM as my primary and CM13 as my secondary. Each ROM can be independent of the other, but there are also options to share data between the two (this feature doesn't always seem to work though). The point is that you should be able to just add an additional ROM to another slot (I've only tried two, but it seems that there are more slots) and test it out to see if you like it. If you don't then you just boot back up to your primary ROM and delete the specific folder to remove it.

I know I'm replying to a slightly older post, but I think this is still relevant since a lot of us want to try new builds without having to backup and restore everything constantly.

Also wanted to say thanks to hsbadr for the work in this ROM and JasmineROM! They're awesome!