All,

I've had this issue for awhile now, but when I'm plugged in and running Android Auto (Waze usually) and someone calls me, I can answer the call, but can't hear them talking. If I call them back, there is no issues. Also, if I just use Sync wirelessly when someone calls there is no issues hearing them right away. If it matters I have a Google Pixel 5 currently. It used to work fine until the last few months.

Anyone have similar issues or know how to fix it?

Thanks! 👍

 

I have the same issue, pixel 6. If i get a call, i just decline it and call them back. Or i have to unplug the phone, answer the call, then plug it back in. It's been going on for as long as i can remember. I have no way of fixing it.

 

I have a similar issue. When I get a call, I can hear them talking, but they can't hear me. If I hang up and call them back, everything is normal. I had a Galaxy S20 and now an S22. Didn't make a difference.

 

I was also having this issue and some research helped me out. Go in to the phone settings for the truck itself and change the ringtone to use to the one on the phone. I've had it happen a couple times now and each time it was that setting that had changed. Hope that helps

 

I have that issue also. I answer the phone call, then quick press the bluetooth button on the phone call screen on the phone and turn it back on. It's fast enough that the person on the other end doesn't notice. It's annoying but I do it without thinking about it anymore.

 

@PKock That's exactly what I ran across online today as well. I'll try it out. Thanks for the response! 👍

 

Have had this happen more times than I can count and can confirm this is the solution that solves the problem every time. What I have yet to discover is how or why the setting gets changed from time to time in Sync.

 

I'm having the same frustration. It seams like a Sync 3 issue. Has anyone determined how, when, or what triggers the Ringtone setting in Sync 3 to revert to "Ringtone 1" after it is manually changed to "Use Phone Ringtone"?

 

Upgrade to 3.4 SOLVED my same issue. It's a work around but not a FIX.