Quirks with establishing incoming channel
Quirks with establishing incoming channel
- Subject: Quirks with establishing incoming channel
- From: "Crichlow, Eric" <email@hidden>
- Date: Tue, 29 Jul 2003 19:03:06 -0400
Are there known issues with incoming channels? I'm having a problems
which seems to be my incoming channel and my application getting "out of
sync".
Here's how things go when it works:
I have a Bluetooth tablet. When my application starts, it sets up an
incoming channel. I then use my application to establish a connection to
the tablet. When it connects, my application transmits my local Bluetooth
address to the tablet. The tablet stores that address. The tablet has a
"Link" button that, when pushed, attempts to connect to the Bluetooth device
corresponding to the address that it has stored.
Usually, this works great. I can connect to a number of tablets, have my
BT address transmitted to each one, and from that moment on, use the Link
button on the tablets to re-establish connection to my application when
desired.
But there's two circumstances where the process gets hosed.
First, if I attempt to connect to a tablet, but the tablet is off (and
thus the connection attempt fails,) and then I turn the tablet on and hit
the Link button to establish the connection from the device to the
application, the tablet goes through its connection attempt cycle (about 10
seconds) and fails. And it continues failing each time I try it after that.
Second, if my application unexpectedly quits (and thus never calls
IOBluetoothRemoveServiceWithRecordHandle or unregister) and I start it up
again and try to hit the Link button on a tablet to establish a connection,
the tablet doesn't connect. But then if I exit my application (which goes
through the the normal exit routine and removes the service) and restart it,
I immediately get the incoming connection from the tablet, even though the
tablet stopped trying to connect already and thinks that the connection
failed.
It's like the incoming channel is still open, and the tablet really does
connect to it, but the connection between my application and the incoming
channel is broken, so I never get notification of an incoming connection,
until I restart the application, and then it apparently re-establishes
connection to the incoming channel.
Is there something about a failed connection attempt that screws up the
incoming RFCOMM channel?
...Eric Crichlow...
...GTCO CalComp...
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.