@Swapnilsyes, as written in my previous comment, i got the update over "device manager" by choosing the bluetooth adapter, right-click and then select "update driver".
This brought the following driver version to my system: 15.68.17015.112
Driver date: 09.08.2019
And yes, I could do some rough tests. But in the meantime the incompetent bose developers released the new nc700 firmware 1.3.1 which got installed automatically. And it seems that it makes things even worse again.
As I am mostly conferencing with my clients, I can not test pc telephony a lot as they would go crazy. I had a teams call with one of my employees and can provide the following infos / result from that call:
- Setup in prior to the call is a pain. Although nc700 is connected over bluetooth with my windows10 and device settings in teams are correct, I can not hear the voice of the lady provided in teams test call functionality (settings - devices - make a test call). Either i hear nothing or it sounds robotic, so no chance to understand anything.
- I suppose that it helps when you switch the audio device in the task bar to "Headset Earphone (Hands-Free AG Audio)".
- If test call still doesn't work: disconnect nc700 in win bluetooth settings and connect again. After, ensure again in the task bar, that "Headset Earphone (Hands-Free AG Audio)" is selected.
- Once test call works, start your teams call and pray!
Results:
After having an active call for around 10-12 Minutes with my emloyee, the audio output in nc700 just disappeared. I could "restore" it without having to end or restart the call by going to teams device settings and switching audio output device to "speaker" and then back again to Headset Earphone (Hands-Free AG Audio). So i lost some seconds of the call, but could continue.
After another 10 minutes, the same bloody sh.. happend again. And i could fix it again bei switching audio output to "speaker" and back to "Headset Earphone (Hands-Free AG Audio)"
For the last 40 minutes of the call, everything stayed stable.
So, it's still pretty **bleep**ty and embarrassing for bose. But before, I've never managed to keep a working audio connection for more than 10 Minutes in an active call.
Of course, I will do some more testings. But on the other hand, I am pretty sure that it will not help any further and that a viable workaround will not be found as long as Bose does not address these issues in their firmware.
@bose: isn't it bizarre? You don't care about this issue although it must have a huge negative impact on both your revenue and your brand image. So many customers just have returned your flagship high-end product. The web is full of negative criticism. And disappointed customers are spreading the word in their networks. Same with me. Whoever asks me about my nc700 experience my only answer is: Hands off!
Now you have released the new firmware 1.3.1 and the few things that worked almost perfectly on former firmware versions now are buggy on the new firmware. I now also have lots of issues when my nc700 is connected to my android mobile device. Cracklings, robotic voice, ... it's just a piece of **bleep**.
