From: "Frédéric Dalleau" <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [Patch] org.bluez.audio.headset.Connect() to handsfree
Date: Thu, 06 Dec 2007 12:27:57 +0100 [thread overview]
Message-ID: <4757DCBD.40602@access-company.com> (raw)
Hello,
As of today, when calling org.bluez.audio.headset.Connect(), the hfp
profile is searched only if the headset->hfp_handle is initialized.
This member variable is initialized upon CreateDevice the first time the
device is created (during resolve_services).
The variable is not initialized when the audio service is restarted, so
after restarting audio service, it is no longer possible to connect to hfp.
The attached patch fix the problem as follow : first search the hfp
profile handle, then search an hsp profile handle, by getting rfcomm
channel to connect to.
It is based against latest git tree.
Frederic.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-12-06 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 11:27 Frédéric Dalleau [this message]
2007-12-06 11:30 ` [Bluez-devel] [Patch] org.bluez.audio.headset.Connect() to handsfree Frédéric Dalleau
2007-12-06 11:40 ` Marcel Holtmann
2007-12-06 15:16 ` Frédéric Dalleau
2007-12-07 14:02 ` Frédéric Dalleau
2007-12-11 15:44 ` [Bluez-devel] [Patch] Service Level Connection for HFP Alok
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=4757DCBD.40602@access-company.com \
--to=frederic.dalleau@access-company.com \
--cc=bluez-devel@lists.sourceforge.net \
/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.