Both Bluetooth (SPP profile) and USB are are essentially serial connections. USB has an advantage in that the connection can be left as always on, where you have to close the connection on Bluetooth at least occasionally or you run into issues with timeouts and battery use.
Given this, we recommend spooling print jobs be handled in a client-server queue architecture. We are working on some documents and sample code to show how to do this better, but I've attached a draft framework. It is just one way to work it, and we know there are others, but this seems to fix most issues. It decouples the UI and slow running print connection so it can happen asynchronously. Hopefully it helps.
ResponsivePrinting.pdf 141.6 K