Back to Blog
Jabra direct mac6/24/2023 ![]() ![]() Technology is supposed to improve, not get worse… we are so disappointed with this. I recorded my self talking (and not talking) with both 65’s a minute appart while 2 of my colleagues where having a meeting in front of me, and while I could hear only my voice and silence with the older revision, I could clearly hear my colleagues on the recording with the Evolve2… I was also very disappointed by Jabra regarding the noise cancellation on the Evolve2 65’s boom mic. I am highly confident Jabra doesn’t give a damn about their headset having issues with MAC’s. A colleague got the evolve2 65 since his Evolve 65 was acting up, only to find out this one is also acting up. I kept using the company supplied Evolve 65 and 370 usb-a link… for a month or two this dongle/headset combination started acting up, to the point I often have either to remove the link, or reboot the headset to try and fix the robotic voice getting in my life again. I can’t understand why this device is not compatible with the MAC OS stack. The only resolution I had was to send back every evolve2 85 (and associated link 380 either USB-C or usb-a as I tried both variations). My own MacBook Pro 16 running up to date Big Sur without Jabra direct since it does not work : evolve2 85 UC w/ link 380 USB-C evolve2 85 TEAMS w/ link 380 USB-C. He’s been testing a USB-A link 380 w/ evolve2 85 Teams certified for around 10 days so far, still working great, crossing fingers. My friend’s MacBook Pro 13 running Catalina and Jabra direct : evolve2 65 UC w/ link 380 usb-c sent it back then tested evolve2 85 UC w/ link 380 usb-c. This happened with several headsets / link 380 and MacBook pros, working great at first then messing our voice after around 10 days of usage : ![]() This won’t happen if I connect the evolve2 85 to the Mac via Bluetooth or direct cable connection (which is possible since the last update) OR if I connect the link 380 to my windows VM (using parallels). At first everything is fine then my voice get scrambled with a sort of robotic sound almost every time I make a call using the link 380. It seems to appear after roughly 10 to 15 days of usage. Big Sur has additional requirements for kernel extensions, as Apple is trying to move developers to alternatives for security reasons.Just wanted to report that the USB-C Jabra link 380 seems to have an issue while being used with Mac OS (either Big Sur or Catalina). I expect this process to be more involved or to stop working with macOS Big Sur (currently in beta, so YMMV, test and report beta feedback to Apple if you are in a position to do so). Computer Headsets Enjoy fast, FREE delivery, exclusive deals and award-winning movies & TV shows with Prime Try Prime and start saving today with Fast, FREE Delivery Buy new: 6999 FREE Returns FREE delivery Friday, May 19 Or fastest delivery Wednesday, May 17. If you have approved the kernel extension and it still doesn’t work, I don’t know what the problem is. If you don’t approve the kernel extension, the firmware update will look like it starts and gets to a low progress %, but it won’t complete. Select the device to update and proceed through the update process.It could also be marked as approved if your Mac is managed by an MDM and your organization employs Jabra devices “contact your system administrator.” You should only need to do this once per computer. I believe it is from “Kim Jensen,” who appears to be a Jabra employee. Switch to System Preferences > Security and Privacy > General.The updater then launches, after a delay. Step through the installer process to install the firmware updater.You should see a kernel extension listed for approval at the bottom of that screen after you run the Jabra firmware installer. In macOS Mojave (v10.14) and later, you must authorize the kernel extension in System Preferences > Security and Privacy > General. I found that the firmware updater currently requires a kernel extension.
0 Comments
Read More
Leave a Reply. |