bt-dualboot
bt-dualboot copied to clipboard
added bt 5.1 support
Hi, I had the same issue like #7 for a BT 5.1 device. So I've added support for that. Check it out :)
Thanks! @x2es could we merge it in?
If there is no response from upstream, maybe it's time to fork the project then?
FYI In latest Arch Linux / Fedora installations it seems to be SlaveLongTermKey
so this PR unfortunately doesn't work on such systems. Altough it was a simple fix to get it working, great work!
FYI In latest Arch Linux / Fedora installations it seems to be
SlaveLongTermKey
so this PR unfortunately doesn't work on such systems. Altough it was a simple fix to get it working, great work!
Simple fix? details please?
Is there any fork that works with BLE devices?
To make things worse:
https://github.com/bluez/bluez/blob/6fc599e334cead9cbd014f7830753bc28ee5868b/src/adapter.c#L4100
Later releases will change the key name to "PeripheralLongTermKey"
And I just checked my /var/lib/bluetooth
info files, all three variants are there:
- LongTermKey
- SlaveLongTermKey
- PeripheralLongTermKey
And they're all different.
This runs for me without the nasty errors of the main branch, but fails to actually sync my devices.
- Orochi V2 (Mouse)
- JBL Extreme 2 (Speaker)
In the /var/lib/bluetooth info files, the JBL speaker has a LinkKey
section and the Orochi mouse has Key sections titled IdentityResolvingKey
, PeripheralLongTermKey
and SlaveLongTermKey
.
I can provide more info and testing if that's helpful.