Open-connection bug, workaround request
site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=FnVNlNbsZcYbSj0KWF/0OPUa0tloGtyz4qW6wR8dHvE=; b=t/WcaVHZjStivQjuqlQZRGezX9BY3dGujtzeOOvL9mMx765O+AJ0cSEDkrMcFk7knl HmJS/xRaXPh8wtF7We3xFEKjaTCHxQJVe0R0z8uJLLx9BgeFR+NW4hlvf7ShK9ztlSfZ Y2yoZI2jHzzk9z+3SJ8V5EIobiJGqfp+iYbOs= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=ukbJHRqruG9AJCOU+w8IKxYFzG/ooNahqvMaC5Huc8JnVSVxY/IA3kXTCtsVOOEUdD JeiQn/AlyiIoQiWdP4j+iSodIITaAkndW57FnnCiPOz7UTHFqJh8iPs9C9oNTX4LHDm2 8QVTjfhHqHkq3qF7H3s7qIm851q46LUJ1nDqY= Hey list, I'm having an issue where opening a connection to a Bluetooth device results in -connectionComplete:status: being called claiming the connection was successful, but -isConnected returns NO for the Bluetooth device. Repeated attempts to open a connection results in the same behavior, and calling -closeConnection returns 0xE00002C0 ("no such device", according to IOReturn.h.) Once in this state, opening a connection to the device becomes impossible, and other Bluetooth operations fail for the device. I'm looking for an API to get the Bluetooth stack out of this inconsistent state. So far, disabling/reenabling Bluetooth fixes it, as does the "Modify Software Configuration" dialog in the Bluetooth Explorer app (I'm still investigating which specific option fixes it.) There are a few other interesting details: o -connectionComplete:status: claims success, but PacketLogger says the actual status after attempting to open the connection is "0x0B - ACL connection already exists." o Calling -closeConnection does not generate an HCI command; I'm hypothesizing that the problem would be fixed if the APIs would actually issue the HCI command. o Here is the PacketLogger log for the repeated connection attempts (which contains information about my host system, Bluetooth chipset, etc.): http://themha.com/OpenConnectionLog.zip. Perhaps someone knows of a programatic way of getting the Bluetooth stack out of this corrupted state? Thanks! David _______________________________________________ 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... This email sent to site_archiver@lists.apple.com
participants (1)
-
Dave Keck