3 ms·

I'm surprised this is still an issue, even after Bluetooth 5. Anyone know if there are plans to fix it?