Note 20 Ultra Change in Bluetooth car and headset behavior

[Darth Mo]

Up until a couple weeks ago (may have been the same time as the VZW Nationwide 5G update, not sure) I would start my day leaving the house with my LG Tone neckband powered on and connected. But when I got in my car (2017 Infiniti Q50), the call function of the phone would pass over to the car automatically then pass back to the neckband when I turned off the car.

However, it no longer does this. When I get in the car, I have to manually go into the Bluetooth settings and enable call control for the car, then do the same thing to turn it back on in the neckband when I turn the car off. My Gen 5 Fossil watch always stays connected and available calls though for whatever reason.

I've tried unpairing and re-pairing everything in various combinations, but the automatic handover just doesn't work anymore. Any ideas? And the reason this is really annoying is because I am a field engineer so I'm in and out of my car a dozen times per day so it's a bit of a pain to have to switch back and forth, especially with several 5-10 minute stops/car rides.

Thanks in advance.

 

[mustang7757]

Hi, you tried reset the network in settings?

 

[Darth Mo]

Hi, you tried reset the network in settings?

Hello, not sure what setting you're talking about? All devices can connect fine, it's just the calling handoff. If I have an active call it will not drop, it just won't switch devices. This worked fine from August until a couple weeks ago as well as with the S20 Ultra I had previously.

 

[mustang7757]

Hello, not sure what setting you're talking about? All devices can connect fine, it's just the calling handoff. If I have an active call it will not drop, it just won't switch devices. This worked fine from August until a couple weeks ago as well as with the S20 Ultra I had previously.

Ok what I'm suggesting is try network reset , this resets Bluetooth also incase a update or glitch did something to Bluetooth.
To do this go to settings >general management >reset>reset network ..try this as a first step in trying to troubleshoot .

 

[Darth Mo]

Ok what I'm suggesting is try network reset , this resets Bluetooth also incase a update or glitch did something to Bluetooth.
To do this go to settings >general management >reset>reset network ..try this as a first step in trying to troubleshoot .View attachment 328762

Thanks, gave that a go, but no change.

 

[mustang7757]

Thanks, gave that a go, but no change.

Can you send any apps that control Bluetooth history?

 

[Darth Mo]

Can you send any apps that control Bluetooth history?

I think I have it sorted...or at least well enough lol. It seems having the watch configured for calls was causing the issue. Since it's always connected, I guess that was making either the neckband or the car the "second" device configured for calls so whenever I'd activate one or the other the car or neckband was getting bumped out. I disabled calls for the watch and now call functionality hands off how it did before.

Only drawback is I can't see who is calling by checking the watch, but I can live with that.

 

[mustang7757]

I think I have it sorted...or at least well enough lol. It seems having the watch configured for calls was causing the issue. Since it's always connected, I guess that was making either the neckband or the car the "second" device configured for calls so whenever I'd activate one or the other the car or neckband was getting bumped out. I disabled calls for the watch and now call functionality hands off how it did before.

Only drawback is I can't see who is calling by checking the watch, but I can live with that.

Ok so you have multiple devices on BT , well at least you got a handle on it , nice work

 

[CKwik240]

I think I have it sorted...or at least well enough lol. It seems having the watch configured for calls was causing the issue. Since it's always connected, I guess that was making either the neckband or the car the "second" device configured for calls so whenever I'd activate one or the other the car or neckband was getting bumped out. I disabled calls for the watch and now call functionality hands off how it did before.

Only drawback is I can't see who is calling by checking the watch, but I can live with that.

Interesting. I have issues with bluetooth playback in my car if I'm not wearing my watch. It ends up skipping a lot. I keep thinking it's somehow trying to communicate with my watch at home for player controls. Its not a huge problem as I also always wear one of my watches when I leave the house, but still an odd problem. This has occurred with every Samsung phone I've had since I got my watch. I haven't changes cars, but doesn't happen with the gf's iphone when she takes the car.