Long Device Name Getting Cutoff about flutter_reactive_ble HOT 7 CLOSED

@ealanhill I see you didn't tick the tried-doing-this-with-a-generic-BLE-scanner-app checkbox. Could you please confirm that a generic BLE scanner app (like nRF Connect mentioned in the template) reads out a long device name in full on the same device?

from flutter_reactive_ble.

@werediver Thank you for getting back to me! When I scan with nRF Connect, it gives me the version that is cutoff as well (using my Samsung Galaxy Note8). But, they label it as "Shortened Local Name".

Not having used nRF Connect is that a report?

It also seems like this is an Android specific limitation then?

from flutter_reactive_ble.

Not having used nRF Connect is that a report?

It sure is, but in many cases—as this one—that provides useful insights.

It also seems like this is an Android specific limitation then?

It looks like this, but it still may be worth checking whether there is an API or otherwise a way to get the full name.

@remonh87 Would you have a moment to check on this?

from flutter_reactive_ble.

@werediver @remonh87 Any more info I can provide to help look into this? Any steps I can take to check?

from flutter_reactive_ble.

@ealanhill this is an interesting question and it took me a bit of studying to find an answer to clarify the behaviour on Android.

The max size of a field in an advertisement packet for BLE is 31bytes. 2 of those are used for the header so this leaves you with 29bytes for the device name. The size of your device name 11111111-2222-3333-4444-123456789012 is 36 bytes which is too long. The size of the string 11111111-2222-3333-4444-12345 is exactly 29 bytes and this fits within the spec. For more details see for example: source1 and source2 .

I have really no clue why on iOS the name is not cut off that is a mystery to me. I did study the Android specs and also the implementation of the Android library we use and we do not cut off the name. So my guess is that it is limited by the chip of the phone.

from flutter_reactive_ble.

@remonh87 Thank you so much for your research and answer! That helps quite a bit

from flutter_reactive_ble.

You are welcome. For now I close this issue. Feel free to open it in case you found some other insights.

from flutter_reactive_ble.