From: "João Santos" <jsantos_pt@hotmail.com>
To: marcel@holtmann.org
Cc: bluez-users@lists.sourceforge.net
Subject: Re: hci goes down
Date: Tue, 02 Mar 2004 16:53:42 +0000 [thread overview]
Message-ID: <Sea2-F4627YoYkdh0cX00047c34@hotmail.com> (raw)
Hi marcel,
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
>SCO data: handle 0x002c dlen 144
Receive failed: Broken pipe
>can be a bad USB host controller (some VIA or SIS had problems) or it is
>the wrong host controller driver (try the other one). And of course the
>disconnect came from the phone, so maybe only listening on the RFCOMM
>channel is not enough and you must fulfill all AT commands for the
>Headset or Handsfree profile.
Using the hstest i had record some speech from the phone, but after that the
hci goes down. Could the problem be caused by the software.
I couldn't send any at commands after i made a rfcomm to channel 12, because
i start receving sco data, and after a while hci goes down.
Sorry about the stupid question, but host controller driver is the hci,
right?
When i start using the bluez i remember that when i use hciconfig it appears
hci0 and hci1, but now it only appears hci0.
Thanks
João Santos
_________________________________________________________________
Fast. Reliable. Get MSN 9 Dial-up - 1 month FREE! (Limited-time Offer)
http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/
next reply other threads:[~2004-03-02 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 16:53 João Santos [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 16:08 hci goes down João Santos
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=Sea2-F4627YoYkdh0cX00047c34@hotmail.com \
--to=jsantos_pt@hotmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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