May 2009 - Bluetooth-dev - lists.apple.com

Re: IOBluetoothDevice closeConnection behaves differently on Mac OS 10.5.7
by Ken Aspeslagh 17 May '09

17 May '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Thanks, Ken Date: Thu, 14 May 2009 12:16:03 +0200 From: Camille Troillard <camille(a)osculator.net> Subject: IOBluetoothDevice closeConnection behaves differently on Mac OS 10.5.7 To: bluetooth-dev(a)lists.apple.com Message-ID: <de35c4ed0905140316s5129c588t925689941c528b49(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hello, I have filled a bug on radar, and I'd be happy to know if there's a workaround. Best Regards, Camille _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… We've also noticed some different behaviors with connection closing on 10.5.7. I know the bluetooth-dev list doesn't seem to be monitored by anyone at Apple, but maybe if someone on the BT team is reading this they could try to summarize what's changed behind the scenes in 10.5.7 so we can better think about how it might affect us. ------------------------------------- "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair." - Douglas Adams On Mac OS 10.5.7, calling -[IOBluetoothDevice closeConnection] returns an error: "(iokit/common) device(s) still open". Although this only happens 6 times out of 10, it can be clearly shown that it happens only on 10.5.7 and never on previous versions. This email sent to site_archiver(a)lists.apple.com

1 0

IOBluetoothDevice closeConnection behaves differently on Mac OS 10.5.7
by Camille Troillard 14 May '09

14 May '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=JMCOwcCYGFXj/c059UF2Nw+sG4tSj3M8BNkPiT9YlGM=; b=DEY9a4cAClX0l43ucOXWaw5kjK12qFx1+B5LWLXG3WtYhDwPWujckE27kQOytnd0iY kLZR2BlehxSCwPbA6BLbYSKXl9Gw13Jd3j+Toy8HKryKUNev2KZ51FMljKip10xuaa4I 4L0QMHUCuJLDrlCBWsCnj1+9ofehyOLfh5SMk= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=o62Je6xskxsarsUbgBxXVwD5/aSD8vkeYsesWr4liaPH91QLOgw05ayQtOddcle792 3IaI/p+ysmYNlSkG+fBM/WStXUToh6XsxYLR+Bz0rNmsnXETqu0XvPvx5kTgZrhr0o5n qSmfXNGydV37sKtD9RfySPBEfEFl4n/3mXnyk= _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Bluetooth unresponsive - please help!
by Allan Third 08 May '09

08 May '09

site_archiver(a)lists.apple.com Delivered-To: bluetooth-dev(a)lists.apple.com Hi, Sorry if this is a newbie type of question but I've been banging my head against a brick wall with this for ages. I've searched through the archives thoroughly and I really can't find anything that seems to be relevant - I have no doubt that it's something very very simple. I'm trying to write an app which responds to incoming connections over both Bluetooth and TCP/IP and engages in various kinds of chat with clients on the other ends of both connections. So far, I'm receiving events (NSStreamEventHasBytesAvailable, etc.) from the TCP connection (based on TCPServer in the MiniSOAP example) and that seems to be fine. The problem seems to be with the Bluetooth connection. I started out with the code from RFCOMMServerSample, and adapted ChatBluetoothServerInterface so that it publishes my own SDP record for a new service (which works), and it registers my main object as the delegate for the RFCOMM channel. When a client connects, the delegate methods for receiving a remote connection, RFCOMMOpenComplete, etc., get called successfully, I set up my main object appropriately and send an init message over the RFCOMM channel to the client - [mRFCOMMChannel writeSync:...] completes with kIOReturnSuccess, so it looks like that message is being sent over the right channel successfully. What I then expect to happen is the same as for the TCP connection - the event handlers for new data should be called as and when anything arrives over the connection and my own code deciding what to do with the data should be called from the event handlers. What in fact happens is nothing. My app isn't frozen - if I start a TCP connection after the Bluetooth init has been sent, I still receive those events and get the right NSLog messages. But no further Bluetooth delegate messages are received - particularly, the new data available callback never runs. I'm pretty sure that the client *is* sending data - although I don't have access to its source, I'm sending it exactly the same init messages that I send in Linux over Bluez, and the client certainly seems to *think* it's got a connection to my server, so I believe it will try to send the right messages back. But I'm just not getting anything. The other RFCOMM delegate methods (which I mostly implemented just to see if they ever happened) all get called at least once when the new connection is made by the client, but never again. I've read in the archives that all Bluetooth access should be done in the same thread. I'm not explicitly creating any separate threads, nor, to the best of my knowledge, am I using anything like NSOperation which creates threads in the background. But I have to say, I am thoroughly confused about the structure of Cocoa apps so it is quite possible that I'm doing something incredibly stupid that's causing the BT data-in stuff never to be called. I'd really appreciate anyone's help or advice over this. I tried to include sample code but it made the message too long for the list. If there's anything that it would help to see, just let me know and I'll send it. Thanks, Allan _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0