From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] "comlicated" setup - known issues for hid and SCO?
Date: Mon, 09 Aug 2004 19:13:17 +0200 [thread overview]
Message-ID: <1092071597.4564.17.camel@pegasus> (raw)
In-Reply-To: <4117A907.7010006@dark-reality.de>
Hi Lars,
> right now I'm using two BT devices with my Epox dongle, an MX900 mice
> and a Sony Ericcson HBH-35 Headset with snd-bt-sco (voice mode 0x0060,
> before you ask ;)
what does "hcitool info ..." say about your headset? What is the
firmware version of your EPoX dongle?
> both devices work fluently when used without the other, but when I use
> headset and mouse at the same time there are various problems during
> connect, scan and usage.
>
> The main usage problem was that the sco layer got scrambled audio
> (sounded much like random data) on about every third sco connection.
> After a while, mouse and headset began to block each other, and the
> stack seemed to get more and more, well, muddy. After some more
> connection retries even the mouse, before only "hanging" when the
> headset tried to connect, stopped working fully.
>
> dmesg only noticed this:
>
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 76
>
> When even connection was impossible, I plugged the BT dongle out and put
> it back in. After reloading the hid module and programs the mouse and
> headset worked again.
I think that is a hardware problem. A protocol analyser would help to
track this down ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-09 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 16:40 [Bluez-devel] "comlicated" setup - known issues for hid and SCO? Lars Grunewaldt
2004-08-09 17:13 ` Marcel Holtmann [this message]
2004-08-09 17:25 ` Lars Grunewaldt
2004-08-09 17:44 ` Marcel Holtmann
[not found] ` <4117BA71.5000800@dark-reality.de>
2004-08-09 22:29 ` Marcel Holtmann
2004-08-10 0:03 ` Lars Grunewaldt
2004-08-10 12:51 ` Marcel Holtmann
2004-08-10 12:25 ` Lars Grunewaldt
2004-08-10 12:49 ` Marcel Holtmann
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=1092071597.4564.17.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lgw@dark-reality.de \
/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