Re: Failed to open an RFCOMM, how to kill dialog ?
Re: Failed to open an RFCOMM, how to kill dialog ?
- Subject: Re: Failed to open an RFCOMM, how to kill dialog ?
- From: dave Boydston <email@hidden>
- Date: Mon, 22 Nov 2004 14:12:33 -0800
Marco,
Thanks for the reply.
1 and 2 are definitely not the case, 3 is a bit vague so I'm not sure.
I can say with absolute certainty, that simply turning on the BT device
or bringing it in range _does_ allow a connection.
Can you provide information on how to prevent the dialog, or
an alternative open method that won't throw the dialog?
--
Dave Boydston
805.964.4868 x115
866.546.4523 FAX
Serialio.com - Bringing your bright ideas to Life
Marco Pontil wrote:
Usually there are 3 reasons why that dialog appears:
1] The device with the RFCOMM channel you want
to connect to requires paring and you are not paired.
2] You are attempting to open an RFCOMM channel ID
that does not exist.
3] Something during the opening of the channel goes
really bad or does not happen and the timer that
oversees the open sequence fires.
All these cases are different from the "open busy" because
they report an error that can not be solved by simply turning
on your device, or putting it back in range.
With the given information there is not much more I can guess.
Marco
On Nov 21, 2004, at 9:30 PM, dave Boydston wrote:
We have a program that worked fine until we updated
to OS X 10.3. The program opens an RFCOMM port
using the OS X system open() call. We catch the open
exception (16 - port busy) which occurs when the
Bluetooth device is inactive.
When we updated to OS X 10.3 we now get the following
dialog that pops up when the port open fails.
------------------------------------------------------
A Bluetooth serial failure has occurred.
Failed to open an RFCOMM serial channel.
Check if authentication need to be enabled in your
device.
------------------------------------------------------
How can we prevent this dialog from showing since the
only purpose it serves is to annoy the users?
-- Dave Boydston
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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