30,000 records over BLE in 5–6 minutes
Two BLE projects, one limit: how much data fits in a packet. In a phone app, 30,000 records now download in 5–6 minutes, every chunk CRC-checked. In tracker firmware, smaller chunks fixed the iPhone link, and I built the MTU exchange the vendor wouldn’t add.
BLE sends data in small packets. Both sides agree on a maximum size, the MTU, and anything bigger doesn’t get through.
I ran into this limit from two sides: a phone app that downloads logs from a cold-chain temperature recorder, and tracker firmware that iPhones couldn’t talk to.
The app: every record has to arrive
I co-developed the React Native app for a family of BLE sensors, on iOS and Android: about 140 commits, about 85 tickets and 14 releases to Google Play and TestFlight.
For the recorder’s cold-chain certification, every record has to arrive, and you have to be able to show it did. I added a CRC check on every chunk, so each row in the export says whether its chunk arrived intact. I also fixed a page-header shift, where the header sometimes arrived one slot late and the app read a record chunk as the header. Then I raised the MTU to 247 and the chunk size from 15 to 60 records.
To test full-size downloads, I added a fake-record generator to the app. 30,000 records now download in 5–6 minutes.
The firmware: iPhones and 512-byte chunks
An iPhone can only reach the tracker over BLE. The tracker isn’t MFi certified, so iOS can’t use its Bluetooth Classic serial link. And our firmware sent BLE data in fixed 512 B chunks, which iOS can’t take.
In 2024 I wrote up how MTU negotiation really worked on the platform. The chip vendor’s Bluetooth layer negotiated the MTU, and our code sent fixed 512 B chunks on top of it. I set the chunk payload to 182 B, tested on iOS and Android, and released it as an experimental iOS-compatible firmware. That fixed the iPhone link.
When the vendor said no
The vendor SDK had no MTU negotiation in its GATT server layer. In 2025 I opened a support case, and they declined to add it. So I built the MTU exchange in the GATT client layer myself, for links where the tracker is the client. I tested it in the cold-chain firmware, where the tracker reads temperature recorders as a client, and updated the BLE MTU docs.
Conclusion
In the app, 30,000 records download in 5–6 minutes, and every chunk is CRC-checked. In the firmware, QA verified 182 B chunks on two tracker models.
On the firmware side, the write-up mattered more than the code. Once it was clear who negotiated the MTU and what our code did with it, the iPhone fix was small.