From: Tim Chick <chick@computergeek.freeserve.co.uk>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Same Old Speed Issues
Date: Fri, 18 Jan 2008 20:17:35 +0000 [thread overview]
Message-ID: <200801182017.36181.chick@computergeek.freeserve.co.uk> (raw)
In-Reply-To: <BAY102-W17970DD14D6076D3F44BCBF0420@phx.gbl>
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
next prev parent reply other threads:[~2008-01-18 20:17 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 ` Tim Chick [this message]
2008-01-19 16:16 ` [Bluez-devel] " 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=200801182017.36181.chick@computergeek.freeserve.co.uk \
--to=chick@computergeek.freeserve.co.uk \
--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