public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Rawlins <robert_rawlins@hotmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Same Old Speed Issues
Date: Mon, 28 Jan 2008 12:59:19 +0000	[thread overview]
Message-ID: <BAY102-W375A5FB8242F3B1245148AF0340@phx.gbl> (raw)
In-Reply-To: <BAY102-W618F2CC7E41A78CBBCE7CF0390@phx.gbl>


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

Afternoon Guys,
 
I know that you're probably getting tired of hearing about this problem but thought I would post some more information in the hope that it might shed some light on the situation and hopefully solve the problem. I just wanted to get your opinion on the HCI dump information which gets output when a file is transferred.
 
It generally seems to be the following repeated continuously throughout the transfer:
 
< ACL data: handle 42 flags 0x02 dlen 25    L2CAP(d): cid 0x004f len 21 [psm 3]      RFCOMM(d): UIH: cr 1 dlci 12 pf 0 ilen 17 fcs 0x4f > HCI Event: Number of Completed Packets (0x13) plen 5> HCI Event: Number of Completed Packets (0x13) plen 5> HCI Event: Number of Completed Packets (0x13) plen 5> ACL data: handle 42 flags 0x02 dlen 12    L2CAP(d): cid 0x0040 len 8 [psm 3]      RFCOMM(d): UIH: cr 0 dlci 12 pf 1 ilen 3 fcs 0x89 credits 2< ACL data: handle 42 flags 0x02 dlen 310< ACL data: handle 42 flags 0x01 dlen 310< ACL data: handle 42 flags 0x01 dlen 310< ACL data: handle 42 flags 0x01 dlen 86    L2CAP(d): cid 0x004f len 1012 [psm 3]      RFCOMM(d): UIH: cr 1 dlci 12 pf 0 ilen 1007 fcs 0x4f 
Does that look normal to you guys are should it be looking any different? I know this is a bit of a tedious thread but I really would appreciate some help solving this as it seems to be driving me a little crazy, Even if you can point me in the direction of a dongle you are using which you are SURE works at full speed, just so I can test it out.
 
Thanks guys,
 
Rob


From: robert_rawlins@hotmail.comTo: bluez-devel@lists.sourceforge.netDate: Fri, 25 Jan 2008 10:28:36 +0000Subject: Re: [Bluez-devel] Same Old Speed Issues


Good morning, Another update on my progress with the problem. This morning I had two new version 2.0 + EDR dongles arrive in the post, both from different manufacturer and both listed on the compatibility list for bluez. I've run some tests this morning on these other two dongles and receive the exact same problem, still not getting anything over 25kBytes/s. I'm running out of different tests to run, I've tried different dongles, system boards, linux builds, kernel versions, bluez versions and every single one keep presenting the same problems, Am I missing something? Thanks guys, I would really appreciate any ideas you might have. Rob


From: robert_rawlins@hotmail.comTo: bluez-devel@lists.sourceforge.netDate: Mon, 21 Jan 2008 16:11:14 +0000Subject: Re: [Bluez-devel] Same Old Speed Issues


Hello Guys,
 
I've been playing around with this again today, looking into ALC MTU's and things like that but really can't find any resources to suggest why I might be getting such poor speeds, I thought it would be a plug-and-play kinds of affair. 
 
I also made an effort to try a couple of other kernel versions, just in case, but they all gave the same results as 2.6.23.
 
Thanks for any further advice guys. Is it worth me giving you some HCI_DUMP information? Is that likely to hold any clues as to what's going wrong?
 
Cheers,
 
Rob

> From: chick@computergeek.freeserve.co.uk> To: bluez-devel@lists.sourceforge.net> Date: Fri, 18 Jan 2008 20:17:35 +0000> Subject: Re: [Bluez-devel] Same Old Speed Issues> > On Friday 18 January 2008 15:04:58 Robert Rawlins wrote:> > 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> >> > Have you tried changing the OBEX block size - try forcing the minimum size to > 64kB-1?> > Cheers,> Tim> > > -------------------------------------------------------------------------> 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/> _______________________________________________> Bluez-devel mailing list> Bluez-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/bluez-devel

Everything in one place. All new Windows Live! 

Everything in one place. All new Windows Live! 
_________________________________________________________________
Free games, great prizes - get gaming at Gamesbox. 
http://www.searchgamesbox.com

[-- Attachment #1.2: Type: text/html, Size: 7004 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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-01-28 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:04 [Bluez-users] Same Old Speed Issues Robert Rawlins
2008-01-18 20:17 ` [Bluez-devel] " 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 [this message]
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-W375A5FB8242F3B1245148AF0340@phx.gbl \
    --to=robert_rawlins@hotmail.com \
    --cc=bluez-devel@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