site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com On 24/10/2007, at 11:55 AM, Daniel Birns wrote: Nigel Spon _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... I'm not familiar with IOBluetoothDeviceOpenRFCOMMChannelSync, however it says that it opens a channel, and you've already opened it with OpenConnection()... Perhaps that's the problem. Apparently not; the documentation implies you have to do both, and if I don't try to call IOBluetoothDeviceOpenConnection() first, IOBluetoothDeviceOpenRFCOMMChannelSync() just returns kIOReturnNotOpen - meaning device not open. Unless it means I have to wait for it to open itself - which doesn't seem to happen in my tests - its difficult to see whats inappropriate about calling IOBluetoothDeviceOpenConnection(). Its supposed to open the baseband connection, and that did close. And it does eventually work, is just that after that IOBluetoothDeviceOpenRFCOMMChannelSync() goes into a snit. I am beginning to wonder if my device is misbehaving in some way, although the BT stacks reaction seems a bit unsympathetic if thats the case. --- " I was taken out into a pleasant exercise yard and offered a cigarette. After a few moments I perceived a line of gentlemen with rifles. They were looking in my direction. I looked around, but I could not see the target." This email sent to site_archiver@lists.apple.com