From: Marcel Holtmann <marcel@holtmann.org>
To: Laszlo Sogor <shogy@shogy.ohsh.u-szeged.hu>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Linux + Bluez problem
Date: Sun, 28 Dec 2003 15:03:34 +0100 [thread overview]
Message-ID: <1072620213.27286.17.camel@pegasus> (raw)
In-Reply-To: <E1AaCHm-0004YL-00@shogy.ohsh.u-szeged.hu>
Hi Laszlo,
> I have a problem with the Bluetooth connection between my computer and
> my phone. Sometimes it drops the Bluetooth connection, I could reproduce
> it in two different ways:
>
> case #1
> I use GPRS with my phone, the phone is connected to my computer using
> Bluetooth. When I try to retrieve a page with images, the Bluetooth
> connection fails with high probability (90 %).
>
> I use /dev/rfcomm2 to access DUN (channel 1) service of my phone.
> I monitored the Bluetooth connection with l2ping:
>
> # l2ping 00:60:57:2F:11:8C
> ...
> 0 bytes from 00:60:57:2F:11:8C id 215 time 94.99ms
> 0 bytes from 00:60:57:2F:11:8C id 216 time 121.83ms
> 0 bytes from 00:60:57:2F:11:8C id 217 time 26.51ms
> no response from 00:60:57:2F:11:8C: id 218
> no response from 00:60:57:2F:11:8C: id 219
> no response from 00:60:57:2F:11:8C: id 220
> no response from 00:60:57:2F:11:8C: id 221
> Recv failed: Software caused connection abort
> #
don't use l2ping. Maybe your phone don't likes it. Run hcidump and look
the packages on the HCI layer.
> At this point, the pppd drops the connection and the Bluetooth subsystem
> will be unusable until I remove and re-insert the USB dongle (for the sw
> and
> hw specification, see the end of the mail).
>
> Unfortunately I have only one Buetooth device, so I could not determine
> whether the error is in the device, the driver or anything else.
>
>
> case #2
> I use p3nfs package (5.12) to mount my phone (Symbian Series 60). I
> mounted the phone and did some tests:
> - in a loop
> - copy a large (3MB) file to the phone
> - wait 20 seconds
> - delete the file
> - monitor the Bluetooth connection
>
> I found that the Bluetooth connection failed just like when I used GPRS.
>
> Used SW:
> - Linux kernels 2.4.22 and 2.4.23 (with and without -mh1 patch for both)
> - Debian Woody and Sarge
> - bluez-libs-2.4 with bluez-utils-2.3
> - bluez-libs-2.5 with bluez-utils-2.4
>
> Used HW:
> - Nokia 3650 (sw ver 3.16)
> - Epox BT-DG03 USB dongle
what do "hciconfig -a" say? Do you have SCO support activated for the
USB driver? If yes, try without it. Change from usb-uhci to uhci or vice
versa.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2003-12-28 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 11:07 [Bluez-users] Linux + Bluez problem Laszlo Sogor
2003-12-28 14:03 ` Marcel Holtmann [this message]
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=1072620213.27286.17.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=shogy@shogy.ohsh.u-szeged.hu \
/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