Bluetooth Exe
Alfonzo Liebenstein
When the setup is running from the bluetooth driver i saw a message during setup it was doing something with the intel smartsound driver (Intel Smart Sound Technology Detection Verification).
Hello MichelN86,
Thank you so much for the response and for providing us with the details that we requested.
We will do further research on this matter and post the response on this thread once it is available.
If you have an OEM driver or a manual-install generic driver issue, please try updating the latest driver using Intel Driver & Support Assistant. Capture video and share it if BT installation issues occur again in the future.
Furthermore, based on our research and some MSI forums, it looks like the BT installation issue occurred only with your laptop. Other MSI users reply that it works fine or that using IDSA is no problem.
I use the intel drivers from your site since last year and since msi does not provide updated drivers ( -15-B12UGSZ/support?sub_product=Crosshair-15-B12UGSZ#driver). I even clean installed (added 2 new nvme drives) the whole system. Every bluetooth driver from intel worked fine during installation except the last 2. If you say you did good research you failed, i posted this issue on the msi forum on my own topic and 1 user reported he had no issues with the install, please point me to the topic where more users say it is working fine for them ??? please do.
We can only suggest that once you have installed the next driver revision, please capture screenshots and videos of the BT/wi-fi driver version and hardware ID from Device Manager, including all impacted drivers as listed in the forum, e.g., Arc, Windows Update, Realtek Audio, Nahimic Audio, Realtek PCIe GbE Family Controller, Intel(R) Dynamic Application Loader Host Interface, Intel(R) Management Engine Interface #1, and Intel Smart Sound Technology Detection Verification, Intel Smart Sound driver, etc., and then please share them with us if the issue occurs again.
By the way, when you reach us again, we recommend that you submit a web ticket, chat, or call. This will allow us to provide more personalized assistance, potentially including remote access, so we can access your system for a more thorough resolution.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I had the same problem and upon going through a few forums, someone finally found the solution and it works. This is what you should do: add the "nearby devices" permission through the Zoom app settings.
The settings to change are Not in the Zoom app. They are in the Phone Settings itself!. now i get why so hard to find as very confusing instructions given here.. Open Settings tab on your Phone. It's the Gear icon. Then go to Apps, and click Zoom there... Then Permissions tab inside there.. so Phone Settings > Apps > Zoom > Permissions > add Nerby Devices.
I have a Fire 10 HD and these instructions do no work for it. There is no ready option to Add Nearby Devices under Permissions. Rather, under Permissions clicking the three dots in the upper right opens All Permissions. Under Other App Capabilities, there is an option to Pair with Bluetooth Devices. Clicking that enables Bluetooth speakers to work.
same for me. zoom auto updated overnight and i've lost bluetooth. became aware of the issue during an important meeting of course. an hour trying to fix settings with no luck. why not just tell me to use Teams instead.
Access to the API is controlled by the Permissions Policy directive bluetooth. The default allowlist for the bluetooth policy is self, which enables Bluetooth usage in same-origin nested frames but prevents access by third-party content by default. Cross-origin access is enabled by specifying the allowed origins in both the Permissions-Policy: bluetooth HTTP header and the desired .
In order to use the feature the user must first grant explicit permission (they will not be prompted for access if it is not allowed for other reasons, such as being blocked by a Permissions Policy). The permission prompt is displayed when calling Bluetooth.requestDevice() to request access to a new Bluetooth device for which permission is not granted (the owning global object must also have transient activation). You can use Bluetooth.getDevices() to retrieve any devices that have previously been granted permission for the site.
The Permissions API navigator.permissions.query() method can be used with the bluetooth permission to test whether a site has permission to use Bluetooth devices. The permission state will be granted, denied or prompt (requires user acknowledgement of a prompt):
\n Access to the API is controlled by the Permissions Policy directive bluetooth.\n The default allowlist for the bluetooth policy is self, which enables Bluetooth usage in same-origin nested frames but prevents access by third-party content by default.\n Cross-origin access is enabled by specifying the allowed origins in both the Permissions-Policy: bluetooth HTTP header and the desired .\n
\n In order to use the feature the user must first grant explicit permission (they will not be prompted for access if it is not allowed for other reasons, such as being blocked by a Permissions Policy).\n The permission prompt is displayed when calling Bluetooth.requestDevice() to request access to a new Bluetooth device for which permission is not granted (the owning global object must also have transient activation).\n You can use Bluetooth.getDevices() to retrieve any devices that have previously been granted permission for the site.\n
\n The Permissions API navigator.permissions.query() method can be used with the bluetooth permission to test whether a site has permission to use Bluetooth devices.\n The permission state will be granted, denied or prompt (requires user acknowledgement of a prompt):\n
I have a pair of Taotronics Soundliberty 79 earbuds. They've pair fine with my laptop running Win 10 and work for listening to music. I've also tested joining a Google Meets meeting and audio works fine in both directions.
However, when I join a MS Teams meeting after a minute or two I can no longer hear audio through my earbuds, but the microphone continues to work and others can hear me. I need to go to device settings in Teams and switch to PC speaker/mic then back to the earbuds to restore audio which only lasts a couple of minutes before dropping out again.
I am also experiencing this issue. BT speaker connected, works fine, until a Teams call is made, or answered. BT speaker is connected, and I tried force closing teams, however the only way to resume audio from the BT speaker, is to reboot the PC.
Also having this issue. Currently connecting using the Bose 700 headphones, they work fine in google meetings, webex etc for both audio and mic. As soon as I receive or make a Teams video call, the mic continues to work, but Im not able to get any audio. Change it to PC speaker and mic, and works fine. If I ever do get it to work for a teams meeting, if I disconnect the call, and reconnect into a new video call, the problem presents itself. I have tried different Bluetooth headsets, and get the same problem. @JBF_SE
@ThereseSolimeno The issue is, audio devices, such as BT speakers stop altogether after a teams call. My Jabra Evolve works fine, connected via the supplied dongle, and BT keyboard and mouse work fine. BT SPEAKERS however, teams for some reason will stop streaming audio after a call, even though all connections are OK. Can switch devices, from monitor speakers, OK. Laptop speakers, OK. Headset, OK. BT speakers? NO, and even re-pairing will not work, a reboot is needed.
@derekjwhitten I'm having the same problem with the Liberty79s . I want to alternate using my Tribit BT headphones, which work really well within Team for both sound and mic, with the Liberty79s but, no matter what I try, I just can't get the consistency of sound or mic quality - few garbled mutterings from the Test Teams Call then nothing.
The Libtery79s work well with other devices and apps, I just can't get them to work within the Teams environment.
I'm having the same issue with the SounLiberty 79. Two minutes is the longest. In my experience, in some cases, only some seconds go by until I lost the incoming audio. The mic seems to keep working, even though I couldn't confirm this with the other people on the call. If I switch to the laptop (Surface Pro 4) audio speakers the audio starts to work perfectly again.
@derekjwhitten any answer on this yet? i've had this 2 weeks in a row now with new clients. using apple airpods. worked on Zoom call just before. never works on Teams. also noticed that as soon as i enter the Teams meeting my bluetooth 'toggle' disappears! thought it was a bug in my laptop but obviously not. any idea where we can go to find answer to this thread pls?
I was having a lot of the same issues with drop outs and failure to get clarity of calls in MS Teams. Especially with a set of Bose 700 NC on a Surface Laptop 3. I researched some testing that had been done using Broadcom chipset Bluetooth dongle. Ended up ordering an "MPOW Bluetooth dongle" for my Laptop and PC at home, and works without fail every time. Just had to disable the local bluetooth adaptor first, but Its been working without fail ever since after 4 weeks and allot of video meetings during that time.
Hope that helps anyone here.
@AnnieH unfortunately I haven't had any luck with this. I have resorted to just using the built in speakers and microphone, and joining calls from my mobile if I need/want to use my bluetooth earbuds.
59fb9ae87f