pixel 2XL will not answer/place calls if S3 watch is connected

[brazeagle]

My Pixel 2 XL will not allow me to answer or make a calI while my Samsung's S3 Frontier is connected via Bluetooth.
I can click the phone, speaker buttons and it will be mute for both sides.
My Pixel will only work if I shut down or disconnect my S3 watch.

I tried calling T-Mobile, Samsung, Google and yet to find a solution.
No one seems to know this problem, and I am sure I cannot be the only one.
Please help if possible.
Thank you
LCL

 

[racedog]

I had this same problem. No one could help with this issue and I called tmobile and Samsung. Ended up getting rid of the Pixel and am using the S3 with an LG V30 with no issues.

 

[Ca_lvn]

Pixel 2 Bluetooth problem end of story

 

[dmits]

Yeah, calls don't go to phone so need to untick phone in its Bluetooth settings to be able to use it.

 

[MikeC01]

I just got an SG3 Frontier and noticed that my Pixel 2 XL won't connect to my car's Bluetooth system while the SG3 is connected (or I can turn off phone calls as shown above).

Anyone know if watches running AW 2.0 have the same issue? I'm probably going to exchange my SG3 for and LG sport regardless because I prefer AW 2.0 to Tizen.

 

[Ca_lvn]

I just got an SG3 Frontier and noticed that my Pixel 2 XL won't connect to my car's Bluetooth system while the SG3 is connected (or I can turn off phone calls as shown above).

Anyone know if watches running AW 2.0 have the same issue? I'm probably going to exchange my SG3 for and LG sport regardless because I prefer AW 2.0 to Tizen.

It's not the watch it's your phone 100%

 

[Devhux]

So that means there's no way to use the speakerphone on the watch to place phone calls? (Gear S3 Frontier non-LTE) when paired with a Pixel 2 XL?

 

[Ca_lvn]

So that means there's no way to use the speakerphone on the watch to place phone calls? (Gear S3 Frontier non-LTE) when paired with a Pixel 2 XL?

Correct fault with pixel 2 Bluetooth will create issues if used that way.
Hoping for a future update to correct this from Google

 

[Devhux]

Good to know, thanks.

Also good that I saw this thread before my phone (and watch) go crazy tomorrow with Christmas wishes. Last thing I would have needed was to keep getting silent calls and wondering "what the heck is going on?"

 

[paradroid]

I can answer and place calls on watch with Pixel XL just fine, however, there is a problem with calls on my phone. They are really choppy or silence on the other end.

A new customer called me the other day, I answered the phone and there was silence. Later I get a customer complaint that I don't answer phone.

Turned off phone on the bluetooth connection and wishing for a fix one day. If I did not use my phone for business I'd give it more of a try but can't afford to miss customer calls.

 

[MikeC01]

Correct fault with pixel 2 Bluetooth will create issues if used that way.
Hoping for a future update to correct this from Google

This is so strange. When I first got the phone I had it paired with a Moto 360 Sport and I would have sworn that I didn't have any of these issues. So, I'm surprised to hear that it's the phone.

 

[Lew Hale1]

Same exact issue with Pixel 2xl on Verizon
Exactly the same but with gear 2

 

[GirlNerd]

I had the smaller original Pixel after being a loyal Apple user for years. I had the Samsung Gear S3 before I bought the Pixel. Phone worked well for a couple of months with the watch but then I had trouble making calls. There would be silence on both ends. The phone would default the call to the watch even if made from the handset but still silence. It eventually became unusable. I don't have a home phone and have kids so having a phone that doesn't work isn't cool. Got rid of the phone and bought the new Pixel 2 XL. Again had problems though not as bad. My Gear stopped vibrating with text messages so I sent it back to Samsung to get fixed. While I didn't have the watch, my Pixel 2 XL worked like a dream!!! The phone manages bluetooth connections to my beats, my bose, my chromebook, my car - but not the watch. The only logical conclusion is that the Pixel 2 XL doesn't know how to manage connections to Android Wear OS. Terrible. I know others who have the Gear S3 (mostly because I have convinced many to buy it) and I am the only one who has these problems. I am the only one with the Pixel phone. I love my Pixel but I don't love that it doesn't work with the watch. It's only the Google phone that doesn't work with the Android Wear OS. Ironic isn't it? Will likely go back to Apple. Very disappointing.

 

[thunderup]

I had the smaller original Pixel after being a loyal Apple user for years. I had the Samsung Gear S3 before I bought the Pixel. Phone worked well for a couple of months with the watch but then I had trouble making calls. There would be silence on both ends. The phone would default the call to the watch even if made from the handset but still silence. It eventually became unusable. I don't have a home phone and have kids so having a phone that doesn't work isn't cool. Got rid of the phone and bought the new Pixel 2 XL. Again had problems though not as bad. My Gear stopped vibrating with text messages so I sent it back to Samsung to get fixed. While I didn't have the watch, my Pixel 2 XL worked like a dream!!! The phone manages bluetooth connections to my beats, my bose, my chromebook, my car - but not the watch. The only logical conclusion is that the Pixel 2 XL doesn't know how to manage connections to Android Wear OS. Terrible. I know others who have the Gear S3 (mostly because I have convinced many to buy it) and I am the only one who has these problems. I am the only one with the Pixel phone. I love my Pixel but I don't love that it doesn't work with the watch. It's only the Google phone that doesn't work with the Android Wear OS. Ironic isn't it? Will likely go back to Apple. Very disappointing.

The Gear S3 isn't Android Wear. It's Tizen. I'm also using a Pixel 2XL and had read about similar issues with phone calls on non-Samsung phones. Because of those issues, I disabled "Phone calls" in the Bluetooth settings on my phone immediately after setting up the watch. Everything else works perfectly for me. Obviously I can't answer calls on the watch with that setting turned off, but that doesn't bother me in the slightest as I wouldn't realistically want to do that anyway.

Edit to add - I've read that Android P is supposed to address/fix this issue, but we can only hope at this point. Bluetooth on the first 2 generations of the Pixel has been less than perfect.

 

[alancath]

Yeah, calls don't go to phone so need to untick phone in its Bluetooth settings to be able to use it.

This fixed my nightmare so thank you. As of when I got a replacement Fossil Q Explorist (gen3) from Fossil (replaced under warranty; the first one bricked at about 3 months), all my calls were going to my watch, but only occasionally had audio - and even then - only from the watch. Most of the time after answering a call, my caller could not here me and would hang up. I didn't know about this switch; turning off "Phone Calls" made everything normal again - so thank you. Observations:
1) this problem is not specific to watch brand
2) this switch apparently can get turned on when pairing (I didn't turn it on, and I did not have this problem with the first Fossil Q Explorist watch, or with a Moto 360 Sport Gen 2 before it.
3) Even if you want the switch on (so you can answer calls from the watch), the answering behavior is broken and completely unpredictable, but mainly you can ONLY answer calls from your watch. If you try to answer calls on the phone, good chance your caller won't be able to hear you.