end is e.g. a phone device, audio device, computer device, etc. Some other BT Apis support this feature - Multi dongle support. Allow bluetools to address more than one dongle on one PC. 2 Dongles would be fine, 4 would be great. Not sure if windows and the bluetooth stacks can handle that today - Ability to get more details about receiving device, e.g. phone manufacturer. As far as I know Bluetooth does not support natively so might have to rely on fingerprinting, which might be to much hassle to implement as it requires constant updates to device databases Thanks again for taking the feedback. Will you be providing a kind of roadmap for future Bluetools releases so that we know what to expect? Also I would be willing to pay for an upgrade if it offers enhanced features. quote: Originally posted by MacSass - Overall stability: Make Bluetools work as stable and reliable as possible for continuous running. With the current version I do see intermittend failures where exceptions are not thrown for discovery finished or sends get stuck. Stability is the most important for me - everything else is second. If that would require to drop support for Widcomm-Stack I would accept that, although I would prefer to see continued support for the Widcomm stack (eventually requiring a certain level of stack version) Dropping support for Widcomm would not automatically give better stability for the MS stack. A lot of the issues are due to the poorly implented