QC35 disconnects immediately from Mac when microphone is activated
I've got a problem with my QC35 (original series 1) headphones. They disconnect immediately from my Late 2014 Retina 27" iMac (once an app requests to use the microphone (i.e. Microsoft Teams). They work fine for audio playback from the Mac; it's only when the computer requests mic access that they disconnect.
Specifically, when the computer activates the mic on the QC35s, there is a pop in the headphones and the noise cancelling turns off, then the headphones announce the source (iMac) has been disconnected, and then it says it can't find the mobile device.
I've done a lot of troubleshooting:
- have updated the firmware to 3.0.3;
- have downgraded to the previous firmware;
- have updated to 3.0.3 again;
- have cleared the bluetooth source list and re-paired;
- have rebooted them with the 5 seconds connected to power then unplug and wait 1 minute method;
- this past week I even did a full clean install of MacOS Catalina (10.15.4) on a new partition on my Mac to see if a totally fresh install of the OS would fix it
- I've tried the default MacOS bluetooth settings, as well as changing the settings in Bluetooth Explorer (i.e. Current/Initial bitpool 40, Minimum bitpool 2, Maximum bitpool 64).
Unfortunately none of these things have fixed the problem.
Several interesting differential diagnostic points:
- The QC35s work fine with the microphone when being used with my iPhone.
- I also have Soundlink II headphones (running 3.0.3 firmware) as well and they do not have the problem with the iMac.
- The QC35s do not have the problem on my 2019 MacBook Pro, running the same version of MacOS etc. The 2019 MacBook Pro has Bluetooth 5, while the iMac has 4.0, but that shouldn't be a problem as the QC35s themselves used Bluetooth 4.2 (as do the Soundlink IIs).
Does anyone have any suggestions? Or, do you use your QC35s successfully on an iMac with microphone?
I see a lot of threads on these forums around this issue, so I assume it is a software issue that is unresolved by BOSE so far, but I'm hopeful that these very expensive headphones won't have to be consigned to the dustbin. I don't think I'd be able to buy BOSE again given this problem (and I see people are having similar issues with QC35 II and NC700s).