[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
Ok im on my phone at the moment so its hard to really focus on the screen for too long.. Ill get to my pc shortly and we are gonna go through this one step at a time, because clearly something IS wrong. Regardless of it working fine previously.. Something has been done differently/wrong etc. And im betting its something very basic.. Because it cannot be this complicated to boot your phone in system with a freshly installed rom and Still get google app crashing errors and su errors. Give me 5 minutes mate.

---------- Post added at 03:16 AM ---------- Previous post was at 03:01 AM ----------

Just a suggestion to try and make things a little easier/faster for you. But are you able to take a screenshot of the ext sdcard that contains your gapps and ROM?? I would just like to compare your files and to the ones im looking at infront of me

Sent from Sony Xperia Z5 E6653

---------- Post added at 03:32 AM ---------- Previous post was at 03:16 AM ----------

Well.. Velvet is actually one of the colours for the color theme ..

That really isnt all that important.. im more concerned about the other errors..

im going over the logcat now as we speak

well Looky here..

--------- beginning of crash

09-03 01:40:04.974 8863 8863 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8863 (su)

09-03 01:40:04.974 8961 8961 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8961 (su)

09-03 01:40:04.976 8916 8916 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8916 (su)

09-03 01:40:04.977 8945 8945 F libc : Fatal signal 13 (SIGPIPE), code 0 in tid 8945 (su)

Super User is most likely the cause... The Forced reboots that you are getting is common and 9times out of 10 it's caused by an APP that's either conflicting with your Android OS System, or from a system app that's incompatible with the current installed Rom, and also from any third party app thats installed..

And with Nexus 6P specifically, IF your device RUNS in SAFE MODE without any app crashes and reboots, then you KNOW for a fact that the culprit is one of the apps that you have installed and my bet is that your CYANOGENMOD might be corrupted, or a broken installation.. because custom recovery = Root.. SuperSU is an interface for the Root Binaries to allow your device to run properly and allocate all necessary permissions for apps etc etc..

So that should be the first thing to look in to.. start from the beginning of the crash, and try to narrow down the source of the problem :).

dont worry ill help you all the way through, but because i dont have your device infront of me unfortunately, i have to make sure i ask as many questions as i can, even if i ask the same thing 2-3-4 times :P

ANyway...

So since you're telling me the SuperSU or superuser.apk is embedded in the rom already, is raising alarms in my head because that almost hits the nail on the head when i was saying to you it has something to do with your Root.. either youre not properly rooted and that will be the main cause of being denied permissions to open apps and read/write to the system partion and your storage..

so lets go 1 step at a time.

---------- Post added at 04:16 AM ---------- Previous post was at 03:32 AM ----------

Something else i just noticed... you ARENT using the latest release

09-03 01:40:05.089 527 527 F DEBUG : CM Version: '13.0-20160901-NIGHTLY-angler' <----- Latest release is 20160904

09-03 01:40:05.089 527 527 F DEBUG : Build fingerprint: 'google/angler/angler:6.0.1/MTC20F/3031278:user/release-keys'

09-03 01:40:05.089 527 527 F DEBUG : Revision: '0'

09-03 01:40:05.089 527 527 F DEBUG : ABI: 'arm64'

09-03 01:40:05.089 527 527 F DEBUG : pid: 8961, tid: 8961, name: su >>> /system/xbin/su <<<

09-03 01:40:05.089 527 527 F DEBUG : signal 13 (SIGPIPE), code 0 (SI_USER), fault addr --------