From: Marcel Holtmann <marcel@holtmann.org>
To: Steve Drew <steve.drew@empics.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Problems connecting to multiple rfcomm sockets
Date: Thu, 04 Nov 2004 19:01:13 +0100 [thread overview]
Message-ID: <1099591273.7022.70.camel@pegasus> (raw)
In-Reply-To: <0DD4EA5DCF754A409C4E182C758C37F38231@tigris.i.empics.co.uk>
Hi Steve,
> I've tried increasing the page timeout and the error still
> remains.
two more options left to try.
> I have found that the problem is due to the mobile handsets we
> were using (3x Nokia 6310i). Using a different handsets (Nokia
> 6230's) we were able to get bluetooth connections to 3 6230s (on top of
> this we could also have 2 6310s connected).
Yeah, the old Nokia Bluetooth chips are not quite the best for such
scenarios. The 6230 contains a CSR chip, right?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users
next parent reply other threads:[~2004-11-04 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0DD4EA5DCF754A409C4E182C758C37F38231@tigris.i.empics.co.uk>
2004-11-04 18:01 ` Marcel Holtmann [this message]
2004-11-04 18:15 ` [Bluez-users] Problems connecting to multiple rfcomm sockets Peter Stephenson
2004-10-27 16:32 Steve Drew
2004-10-27 16:45 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 15:42 Steve Drew
2004-10-27 15: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=1099591273.7022.70.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=steve.drew@empics.com \
/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