From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco
Date: Fri, 21 Jan 2005 18:04:56 +0100 [thread overview]
Message-ID: <41F13638.1080207@dark-reality.de> (raw)
In-Reply-To: <41F128F4.2020006@webstuhl.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ben Pezzei wrote:
| Hi Lars,
|
| Tnx for your reply
|
| Lars Grunewaldt schrieb:
|
| ...
|
|> 3. disconnect the headset by pressing the "connect" button of the
|> headset again. Audio stops working until you "connect" again with the
|> button.
|
|
| like i said, the rfcomm connection is fine: (output from btsco <addr>):
btsco handles rfcomm and sco connections, so...
| Device is 1:0
| Voice setting: 0x0060
| RFCOMM channel 1 connected
| recieved AT+CKPD=200
| opened hwdep
| connected SCO channel
| Setting sco fd
| Done setting sco fd
this looks good.
| after reconnecting via headset:
| disconnected SCO channel
| recieved AT+CKPD=200
| opened hwdep
| Can't connect SCO audio channel
| : Connection timed out
this does not. It should re-connect without problems, but I can't tell
whether this would be solved with mh1-patches or what might causing that
you can't reconnect to the headset.
You can try the patches out, I use them and it works well.
| I guess the Problem has to do with the SCO or ALSA Stuff
sco, not alsa I think. The alsa stuff is only needed to transmit the sco
data to the alsa functions and vice versa, so it's unlikly that the
impossibility of reconnecting on a new sco channel is the problem. More
likely the sco channel is not terminated correctly in the first place.
best regards,
~ Lars
- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB8TY3QWC6DTWkDAoRAlCCAJ9CyuecdSlBzOw+WP2AOqK5G0BOoACfWSNH
P0eRv2FWV2wQNyVtdZ3+m9I=
=NCy7
-----END PGP SIGNATURE-----
-------------------------------------------------------
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-21 17:04 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 [this message]
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 ` [Bluez-devel] " Paul Ionescu
2005-01-22 15:40 ` [Bluez-devel] " 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=41F13638.1080207@dark-reality.de \
--to=lgw@dark-reality.de \
--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