Jimmy_D

I recently purchased a Nexus 6P phone and paired it without issue to my 2015 TLX I4 Tech. Music streams wonderfully, again, without issue. I can even receive calls without issue. No complaints there.

When I initiate calls from the phone or from the car, however via Bluetooth, this is what happens:

1. Call is initiated
2. Phone begins to dial and this is reflected both on the phone and the infotainment screen
3. Almost instantly, on the infotainment screen, the "Hang Up" soft button is activated and I hear the "Hang Up" chime from the car's audio, however the phone is continuing to make the call. I hear no audio at this point from the phone or car audio.
4. After about ten seconds, I do hear my call on the car's audio system and by this point, the person I'm calling is frantically yelling, "HELLO?!?! HELLO?!?!", since they haven't heard anything from me for 10 seconds or so.
5. At this point, I explain the trouble I'm having with calling over Bluetooth and the call is perfectly fine from that point forward

Anyone else have this experience with their cars / phones?

I originally had a 2013 Moto X paired to it and did not experience that issue, so I'm guessing it's got something to do with the phone and will be hopefully fixed in due time with a software update, but wanted to throw this question out to see if anyone else has any tips or tricks or has had a similar experience. I've repaired it a few times, but the issue persists.

Thanks for your thoughts.

a77

yep - exactly the same problem for me (nexus 5 with Marshmallow). warning android users - do not update to marshmallow! I tried deleting the phone and repairing and thought this had fixed it - it doesnt. I had other problems when going to lollipop before the earlier confectionery. It inverted fist and last names and rendered dialling by voice impossible. and I never got round that problem. There's a bigger issue at stake here too - more and more cars interfaces are designed to work with phones. But phones update themselves so often it becomes impossible for the manufacturers to ensure their vehicles remain compliant. I am calling Acura tomorrow if I get a minute.

a77

maybe it only effects white/espresso 2.4 Techs....snap!

a77

oh dear....

https://productforums.google.com/for...ce=forum/nexus

we are not alone....

Jimmy_D

Thanks for posting that. Makes me feel a little better knowing that there are plenty of others with the same issue.

I'll follow that thread and keep my fingers crossed for a software update that resolves it.

SRT ACE

Nexus 5, 2008 Acura TL-S - was working well together until going from Lollipop to Marshmallow (clean install with factory image)...

My phone just got the November security patch update (dated 2015-11-01) and it seems to have resolved the HFL disconnect problem. What a relief...

Hope yours resolves soon.

-ace

niray9

Same problem with Nexus 5.
Also additionally in my case, First time the voice call is garbled/has static noise always when call initiated from the car via bluetooth.

Anyone found any solutions yet?

jctiii

I haven't taken delivery of my new TLX yet, but I also have a Nexus 6P, so I hope that SRT ACE is correct that the November update fixes this problem. I use BT connectivity a lot!

On another note (but still within topic), I've ready a few (older) threads about being able to get Android devices to work somewhat like the "Siri Eyes Free," such that they can activate Google Now with the Talk button. In the threads I saw, it seemed that the procedures to do so worked for some, but not others, and a consistent conclusion was never presented one way or the other. Does this just work with Android now (presumably, via a software update), or if not, has anyone figured out a sure-fire way of making it work?

JT3

Heh... I was wondering why I only had a really low number of posts when I used to hang out on this forum a lot. Turns out, I somehow had two accounts. I found my original one, and will be using this. So... JCTIII is now JT3. I'd edit the post above to reflect this, but I think it's too new for editing privileges.

JT3

Well, well... Looks like this issue is bigger than we knew:

[Bug Watch] Vehicle Bluetooth Call Audio Problems Being Reported On All Four Nexus Phones With Marshmallow

a77

well....I have now downloaded Android 6.0.1...which some say fixes the issue. Will report shortly.

audioxbliss

A bit late, but wanted to report in. My 5X was having the same issue, but a recent app update seems to have fixed it. Not on 6.0.1 yet.

a77

Now works fine :-)

JT3

My Nexus 6P suffered from the dreaded "Outgoing Calls" issue, running Android 6.0.1, with Google Connectivity Services C.1.6.6. However, yesterday, I got an update to GCS C.1.6.7, and it seems to be resolved.

audioxbliss

Good to know what solved it

jim256

Anyone with a Nexus 6P and Tech package getting Text message notification (the envelope on the upper screen)?

I'm on 6.0.1, no calling or drop issues, but also no text notifications. If I get a text and go to the Inbox, the incoming text is there and after I view it, the envelope icon appears when I return to the NAV display. I have alerts on, deleted and re-paired after the OTA 6.0.1, select account on SMS. I reviewed the google forum posts above, and found one similar problem after 6.0.1. Text notification works fine on my '15 Lexus NX NAV.

JT3

I'm getting the little envelope, but that's it, and I get it all the time, as if it's reading that I have text messages (although no new ones). If I get a text message while linked up via bluetooth, I get no additional notification, and the text is not read to me.

I can go into the history, and I can see the prior text messages listed, although I'm not sure I can read them.

jim256

Same here, but I never get the envelope unless I go to the Inbox. On my old Lollipop phone, it would alert then read if I chose, as you indicate. If I delete all the text messages or reply to the last one from the Inbox on the car, then the envelope disappears. Not a big deal, Google will probably resolve it.

a77

There's still a problem. my first call out is sometimes impossibly garbled. subsequent calls are usually ok. How can this even be possible? I am preserving for now, but its potentially dangerous. I have to stop the car and switch it off to make a call to be safe...and it isnt always that easy finding somewhere safe to stop. I know...just dont make a call.....makes you wonder how troublesome just making a bluetooth call is - how the hell is something as complex as android auto or apple car play going to be. Moral is....never update your phone.

jim256

FYI, my Nexus 6P is exceptionally clear on first and subsequent calls per my wife when I call her, better than the prior Moto X on Lollipop. Aside from deleting your phone and re-pairing under 6.0.1, no suggestions here.