Open justinfriberg opened 2 days ago
Change the MTU to 512 and test again to see if this issue is resolved.
Same behavior with MTU at 512.
I just noticed that even though the request was 512, the response indicated it's still at 517:
D/BluetoothGatt(13764): configureMTU() - device: XX:XX:XX:XX:4E:32 mtu: 512
D/BluetoothGatt(13764): onConfigureMTU() - Device=E0:5A:1B:C6:4E:32 mtu=517 status=0
I just noticed that even though the request was 512, the response indicated it's still at 517:
D/BluetoothGatt(13764): configureMTU() - device: XX:XX:XX:XX:4E:32 mtu: 512 D/BluetoothGatt(13764): onConfigureMTU() - Device=E0:5A:1B:C6:4E:32 mtu=517 status=0
I think you should check if there are issues on the peripheral side. You can use other debug tools like nrf connect to check this.
We're observing a BLE GNSS device notification characteristic that returns a chunk of data every second. This data is generally larger than the MTU (over 514 bytes). On iOS, we get notified each time an MTU chunk is reached. On Android, we only get partial amount, which appears to be the size of whatever is in the last chunk (decoding the bytes bears this out). Not seeing any configuration outside of the requestMTU call to fix this.
Code:
Android:
iOS: