From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] hfp_hf_bluez5: Fix re-registering a modem for a device
Date: Tue, 23 Apr 2013 04:06:18 -0500 [thread overview]
Message-ID: <51764F0A.3090602@gmail.com> (raw)
In-Reply-To: <1366671224-8777-1-git-send-email-vinicius.gomes@openbossa.org>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hi Vinicius,
On 04/22/2013 05:53 PM, Vinicius Costa Gomes wrote:
> Even for outgoing pairing requests we may receive the UUIDs property
> changed after the device is paired and try to register it twice.
>
> The easiest way to reproduce this is when Extended Inquiry Response is
> supported.
>
> When the device is paired, we receive the "Paired" PropertyChanged,
> inside modem_register_from_proxy(), g_dbus_proxy_get_property() gets
> the UUIDs extracted from the EIR data. Later, when the service
> discovery is finished, the UUIDs property is re-sent and both may
> contain the HFP AG UUID.
My sources indicated to me that BlueZ should perform the SDP query
first, and then signal Paired. Is this something we can not count on or
is this an implementation issue inside BlueZ itself?
Regards,
-Denis
next prev parent reply other threads:[~2013-04-23 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 22:53 [PATCH] hfp_hf_bluez5: Fix re-registering a modem for a device Vinicius Costa Gomes
2013-04-23 9:06 ` Denis Kenzior [this message]
2013-04-23 15:23 ` Johan Hedberg
2013-04-23 15:34 ` Marcel Holtmann
2013-04-23 16:15 ` Johan Hedberg
2013-04-23 16:27 ` Marcel Holtmann
2013-04-23 17:28 ` Johan Hedberg
2013-04-23 18:39 ` Vinicius Costa Gomes
2013-04-25 8:51 ` Mikel Astiz
2013-04-25 9:37 ` Johan Hedberg
2013-04-25 8:27 ` Denis Kenzior
2013-04-25 17:47 ` Vinicius Costa Gomes
2013-04-25 22:48 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51764F0A.3090602@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.