I have Beelink SER5 W11 Pro 6 Cores AMD Ryzen 5 5560U, 16GB DDR4 RAM 500GB headset problem tried connect via differently but won't fix the problem.
Could Beelink assist or anyone has workaround?
- Connect via Bluebooth headset audit output audio is fine no problem, input audio stutter i am next to the machine
- Connect via USD dongle no in/output audio
- Connect via USB headset same as above
Hello there,
Have you tried the method that others shared on the forum a few days ago?
You can also try to do this:Good day.
1/Please right click window--click “”setting“---Sound----more sound setting --click "playback"--right click speaker---properties--controller information ---properties---update the driver. You also need to check if the speakers is disabled or not in the playback setting.
2/You can try to update the driver.
Here is the driver file: https://beelink.oss-cn-hongkong. ... R%205900/Driver.zip
Here is the tutorial: https://mega.nz/file/mvAS1bQK#xX ... LDUFcxN5WUi6OrYy2js
Support is only pretending to assist you - he sends the same file to everyone. Somehow I doubt he's even tested one of these computers. You will never be able to install Realtek audio drivers on these computers - it's not possible without a forced install and that will only work until Windows updates. That is not a fix, the drivers are force installed in China and the machines are shipped with Core Isolation disabled. In other words - Beelink knows these computers are defective before they ship them. Bluetooth stutter happens because the Meditek wifi / bluetooth modules are cheap crap. You can however get the Realtek ALC897 Codec to work (the chip that controls the 1/8" headphone jack) by clean installing windows and using the default Windows driver. If you want dependable Bluetooth you can order an Intel AX210 module for about $20 on ebay and swap the garbage mediatek module shipped with these machines. This is not going to fix all of your audio problems - nothing but stereo will come out of the HDMI ports and I've been working with several techs and so far we can't find a fix for that.