From: Paul Ionescu <i_p_a_u_l@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Re: Again: Problems with Dongle, Headset or btsco
Date: Sat, 22 Jan 2005 21:24:43 +0200 [thread overview]
Message-ID: <pan.2005.01.22.19.24.42.369346@yahoo.com> (raw)
In-Reply-To: 41F290CB.9010504@webstuhl.net
On Sat, 22 Jan 2005 18:43:39 +0100, Ben Pezzei wrote:
> Hi ,
>
> Paul Ionescu schrieb:
>
>> How do you know the dongle can't be re-initialized ? What does it say
>> when you launch again btsco ?
>
> After disconnecting via Headset (press Button) and connecting again the
> btsco looks like:
> disconnected SCO channel
> recieved AT+CKPD=200
> opened hwdep
> Can't connect SCO audio channel
> : Connection timed out
you can try to disconnect btsco (with ^C)
verify with
hcitool con
that you don't have any connections still active after you disconnect
btsco, (if they are, delete them with hictool dc MAC_OF_HEADSET)
and then try again to connect with btsco.
I had this problem and I solved this way.
> Same when exiting ctrl+c btsco and start it again
>
>> I was able to use gnomemeeting, mplayer and other programs that use alsa
>> or oss.
>> For mplayer I used -ao alsa:device=hw=Headset -srate 8000 -channels 1
>
> no X installed ;(
You don't need X for mplayer
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-22 19:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 11:44 [Bluez-devel] Again: Problems with Dongle, Headset or btsco Ben Pezzei
2005-01-21 13:07 ` Lars Grunewaldt
2005-01-21 16:08 ` Ben Pezzei
2005-01-21 17:04 ` Lars Grunewaldt
2005-01-21 17:14 ` mirko_3
2005-01-22 13:59 ` Ben Pezzei
2005-01-22 14:19 ` mirko_3
2005-01-22 14:40 ` ligi
2005-01-22 15:35 ` [Bluez-devel] " Paul Ionescu
2005-01-22 17:43 ` Ben Pezzei
2005-01-22 19:24 ` Paul Ionescu [this message]
2005-01-22 15:40 ` Sebastian Roth
2005-01-22 17:50 ` Ben Pezzei
2005-01-23 17:52 ` Lars Grunewaldt
2005-01-24 10:46 ` Ben Pezzei
2005-01-24 11:21 ` Lars Grunewaldt
2005-01-24 12:20 ` Marcel Holtmann
2005-02-02 5:00 ` [Bluez-devel] " Jesse Guardiani
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=pan.2005.01.22.19.24.42.369346@yahoo.com \
--to=i_p_a_u_l@yahoo.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.