Plantronics Dongle Not Working

[Perpetuo Carlson]

InterestingWe are experiencing these problems as well. Seems very similar. I can deploy a 5400 with this same image and have no issue, but a 5420 will get issues. Did you notice when you disconnect the device the computer returns to normal operation? We found that when the problem was triggered everything on the computer slowed down almost to a halt. Then disconnecting the offending headset would get things working again. It has to be something to do with the USB Audio drivers and Realtek. Yet, I have tried the fixes you mention and can only get the device to work for now, then it stops working again. Has anyone solved this yet?

SO far I narrowed it down to some sort of issue with the Intel SST Audio driver, and the Realtek chipset. I noted I am deploying an image using 20H2 audio works fine, then when its upgraded to 21H1 this issue happens almost every time. Subsequent upgrading to 21H2 triggered an audio driver download in Dell command, and then it seems to have alleviated the issue. I am still in the early testing phases, but I think it is specific to those 2 drivers not working well for some reason under 21H1.

Dell is aware of that issue and working on a fix together with Intel and Realtek. The Problem seems to be caused by Teams' Audio Device Access after Audio Devices have changed (Headset connected or removed) between or during calls.

1. Install the newer Audio driver that is already available for the Latitude 9520 but not finally validated for the 5520. This Driver does not fully fix the issue but it reduces the chance of the Audio Service to crash in the first place. If the Service still crashes, it will recover itself after about 10-20s and audio is working normally again, so no reboot is required. -de/drivers/driversdetails?driverid=fy22f

2. Disable Audio Enhancements in the Advanced Audio Device settings. This will prevent the Service Crash from happening but has the side effect that the sound quality might be reduced on the system speakers.

Maybe the engineers at Dell should reach out to us for one of our 100's of units that are effected, and we can supply them with a broken one to test. There is no way they cannot reproduce this as it gets reproduced over multitudes of machines.

Only if I plug the headset to a docking station which is then connected to the laptop USB port then I encounter this headset issue. Tried multiple handset models and have same issue. Good to know fix is coming out soon.

I have a Dell 5420, using a Dell D6000 docking station. On the laptop I have a bluetooth Headset (Plantronics UC Focus) with its original dongle, on the docking I have a Jabra Speak 710 connected through USB.

Symptom is the following: using Teams calls with Jabra Speak connected, middle of the meeting all audio devices disappear and I cant hear anything anymore. All device including microfone has been disappeared and only the reboot helps. If I am using my Plantronics bluetooth headset, I am not experiencing such issues. Other symptom is the USB connected keyboard through the same doscking station. Sometime the keyboard start lagging and entering long ad-hoc character sets. For me it seems to be an issue with USB and I do not think it is only audio.

No, these driver comes with other bugs and issues. I have 5420 and from beginning this laptop has a problem with audio drivers....I am using 3 devices, headset to USB, laptop speakers and external speaker to 3.5mm jack audio. With new driver you mentioned, sound stop working for external and internal speakers, just usb device is working....so I need to rollback drivers back...My Windows version 20H2

Q: What wireless chip is used in this device? No mention here or the manuals at Panda Wireless website.

A: It works out of the box on any Linux distribution running Linux Kernel v5.0 or higher. i.e. Ubuntu, Linux Mint, Raspbian and Debian Buster/Bullseye/Bookworm, Fedora, TailOS, OpenWRT and more. Please send an email to sup...@pandawireless.com if you have any questions.

For the device you listed there is a WikiDevi page at Panda Wireless PAU0B. If a device has an entry in WikiDevi it could provide enough information to determine whether you would have success in using the device in OpenWrt. If the WiFi chip is listed it will usually provide the possible Linux driver.

USB3 does cause trouble on devices using 2.4Ghz if they are not exceptionally shielded. It is an established problem (especially with 2.4 mice and keyboards) and moving the dongle away is the most often suggestion.

I know about this issue, so during the test I didn't enable the onboard 2.4GHz, and it's headless without any keyboard/mouse, I tried keeping everything in "minimal" to test, but the CF-953AX is really difficult to find a suitable USB3 extension that won't drop speed, luckily I found one, but still it works terribly bad on my Pi4 with OpenWrt 23.05.2 as AP. I am going to try with a Raspbian 64bit desktop as client mode to see how it goes, will also update EEPROM and go back OpenWrt to test again later in the week.

BTW about the Asus USB-AC51, I just did some more little test, though I know almost no one will be using the ancient RPi 1B+, I still have it so I was trying to see how well it work. So I think while it's published as "OpenWrt supported" but in fact this is strongly "not recommended", not even as a travel router.

First thing, when I plugged Asus USB-AC51 to Pi 1B+, the whole thing rebooted! OMG I guess it's related to power? So after reboot the system came back. I must say this is not issue with my power supply because I had a test with Raspberry Pi 3 using the same one and no reboot at all. Note that when I measure with RPi 4 using USB-C power meter this dongle doesn't even use 200mA while on load, so it's not possible that USB bus power exceeding.

Second, I put it in AP mode, so no routing/NAT, simply bridging, AP comes up, firing up a speedtest. And....? System load jumped to 6.00! And the WiFi speed ranging from 50-70Mbps, during the test there was one time that probably due to extremely high system loading the AP disconnected me for 5-10 secs, IRQ statistics showing USB interrupt storm which might explain the whole thing.

But I still hope someone somewhere made a most durable USB two radio (for at least 2 AP modes) solution.

Because: the Pi4 and probably the Pi5 are inexpensive and can handle 1Gib router functions, but the darn radios present problems.

If you have a Pi 4, you, probably, already have all the accessories.

I believe this is really a big thing blocking most people from building kind of 1G throughput router with USB WiFi, difficult to find a dongle that supports such high speed and working well as AP under Linux, and to be honest the amount of supported client also can't compare to mid-tier router.

I have come to understand this is, mostly, a chipset limitation.

I.E. a chipset that is used in both routers and dongles (or even the same chipset across different models of routers) the number of active clients is a chipset issue.

There's another aspect, two decent USB WLAN cards (the internal brcmfmac card of the RPi is just too bad, even for 2.4 GHz) cost more than a dap-x1860, covr-x1860, wsm20, but these run circles around any USB WLAN card and are just fast and reliable.

In fact even the "kind of problematic" COMFAST CF-953AX isn't hot during on load, it's interesting that this dongle (I guess same for all mt7921au solution) has on chip temperature sensor that I can query from OpenWrt, I never seen it go above 40C (room temperature 20C here) after sending 10GB files from client to server through this dongle. For the other 2 x mt7610u little dongle, they were also not hot at all, so that's why I think RPi 3B/3B+ with such mt7610u can be a good travel router combination (using the onboard WiFi only for 2.4GHz).

Teams added a new feature today called "Spatial Audio". Even with this feature disabled, my wireless head set no longer works correctly with teams - the speaker is not transmitting the meeting sounds/audio. Please fix. I don't care/want Spatial Audio - I want to use my wireless headset!

All of a sudden & out of the blue, my Aftershox headset stops working with MS Teams. Only teams no other issues with standard Windows sounds, in fact I can use this headset with Zoom, Ring Central, etc... on the same computer. I've verified that Teams is using the headset. Crazy, WHY would it suddenly stop working out of no where?

Re-installing the audio driver fixed this for me. Frustrating how often Teams stops working in some way or another - usually restarting computer fixes it. My guess is there are constant updates getting pushed from Microsoft and that seems to require restarts.

I'm having the same problem since updating to the new Teams. Bluetooth headset usually works for one meeting, then does not work for any subsequent meetings until I reboot the machine (again works for one meeting, rinse, repeat). Same problem across multiple bluetooth headsets (multiple brands). Doesn't seem to be a audio settings issue in Teams. Audio works fine for systems sounds and other applications.

Please help me understand why Microsoft Teams has SO many problems with audio connections of ANY kind. The internet is littered with hundreds and hundreds of forum pages of people complaining, with zero action on Microsoft's part. I have been in situations where I have tried 2 different Bluetooth headsets AND a wired headset on 3 different devices (phone, tablet and laptop) trying to get Teams to enable audio or microphones, and nothing works. Disconnecting calls, and trying direct calls, nothing works. Except when you try the Test Call, perfect audio...miraculous!. Reset/reinstalling the audio drivers (i.e. "It ain't our fault gov") is about all that Microsoft can come up with, despite telling them that these issues happen on multiple devices and multiple headsets, logic does not seem to register as far as Microsoft are concerned (here's a hint..." ITS YOUR SOFTWARE!"). It is maddeningly frustrating and Microsoft, in typical Microsoft fashion couldn't give a fig.

3a8082e126