From: "John H." <mistamaila@gmail.com>
To: "BlueZ development" <Bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] skype and bluetooth
Date: Mon, 14 May 2007 13:02:12 -0500 [thread overview]
Message-ID: <5b9417770705141102w6282efbl6bba1ec14a65591c@mail.gmail.com> (raw)
In-Reply-To: <5b9417770705141014w20611f52v50526f928501803c@mail.gmail.com>
Here's the output of headsetd, which "connects" after i hit button on
headset, but the rest is what outputs when I try to use skype with it.
headsetd -n
headsetd[20485]: Bluetooth headset daemon version 0.5
headsetd[20485]: Incoming RFCOMM hs connection from 00:16:8F:F9:97:BB accepted
headsetd[20485]: Changing state: Idle-->Connected
headsetd[20485]: Changing state: Connected-->Ready
headsetd[20485]: Changing state: Ready-->Opening
headsetd[20485]: SCO channel opened handle=0x0031 mtu=64
headsetd[20485]: Changing state: Opening-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Changing state: Zombie-->Streaming
headsetd[20485]: Appli closed socket
headsetd[20485]: Changing state: Streaming-->Zombie
headsetd[20485]: Nobody uses SCO channel anymore, closing it.
headsetd[20485]: Changing state: Zombie-->Connected
On 5/14/07, John H. <mistamaila@gmail.com> wrote:
> Hi,
>
> Motorola h700.
>
> I have plugz installed, and the corresponding asound.conf from it.
>
> fc6 and headset paired.
>
> I tell new alpha skype 1.4 to use headset for in, out and ring(as
> headsetd is running)
>
> When i try test call, it says problem with audio playback? However,
> the headset beeps at this time, so there's definitely some kind of
> communication.
>
> What to do? Am I supposed to be using hijacker?
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-14 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 17:14 [Bluez-devel] skype and bluetooth John H.
2007-05-14 18:02 ` John H. [this message]
2007-05-15 0:00 ` Robert Huitl
2007-05-15 0:16 ` Robert Huitl
2007-05-15 20:22 ` Robert Huitl
2007-05-15 21:20 ` Tim Chick
2007-05-16 0:21 ` Robert Huitl
2007-05-16 2:26 ` John H.
2007-05-16 8:02 ` Robert Huitl
2007-05-16 21:37 ` John H.
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=5b9417770705141102w6282efbl6bba1ec14a65591c@mail.gmail.com \
--to=mistamaila@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox