This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am using Teams app android to attend my online classes but I am facing issues with bluetooth speaker. I wanted to use Nest mini for audio output so I paired to it through bluetooth on my android device and audio output of all the apps work except teams. This issue seems to be only on android app because on the desktop app on windows 10 the same speaker works absolutely fine. In the android app when I try to switch the audio output to bluetooth, within a second it switches back to device audio. I tried on another android device as well but no luck. I am running the latest teams version (as no updates available in Play store). Any help is welcome.
Managing sound and video settings during Teams meetings and calls
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Siggi Nann thank you, it worked for me too. I didn't need to clear the cache, just allow "Nearby devices" permission.
TLDR;
Go to Settings -> Apps -> Teams -> Permissions -> Allow access to "Nearby devices"
Again, this is not an app fault, it is a core security functionality of never Android OS.
That's not what's happening here, it's not a permissions issue. To get Bluetooth to work we have to turn the device's Bluetooth off and back on, then Teams will see the option again in the call or meeting.
Agreed. If that were the case it would only happen after not using Teams with bluetooth after 90 days of non-use.
That's not what's happening here, it's not a permissions issue. To get Bluetooth to work we have to turn the device's Bluetooth off and back on, then Teams will see the option again in the call or meeting.
Hi,
the general issue is actually not Microsofts fault. What Android is doing, as I found out, is on a regular basis go over all your App Authorisation settings and removes unused once. So happened to my teams app.
The solution is go into the app settings of Teams and re-enable the bluetooth authorisation. And when Android gives you the notification that it removed some settings, interact and make sure Teams keeps the access to bluetooth.
Again, this is not an app fault, it is a core security functionality of never Android OS.
Cheers,
Christian
Hi all,
it seems that i had similar issues since today and sorted it today. Since today When i am in a teams call i had only 2 options for audio:
* device
* speaker
Usually there was also "* bluetooth" and I assume this was coming with the last Android installation i did on the weekend... potentially Android changed something with auths for apps.
I was following some instruction from the beginning of this thread and cleard the cache for MS Teams on Android. after restarting MS Teams, Teams requested that MS Teams is allowed to search for nearby devices (i assume that was the one missing -> bluetooth is for nearby devices) and i approved it (i can hardly remembered, that I rejected it the first time). Another authorization request came up to make phone calls, I also allowed in MS Teams. First i was some kind of resistance to grant all those authorization, as i usually question, why this is needed. But based on my experience, when you have any kind of problem, just grant at the beginning all requested authorizations to see if it is working. Afterwards you can limit them again in android settings.
After that MS Teams showed me in a Teams call the option to choose
* device
* speaker
* bluetooth
and i was able to join calls again via bluetooth headset. Problem solved... lets see how long.
Hope that helps anybody having the same problem. I did not read this full thread with 6 pages, but i am really wondering why the MS-Support is not offering this walkthrough and pin it to the top of this thread as a potential solution... but maybe i just missed it. But when users having problems they want to have it sorted fast and not searching 100 of pages for a solution.
BR
Siggi