Since getting Marshmallow, why can I no longer hear outbound call ringtones over Bluetooth?

[AC Question]

Marshmallow. No longer hear outbound call ring tone over bluetooth.

Prior to upgrading to Marshmallow on my Nexus 5, I would always hear the phone ringing until call answered when making a call over Bluetooth. Now, I no longer hear the ringing and radio continues to play until call is answered. Then Bluetooth kicks in. I'd like to hear the ringing again. Anyone else experiencing the same issue?

 

[pascanu]

Same here. Any solutions? Anybody?

 

[B. Diddy]

Welcome to Android Central! I haven't noticed that. Have you both already wiped the cache partition? http://forums.androidcentral.com/nexus-5-rooting-roms-hacks/352008-guide-nexus-5-recovery.html

 

[olle_1]

Yes, I'm also experiencing this issue however the radio gets mute (on Mazda) while "dialing".
Tried to reset the cache as been advised above but no success.

 

[pascanu]

Tried clearing cache, no success.

To better describe the symptoms:
"Devices: Nexus 5 + Mazda CX-5 (2013)
What actually happens: if I initiate a call while connected via BT to the car system the phone starts dialing, the car audio (radio) turns off, then there's a beep just like the phone has hang up, radio starts playing again but the phone is actually dialing and is still connected tot the car BT. As soon as the other party picks up the audio system switches to the phone and everything goes back to normal. Strange and annoying becaus you don't know if the phone is actually dialing unless you look at it.
This started happening after I upgraded to M.

 

[anon(243620)]

Tried clearing cache, no success.

To better describe the symptoms:
"Devices: Nexus 5 + Mazda CX-5 (2013)
What actually happens: if I initiate a call while connected via BT to the car system the phone starts dialing, the car audio (radio) turns off, then there's a beep just like the phone has hang up, radio starts playing again but the phone is actually dialing and is still connected tot the car BT. As soon as the other party picks up the audio system switches to the phone and everything goes back to normal. Strange and annoying becaus you don't know if the phone is actually dialing unless you look at it.
This started happening after I upgraded to M.

Same problem after m update
Mazda 6 2015

 

[B. Diddy]

Interesting--I wonder if that's a Mazda issue. I'm not having that problem on my car. My wife has a 2010 Mazda 6, though, so I could experiment with that later.

 

[Tmarto]

Same here. Mazda 6 2014.

Tried: clearing cache, reset to factory defaults. Still not working

 

[corpgator]

Not just a Mazda issue. I have the same problem on a Honda Civic and a Hyundia Elantra.

 

[B. Diddy]

This probably won't help, but try unpairing the phone, then re-pairing again.

 

[anon(243620)]

Yeah that didn't work

 

[Melophat]

I'm having the same issue in my 2015 Hyundai sonata with my Nexus 5.. Definitely not just a mazda issue. I also have the Android Auto upgrade for my car and this issue occurs while using both the factory bt screen/system and in when im in Android Auto. Didn't have it on any of the M developer previews, it started when I moved to M final.. Also, I did a fresh flash straight from the Google provided images, including a factory wipe after the images were flashed, so there's not really any possibility of left over files mucking up the mix.. This is killing me, as I make a lot of business calls while driving and there is a good 5-7 second delay from the point where the other end picks up and when I can actually hear them.

 

[olle_1]

Eventually downgraded to hammerhead - happy camper now

 

[Siddharth Shah4]

Same problem

 

[Siddharth Shah4]

Re: Marshmallow. No longer hear outbound call ring tone over bluetooth.

I have the same problem. Major hazard as it messes with hands free

 

[hallux]

Re: Marshmallow. No longer hear outbound call ring tone over bluetooth.

I have the same problem with a headset and my Nexus 6P. New phone, freshly-paired hands-free device so it's a core OS issue it seems.

 

[Melophat]

I just got a brand spankin' new Nexus 6p and it's still having this issue, same as my n5.. this is definitely a CoreOS issue

 

[patruns]

This is a known BT issue. See here: https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=189188&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=189188