You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Windows with a UGREEN Bluetooth adapter with the same RTL8761BUV chip as the dongle in the readme.
Starting the server works without any issues, but I cannot find the HID device (tested with Android, Windows, and Linux). After some debugging, I figured out that it is necessary to upload a firmware blob to the dongle after each power loss. This issue might not occur on Linux, as the kernel driver should take care of that before getting detached.
After porting the firmware patching code of bumble the example server works as expected.
I understand that it's outside the scope of this project to support vendor-specific functionality, so here are a few suggestions that would make it possible to implement this functionality in an external crate:
allow the construction of vendor-specific opcodes.
ignore vendor-specific opcodes during the supported opcode check
(provide a firmware check hook during initialization)
The text was updated successfully, but these errors were encountered:
Thank you for looking into this! Those are good suggestions that I'd like to implement, but right now, I don't have the time to keep working on this project. I'll keep this issue open for whenever I can get back to it.
No Stress, I also don't have time right now to actually use this, I just came across this project, tried it, and got nerd sniped when it didn't work for some unknown reason.
I'm using Windows with a UGREEN Bluetooth adapter with the same RTL8761BUV chip as the dongle in the readme.
Starting the server works without any issues, but I cannot find the HID device (tested with Android, Windows, and Linux). After some debugging, I figured out that it is necessary to upload a firmware blob to the dongle after each power loss. This issue might not occur on Linux, as the kernel driver should take care of that before getting detached.
After porting the firmware patching code of bumble the example server works as expected.
I understand that it's outside the scope of this project to support vendor-specific functionality, so here are a few suggestions that would make it possible to implement this functionality in an external crate:
The text was updated successfully, but these errors were encountered: