yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] sam3000:
snakecharmer23: does BT audio streaming work okay for you ? I have been assuming it was broken for everyone.

There are underflows occurring in the BT stack (don't have logs to hand but you can see it clearly in logcat when a glitch occurs). We might need to adjust some buffers or timers somewhere.

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

No, we don't have ok google from screen off right now. We're compiling audio hals from source and from past examination it looks like we need BOARD_SUPPORTS_SOUND_TRIGGER := true for the hal to include always on trigger detection. Unfortunately, this depends on proprietary headers that cm doesn't have. If we copy the google image audio hal binaries (and also hotwordenrollment.apk), it almost works. That is, it now always wakes on hot word but doesn't trigger google now. Probably something else is required too. Either way, it's regrettably not supported right now.

We could add project fi apks to stock angler cm but can't you just install separately ?
[Nexus 6P General] oned:
Hi guys, just bought my new 6p, and want to flash CM13. Question, is it as fast and smooth as last stock rom ? Thank you for your answers and plz be objective
[Nexus 6P General] alessandro_xda:
when i bought my 6p i started using it with the stock rom,

then i added Xposed and then i tried cm13 nightlies.

to be honest i think that it's not worth it!

i've had some nexus devices many years ago (nexus s, and galaxy nexus) and there was a lot of interest about cm but now i don't see it any longer.

i've found many bugs in cm13 nightlies like:

-a system error on every reboot

-locked screen when i have to answer a call

-bad audio performances (really low volumes)

-cant record calls (boldbeast app is not supported)

-bluetooth issues (noises while listening)

many years ago it was worth it to have issues because you could also get many benefits out of cyanogen rom but now the important features can be found on many roms so i decided to move to purenexus rom and i'm really satisfied so far.
[Nexus 6P General] snakecharmer23:
I stopped using CM13 in January. It is more trouble than it's worth. I still follow this thread and the changelog closely in hopes that it will get more stable but the truth is, Stock Marshmallow has almost all the features I'm looking for and it is rock solid.
[Nexus 6P General] Smallsmx3:
I flashed yesterday for the first time on my 6p. Thought to myself, wow, smooth and well done. Then 12 hours later reboot city... Can't make a phone call or receive one, never again
[Nexus 6P General] Fralund:
I also reported about this several times in this thread. I had to reflash my device when the problem started and then I could use a couple of hours up to several days, then it started again. I finally gave up and switched to another ROM. I haven't had a single issue since then using the same apps and hardware.
[Nexus 6P General] kogone:
snapshot is stable as a table!

6p,c2,pi0
[Nexus 6P General] farfromovin:
No distorted sound upon first reboot? No battery drain or random reboots?
[Nexus 6P General] MaxNXS:
What about Bluetooth sound? Any crackling, skipping or sound quality issues?
[Nexus 6P General] Ok_Kaleidoscope5109:
21-APR nightly is rebooting like mad. I'm going back to 20-APR.
[Nexus 6P General] hanschke:
can anyone to a mirror for the cm dialer because the google is only crashing and I cannot do a call. I try to flash the nightly again but it is not installed anymore :(
[Nexus 6P General] AndyYan:
I'm on an earlier nightly (0412), and it seems the distorted sound on boot is finally gone. Slow boot time and bluetooth audio skipping are still there, and I don't know whether these are fixed in the past 2 weeks or so.

Anyways, people who are still sticking to CM by now must have learnt to tolerate its disadvantages ;)

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Nexus 6P General] rwong48:
fresh installed 4/23 nightly (if it means anything, opengapps 4/22 arm64 nano), and I can't slide down for quick settings or notifications. plugged into the computer for file transfer, but there's still "no notifications"

went to 4/19 snapshot instead and it's fine.
[Nexus 6P General] razorloves:
MMB29V https://github.com/CyanogenMod/android_device_huawei_angler/blob/stable/cm-13.0-ZNH0E/cm.mk#L25

link, if you need it: https://www.androidfilehost.com/?fid=24499762636007868
[Nexus 6P General] winxuser:
Clean installed 24/4 nightly. No lock screen, no notifications, can't slide quick settings down. Tried to update to latest nightly made no difference
[Nexus 6P General] farfromovin:
The no pull down menu is a pita. Biggest Nexus CM bug I've encountered on 2 Nexii.
[Nexus 6P General] winxuser:
Its not just nexus phones, its all phones using cm
[Nexus 6P General] razorloves:
Heads up:

Starting with 27 may nightly, the cLock app has been revamped. Weather providers are no longer in the app, or in the rom. Not sure if they plan to add any in the future, but for now they have added a weather provider to the app store. Here: https://play.google.com/store/apps/details?id=org.cyanogenmod.wundergroundcmweatherprovider

After you install the app, you can see it in Settings > Weather. It's a bit of a pain to get going because you have to signup on the weather underground site to get an api, but after that it seems to be working perfectly great.

---------- Post added at 06:22 AM ---------- Previous post was at 06:15 AM ----------

It was caused by a bad change made in opengapps, in case you didn't know.

The opengapps dev reverted the change 4 days ago, so it's no longer a problem on new gapps.

See comments here: https://github.com/opengapps/opengapps/commit/ca0704182ac3c9f47d1ad4c5494500866ba42665
[Nexus 6P General] razorloves:
More info about the weather change http://www.cyanogenmod.org/blog/plug-play-weather
[Nexus 6P General] Michalko5896:
Hey guys, can I use the latest vendor (MHC19Q) with the latest nightly build?
[Nexus 6P General] tibere86:
Yes you can :good:
[Nexus 6P General] Exostenza:
Are the developers aware of the bluetooth audio issues? It seems like that problem has been going on for too long now...

Also, I am on the latest snapshot and every time I switch between the two networks in my house, even though it says they are both saved, I have to put in the password. It is really annoying as I do it a couple times a day. Does anyone else have this problem and/or know what to do to have it save the password so I don't have to put it in every time. The weird thing is that it only happens when I manually switch but if I turn Wifi on it will automatically connect without asking for a password but it never connects to my secondary network even if the signal is stronger. Not the biggest deal but still annoying nonetheless.

Thanks XDA!
[Nexus 6P General] coolswap11:
Hey Guys there is an issue in the stock android of nexus 6p for the headphones without mic when connected to device renders microphone of the device disabled. I had raised the issue and an Android Engineer is asking for kernel level logs for the same. Since my device is not rooted one , if someone could help me out with the logs it'll be really great.

https://code.google.com/p/android/issues/detail?id=195815

The Android Engineer is asking for the following

Hi Any one here can help us with dynamic logs ?

Please follow these steps :

1. adb root

2. adb disable-verity

3. adb reboot

4. adb root

5 .adb remount

6 .adb shell

7.adb shell "echo -n "file wcd9xxx-mbhc.c +p" > /sys/kernel/debug/dynamic_debug/control"

8.then did what you test with headset

9.adb shell dmesg > kernel_logs.txt (This captures the kernel log)

please share the logs.txt with us
[Nexus 6P General] razorloves:
The monthly ota security update from google for the Nexus 6p (MTC19T) is out and the changes have been merged into cm today. (special thanks to romanb, sam3000 and nuclearmistake)

Starting with the May 4th nightly, you will need the vendor img from that monthly update. I have downloaded the factory image (MTC19T) from google and extracted the vendor img and uploaded it to AFH. Link is here, if you want it:

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

I also hash checked the radio and bootloader in this new factory image (MTC19T) and they're the same as the ones in the last few updates, so no need to update them. (bootloader v3.51 / baseband v3.61)

Side Note: Screen off "ok google" hotword detection is about to be fixed and should be in the nightlies soon. Just waiting on a few changes to be reviewed and merged:

http://review.cyanogenmod.org/143135/

http://review.cyanogenmod.org/141016/

http://review.cyanogenmod.org/137818/
[Nexus 6P General] Mr.Zombie:
Hello. I've downloaded the latest vendor from your link given. How to fastboot "only" the vendor.img? Any idea?

I'm using the "flash-all.bat" before this. Any steps please? :confused:
[Nexus 6P General] razorloves:
use twrp. click install, click images, then select vendor img, then select vendor partition
[Nexus 6P General] Mr.Zombie:
Is that all? That's easy? Thank you so much for your help! :D :good:
[Nexus 6P General] XAL2:
I flashed your Image file in TWRP and now when I go back into twrp I cant access anything because it says that its ecrypted. I cant flash anything in twrp atm because nothing shows up. Any ideas on what happened and how to fix?
[Nexus 6P General] razorloves:
The vendor img has nothing to do with that.

What else did you do while in recovery?

What version twrp you using?

Might want to seek help in the twrp thread here.
[Nexus 6P General] Smallsmx3:
Any idea if hotword detection is CM implementation or Google's? Cause Google's on the 6p sucks ass. It was amazing on shamu but on angler it's the only thing that doesn't work....
[Nexus 6P General] hi2u2:
Did you perhaps flash the vendor.img to recovery or boot partition by accident? TWRP gives you an option for which partition to flash after selecting the image. The older versions of TWRP did not have an option for "vendor," which is the correct one to flash to.
[Nexus 6P General] Exostenza:
[MENTION=614507]razorloves[/MENTION] do you know anything about any development going on to fix the bluetooth audio stuttering issues? It seems to have been plaguing us on angler for much too long. I read a while back that a new merge would fix it but upgrading to the snapshot after it was merged hasn't made a difference for me. Also, I have the problem where whenever I want to manually switch a Wifi network (when the network is saved) it always asks me for the password. Any idea why this is going on? Thanks!
[Nexus 6P General] razorloves:
Both.

It's using google's HotwordEnrollment.apk, but the deeper level coding that triggers it is cm and caf.

The hotword fixes were merged a few hours ago, so try out the May 5th nightly and see if it's better than stock.

Sorry, haven't heard anything about those. I looked through jira a few days ago and didn't even find a report on our bluetooth issue, so that really needs to be done. The wifi password bug you mentioned doesn't happen with me. Have you tried factory reset or just wiping wifi settings? You can do that by deleting these 2 folder: /data/misc/dhcp and /data/misc/wifi
[Nexus 6P General] coldconfession13:
What you didn't know about the bluetooth audio bug. I guess cause nobody reported to jira but it is all in this thread like crazy. That is why I left cm on angler/
[Nexus 6P General] MaxNXS:
Same here. There is even a thread on the official CM forum about it. The question is, anybody NOT having BT audio issues? I can't believe this has not been addressed yet.
[Nexus 6P General] razorloves:
I don't know what you're saying. I've read about the bug plenty of times in here. You can report bugs on xda a billion times and our cm device maintainer will still not know about it. Maybe he's never played music over bluetooth and is not aware of it. Or maybe he is aware and doesn't know how to fix. Idk. But anyways... JIRA is where you have to report bugs. That is their bug tracking system, so we have to use it.
[Nexus 6P General] anderssonyang:
What bug is it? I'm on 5/4 build and bluetooth audio is perfectly fine. I've been using it on my car for quite some time
[Nexus 6P General] mimmo13:
Hi, I've a question. I know that from the 20160504 nightly I have to flash the latest vendor Image MTC19T. What's the procedure if I have a previous build? First flashing vendor Image and then the rom or vice versa? How?

Thanks﻿

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P General] beinartas:
You can firstly flash the rom. Nothing terrible will happen if you don't flash vendor - you will get a message when booting up about things being not right and thats basically it.

You can then flash vendor in TWRP or from PC using USB cable.

If using TWRP:

Download vendor.img from Google https://developers.google.com/android/nexus/images Extract from zip to your phone. Reboot into Recovery. In TWRP navigate to folder where vendor.img is. Bottom right button choose to flash images, not zips. Choose vendor.img, choose vendor partition.

When booting CM warning should be gone.

If using PC:

Use some tutorial e.g. http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Basically reboot your phone into bootloader (just press and hold power and volume down until phone reboots and shows bootloader),

Connect phone to PC with USB cable.

Extract vendor.img from zip to your computer, open terminal in that directory where image is.

You can check if device is seen with

"fastboot devices".

If some ID is shown you can proceed with

"fastboot flash vendor vendor.img"

and it should be done in a second.

Reboot phone to see if warning is gone.

Of course you can e.g. flash new CM build in TWRP, don't reboot phone, flash vendor img you prepared before. Then you will never see the warning in the first place.
[Nexus 6P General] mimmo13:
Thanks! [emoji2]

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P General] Smallsmx3:
Anyone use the latest OK Google in the latest nightly? How's it working? And does it work with the screen off
[Nexus 6P General] beinartas:
Yes, it does work with screen off. Not always gets my voice, not 100% accurate but definitely can hear you, unlock phone if voice is recognized and etc.
[Nexus 6P General] Smallsmx3:
OK. So it's pretty much the same as stock behavior. I'm just curious what is different about the 6p vs the Nexus 6 that its not as consistent. On shamu voice recognition was amazing. Sometimes my angler never responds
[Nexus 6P General] MaxNXS:
It's a bug that makes the audio playback through BT devices skip, stutter, pop. In my case it varies in severity depending on the device I connect to. I tried the following:

- Boston Acoustics BT Speaker (worse case, with audio stuttering every second. Unusable)

- Bose SoundLink Color BT speaker (almost as bad as the one above, still unusable)

- Mazda 3 Sport BT Audio (audio stuttering every 10-15 seconds if phone is left alone, otherwise it's worse)

- Jabra Sport Pace BT earbuds (same as above)

- Vizio soundbar (popping and stuttering every 30 seconds with phone not in use, more frequent with phone in use)

- Kivio BT headphones (same as above)

Once I reverted back to stock rom all the BT issues disappeared and the audio playback on those same devices is flawless. In CM13 I even tried ElementalX and Franco's kernels and the BT issue still persisted.

Over 90% of my audio listening is through BT so in the current state CM13 is completely useless to me.
[Nexus 6P General] sam3000:
We'll be tackling this (it's caused by internal buffer underflow). I see it as the last big thing we need to fix for cm angler.
[Nexus 6P General] MaxNXS:
Thank you for the update! I'm looking forward to it.
[Nexus 6P General] anderssonyang:
I tried BT audio on my pioneer car audio, UE boom and Bose soundlink 3 and did experience maybe 2 seconds of skips when I unlock my screen, but they work alright since then. Are you on the latest nightly build?
[Nexus 6P General] sam3000:
FYI - it's not a fixed problem. Symptoms vary in severity depending on how much other background app activity you have going on.
[Nexus 6P General] anderssonyang:
I see. I thought they fixed part of the problem so it is at least usable right now:)
[Nexus 6P General] razorloves:
For those interested, there's a new weather provider in the play store. This one is a lot easier to use. No api needed.

https://play.google.com/store/apps/details?id=org.cyanogenmod.yahooweatherprovider
[Nexus 6P General] kogone:
no QS function in 05/07. everything else is flawless

6p,c2,pi0
[Nexus 6P General] AndyYan:
I traced this issue back on JIRA and it seems there are changes with CMSetupWizard, such that makes the phone misbehave if you remove it on a clean install (e.g. when flashing OpenGapps). I really don't see what's the point behind the change, but for now the solution is to not remove it (e.g. adding an exclusion when installing OpenGapps).

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Nexus 6P General] kogone:
awesome thanks man. saved me a lot of time :highfive::highfive::highfive:

how do you go about adding an exclusion?

edit: nvm following this : https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

edit2: worked like a charm!
[Nexus 6P General] be_vigilant:
Still BT skipping when playing to my car audio system. Back to stock. I will keep an eye on this thread for if its ever fixed.
[Nexus 6P General] coldconfession13:
Yea I went back to CM but the BT skipping still exist. What is the jira link
[Nexus 6P General] hi2u2:
The phone is stuck on "finishing boot" after flashing latest nightly (051116). Anyone else seeing this?
[Nexus 6P General] jr67:
Same thing here. Same thing happened with the 0509 build. Had to flash back to the 0508 build.
[Nexus 6P General] razorloves:
weird. no problem here. went from 0509 to 0511 nightly using cmupdater. working fine
[Nexus 6P General] beinartas:
Updated from 0505 to 0511 with no issues. Something else should be causing problems for other guys. Custom kernel?
[Nexus 6P General] mamv:
No problem installing also, but getting random reboots.
[Nexus 6P General] std396:
Do fresh install. We all no dirty flashing may cause issues, even if its an update.
[Nexus 6P General] Ok_Kaleidoscope5109:
Clear cache. Worst case try a fresh install. I updated from 5/7 to 5/11. Working just fine.
[Nexus 6P General] sam3000:
I'm getting soft reboots too and it looks like it's happening on bullhead as well.

If you see this in your logcat after a soft reboot has occurred then we have the same issue:

W Watchdog: * WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on main thread (main)

W Watchdog: main thread stack trace:

W Watchdog: at android.media.AudioSystem.setParameters(Native Method)

W Watchdog: at com.android.server.audio.AudioService$AudioServiceBroadcastReceiver.onReceive(AudioService.java:5392)

[cut]
[Nexus 6P General] mamv:
Yeahp, that's it. Using today's nightly:

05-13 15:38:40.555 E/Watchdog(5808): Triggering SysRq for system_server watchdog
05-13 15:38:40.564 W/Watchdog(5808): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on main thread (main)
05-13 15:38:40.565 W/Watchdog(5808): main thread stack trace:
05-13 15:38:40.565 W/Watchdog(5808): at android.media.AudioSystem.setParameters(Native Method)
05-13 15:38:40.565 W/Watchdog(5808): at com.android.server.audio.AudioService$AudioServiceBroadcastReceiver.onReceive(AudioService.java:5392)
05-13 15:38:40.565 W/Watchdog(5808): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:882)
05-13 15:38:40.565 W/Watchdog(5808): at android.os.Handler.handleCallback(Handler.java:739)
05-13 15:38:40.565 W/Watchdog(5808): at android.os.Handler.dispatchMessage(Handler.java:95)
05-13 15:38:40.565 W/Watchdog(5808): at android.os.Looper.loop(Looper.java:148)
05-13 15:38:40.565 W/Watchdog(5808): at com.android.server.SystemServer.run(SystemServer.java:300)
05-13 15:38:40.565 W/Watchdog(5808): at com.android.server.SystemServer.main(SystemServer.java:172)
05-13 15:38:40.565 W/Watchdog(5808): at java.lang.reflect.Method.invoke(Native Method)
05-13 15:38:40.565 W/Watchdog(5808): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
05-13 15:38:40.565 W/Watchdog(5808): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
05-13 15:38:40.565 W/Watchdog(5808): *** GOODBYE!
05-13 15:38:40.750 E/AndroidRuntime(8147): Error reporting crash
05-13 15:38:40.750 E/AndroidRuntime(8147): android.os.DeadObjectException
05-13 15:38:40.750 E/AndroidRuntime(8147):	at android.os.BinderProxy.transactNative(Native Method)
05-13 15:38:40.750 E/AndroidRuntime(8147):	at android.os.BinderProxy.transact(Binder.java:503)
05-13 15:38:40.750 E/AndroidRuntime(8147):	at android.app.ActivityManagerProxy.getConfiguration(ActivityManagerNative.java:3964)
05-13 15:38:40.750 E/AndroidRuntime(8147):	at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:88)
05-13 15:38:40.750 E/AndroidRuntime(8147):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
05-13 15:38:40.750 E/AndroidRuntime(8147):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
05-13 15:38:40.783 E/AndroidRuntime(3460): Error reporting crash
05-13 15:38:40.783 E/AndroidRuntime(3460): android.os.DeadObjectException
05-13 15:38:40.783 E/AndroidRuntime(3460):	at android.os.BinderProxy.transactNative(Native Method)
05-13 15:38:40.783 E/AndroidRuntime(3460):	at android.os.BinderProxy.transact(Binder.java:503)
05-13 15:38:40.783 E/AndroidRuntime(3460):	at android.app.ActivityManagerProxy.getConfiguration(ActivityManagerNative.java:3964)
05-13 15:38:40.783 E/AndroidRuntime(3460):	at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:88)
05-13 15:38:40.783 E/AndroidRuntime(3460):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
05-13 15:38:40.783 E/AndroidRuntime(3460):	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
--------- beginning of main
[Nexus 6P General] Smallsmx3:
Sweet broken build after broken build
[Nexus 6P General] AndyYan:
CM is breaking things like a cat trapped in a house these days. The newly introduced CMSetupWizard is an example. At this rate I might have to jump ship.

"If it ain't broken, don't fix it."

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Nexus 6P General] snakecharmer23:
Development channel AKA nightlies are experimental and unstable. That is the nature of the beast. If you want something more stable, stick to the release channel AKA snapshots.

https://wiki.cyanogenmod.org/w/Release_Versioning#CyanogenMod_11_-_13_Community_build_tags
[Nexus 6P General] AndyYan:
Sure...

Been using CM nightlies since CM7, and had it on dozens of devices, and apart from when an Android version initially comes out (e.g. my Nexus 4 got fked up by 4.3), things are fairly stable on all fronts. Nightlies on Nexus 6P is where I start to notice bugs constantly.

Plus, things like CMSetupWizard are CM's decision and will be there regardless of nightly or not.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Nexus 6P General] andyc2d:
Having a bit of a frustrating issue here, hopefully someone can weigh in on it. I just clean flashed the latest snapshot along with the latest Open GApps stock package. Everything seems to work fine with the exception of calling. I cannot make or receive phone calls as it causes CM to crash. I had this issue a few weeks ago when I was running nightlies and when I realized this was happening I just went back to the stock ROM because I was expecting an important call. Anyone have any ideas?
[Nexus 6P General] jr67:
Go to settings > apps > phone > permissions make sure the phone permission is set on. And since your already in apps make sure that the phone app is set as they default phone app (in apps click on settings icon > default apps). If that doesn't work then try a smaller open gapps package (full, mini, micro, pico)