Pixel II XL with Bose QC35 II headphones- Keeps Disconnecting during calls

[vodwills]

Bose QC 35 II keeps disconnecting during calls if I am using Mac when i receive calls. With my iphone 6S this never happened. 

Bose connect app: Latest update

QC 35 II : 4.3.6
Pixel 2 XL: Latest update Android 9

Kindly help me out as thisis driving me crazy. All answers on web are w.r.t firmware 3.1.8. That was eons ago.

[Hector_B]

Hi Vodwills,

Thanks for your post and welcome to the community. 

Firstly I would recommend a product reset. This can be done by: 

• Turn off the headset and wait 30 seconds
• Plug the headset into a wall outlet using a USB charger, then wait 5 seconds
• Unplug the USB cord from the headset and wait 1 minute
• Turn on the headset

Kind Regards, 

Hector B - Community Support 

[vodwills]

Hi Hector,

It seems to be working now. Let me check it for a few more days and if it doesn't disconnects I'll accept the solution. Thanks for the prompt reply. I had tried the reset but I think I didnt do it correctly.

[Hector_B]

Hi Vodwills, 

I am glad to hear this! Please update me if the issue comes back. 

Please also mark this post as a solution if it resolved your issue! 

Kind Regards, 

Hector B 

[vodwills]

Hi Hector,

So the problem persists. It only happens when I get a call while my bose is connected to both my Mac and Pixel 2XL.

Even if I'm not playing any media on my Mac after a minute or so my phone gets disconnected. After that it doesn't reconnect.

Even if I hangup and try to re-connect it takes time and shows error message like aww device not detected/not in range etc.

and once i reconnect it, it doesn't automatically reconnect to my mac. So after I hangup i again have to switch off/on to reconnect to both devices. Kindly advise.

[Hector_B]

Hi Vodwills, 

Thanks for posting and updating me on this. Can you attempt to connect two phone devices to the headphones to see if this issue happens again? 

Thanks, 

Hector B 

[vodwills · Accepted solution]

Hi Hector,

Apologies for the late reply. The issue wasn't resolved. But now with the latest update it has been resolved. 

Thank you for your help!!