CASE STUDY · SEDA G-TECH

Bluetooth protocol recovery

No documentation. No SDK. Just radio captures and patience.

My role
Worked out the protocol and built the macOS driver.
Built with
Bluetooth Classic · RFCOMM · macOS · Flutter

The problem

A label printer worked only with its maker’s Android app. There was no documentation, no SDK and no macOS support.

The job: make it print from a Mac app anyway.

What I built

  • Studied the vendor’s Android app alongside live Bluetooth HCI captures to work out the command frames and the raster image format.
  • A native macOS transport over Bluetooth RFCOMM using IOBluetooth.
  • A bridge into the Flutter app with MethodChannel and EventChannel, so the app treats the printer like any other device.

The hard parts

Frames cut short
Data was being truncated at the RFCOMM MTU. Found it and fixed it, so print jobs arrive whole.
Reconnect races
The system’s Bluetooth device cache caused races on reconnect. Fixed, so the printer comes back reliably.

How it was checked

Checked on the real printer, with live Bluetooth captures to confirm what goes over the air.

What changed

Labels print from macOS, with no vendor SDK involved.

Bluetooth ClassicRFCOMM / SPPHCI capturesIOBluetoothmacOSFlutterDart