yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] StayingSober:
So I've been running the 03/21 build since the day the bootloader unlock was released, mainly because it had the best battery life for me. Now I want to perform a complete wipe (dalvik, system, data, & internal storage) to run either 02/01 or 02/14 because of the reports of it being the most stable. The only thing stopping me is I'm nervous that wiping data and internal storage will make my external SD unmountable in TWRP as some people have been reporting, despite it clearly being listed as external. I have my full backup of my current setup on my external SD, as well as any personal media and the 02/01 or 02/14 build on there.

Can anyone confirm that if I've formatted/setup my external SD from within my current CM13 DD (wasn't mountable in TWRP prior to doing so) that it won't become unmountable in TWRP after performing a near-complete wipe?
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I'm going to go out on a limb and say you should be OK. I setup my SD card the same as you and have wiped and flashed every CM13 build available with no SD card problems. I'm currently running the 2/1 build.
[Verizon Galaxy Note 4 Android Development] StayingSober:
Thanks for the quick reply and reassurance! I remember finding out the hard way that my external SD wouldn't mount after flashing CM13 for the first time :p having to ADB sideload stuff from my PC. But once it was up and running and formatted through CM13 it mounted fine ever since. Just dont want to do a complete wipe, only to find out my backups and media and ROMs can't be accessed again lol
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I totally understand. For safe measure I would do another backup which is saved to internal memory... just for insurance [emoji1]
[Verizon Galaxy Note 4 Android Development] StayingSober:
Despite planning to wipe Internal Storage? Lol the only reason I plan on wiping internal storage this time around is because I want to get the most accurate results. Previous builds ive wiped just about everything BUT internal storage and got some pretty funky results, even once causing a bootloop.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
OK, well, suit yourself.
[Verizon Galaxy Note 4 Android Development] hsbadr:
[ROM] [6.0.1] CyanogenMod 13.0 [May 1, 2016]

I've added a new

testing

build to DEVDB Downloads.

Besides upstream CyanogenMod changes since last build (Apr 26- May 1), I've applied some experimental camera tweaks while we're waiting for the new proprietary blobs from the forthcoming Marshmallow update. Let me know if it makes any difference, compared to previous build!

Focus Area:

You may want to test the built-in Snap Camera and other 3rd-party camera apps such as Open Camera.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Welcome back. Thanks for all your support and work, hsbadr!!
[Verizon Galaxy Note 4 Android Development] hsbadr:
Thanks and you're welcome! Hope you're enjoying CM13 :)
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I'm lov'n CM13. I've tried all builds but run the 2/1 build as my DD.
[Verizon Galaxy Note 4 Android Development] tubasteve:
april 26 review

To keep from sharing where I've been....long story short I have not been on here in a very long time doing anything, But i did unlock the boot-loader on 5.1.1 with little/no issues.

im running 4/26 most of the day today and some issues that bug me so far, but work around as long as i have a desktop:

Sd card access in syncme or some other apps.

Camera app...while open camera can hold me over thats for sure.

LONG boot times, granted i dont always reboot, but when I do i grab a beer.

Issues ive noticed others have, but I seem to be so far so good 48 hours in:

Bluetooth in my car, both music and hands free work pretty well:good::good::good:

Battery life, is on par with what I get during the week, maybe 10% better.:good:

Phone stays cool:good:

Just a random rant about samsung and android 6.0.1

Galaxy Gear watch...sammy's fault becuase its been tampered with anyway. Horrible app tray from 6.0.1
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Will download now and test. Thanks for all your work!
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
One thing I haven't figured out. Is there a way to save your Pictures/Videos from the stock Camera app on your MicroSD? I haven't found the setting, if there is one.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Just pull down the menu and press the location icon and select the SD card option.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
I'm not seeing it, sorry. I found a Save Location, which I turned off. I figured that had to do with Geotags which I don't like.
[Verizon Galaxy Note 4 Android Development] dynamix911:
Awesome, thanks. Going to provide feedback shortly. I owe you a coffee [emoji1]
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Sixth option down... "Storage Location"
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I took one picture (no flash activated, default settings, no gapps installed) with default settings in the stock camera. It appeared to capture successfully, but then the camera app froze completely, and I received a "camera has stopped responding" popup that stopped short of a force closure of the app.

---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------

The viewfinder continues to update despite the controls being frozen.

---------- Post added at 07:28 PM ---------- Previous post was at 07:20 PM ----------

Trying to reopen the Camera results in some forced closures immediately after it has frozen. Pictures seem to be taken successfully without problems immediately afterward when the flash is disabled, but so far in Flash On or Auto, and when toggling HDR, the camera app freezes completely.

---------- Post added at 07:35 PM ---------- Previous post was at 07:28 PM ----------

That button next to the HDR toggle on the stock camera, that brings up the menu with the starry post-it note button and the "HDR HDR" button seems fully functional (edit: it worked once, and force closed once), but the HDR toggle in the corner next to that menu button consistently freezes the camera.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
By "sixth option down", do you mean swipe to the right and what I should be seeing along the left side of the screen is:

Photo Sphere

Panorama

Lens Blur

Camera

Video

"Storage Location" ??

Because I don't see a sixth option. I see the settings button along the right side. I tap this and see:

Resolution & quality

Save Location (on/off toggle)

Advanced (tapping this I can toggle Manual Exposure)

Help & Feedback

Either we're not on the same page or something is wrong with my CM.
[Verizon Galaxy Note 4 Android Development] SoulSmash3r:
I love this rom but...

I love this rom and I know it's still has some bugs but I would like to see if it's possible to implement the S View capabilities so that I and other people like me that have the S View cover can use it.:good::good::good:
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Panorama and video seem functional in the stock camera. Still photography seems functional when flash is disabled and you don't try to toggle HDR. Will now see how this build likes the Google Camera.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Maybe we're using different cameras. I'm on the 2/1 build with the stock camera. When I swipe right I get about 20 options running down the left side of the display.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
I'm starting to think so, too. I'm using the Stock camera app, too. It literally is just called "Camera". It doesn't make any sense why we're seeing different things.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Google's Camera app is the one with the "Lens Blur" option. If you install certain GApps packages, you'll add Google's Camera and remove the stock CM camera by default.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
[MENTION=4513158]jpcalhoun[/MENTION] did you install gapps? I did. Maybe that's the difference.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
Humm, maybe that's the issue. I'm using the mini Gapps.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Google Camera on newest build: toggling HDR is as problematic as it is for the stock CM camera. 4k video recording force closes the camera, but 1080p works fine. Panorama works, lens blur still doesn't successfully process the effect. Flash ON seemed fine for the Google Camera, but switching to Auto flash and trying to capture an image immediately resulted in an apparent shutdown of my device.

---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------

https://github.com/opengapps/opengapps/wiki/Mini-package

Mini open gapps does not include the Google Camera, but I believe all packages above it do. I have both cameras installed on my device and can confirm that jpcalhoun is using the stock cm camera, while JOSHSKORN is using the stock Google Camera.

---------- Post added at 08:15 PM ---------- Previous post was at 08:12 PM ----------

Have now tested the flash in the Google Camera app. It shuts down the device to the point that I need to pull the battery.
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
[MENTION=6485176]Bicknasty[/MENTION] and [MENTION=4513158]jpcalhoun[/MENTION] I'm using Open Gapps, linked from the OP. I see also a Slim Gapps on the OP. Where is the Mini Gapps, or is that the same thing as Sim Gapps?

Is there a way I can uninstall Open Gapps and install Mini Gapps or do I need to start completely over and reflash everything?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
No no no, It's not "Mini Gapps", it's the mini package available from the Open Gapps website. You're probably using the Open Gapps package labelled "stock", or "super" (most likely "stock", as it's their recommended package for most users). I believe you'll have to reflash everything, but it might work if you MAKE A BACKUP, and then flash your current build with the "mini" package available from Open Gapps.

EDIT: You could also use the Open Gapps "full" package, which is like their "stock" package, but it does not replace non-google apps like Camera and Browser.
[Verizon Galaxy Note 4 Android Development] jpcalhoun:
I believe you just flash a different GApps. There are several sites to download GApps.

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

Thanks Bicknasty! Good work.
[Verizon Galaxy Note 4 Android Development] cylamanae:
Anyone still having issues with the pull down quick settings?
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Another issue I'm having. I use an app that will not support a mock location. Before unlocking, I was able to uncheck a box labeled "Enable Mock Locations" in Developer Options. I do not see this option in this ROM, only an option to set a mock location app. Not setting this or setting this to another app does not solve the problem. Is there a workaround for this or am I missing something?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I was, but only after I tried removing simtoolkit and cyanogenmod setup before a clean installation. After allowing their inclusion, the issue was resolved.
[Verizon Galaxy Note 4 Android Development] cylamanae:
I did a fresh install, and still experienced the issue along with a system process error when it first starts up.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Which build are you on? Have you tried wiping everything (including internal storage) and installing without GApps, just to see whether that can narrow down the potential cause?
[Verizon Galaxy Note 4 Android Development] mta1981:
4/26 and 5/1 are "test builds" according to hasbdr, is this the reason theres no pull down settings?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I've tested 5/1 a bit, and am currently running 4/26 on my device. Apart from when I removed Cyanogenmod Setup and a couple of other things prior to first booting my installation, I've had no issues with quick settings.
[Verizon Galaxy Note 4 Android Development] johnnycrosswalker:
I've been using the 2/1 build for the past few days. I've had the same camera issues as a few others with the open gapps camera, as well as with open camera. HOWEVER. Snapchat seems to work perfectly fine (even with flash on, which seemed to be the main cause of trouble with open camera), as long as I haven't opened the other camera apps since my last reboot. Not sure why, just something I noticed.
[Verizon Galaxy Note 4 Android Development] Androidrew101:
SIM card error

Ive now flashed this rom three times. Each time the phone doesn't recognize my sim card. What is the issue? It say No sim card
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Another error I'm having on 2/1. When my phone is plugged in, I see a second lock screen that I cannot seem to get out of without unplugging my phone. It asks me to swipe to unlock and shows me battery percentage very large. My screen is also dim, but I have that problem anyway, I just normally wake up my phone, see it dim, press the power button to turn the screen off, then when I wake it up again, the brightness is back to normal. I don't know if the problem with the second lock screen is related to Gapps or not.
[Verizon Galaxy Note 4 Android Development] mta1981:
so you have a pull down settings menu from swiping down from the status bar? I didnt have that or notifications in the status bar
[Verizon Galaxy Note 4 Android Development] tubasteve:
If weird issues come up, try plugging in power, then remove it.

I noticed the second menu thing just now.

Can confirm that flash off on camera fixes it darn near..... no more open camera
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Yes, I do have proper notifications and quick settings in the status bar pull-down interface.
[Verizon Galaxy Note 4 Android Development] douger1957:
"Allow bluetooth to exist with other interfaces"

Does that mean it'll pair with my car properly?
[Verizon Galaxy Note 4 Android Development] rmc198501:
It should if you can pair it with a Bluetooth headset
[Verizon Galaxy Note 4 Android Development] NickSaul:
I haven't been able to get the GPS working correctly on the 4/26 or 5/1 builds. In Google Maps, if I open it, the blue dot will show where I am, even while I'm moving, but if I try to navigate somewhere it just gets stuck saying "Searching for GPS."
[Verizon Galaxy Note 4 Android Development] hsbadr:
[ROM] [6.0.1] CyanogenMod 13.0 [May 2, 2016]

I've added a new

testing

build to DEVDB Downloads. This build is DEODEXED, uses AOSP Camera2 instead of Snap Camera, and includes more experimental camera and performance tweaks.

Focus Area:
[Verizon Galaxy Note 4 Android Development] shadeau:
What menu is that setting under? I can't seem to find it. Also, what build are you running? Thanks
[Verizon Galaxy Note 4 Android Development] douger1957:
Perhaps I misspoke. It paired to the car fine. It wouldn't stay connected.

I was on 2/1. For me, this isn't quite a daily driver yet.

---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------

It paired with everything I tried pairing it with. In my car, it would either not connect or not stay connected. I'm on the Jasmine ROM now and it works perfectly.
[Verizon Galaxy Note 4 Android Development] tubasteve:
This is for may 1 release

Bluetooth paired fine for me on both devices in my car. My line of work requires constant start and stops. I am beside myself how fast it pairs now than on stock Verizon boat version.

GPS is spot on for me 1 second finding satellites. I use this to track my millage for the day.

I am using it as a daily as I have a back up tablet that can take the same calls, texts, emails or anything else if my phone chokes.

Only had one hiccup earlier. Was browsing for the visual voicemail app when phone started heating up so I had to reboot. Something else was running because it was killing the battery and took forever to shut down.
[Verizon Galaxy Note 4 Android Development] douger1957:
Good. One down, one to go.

When they get the camera fixed, this will be my daily driver.
[Verizon Galaxy Note 4 Android Development] cylamanae:
May 1st build I just tried open gapps it seems to fix the pull down menu issue tho not the system process error during start up I am going to try another download of that when I get off work.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Ignore the system process error. hsbadr has confirmed that it really doesn't mean anything for actual use. I know it's annoying, but you shouldn't let it influence your decision of whether to use a build or not.

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

Were all the builds from 3/31 to 5/1 odexed?

---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------

When I tested 5/1 yesterday and then restored my 4/26 backup, my 4 registered fingerprints weren't working, and trying to register a fifth would immediately close the registration interface before I could even swipe once on the scanner. This was resolved after I deleted all of my existing registered fingerprints. This isn't a really significant issue to me, but I figured it's something worth noting.

---------- Post added at 06:31 PM ---------- Previous post was at 06:24 PM ----------

Flash appears to be WORKING on 5/2
[Verizon Galaxy Note 4 Android Development] dynamix911:
How's the camera quality close to stock Samsung ? The video and the photo, I'm about to flash this version later on and give it a go
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I'd describe it now as functional, but not fantastic. UHD video recording still force closes the camera, and toggling HDR can crash the camera. Samsung's stock camera experience allows for finer control (though not total control) of settings than the Google Camera or AOSP camera2 (default camera in 5/2 without gapps installation), and includes features that I personally find useful, like burst shooting. I can't say much about an actual image quality comparison, but I don't think it's been particularly worse on CM13. Video recording at 1080p seems to be perfectly fine, but understand that I've not tested that for videos of any meaningful length. The main improvement in 5/2 over recent builds appears to be that the flash is now fully functional, in both ON and AUTO modes.

hsbadr, what was the reasoning behind switching from Snap to camera2 for this build?
[Verizon Galaxy Note 4 Android Development] NJDEN:
I'm getting lingering audio anytime I trigger any system sounds. After a beep or boop I can hear a static linger for about 3-4 seconds. This is for the May 2 build, but I remember similar issues on previous builds.

It can be hard to hear the static, but in a quiet room or if you hold the phone up to your ear you can definitely hear it. I'm not sure if this static is exclusive to system sounds or anytime speaker audio is triggered.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I hadn't noticed this, but now that you've mentioned it, I certainly hear a buzzing when holding the speaker to my ear after a system sound.
[Verizon Galaxy Note 4 Android Development] jr_718:
Anyone having issue with GPS on latest build? Seem like I am...
[Verizon Galaxy Note 4 Android Development] shadeau:
I tried GPS and Bluetooth for the May 2nd build and still have problems with both. GPS won't find my location accurately or quickly and Bluetooth won't work with my car. I still need to test the May 1st build.

Thanks again [MENTION=5868929]hsbadr[/MENTION] for making all of these builds and keeping the project alive :good:
[Verizon Galaxy Note 4 Android Development] NickSaul:
I don't have any problems with bluetooth, but I agree that the GPS on the 4/26, 5/1, and 5/2 builds is not locking in Google Maps once navigation starts.

Side note: The new camera app in the 5/2 build seems to work well if you don't use HDR for images or the 4K setting for video recording.
[Verizon Galaxy Note 4 Android Development] shadeau:
I don't know how everyone else is measuring GPS, but I've found the easiest way is by using the GPS Status app. It tells you how many satellites the phone has found and how long it took to fix a signal. It's the first thing I install when testing a new build. It's a bit easier than trying to use Google Maps as a benchmark.
[Verizon Galaxy Note 4 Android Development] dynamix911:
GPS wasn't working for me on the CM builds but if I turned it off then turned on high accuracy it worked fine
[Verizon Galaxy Note 4 Android Development] NickSaul:
I just tried with the app GPS Status & Toolbox and I'm getting 0/18 satellites.

The only thing I really rely on GPS for is Google Maps, so that's why I try it there.

I tried turning location off then on again, but that didn't seem to fix it.
[Verizon Galaxy Note 4 Android Development] chappatti:
GPS:

1. Google Maps fails to find GPS for a very long time......and then it refreshes its position every minute or so, so it jumps around. This is a Google Maps problem. Since CoPilot and TomTom work quite well.

2. BUT TomTom makes the phone get very hot. The heat is a lot and the phone is very hot to hold. So maybe Google Maps uses GPS in low energy and hence cannot pick up signal. TomTom picks up signal but battery gets very hot.

BLUETOOTH:

It works in my car and for other uses. But when turning screen on from sleep it gets very choppy audio, and then settles down after some time.

---------- Post added at 06:57 PM ---------- Previous post was at 06:53 PM ----------

For me GPS works on TomTom and CoPilot, but I have the same bug on Google Maps.. So its google maps thing.
[Verizon Galaxy Note 4 Android Development] jr_718:
Absolutely no problem with Bluetooth.. Just GPS.. Geez somewhere I was going that was like 5 min took me almost 30 min..ahahaha...but other than that I think it's a fantastic build...
[Verizon Galaxy Note 4 Android Development] shadeau:
The reason I suggest GPS Status & Toolbox is because that seems to be a good gauge of how Google Maps (Gmaps) will work. The amount of time Gmaps says "searching for GPS" appears to be the same amount of time you need to wait for an actual fix in GPS Status & Toolbox (from the time you open the app to the time that you get a fix). On the 2/1 build it takes a couple of seconds, but on the newest build it takes 30 or more seconds. I think Gmaps tries to conserve battery by probing GPS every so often instead of constantly. This means that every time it probes for a new GPS location it has to wait 30 seconds to get a response.

TomTom may be keeping the GPS on the whole time, which would explain why it heats up the battery so much. This might also explain the difference in navigating since in GPS Status I don't lose a location once I've found one, it just takes a long time to find the location the first time.
[Verizon Galaxy Note 4 Android Development] roll_tide:
I'm running the 5/2 build as a DD right now - only problem I'm having after a full wipe is the static/crackling of the speaker. Only happens when adjusting the ringer volume up/down or notifications. Weird...
[Verizon Galaxy Note 4 Android Development] jmcturnan:
Been using 5/1 and its predecessors for a couple weeks. Findings:

- Super fast and responsive

- Bluetooth works for car use fine

- Overheating issues that I can't figure out the pattern on...but 5/2 is better

- Camera works, but photo quality is nowhere near that from stock ROM....lack of proprietary blobs is affecting this I guess

- Battery life is very good or excellent... Much better than stock

- Adaptive brightness is often confused and too quick to react
[Verizon Galaxy Note 4 Android Development] JOSHSKORN:
Did you try clearing dalvik cache and cache? That worked for me on my 2/1 build.