public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Rawlins <robert_rawlins@hotmail.com>
To: <bluez-devel@lists.sourceforge.net>, <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Same Old Speed Issues
Date: Fri, 18 Jan 2008 15:04:58 +0000	[thread overview]
Message-ID: <BAY102-W17970DD14D6076D3F44BCBF0420@phx.gbl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3740 bytes --]

Hello Guys,
 
You'll have to forgive me, I've posted a copy of this mail to both the users and developers list in the hope that I might widen the audience a little bit and hopefully find a solution to this problem as its been causing me problems for quite some time, I hope you don't mind.
 
The crux of the issue is that I'm getting very slow OBEX transmit speeds, despite the fact that all the conditions seems to be correct for me to take advantage of the full Bluetooth 2 + EDR specification. I'll try my best to help explain all the details and hopefully you'll have some ideas on diagnosing or solving the problems.
 
I'm running a USB dongle from Ezurio which is based on a CSR chipset, running Bluetooth version 2.0 with EDR capabilities. more details on the dongle can be found on thier site. http://www.ezurio.co.uk/products/highspeedusbadaptor/
 
I'm running this on a Debian based system, which is running kernel version 2.6.23 and has Bluez version 3.24 which has been installed from a package on the apt-get service.
 
At the moment I've tried using both ussp-push and open-obex push clients to transfer the file, both giving me the same results. I'm achieving roughly 25Kbytes/s transfer speed both up and down. I've tried running these same dongles from my Windows PC and achieve well over 100kBytes/s. (This is transmitting to a Sony k850i handset which is v2.0 + EDR). This would lead me to believe its not an issue with the Dongle, more likely something with my Linux configuration
 
The output from hciconfig -a look as follows, I'm unable to see anything unexpected in it:
 
hci0:   Type: USB        BD Address: 00:80:98:E6:38:BD ACL MTU: 310:10 SCO MTU: 64:8        UP RUNNING PSCAN ISCAN         RX bytes:242063 acl:5074 sco:0 events:16608 errors:0        TX bytes:5053795 acl:24234 sco:0 commands:146 errors:0        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3         Link policy: RSWITCH HOLD SNIFF PARK         Link mode: MASTER         Name: 'Hello'        Class: 0x080100        Service Classes: Capturing        Device Class: Computer, Uncategorized        HCI Ver: 2.0 (0x3) HCI Rev: 0xbf4 LMP Ver: 2.0 (0x3) LMP Subver: 0xbf4        Manufacturer: Cambridge Silicon Radio (10)
 
And likewise when looking at the features for the chip, it lists the EDR support as we would expect.
 
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80                <3-slot packets> <5-slot packets> <encryption> <slot offset>                 <timing accuracy> <role switch> <hold mode> <sniff mode>                 <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>                 <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>                 <power control> <transparent SCO> <broadcast encrypt>                 <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>                 <interlaced iscan> <interlaced pscan> <inquiry with RSSI>                 <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>                 <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>                 <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>                 <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>
 
This slow speed has been plaguing me for a long time and I've never been able to find anything which looks out of place, regardless of the different kernel and blues editions I've tried.
 
Can anyone provide any advice? if you need any more information at all them please do let me know.
 
Thanks for your time,
 
Robert
_________________________________________________________________
Get Hotmail on your mobile, text MSN to 63463!
http://mobile.uk.msn.com/pc/mail.aspx

[-- Attachment #1.2: Type: text/html, Size: 5853 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2008-01-18 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:04 Robert Rawlins [this message]
2008-01-18 20:17 ` [Bluez-devel] Same Old Speed Issues Tim Chick
2008-01-19 16:16   ` Robert Rawlins
2008-01-21 16:11   ` Robert Rawlins
2008-01-25 10:28     ` Robert Rawlins
2008-01-28 12:59       ` Robert Rawlins
2008-01-22 17:15   ` [Bluez-devel] [PATCH][HFP] fixes supported features in AG's SDP record Alok
2008-01-23 14:40   ` [Bluez-devel] Same Old Speed Issues Robert Rawlins

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=BAY102-W17970DD14D6076D3F44BCBF0420@phx.gbl \
    --to=robert_rawlins@hotmail.com \
    --cc=bluez-devel@lists.sourceforge.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