From: administrator tootai <admin@tootai.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Connection issue with headset
Date: Mon, 31 Jan 2005 19:20:10 +0100 [thread overview]
Message-ID: <41FE76DA.6000201@tootai.net> (raw)
In-Reply-To: <1107186911.7902.16.camel@pegasus>
Marcel Holtmann a =E9crit :
>Hi Daniel,
>
> =20
>
>>>what is in /proc/bus/usb/devices? I think that this dongle don't has t=
he
>>>needed USB ISOC endpoints for SCO data.
>>>=20
>>>
>>> =20
>>>
>>This is not a dongle output, it's the headset one. Here is the output o=
f=20
>>devices.
>> =20
>>
>
>then forget what I said. You have a CSR dongle with HCI 16.4 and this
>should work fine.
> =20
>
Then is it normal that hcitool scan <btaddr> doesn't find the headset as=20
hcitool info <btaddr> is ok? Meanwhile, I CVS the latest btsco, rebuild=20
everything and tested with the mpg123 sample with a2play. Here the=20
result from output:
MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
subbands =3D 1
allocation method =3D 1
channel_mode =3D 2
blocks =3D 3
sampling frequency =3D 2
bitpool =3D 32
frame len =3D 72
Using address: 00:0b:2e:06:01:2e
Can't connect to 2E:01:06:2E:0B:00. Invalid argument(22)
cannot open psm_cmd =3D 0
Many thanks for your help.
--=20
Daniel
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-31 18:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 9:32 [Bluez-users] Connection issue with headset administrator tootai
2005-01-28 15:53 ` [Bluez-users] " Sebastian Roth
2005-01-29 16:39 ` daniel huhardeaux
2005-01-29 16:43 ` administrator tootai
2005-01-29 17:29 ` Stefan Bellon
2005-01-30 3:13 ` Brad Midgley
2005-01-30 19:01 ` administrator tootai
2005-01-31 14:57 ` administrator tootai
2005-01-31 14:58 ` Marcel Holtmann
2005-01-31 15:30 ` administrator tootai
2005-01-31 15:55 ` Marcel Holtmann
2005-01-31 18:20 ` administrator tootai [this message]
2005-02-01 16:37 ` Sebastian Roth
2005-02-02 13:20 ` administrator tootai
2005-02-02 16:21 ` Sebastian Roth
2005-02-02 16:55 ` administrator tootai
2005-02-03 14:13 ` Sebastian Roth
2005-02-03 21:39 ` administrator tootai
2005-02-04 7:38 ` Sebastian Roth
2005-02-04 12:25 ` administrator tootai
2005-02-03 17:06 ` administrator tootai
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=41FE76DA.6000201@tootai.net \
--to=admin@tootai.net \
--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