yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] zediiiii:
See this post on this issue. Can you give specific steps to reproduce? I haven't been able to intentionally cause the issue.

---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------

No sir. The microphone doesn't work at all (except in phone calls) when the issue is occurring, regardless of whether or not headphones are plugged in. I was musing about my observation that I don't think I've seen the issue occur occur unless I had also used headphones recently, but I'm not sure the headphone jack is the culprit. For instance, I've noticed the issue when I was sitting down at my house - but the issue may have already been present earlier and I just hadn't tried to use the microphone yet, so I hadn't noticed. Many thanks for response to my long post.

---------- Post added at 02:53 AM ---------- Previous post was at 02:50 AM ----------

Can you reproduce this issue? See post here for my bug description.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Not really sure what to suggest. I'd recommend condensing your problem description and posting it in the General section of this device's forum, and hopefully getting a broader audience.
[Verizon Galaxy Note 4 Android Development] zediiiii:
I had similar issues on Jasmine Rom, but not on PaulPizz. Can you describe exactly how to reproduce this issue, or is it too long ago? =)
[Verizon Galaxy Note 4 Android Development] morgej:
Too long ago, Apologies.
[Verizon Galaxy Note 4 Android Development] ericthered5000:
I have this same issue & it drives me nuts. I haven't figured out how to recreate it, but a hard reboot is the only way I can get it fixed. I don't come out here much since there aren't many updates on a new versions anymore. But, if I can help test something message me and I will be glad to help if I can.

Also, another bug I have is the GPS constantly drops the signal. I will be trying to use the GPS and I will get "GPS Signal Lost". After about 30 seconds later it will usually reconnect.
[Verizon Galaxy Note 4 Android Development] zediiiii:
I got a log cat that has the critical error in it, but I ain't know where yet. I hadn't used my phone for several hours when I noticed the issue (i noticed the issue at 1630, and it was definitely working correctly at 1200). I haven't had time to skim through, but if you were able to catch it on a log cat and then export, we could compare for similarities, especially in audio errors. I suspect attaching the whole log might be a privacy risk in some way, but I'll attach it here until someone tells me so.

link

https://drive.google.com/file/d/0B0kACq1BZaNvSHZwamJ4X2ZDa1k/view?usp=drivesdk

I had GPS issues until I selected device only, then changed back to high accuracy. I can often use device only, but it will sometimes stutter and I'll change back to high accuracy to fix it.

posted from mobile
[Verizon Galaxy Note 4 Android Development] zediiiii:
I definitely caught a log cat where the mic was working and then it wasn't working. Sadly, it's an hour long, but this is better than 4 hours last time. Still haven't got home yet today (long work day), but I'll dig through it and compare the two logs when I get a chance.

logcat link

https://drive.google.com/file/d/0B0kACq1BZaNvYUhVNEU4UndPQXc/view?usp=drivesdk
[Verizon Galaxy Note 4 Android Development] ericthered5000:
I looked at the log file and honestly, I don't know what the hell I am looking at. I searched for the word "fail" and it occurred over 135 times. I also looked for "launcher" and found several things that looked interesting, if I knew more about Android's operating system. Here are the ones that stood out to me based on key words:

10-27 16:13:31.958 E/dex2oat (7104): Failed to create oat file: /data/dalvik-cache/arm/system@framework@com.google.android.media.effects.jar@classes.dex: Permission denied

10-27 16:22:55.345 W/BroadcastQueue(1401): Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } from com.cyanogenmod.trebuchet (pid=3032, uid=10030) requires com.google.android.launcher.permission.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.icingsync.ApplicationLaunchReceiver
[Verizon Galaxy Note 4 Android Development] zediiiii:
After comparison of the two files and accounting for when the issue occurred, I think I've found the relevant log entries. The top two (other input and -38) only occur when the issue requires a reboot, while the -4 error occurs either way.

10-27 21:21:41.286 E/APM::AudioPolicyManager(17528): startInput(274) failed: other input 272 already started

10-27 21:21:41.287 E/AudioRecord-JNI(3578): Error -38 during AudioRecord native read

10-27 21:21:46.603 E/APM::AudioPolicyManager(17528): startInput(277) failed: other input 272 already started

10-27 21:21:46.603 E/AudioRecord(3578): start() status -38

10-27 21:28:21.773 E/AudioRecord-JNI(25094): Error -4 during AudioRecord native read

(Last line repeats x 3)

10-27 22:23:39.154 E/OMXMaster(25094): A component of name 'OMX.qcom.audio.decoder.aac' already exists, ignoring this one.

This entry is probably a symptom of the previous

10-27 23:21:03.738 I/AudioRouter(1904): Route changed: ROUTE_NO_AUDIO->ROUTE_NO_BLUETOOTH,CONNECTION_TYPE_NONE->CONNECTION_TYPE_NONE

And a few more since I don't know exactly what I'm looking for

10-27 23:24:33.462 E/OMXNodeInstance(17528): setConfig(4b:google.mp3.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)

10-27 23:32:08.184 I/MediaFocusControl(1528): AudioFocus requestAudioFocus() from android.media.AudioManager@a62c311com.google.android.apps.gsa.speech.audio.c.a$1@3a26c76 req=4flags=0x0

10-27 23:24:28.141 W/SpeechLevelGenerator(1904): Really low audio levels detected. The audio input may have issues.

10-27 23:32:13.185 I/AudioController(1904): internalShutdown

10-27 23:24:33.104 I/MicrophoneInputStream(1904): mic_close com.google.android.apps.gsa.speech.audio.ae@151c7b9

10-27 23:32:13.185 I/MicrophoneInputStream(1904): mic_close com.google.android.apps.gsa.speech.audio.ae@fb0b26

Bonus: this location service error is everywhere - possible indication of GPS issues mentioned by some users (including myself)? ,

10-27 23:24:42.158 E/LocSvc_ApiV02(1528): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 105 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
[Verizon Galaxy Note 4 Android Development] avenged06x:
On the latest download of CM13 and on CPD1 currently running PaulPizz I am getting a bootloop after a full wipe and fresh install. Anyone know what my issue would be?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
The 9/19 kernel is broken. You have to install 7/24, backup the kernel (Boot) in TWRP, install 9/19 and then restore the kernel backup over it.
[Verizon Galaxy Note 4 Android Development] avenged06x:
I appreciate your timely reply Bicknasty. Cheers to you. Solved the problem. :)
[Verizon Galaxy Note 4 Android Development] fateerror:
Is there any way to get rid of the user icon on the right side of the status bar when looking at the lockscreen?
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I don't think there is.
[Verizon Galaxy Note 4 Android Development] shadeau:
I was having the same problem with my screen (push power button, then wait and push power again or home since the screen took forever to wake up). I recently did a clean flash of the 9/19 build with the 7/24 kernel and Stock Gapps (I know it's not recommended, but I wanted the new dialer and some other things so I figured I would try it and re-flash if it wasn't working right) and now my screen turns on instantly with adaptive brightness enabled.

I don't know if the clean flash or the Stock Gapps was what fixed it for me, but I figured I would share regardless. Hope it helps someone;)
[Verizon Galaxy Note 4 Android Development] shadeau:
Bluetooth in my car

Because of the speed, stability, features, and AOSP feel of this ROM I've made it my daily driver. The only thing holding this back from being a perfect ROM for me is that I can't get Bluetooth to work with my car. I don't expect hsbadr to fix every Bluetooth profile that isn't working so I was wondering if someone with more experience than me could point me in the right direction.

I have a clean flashed version of 9/19 with the 7/24 kernel.

The Problem:

-I can pair with my car and I have the option to share contacts, media, and phone audio with the car, but if I stay on the screen I notice that the phone and media will toggle off and then back on while connected to the car.

-The bluetooth profile "MY CAR" will also display "no phone" or "no calling" (I don't remember the exact phrase used)

-Bluetooth between my car and the phone worked fine with PaulPizz and stock so I know it's not a hardware limitation

-In TW I get a request for MAP access, but CM13 doesn't ask for permission

Googled Solutions I have looked into:

-Apparently CM13 had BT issues that were fixed by changing the line of /system/etc/init.qcom.bt.sh from "setprop ro.bluetooth.hfp.ver 1.7" to "setprop ro.bluetooth.hfp.ver 1.5", but this ROM has no such file that I can find

-Under /system/etc/bluetooth there is supposed to be a file named audio.conf that I can change to allow HFP, but the file does not exist

-Under /system/etc/bluetooth there is a file named auto_pair_devlist.conf which lists my car's ID as blacklisted. I removed it and I'm still having issues.

Since I can't find a very good explanation of the current bluetooth configuration files online I want to know if there are files that I can edit that might enable a profile that works with my car. I'm assuming that the bluetooth protocols from the stock ROM were transferred over, but is it possible they aren't the same? Would any bluetooth changes need to be made on a ROM level (ie by hsbadr)? Could my car be rejecting the phone because it doesn't like the BT or HFP version? Any tips or logs that would make troubleshooting easier?

Again, I don't expect hsbadr to fix every small thing like this, but if there's something that I can do to tweak the BT protocols then I'm happy to test them. Thanks!
[Verizon Galaxy Note 4 Android Development] Corypeach:
Just fyi I was able to dirty flash 9/19 with the 7/24 kernel and everything seems to be working
[Verizon Galaxy Note 4 Android Development] fateerror:
Is anyone else having problems with google maps? It works but then it keeps trying to find gps signal and it does this a lot. I came from stock and never had this issue with gps.
[Verizon Galaxy Note 4 Android Development] bertmag:
I've had that issue quite a few times myself, where it'll pick up my location then mid route it'll stop moving and say "Searching for GPS...". Glad I wasn't the only one.
[Verizon Galaxy Note 4 Android Development] abraha2d:
Ya, occasionally I have that issue... But then I only use Google maps occasionally...
[Verizon Galaxy Note 4 Android Development] abraha2d:
I've noticed that for approximately 30 secs after turning off the screen, I can swipe the fingerprint sensor, and if the finger matches, it will turn on the screen and unlock the device. Otherwise, the screen stays off. After around 30 secs, the sensor stops working.

Is this supposed to be a feature (like the latest Nexus/Nexii)? It would be nice if the fingerprint sensor would stay on always, instead of for the first ~30 secs (or at least an option to do that).
[Verizon Galaxy Note 4 Android Development] billyburly:
I'm seeing my phone randomly reboot when the battery falls below 50%. Haven't come up with anything else to trigger it other than lower batter. Typically seen somewhere in the 30% range. Seen on both 724 and 919 builds. Phone will bootloop after unless plugged into charger. Anyone else come across this?
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Replace your battery.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Can confirm. Replaced my OEM battery with an Anker one and stopped having the problem
[Verizon Galaxy Note 4 Android Development] chadwick359:
So long and thanks for all the flashes [MENTION=5868929]hsbadr[/MENTION], but I picked up a Pixel XL and am going to be selling/returning my note after its years of faithful service. Thanks again for the post manufacturer/carrier support on this awesome device!
[Verizon Galaxy Note 4 Android Development] swolfe2:
Any news on a new update on the horizon? Haven't seen anything in the last couple of pages, and would love to see this continue.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
I believe hsbadr is focusing on a CM14 for this device.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
That's right. Hsbadr is working on CM 14. The 9/19 update is actually a bit of a casualty of that development. He found some fixes and made a new MM build.
[Verizon Galaxy Note 4 Android Development] swolfe2:
Gotcha. So, CM13 is gonna go away, and be replaced with CM14.

I definitely don't want to sound pushy, but was just wondering if there was an ETA. I'm trying out Note4Grace in the meantime, but I don't think I like it as much.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Inb4 "don't ask for ETA!!" to politely say don't ask for ETAs. I made that mistake once and got bombarded with posts saying how rude it is.

Developers don't really want to provide an ETA because of the obligation to hold to that ETA. I think asking how it's going; if any progress has been made; etc is OK though.
[Verizon Galaxy Note 4 Android Development] swolfe2:
I mean, I can get that. I just looked through the last few pages and didn't see anything about updates for the past couple of months. Other roms are continously updating, so I was just curious.

No worries.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Hsbadr has a family, so I'd imagine that takes quite a lot of his time :p
[Verizon Galaxy Note 4 Android Development] outpost785:
Have the same problem, taking pics our YouTube. I have 4 batteries they all do it.
[Verizon Galaxy Note 4 Android Development] :
Same here :(
[Verizon Galaxy Note 4 Android Development] Bicknasty:
!!!!!!!!!!!!!!

http://xdaforums.com/note-4-verizon/development/cyanogenmod-14-1-t3495231/
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Thanks for sharing that! I'm on mobile, so it's hard to see new threads. So excited to see how it works.
[Verizon Galaxy Note 4 Android Development] Bicknasty:
Downloading now, but it's oh so slow
[Verizon Galaxy Note 4 Android Development] Carousser:
So I updated snapprefs because a snapchat update was mandated, and after installing the later versions, video recording on snapchat fails every time and gives a toast saying "video recording failed". Some searching stated that it was not affiliated with snapprefs, but the newer version of snapchat. More specifically, people running CM and using the new version of snapchat.

Anyone find a workaround for this?

Off topic - i'm very excited about CM14, but i'm staying with this for now as a daily use.
[Verizon Galaxy Note 4 Android Development] swizard210:
I'm having this exact same issue with the phone rebooting under 30-40%. I've even tried new batteriers. Additionally, I keep having a problem where my phone reboots frequently, when I am in my camera (Google or Snap Camera), and when I'm in Snapchat, it happens frequently despite the battery percentage, but consistently when my percentage is under 40%.

I'm facing this same issue as well. In addition to the constant reboot when in snapchat or snap camera as mentioned above. =(
[Verizon Galaxy Note 4 Android Development] Carousser:
So I've stumbled upon the answer for snap prefs and Snapchat creating with snap prefs. However, it does not fix video recording. I'm on mobile so when I get home I'll gather the links for the Snapchat apk and snapprefs apk

Edit - You will need Snapchat version 9.39.5.0, located here http://www.apkmirror.com/apk/snap-inc/snapchat/snapchat-9-39-5-0-release/

And snapprefs official dev version, revision #54 located here http://138.68.21.49:8080/job/SNAPPREFS%20-%20Official%20-%20stable/54/artifact/app/build/outputs/apk/app-debug.apk

The Snapchat version links to apkmirror, and the snapprefs is right off the Jenkins site so it's a direct download.

Uninstall Xposed framework, uninstall Snapchat. Install new Snapchat, log in and make sure it doesn't crash. Then reinstall Xposed and install snapprefs, reboot, and you're golden
[Verizon Galaxy Note 4 Android Development] hugo.vasquez77:
Dirty Cow Flaw

Is the kernel included in this ROM vulnerable to the dirty cow flaw?
[Verizon Galaxy Note 4 Android Development] the0darkness:
Camera Problem

Hey,

I installed cm-13.0-20160719 on my Note 4 and the Camera is having so much trouble now Focusing.

Installed cm-13.0-20160724 before I installed cm-13.0-20160719, It was just stuck on Boot Animation.

Any fix for the Camera focus problem? Thanks :)
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Use another app.
[Verizon Galaxy Note 4 Android Development] the0darkness:
Thanks for the reply, I'll try another camera app.

Is there any way to add SPen functions to this ROM?

Thanks again :)
[Verizon Galaxy Note 4 Android Development] Zacharee1:
CM SPen Add-On will give you detection functionality. You can then use it with Note Buddy to replicate SPen functionality. You'll need to get the Pro versions of both apps though.

You can also buy SPenCommand to get the Air Command window.
[Verizon Galaxy Note 4 Android Development] bobo2xtreme:
Deleted
[Verizon Galaxy Note 4 Android Development] bishop0114:
I tried installing CM13 dated 09/19/16 with Open GAPPS Mini after a full wipe of system,data, internal storage and cache. I am currently on the boot loader unlocked MM version PF3.

Every time I try to install CM13, it boot loops. At first, the animation runs as expected and after about 5 minutes, it acts like it is running in fast forward and never boots.

I searched the forum and didn't find anything. Anyone have any suggestions?
[Verizon Galaxy Note 4 Android Development] shadeau:
You need to use the kernel from the 7/24 version for it to boot. The way I did it was by extracting both and copying the boot.img from the 7/24 to the 9/19 (overwriting the file) and then rezipped and flashed it.
[Verizon Galaxy Note 4 Android Development] bishop0114:
I copied the boot.img, flashed the 9/19 zip, switched to flash image in TWRP and flashed the boot image. Worked perfectly! Thanks!
[Verizon Galaxy Note 4 Android Development] Zacharee1:
If someone follows this, I believe the ZIP needs to be or at least should be made with the "Store" compression mode.
[Verizon Galaxy Note 4 Android Development] zediiiii:
I had the same issue, but I fixed it by calibrating the battery on another rom (PaulPizz) using both a root battery calibrator and by discharging and recharging fully 3-4 times. Swapping the battery for a new one worked too.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I don't think most battery calibration apps really do anything.
[Verizon Galaxy Note 4 Android Development] zediiiii:
I've been had! You are correct in this regard per battery university. I hate being ignorant like that, so thanks for fixing me up.

However, I'm pretty curious as to why the immediate shut down at 20-30% has actually stopped happening. Probably the kernel in PaulPizz worked correctly, and I just haven't seen it happen in hsbadr's cm13 ROM again yet.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
The battery cycles you did may have helped, but I'm not sure how much those actually help on Lithium batteries. Maybe it's the battery "undying" for one last stand? :P
[Verizon Galaxy Note 4 Android Development] bishop0114:
Tried the CM13 ROM. Really liked it but noticed several issues. My battery drained about 10% every 20 minutes. GPS would never get a lock, although it showed accuracy within 10 feet and Spotify over Bluetooth would pause after playing for 1 second. Is there possibly an alternative Kernel that could be installed?
[Verizon Galaxy Note 4 Android Development] zediiiii:
Ha! Just to spite me, it died at 24% last night. This issue is definitely caused by the kernel/ROM, since I didn't have the issue at all on PaulPizz Rom.

---------- Post added at 02:48 PM ---------- Previous post was at 02:44 PM ----------

I had the battery drain issue when I did a dirty flash and installed a bunch of apps from titanium, but a clean flash and clean installs of my apps yielded pretty good results and fixed the battery drain. Google services were wake-locking like crazy, so I wonder if installing the mini gapps made a difference as well. I also had the GPS issue at first, but it doesn't seem to happen as much on the September build, especially if I enable high precision mode. My bluetooth works great, though the mic quits working randomly every 2 days or so (reboot fixes it).
[Verizon Galaxy Note 4 Android Development] bishop0114:
Has anyone tried this on the VRU2CPG2 firmware? Just wondered if it helped resolve some of the issues with bluetooth and GPS?
[Verizon Galaxy Note 4 Android Development] Zacharee1:
I'm pretty sure it won't make a difference. The GPS and Bluetooth issues are CM-related. Flashing firmware designed for TouchWiz shouldn't do very much.
[Verizon Galaxy Note 4 Android Development] bishop0114:
OK. Too bad, the ROM is awesome. Had hoped the new modem and bootloader might help.
[Verizon Galaxy Note 4 Android Development] Zacharee1:
Subscribe to the CM14.1 thread. Audio issues are still being worked out, but I think GPS works, and battery life is better.
[Verizon Galaxy Note 4 Android Development] Nikolai2129:
Hi everyone! I've been using the 9/19 build of this ROM for a few weeks and it's been really great. I have had an issue with the screen going black and locking up. I have to pull the battery to reset the phone. Has anyone else had this issue?

I've attached a log that contains the issue. It occurs at "11-18 02:55:46.663" line 9841.

Thanks for the help.
[Verizon Galaxy Note 4 Android Development] kpballing84:
i still cant get this to work after installing from twrp it just stay on the cm loading animation i even let it sat for in hr still nothing it also do this on the cm 14 build i have a Verizon Note 4 updated with the latest bootloader (PG2) so if anybody have tips on getting this to start up on the verizon note 4 pls let me know that would be a big help
[Verizon Galaxy Note 4 Android Development] haitianluv05:
Same thing happened to me..someone posted a few post ago that the latest Cm has an issue with the boot image. It's recommended to download a previous version of Cm13. I believe the 7/23 release. That worked for me. Once I've downloaded that I was able to get pass the cm loading screen
[Verizon Galaxy Note 4 Android Development] kpballing84:
I tryed that as well cm 13 and 14 it will not work even if I load 13 boot img on 14 it just sits there at the cm loading screen i kinda just have up on it just funny i can boot up every other rom but cyanogenmod roms my phone like nope can't do that
[Verizon Galaxy Note 4 Android Development] shadeau:
To be more specific: you need to flash the boot.img of the 7/23 build on top of the 9/19 build for it to boot (we're talking about CM13 builds here). So you'd extract the zip for 7/23, copy the boot.img file to your phone along with the 9/19 zip and then flash the 9/19 zip followed by flashing the boot.img from the 7/23 build. You can also search this forum for instructions on how to pack a zip with the old boot.img file.
[Verizon Galaxy Note 4 Android Development] haitianluv05:
How would I initiate multi window once I have enabled it?
[Verizon Galaxy Note 4 Android Development] abraha2d:
Press the recent apps button, then on the app you want in split screen, press the multiwindow button (next to the close button).

IMO, multiwindow in cm13 is really hard to use. You should look into [MENTION=5868929]hsbadr[/MENTION]'s cm14.1. :):good:
[Verizon Galaxy Note 4 Android Development] dweezle:
I installed 13.0-20160724 (current stable version) yesterday and the first thing I noticed was that it is molasses slow booting. It takes almost 3 minutes to boot. Sorry about the size of screenshot.