In trying to work through my problems with Win10 Teams NC 700, I came across the following, and seing as discovery is terrible in these forums, I've put them all here.
Aside from this thread (which is not really solved), I've not seen a concerted effort from Bose to resolve these issues. I'm not sure Bose realizes that there is a sizable number of remote workers that fly, thus desire NC Headphones, that also need a reliable Headset with a good mic array. Of course, if it doesn't actually work as a Headset with telephony apps we use, then there's not much point.
Since I only have 5 days before I hit the 30-days-from-purchase, I've requested a return.
I was told I had 60 days from today to mail the item (but needed to get a new UPS shipping label after 30).
So, I will hang on to these while waiting for updates that fix this. Meanwhile, I'm back to my Jabbra headset for voip, as the NC 700 Headphones are unusable.
Bose Software Engineering, if you're listening, I'm happy to run a debugger on my machine, and/or make introductions to the Win10 bluetooth stack devs.
My first pair died 10 mins into a flight after buying them in the airport 😞
Second pair have this weird Dalek thing going on when on longish calls, where the remote caller starts to sound like a Dalek for about 5 mins. Very odd.
Never had this issue with any of the other headphones I have tried on this phone.
looks like the second pair will have to be returned, think i will get a refund as I have lost trust in Bose with thses issues on top of the pairing and connectivity nightmare and I have owned most of their QC headphones and upgraded when new ones have come out.... very disapointed.
Thanks for posting and welcome to the Bose Community! I am sorry to hear that you are experiencing Mic issues with your headphones and would love you assist you further!
So that I can assist you further with this can you please confirm if you have attempted any troubleshooting to resolve this so far?
Again I am sorry that you have had this experience and look forward to hearing back from you.
, you may not realize, but my perspective on your reply is: you just ignored the elephant in the room and then hijacked the thread for a new mic issue.
It's obvoius the role of the Bose folks is just to respond to new threads in a scripted way. They don't appear to be able to affect any meaningful support on topics that are more involved than a reboot.
They did say they were opening a ticket with engineering but I never heard back after I sent them over some info. We've asked them repeatedly in the Surface thread to simply try it themselves and they either won't or did and never reported their results.
Ultimately, the product doesn't work well (at all) with at least some subset of PCs as a meeting headset. Given the demographic of who buys these, this seems like a rather large problem.
Thanks for posting and welcome to the Bose Community! I am sorry to hear that you are experiencing Mic issues with your headphones and would love you assist you further!
So that I can assist you further with this can you please confirm if you have attempted any troubleshooting to resolve this so far?
Again I am sorry that you have had this experience and look forward to hearing back from you.
Kind Regards,
Hector B
Hi Hector,
I can confirm I swapped the first pair with the shop for the second pair.... I had just as much grief in pairing the second pair to my phone and updating the firmware.... then all looked good.
until I started using the headphones for voice calls.
i reset the phones and repaired them..... same issue.
i am taking them back for a refund within the next few days as they clearly are not ready yet.
its a shame as I have owned QC15, QC25, QC35 and never had a problem.... yet both pairs of NC 700 have been faulty.
one fault and I said "hey, these things happen".... but second pair with issues and all the reported issues, my faith in Bose has been seriously dented.
Suffering from all the connectivity issues on my surface book (generation 1) and pc telephony that is not working I came accross device manager and checked for updated driver for my marvell bluetooth adapter, which obviously is making lots of troubles with Bose Headphones NC700. And to my surprise, there was a driver update availalbe although this driver is not pushed over windows update. Today, I've found this article:
it seems so, yes! I got the new firware yesterday and also new bluetooth drivers for my surface book last week. Can't really say which side fixed what kind of issue but during the last 4 hours I could use my nc 700 on my surface book almost without any issues.
- no crackling
- properly working stereo and hands-free profiles
- successfully connects, disconnects, reconnects to my surface book
- less issues when being connected to two devices (galaxy s9 and surface book)
Yes but can you mute/unmute yourself from the headphone controls? I cannot, when connected to the computer, which is the biggest problem. Mute only works when you're connected via an old school phone call.
nope, that doesn't work. Compared to my situation before the firware update where I couldn't use my nc700 at all for pc calls, I can live with this missing mute feature. And hey, we all bought a badly developed device, which still should be taken from the market (full RMA). It seems that such a (simple) mute feature on the device itself is a too big challenge for bose. Just imagine the planning poker in Bose's Scrum Team. I assume that the feature story got at least 40 points 🙂
just adding to this thread -- on macbook pro 2013, I can not use NC700 for conferences in either zoom or Skype -- both audio and microphone quality are very poor.
on Iphone 11, I can use Skype/whatsapp without problems.
I have read suggestions that the Bluetooth chip in the Macbook might be the bottleneck, but I would like to have confirmation on that. As things stand, I will return the headphones if this problem can not be fixed.