How does the NRF54L15 automatically negotiate MTU to support large packets

[yxh_kk]

I'm a new software developer and I'm not a native English speaker. If I ask questions through a translator now, the description might not be clear.

I'm currently facing a problem. The NRF54L15 needs to send a 244-byte GATT packet to the Central. If the Apple end acts as the Central, it can automatically MTU to above 244 when connecting. However, if the Android end acts as the Central, the NRF54L15 can only send a 244-byte packet after the Android end initiates an MTU request. May I ask if there are any configuration methods for Peripheral that can actively negotiate the MTU of large data packets when connecting to an Android device, without the need for an active MTU on the Android end? I realized that the Bluetooth protocol stack of the old NRF52832's S132 seemed to be able to directly send large packets through internal subpacket grouping, but is the NRF54L15 different now?

thanks

[Amanda Hsieh]

Hi,

May I ask if there are any configuration methods for Peripheral that can actively negotiate the MTU of large data packets when connecting to an Android device, without the need for an active MTU on the Android end?

No, it's negotiated by the Phone and device. You can capture sniffer logs to see the negotiated result. 

I realized that the Bluetooth protocol stack of the old NRF52832's S132 seemed to be able to directly send large packets through internal subpacket grouping, but is the NRF54L15 different now?

Could you elaborate on the details of what you see the difference for nRF54L15?

Regards,
Amand aH.