2 files at the same time, while MS Stack seems to handle up to 6 files. Small files &lt;64kB seem to be working ok for both stacks. As said not sure if this actually is in the influence of bluetools or only stack related - Possibility to reliably detect receiver response: Right now there is no way to distinguish reliably between a scenario where a receiver declines a reception actively and a scenario where a receiver does not react at all (ignores receive request). When creating the stream a message is shown for unpaired devices that the receiver must accept. I would like to be able to detect if he accepts / declines / does nothing. Right now I?m using timers to see if the "get stream" fails within a certain time. If it does I assume an active decline. If it fails after my test-period I do assume a time-out. This does not work perfectly as every device has a different time out period. Exceptions thrown are no solid indication of the response. - Possibility to cancel send requests (or better: Get stream requests) if not acted upon within a certain period of time. Similar to issue above. I know one might be able to achieve this with multithreading and asynch send requests, but this is cumbersome to program (at least for my knowledge) - Ability to detect receiving device type. As far as I know Bluetooth supports device groups allowing to identify if the device on the other