HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters
Create DWORD: "DisableRemoteWake" = 1
The BM05E-V2 does not use a unique driver. It uses a generic driver provided by the chipset manufacturer. If you plug this into Windows and it shows up as "Unknown Device" or BM05E-V2 01, you need to identify which chipset driver to install.
There is a 90% chance this device uses one of the following three chipsets:
If you’re trying to write a kernel driver for this module over USB or UART, here’s a minimal example (USB – for learning only, not a complete driver): bm05e-v2 01 bluetooth driver
// bm05e_driver.c – skeleton for USB Bluetooth HCI driver #include <linux/module.h> #include <linux/usb.h>static int bm05e_probe(struct usb_interface *intf, const struct usb_device_id *id) dev_info(&intf->dev, "BM05E-V2.01 Bluetooth device connected\n"); // Attach to bluetooth subsystem (hci_register_dev, etc.) return 0;
static void bm05e_disconnect(struct usb_interface *intf) dev_info(&intf->dev, "BM05E-V2.01 disconnected\n"); The BM05E-V2 does not use a unique driver
static const struct usb_device_id bm05e_table[] = USB_DEVICE(0x1234, 0x5678) , // Replace with actual VID/PID ; MODULE_DEVICE_TABLE(usb, bm05e_table);
static struct usb_driver bm05e_driver = .name = "bm05e_bluetooth", .probe = bm05e_probe, .disconnect = bm05e_disconnect, .id_table = bm05e_table, ; // Replace with actual VID/PID
module_usb_driver(bm05e_driver); MODULE_LICENSE("GPL");
