Hello,
I'm running v3.34. I know it's not the latest. But I've observed what I
describe below on virtually any previous 3.x version.
Somewhere in my code, I perform a call to
Adapter.GetRemoteServiceHandles(btAddress, match). This call blocks as
expected. A few seconds later, I get a RemoteDeviceConnected signal.
Great, looking good. But about 30s after the first call,
GetRemoteServiceHandles finally returns, by throwing a
ConnectionAttemptFailed. The RemoteDeviceDisconnected event arrives at
the same time than the expection.
How can I get I get a ConnectionAttempFailed while I have received a
"Connected" signal previously? Is it to be expected? How should such
apparent non-sense be dealt with? Or perhaps I'm mislead by the
(apparently obvious) "ConnectionAttemptFailed" name?
Thanks in advance,
Best Regards.
Pierre-Yves
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Pierre-Yves,
> > the SDP connection establishment might fail. This is different from from
> > any low-level ACL link that you see. Run hcidump -X -V and see what
> > actually does happen.
>
> Ok, so depending on when I get it, ConnectionAttempFailed might mean
> "ACL link establishment failed", or "SDP connection failed", or
> something else when triggered from elsewhere.
my guess in this case it means SDP connection failed since that is what
you requesting. It should not tell you about failures in other layers
since you don't care about them.
> And it is my duty to correctly figure out what it does mean at any given
> time. Is it right?
In this case run hcidump -X -V to actually figure out what happens. It
is always possible that we have a bug somewhere that nobody has
triggered before.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Marcel,
> the SDP connection establishment might fail. This is different from from
> any low-level ACL link that you see. Run hcidump -X -V and see what
> actually does happen.
Ok, so depending on when I get it, ConnectionAttempFailed might mean
"ACL link establishment failed", or "SDP connection failed", or
something else when triggered from elsewhere.
And it is my duty to correctly figure out what it does mean at any given
time. Is it right?
Regards,
Pierre-Yves
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Pierre-Yves,
> I'm running v3.34. I know it's not the latest. But I've observed what I
> describe below on virtually any previous 3.x version.
>
> Somewhere in my code, I perform a call to
> Adapter.GetRemoteServiceHandles(btAddress, match). This call blocks as
> expected. A few seconds later, I get a RemoteDeviceConnected signal.
> Great, looking good. But about 30s after the first call,
> GetRemoteServiceHandles finally returns, by throwing a
> ConnectionAttemptFailed. The RemoteDeviceDisconnected event arrives at
> the same time than the expection.
>
> How can I get I get a ConnectionAttempFailed while I have received a
> "Connected" signal previously? Is it to be expected? How should such
> apparent non-sense be dealt with? Or perhaps I'm mislead by the
> (apparently obvious) "ConnectionAttemptFailed" name?
the SDP connection establishment might fail. This is different from from
any low-level ACL link that you see. Run hcidump -X -V and see what
actually does happen.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel