yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] D@rekills4:
It looks like so.

We don't even know for sure who the handler for this device is.

No way to directly report any bugs to him either.
[Nexus 6P General] snakecharmer23:
According to CONTRIBUTORS.mkdn, the maintainers are:

* __Google Nexus 6P:__ ciwrl, dhacker29, Sam Mortimer

I doubt they would want people from XDA contacting them directly. Use the JIRA bug tracker.
[Nexus 6P General] sam3000:
Well, as it happens I came here to see if anyone was already working on it ;)

I have some cm-14.0 angler patches and blobs update nearly ready. Should be up within the next few days unless someone else beats me to it.

-Sam.
[Nexus 6P General] AndyYan:
JIRA doesn't accept reports for nightlies (apart from regression), which has been a problem since launch.

Rewind some months and we have bugs like stuttering Bluetooth audio that was there since nightly day 1, and couldn't be submitted because of that. Even today, there are still minor problems like slow boot time (not-up-to-framerate bootanimation is an indication). I assume things will be similar once CM14 drops for us.

Sent from Google Nexus 6P @ CM13
[Nexus 6P General] D@rekills4:
Thank you, Sam.

I have one request though, can we have a specific development thread for it?

I tried contacting you guys to report bugs but I couldn't find any CyanogenMod handler. :(
[Nexus 6P General] razorloves:
I've been waiting for ciwrl to force push remote-tracking branch aosp/nougat-release, but he hasn't been around much lately. Do you have force push privs? If you don't let me know and I'll talk to ciwrl and ask him to give it to one of us so we can get this baby going.
[Nexus 6P General] sam3000:
I was going to ask ciwrl the same (force reset device and kernel trees to aosp nougat) so, no, I don't have privs. We could try intervigil too.
[Nexus 6P General] funebral:
i got bootloop after update with a new nightly. after instal a nightly reboot normal but supersu asked me to update binaries i clicked yes reboot into twrp then automatically binaries installed then bootloop on cyabogenmod start. thenafter tried to flash nougat and the same only nexus tool kit saved me. how to update super su after a update? by flashing supersu .zip?
[Nexus 6P General] sam3000:
FWIW, my current angler cm-14.0 device, kernel and vendor trees are here:

https://github.com/sam3000/android_device_huawei_angler

https://github.com/sam3000/android_kernel_huawei_angler

https://github.com/sam3000/proprietary_vendor_huawei

device and kernel are cleaned up rebases of cm-13.0 onto aosp/nougat-release (plus any specific changes necessary for nougat). It builds and boots, has wifi and data etc. I haven't had time to test much yet so I'm sure there's stuff that's broken.

A few notable changes (compared with cm-13.0):

*) I squashed related changes together where appropriate. There's scope for doing more.

*) blobs are now listed in cm-proprietary-blobs* files to avoid merge issues with us overwriting aosp proprietary-blobs.txt (cm-* filename borrowed from manta).

*) We enable the new AOSPLinks module that creates various symlinks from system pointing to vendor thereby avoiding the need to copy as many blobs.

*) I haven't yet put cm-13.0 kernel f2fs commits into the cm-14.0 kernel.
[Nexus 6P General] ps000000:
Very nice to see the CM14 progress for Angler.:laugh::laugh::laugh:
[Nexus 6P General] winxuser:
Feel free to push those update to gerrit mate.
[Nexus 6P General] kronflux:
I've compiled a completely clean build of CyanogenMod 14.0 for the Nexus 6P thanks to @sam3000's updated sources!

If anyone would like to give it a go, I've stuck it up on AndroidFileHost!

https://www.androidfilehost.com/?fid=312968873555002167

I've also created a thread for it here: http://xdaforums.com/nexus-6p/development/rom-cyanogenmod-14-0-t3470615

I'm not a very skilled developer at this point, but at the very least we can keep track of what's working so far and what's not.

Thanks sam3000! :D
[Nexus 6P General] Ok_Kaleidoscope5109:
Hey let's keep the CM14 discussion separate please.

On that note in CM13, I tried a clean flash with 29-SEP-2016 nightly and 28-SEP-2016 OpenGapps and I noticed OK Google Always On toggle fails to turn on. I tried this on TWO Nexus 6Ps (I just got an RMA for some unrelated issues). See the video here of what happens: https://www.youtube.com/watch?v=wlW5d6BtEkk

This is a clean flash after a full wipe.
[Nexus 6P General] funebral:
i got a problem with super su after update the last nightly it says super su need to update binaries then the phone starts on twrp install the binaries and reboot but sad it blocks on boot animation.
[Nexus 6P General] Jammol:
That's been happening since the first nightly of the month. I have no clue what could be causing it.
[Nexus 6P General] Ok_Kaleidoscope5109:
Oh yeah? I never noticed it (I went through at least 3-4 nightlies on my 6p). However before I wiped it last night I was on 21-SEP Nightly and OK Google was working fine and so was the setting itself. Keep in mind though that the phone was dirty flashed all the way from July til September.

It wasn't until I did a clean flash that I noticed this.

Please vote/highlight this issue: https://jira.cyanogenmod.org/browse/NIGHTLIES-3384
[Nexus 6P General] Ok_Kaleidoscope5109:
[MENTION=4613660]Jammol[/MENTION]: Further testing shows that I think it might be Google App related.

I flashed the August M-build with the latest Gapps (9/28) and the issue persists. However flashing the M-build with older Gapps (8/22), the issue is not there.

Next I will try updating Gapps to 9/28 (because my phone seemed to work fine with dirty flashing)
[Nexus 6P General] Jammol:
Yeah dirty flashing it should be fine. I'm thinking it might even be OpenGapps having a missing file? I have no clue. It wasn't until I came back to CM earlier in the month that I noticed it was gone.
[Nexus 6P General] Ok_Kaleidoscope5109:
The setting stays on when you dirty flash but it no longer works. This explains why while the settings looked fine for the past few weeks in OK Google settings, my phone wouldn't respond to OK Google unless inside the app itself.

After you delete the voice and retrain following a dirty flash it the toggle auto turns off again. I suspect it's something with the newer versions of Google Search.
[Nexus 6P General] Ok_Kaleidoscope5109:
I suspect it's this commit that changed everything: https://github.com/opengapps/all/co...06ac80c#diff-bbae49e95ca340799c5c33580dc7382f

Testing the September 6th GApps = OK Google works fine. September 8th = Fail.

I'm now testing latest Gapps but using the old HotwordEnrollment.apk
[Nexus 6P General] sam3000:
I'd be interested to know the result here (of using the original HotwordEnrollment.apk). If that works, we could try asking opengapps to only copy HotwordEnrollment if it doesn't already exist (they might not like that though).
[Nexus 6P General] Ok_Kaleidoscope5109:
Old HotwordEnrollment.apk works. https://github.com/opengapps/all/commit/be9e037ad2cd3e774a3cb19b742c2bfc6b0022e4

This is taken straight from the OpenGapps Git. I've let the dev know. It's likely because he pulled Nexus 9 apk and Nvidia and Qualcomm choosers have different implementations of OK Google always on.
[Nexus 6P General] Jammol:
Anybody else getting hit with sudden random reboots?

Also does anyone know how to limit the volume level for the speakers all around? And please don't be coy and post push the down button.
[Nexus 6P General] Ok_Kaleidoscope5109:
I am but I'm not sure if it's Xposed or something else. Does anyone have experience reading logs?

Here are my logs
[Nexus 6P General] Jammol:
Not I captain. I skipped log reading class unfortunately.?
[Nexus 6P General] Ok_Kaleidoscope5109:
Do you mind posting a log after your reboots?
[Nexus 6P General] hi2u2:
Me. I was getting so many reboots that I just stopped using CM altogether. Shame because this is one of my favorite ROMs that I've been using for years across several smartphones, but the stability is just not there for the 6p.

No logs unfortunately.
[Nexus 6P General] Ok_Kaleidoscope5109:
Come on you guys. Put a log together so we can all help each other.

SysLog is a very simple app if you don't even want to ADB: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en
[Nexus 6P General] Jammol:
I'm not on cm anymore because of work. Have to go unrooted for another week.
[Nexus 6P General] abusedcloth:
What vendor file should i be using for the current build (10/5) ? Iv'e tried MTC20F but I still get that internal error just before CM starts. I've tried installing the vendor before and after the ROM install and Iv'e also tried installing with fastboot after the flash of the ROM. Nothing seems to work. Maybe I'm using the wrong image?
[Nexus 6P General] Jammol:
You need to be on MTC20L.

https://www.androidfilehost.com/?fid=24686681827314757

Credit to Flipz.
[Nexus 6P General] jeremmie:
If i may ask, how do you use that MTC20L file? Is is via twrp ? Im currentlh on

Nightly oct 5 2016 version

With MTC20F

Sorry noob. Just wanna make sure.. Dont want to half brick my 6p again
[Nexus 6P General] razorloves:
http://xdaforums.com/showpost.php?p=68579632&postcount=982
[Nexus 6P General] case-sensitive:
no notification, no home

I've been running stock run on my 6p. I need xposed so for now I need to stick with marshmallow. I flahsed CM13 (2016-10-09) nightly with open gapps (from a functional MTC20L stock rooted). Everything worked excepted

* when I pulled down the notification it stops at "no notification"; I cannot get to e.g. the quick menu, and I cannot see the "setting" gear on the upper right hand corner

* clicking the "home" circle button does not do anything (I did not set fullscreen mode for anything)

I just tried flashing 2016-10-14 and I got the same error. This is problematic because e.g. I cannot transfer files between the 6p and my computer (I cannot get to the dialog box that switches from charging to file transfer).

I flashed CM13 nightly from October on my moto G (with xposed) and I didn't have this problem. I've sent along the logcat for this

(failure to pull down notification bar, followed by failure to activate the home button).

THANKS!
[Nexus 6P General] AndyYan:
Did you complete the setup wizard (both CM's and Google's)? This happens when you remove it before first boot.

Sent from Google Nexus 6P @ CM13
[Nexus 6P General] case-sensitive:
Thanks --- that solves my problem! Specfically, this time I connected to the wifi first before I go through the rest of the setup and notification/home button now works. In my other devices I was not allow to continue before I connect to wifi, which is why I didn't encounter this problem before.

Sounds like this is a known step. Is there a reason for this? Why can I read more about this?

THANKS!
[Nexus 6P General] AndyYan:
Frankly I don't know either... This just happened to me in the past (since Jelly Bean) so I know it. CM also included a commit back in April that made their own setup wizard compulsory, which I find pointless.

Sent from Google Nexus 6P @ CM13
[Nexus 6P General] tibere86:
I've asked before and never got an answer. Has anyone gotten Google Wifi Assistant working on CM13? I installed Google Connectivity Services from the Play Store but no luck. Does it need to be installed on the system partition?
[Nexus 6P General] Jammol:
On CM it needs to be installed as a system app it looks like. That's the only way I could get it to actually work.
[Nexus 6P General] tibere86:
Worked. Thanks. Moved it to /system/priv-app and gave it the proper permissions :good:
[Nexus 6P General] Donjuanal:
Would you mind linking or attaching the 9-6-16 hotwordenrollment.apk that works? I'm unable to extract it from the opengapps zip for some reason.
[Nexus 6P General] yoonietang:
Same here! I'm not even sure where to start looking tbh, and my google and xda searches aren't turning up anything useful.
[Nexus 6P General] hinxnz:
Here's the apk from the link provided by dmo580
[Nexus 6P General] Donjuanal:
Thank you, do you know if this is sdk 24 or sdk 23?
[Nexus 6P General] hinxnz:
Its manifest says sdk 23
[Nexus 6P General] Donjuanal:
Thanks. Doesn't seem to work for me, perhaps due to being on Android 7
[Nexus 6P General] fadac:
Doesn't work for 7.0 apparently. I extracted HotwordEnrollment.apk from open_gapps-arm64-7.0 09/06 and 09/04 and neither worked.
[Nexus 6P General] Donjuanal:
Good to know thank you. I couldn't get the apk to extract. How did you do it?
[Nexus 6P General] fadac:
I was able to extract 09/04 using 7zip. It looks like for 09/06 opengapps started using a new compression called lzma which makes it more difficult to extract. So I just created a .gapps-config in the same dir of the opengapps zip and used

include
Hotword

then flashed the zip.

It's all on opengapps github
[Nexus 6P General] Ok_Kaleidoscope5109:
Can we keep the 7.x discussion out of here? This is for CM13.
[Nexus 6P General] razorloves:
The laggy bootanimation is finally fixed. :good:

Also, we stopped using proprietary camera blob for the camera hal and now use source built.

In my testing the camera worked the same, but let me know if you notice any negative effect.

These 2 changes will be in the next nightly. 22 Oct
[Nexus 6P General] Prattham:
Anyone running this for a few time can tell how this for daily driver?
[Nexus 6P General] tibere86:
Awesome. Thanks :good:

Yep. No issues with it.
[Nexus 6P General] Prattham:
No bugs at all i mean like call quality Bluetooth quality battery life?
[Nexus 6P General] Jammol:
It's about as flawless as you can go compared to stock. I get really good battery life that's better than stock N
[Nexus 6P General] tibere86:
I keep coming back to CM13 after testing different 7.X ROMs. Nothing else works as nicely as this. Thanks [MENTION=614507]razorloves[/MENTION] for maintaining our device.
[Nexus 6P General] funebral:
sorry for my noob question if it disturbs someone ignore it. i am new with nexus 6p my question is when installed cm13 and want to go back to stock nougat which is the best way to flash again stock and do not get bootloop? thank you
[Nexus 6P General] Jammol:
Flash a stock factory image. Do not restore anything using twrp 3.0.2-1.
[Nexus 6P General] Ok_Kaleidoscope5109:
Hi [MENTION=614507]razorloves[/MENTION] I'm getting soft reboots. Just flashed a new nightly 10/28 (fully clean). No Xposed or anything and I got a reboot when trying to receive a call.

I created a report at the Jira also: https://jira.cyanogenmod.org/browse/NIGHTLIES-3436

Logs here: https://drive.google.com/file/d/0BzLwcc473Qq3ODRodVJqMlhhU3M/view?usp=sharing
[Nexus 6P General] razorloves:
Common problem with all phones on cm13. Caused by the google dialer. Simple fix is go to settings - apps, and set it as the default dialer
[Nexus 6P General] Ok_Kaleidoscope5109:
I only have Google Dialer (as OpenGapps erases the AOSP Dialer), so it is set to Google Dialer. It doesn't happen every call either. I got 2 phone calls today just fine, and the 3rd one I got it froze up on me.

IIRC I've seen the phone softreboot after getting unresponsive from me trying to use Google Voice search. Once again it's not every time either. I tried to review the log and I saw some stuff about the SU binary perhaps?

10-31 02:41:48.166 F/DEBUG ( 4155): signal 13 (SIGPIPE), code 0 (SI_USER), fault addr --------
10-31 02:41:48.172 W/NativeCrashListener( 5249): Couldn't find ProcessRecord for pid 11128
10-31 02:41:48.176 F/DEBUG ( 4155): x0 ffffffffffffffe0 x1 0000007fca661268 x2 0000000000000004 x3 4bcb350eb3cba881
10-31 02:41:48.176 E/DEBUG ( 4155): AM write failed: Broken pipe
10-31 02:41:48.176 F/DEBUG ( 4155): x4 0000000000000011 x5 0000000000000000 x6 0000000000002b78 x7 000000000000006c
10-31 02:41:48.176 F/DEBUG ( 4155): x8 0000000000000040 x9 0000000000000011 x10 0000007fca660bfc x11 0000007fca660c38
10-31 02:41:48.176 F/DEBUG ( 4155): x12 0000007fca660b10 x13 000000000000000d x14 0000007fca660cf8 x15 0000000000000000
10-31 02:41:48.176 F/DEBUG ( 4155): x16 000000557a6bec88 x17 0000007f9a6faecc x18 000000557a6a2a18 x19 0000000000000004
10-31 02:41:48.176 F/DEBUG ( 4155): x20 0000000000000001 x21 0000000000000001 x22 000000557a6be000 x23 0000007f9a5a2000
10-31 02:41:48.176 F/DEBUG ( 4155): x24 0000007fca661250 x25 000000557a6a3000 x26 0000007f9a590008 x27 0000007fca661254
10-31 02:41:48.177 F/DEBUG ( 4155): x28 000000557a6a3420 x29 0000007fca6611b0 x30 000000557a6957fc
10-31 02:41:48.177 F/DEBUG ( 4155): sp 0000007fca6611b0 pc 0000007f9a6faed4 pstate 0000000060000000
10-31 02:41:48.186 F/DEBUG ( 4155):
10-31 02:41:48.186 F/DEBUG ( 4155): backtrace:
10-31 02:41:48.186 F/DEBUG ( 4155): #00 pc 0000000000069ed4 /system/lib64/libc.so (write+8)
10-31 02:41:48.186 F/DEBUG ( 4155): #01 pc 00000000000097f8 /system/xbin/su
10-31 02:41:48.186 F/DEBUG ( 4155): #02 pc 0000000000008598 /system/xbin/su
10-31 02:41:48.186 F/DEBUG ( 4155): #03 pc 000000000001bcd8 /system/lib64/libc.so (__libc_init+100)
10-31 02:41:48.186 F/DEBUG ( 4155): #04 pc 00000000000079fc /system/xbin/su
10-31 02:41:48.206 I/ActivityManager( 5249): Start proc 17056:com.android.providers.calendar/u0a4 for content provider com.android.providers.calendar/.CalendarProvider2
10-31 02:41:48.233 F/DEBUG ( 4155):
10-31 02:41:48.233 F/DEBUG ( 4155): Tombstone written to: /data/tombstones/tombstone_09

Edit: This is another crash on 10/31-- I think this is when I tried OK Google: https://drive.google.com/open?id=0BzLwcc473Qq3eHlrTm9CcGNvVmc
[Nexus 6P General] razorloves:
:D http://www.cyanogenmod.org/blog/cm14-is-landing
[Nexus 6P General] Jammol:
Do you know if recovery will updated as well to use CM14?
[Nexus 6P General] razorloves:
not sure what you mean. twrp works fine
[Nexus 6P General] Jammol:
Sorry, I meant CM recovery. Wasn't sure if we will be able to use the current version or if a nightly would be pushed with CM14.
[Nexus 6P General] razorloves:
Just use twrp like everyone else. Lol
[Nexus 6P General] razorloves:
For those wondering, make sure you use NBD91K vendor img with the cm14.1 angler nightlies.

Should also update your radio and bootloader.
[Nexus 6P General] ariefabuzaky:
Are you running on it ?
[Nexus 6P General] kingbooga:
it doesn't say to update vendor image/radio/bootloader on the cm14 install page. what will happen if we don't? And when should we flash those? Thanks, sorry for the noob questions.
[Nexus 6P General] Jammol:
Theoretically, you should flash those BEFORE the flashing of the Rom. You can get into a bootloop situation, or just get the annoying message that something is wrong with your device at boot.
[Nexus 6P General] hanschke:
bootloop only if you dont clear your settings and not missing vendor.img
[Nexus 6P General] razorloves:
cm14.1 thread

http://xdaforums.com/nexus-6p/orig-development/rom-cm14-1-nexus-6p-angler-t3498453
[Nexus 6P General] Jammol:
Does anyone have a copy of the last nightly that was made for cm13 for angler? My copy on drive is corrupt.
[Nexus 6P General] Ok_Kaleidoscope5109:
I'm pretty annoyed they just remove old builds from their site so quickly!
[Nexus 6P General] AndyYan:
I do build monthly for personal use, but I literally just deleted this month's build... Fortunately, I'm currently experimenting with a problem with the November security patch that breaks Xposed, which is why I deleted the last build. I'll share if I come up with a working test build, but don't put hopes up high - if others have mirrors, just grab theirs.

Sent from Google Nexus 6P @ CM13
[Nexus 6P General] Ok_Kaleidoscope5109:
Hrmm. Odd no one mentioned the November nightlies breaking Xposed. My latest nightly is 28-OCT
[Nexus 6P General] AndyYan:
That just originated from Nov 10, so it's normal nobody actually flashed and reported in this period.

Also, 1st test build failed :/
[Nexus 6P General] Ok_Kaleidoscope5109:
Gotcha thanks. Now I'm pissed at myself when I gave up trying to download 11/08 nightly at a hotel.
[Nexus 6P General] AndyYan:
[MENTION=4613660]Jammol[/MENTION] [MENTION=2249907]dmo580[/MENTION] and anyone else who still needs it - here's my build of CM13 fresh off the oven. Removed a bit of useless stuff, and also incorporated a fix so that Xposed will also work on November security patch.
[Nexus 6P General] ps000000:
^

^

^

^

Very nice AndyYan !!!!

:good::laugh:
[Nexus 6P General] Mr.Zombie:
Hello there. Idk if this thread still active.

Currently still staying with CM13 (11.06) because the CM14 is still experimental.

I have a problem. My Boot Animation just won't change. Using the GRVY Theme boot animation for a few months now. And today, installed a new theme. Changed the boot animation and still, it doesn't change. It stays with the previous Boot Animation. I also applied the CM stock Boot Animation. Resets the theme chooser into stock look again. And still, the boot animation still stays GRVY. Uninstalled the GRVY theme. Cleared cache and dalvik. And still.... It still stays with GRVY boot animation... I'm tired of rebooting a lot of times testing here and there aaaaaaa. Any idea guys? The boot animation just won't change no matter how I try to change it.

Hopefully someone will reply / help me.
[Nexus 6P General] Jammol:
When you first changed to GRVY, was it a physical changes, meaning, you went into system/media and chopped over the original boot animation that was there?
[Nexus 6P General] Mr.Zombie:
I've managed to get the stock cm boot animation back again but sadly now, the cm boot remains even if I changed the boot animation from other themes. It's a CM Bug I must say.

If anyone knows how to fix it. Do let me know. ?
[Nexus 6P General] Jammol:
I just booked back up cm13 to duplicate what you did and it's changing for me back and forth.
[Nexus 6P General] :
Bootanim not changing issue happened to me when the phone was not decrypted.
[Nexus 6P General] Johannes667:
Could somebody Upload the latest cm13 nightly? Lost All my Downloads. I don't want update to cm14
[Nexus 6P General] Mr.Zombie:
Which nightly you're using? Weird. I just can't. :/
[Nexus 6P General] Jammol:
Literally on the previous page.

---------- Post added at 07:25 AM ---------- Previous post was at 07:25 AM ----------

I tried the latest nightly for cm13 that was posted on the previous page.
[Nexus 6P General] djdarkknight96:
Life saver! This was my last stop so I searched five seconds here and boom. Lol
[Nexus 6P General] AndyYan:
For whoever's still on CM13 (now half-rebadged as LineageOS) just as I do, my January build: https://www.androidfilehost.com/?fid=457095661767129423

Marshmallow has been abandoned as there's no more security patches, and we'll be stuck with December 2016 patch set until we move to Nougat, but whatever...
[Nexus 6P General] Abdulaziz6p:
Work on 7.1.2?
[Nexus 6P General] nnth:
Were searching for latest CM13 mirror and found your post. Thank you a lot man!
[Nexus 6P General] AndyYan:
No prob. If you look inside my AFH profile there should be slightly more updated builds for grabs, too.

Sent from Google Nexus 6P @ LineageOS 14.1
[Nexus 6P General] nnth:
Yeah. I'm currently using the 20170216 built. Work great so far! :good:
[Nexus 6P General] cyberdionisio:
Hi, may I ask you if the 20170216 build has CM Theme Engine built in? Thanks.
[Nexus 6P General] AndyYan:
CM/Lineage 13 always did.

Sent from Google Nexus 6P @ LineageOS 14.1
[Nexus 6P General] c_86:
hell.. finally got CM 13 to bot, jesh...

finally was able to get fastboot to work, it was a driver issues (go figure)...

flashed back to 08M stock, fastboot installed TWRP, then flashed the latest nightly and gapps... boot with the red triangle blah blah blah, and boom... booted

currently its optimizing apps...

what a chore to install CM13... jesh
[Nexus 6P General] jgoedhard:
When I first installed cm13, I was installing on the very first stock m6 ROM but after I did a clean + unrooted to the latest stock m6 ROM, I then rerooted + recovery and the cm13 installed fine after the second root.
[Nexus 6P General] tdamocles:
I must say that in a few days CM went from having difficult bugs to work with to one that I may use as a daily driver. It is smooth running.
[Nexus 6P General] Ethian:
Has anyone noticed that icons don't change when switching themes?