Open-connection bug, workaround request
Open-connection bug, workaround request
- Subject: Open-connection bug, workaround request
- From: Dave Keck <email@hidden>
- Date: Wed, 28 Jul 2010 03:57:25 -0400
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden