Most Android devices with USB OTG support will recognize the CM390 automatically if your kernel has Bluetooth USB HCI support. No manual driver installation is possible on Android.
Cause: Corrupt driver installation or conflict with another Bluetooth stack (e.g., Intel or Toshiba stack). Solution:
A: You have a fake or counterfeit UGREEN adapter. Real UGREEN CM390 uses Realtek. Knockoffs use cheaper CSR chips. Return it to the seller. ugreen bluetooth 5.0 usb adapter cm390 driver
Cause: Windows power management turns off the USB port or the Bluetooth radio. Solution:
In an era where wireless peripherals are dominating the market—from noise-canceling headphones to precision gaming mice—having reliable Bluetooth connectivity on your desktop PC or older laptop is no longer a luxury; it’s a necessity. Unfortunately, many desktop computers lack built-in Bluetooth, and older laptops often ship with outdated Bluetooth 4.0 or 4.2 hardware. Most Android devices with USB OTG support will
Enter the UGREEN Bluetooth 5.0 USB Adapter (Model: CM390) . This tiny, affordable dongle promises to bring high-speed, long-range wireless connectivity to virtually any computer. However, a device is only as good as its software. The single most searched question surrounding this product is: “Where do I find the correct UGREEN Bluetooth 5.0 USB Adapter CM390 driver, and how do I install it?â€
This article serves as your complete encyclopedia for the UGREEN CM390. We will cover hardware specifications, step-by-step driver installation for Windows 10 and 11, manual driver methods for legacy systems (Windows 7/8), troubleshooting common errors, and comparing it to other Bluetooth adapters. Cause: Corrupt driver installation or conflict with another
Troubleshooting: If it doesn’t appear in Device Manager after 2 minutes, move to Option 2.
For Arch Linux: Use the rtl8761b-firmware package from AUR.
Note: Some Linux distributions (Fedora 38+) include this firmware by default. Try a live USB first.
Cause: Power management is turning off the USB port or the driver conflict with Wi-Fi 2.4GHz. Solutions: