public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumeet VERMA <sumeet.verma@st.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem with HSP/HFP in bluez-3.22
Date: Mon, 5 Nov 2007 16:30:57 +0530	[thread overview]
Message-ID: <019301c81f9b$24d85b50$832fc70a@dlh.st.com> (raw)
In-Reply-To: <20071105091147.GA23820@localhost>

Hi Johan
Thanks for your help. I was earlier testing it with an application which had
HF service registered and not HS. Now I tested with Nokia HS-12W and it
works fine.  


Regards,
Sumeet 
-----Original Message-----
From: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Johan
Hedberg
Sent: Monday, November 05, 2007 2:42 PM
To: BlueZ users
Subject: Re: [Bluez-users] Problem with HSP/HFP in bluez-3.22

Hi,

On Mon, Nov 05, 2007, Sumeet VERMA wrote:
> [root@dlhl0330 audio]# dbus-send --system --print-reply 
> --type=method_call --dest=:1.3 /org/bluez/audio 
> org.bluez.audio.Manager.CreateHeadset string:XX:XX:XX:11:65:00 method
return sender=:1.3 -> dest=:1.19  string "/org/bluez/audio/device3"
> [root@dlhl0330 audio]# dbus-send --system --print-reply 
> --type=method_call --dest=:1.3 /org/bluez/audio/device3 
> org.bluez.audio.Headset.Connect Error 
> org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with 
> signature "" on interface "org.bluez.audio.Headset" doesn't exist

The CreateHeadset method should actually be considered deprecated.
Currently it simply maps to CreateDevice so you might as well use that
instead. This is also the reason why you don't get an error for this call.
It seems that a HSP service record was not found on the remote device and
the Headset D-Bus interface is therefore not available for the created
object.

Are you sure the headset supports HSP? Can you discover it e.g. through
sdptool search --bdaddr <bdaddr> HS

What is the model of your headset?

Johan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-11-05 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05  9:01 [Bluez-users] Problem with HSP/HFP in bluez-3.22 Sumeet VERMA
2007-11-05  9:11 ` Johan Hedberg
2007-11-05 11:00   ` Sumeet VERMA [this message]

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='019301c81f9b$24d85b50$832fc70a@dlh.st.com' \
    --to=sumeet.verma@st.com \
    --cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox