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.
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.
Hi, Amanda Hsieh
I have solved this problem! I found that I was lacking these two configurations! Now I can actively negotiate large MTU packets from the slave machine without the need for the host side to make MTU requests.
prj.conf changed like this:
add
I solved it Reference from:【NCS随笔】NCS如何更改MTU大小_蓝牙 从机mtu-CSDN博客
Although I solved it myself, I'm still very grateful to you!
Happy to hear that.