From: "siddhant tewari" <siddhant.tewari@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Improving Transmission Speeds
Date: Mon, 20 Aug 2007 19:32:39 +0530 [thread overview]
Message-ID: <57c68ddc0708200702ycd697fbx5911b08fb5956251@mail.gmail.com> (raw)
In-Reply-To: <BAY102-W8887C0357267FC9175899F0DB0@phx.gbl>
[-- Attachment #1.1: Type: text/plain, Size: 2001 bytes --]
hi Robert,
I have had similar experience too .. I want to add one more
point :-
There is a difference in transfer rates while transfer a file between phone
and PC between when i am simply making obex push of the file and when i am
transferring files after pairing up the device.
Is the above behavior expected. I feel that this should happen but a
confirmation from more experienced people will give more confidence.
regards
siddhant
On 8/20/07, Robert Rawlins <robert_rawlins@hotmail.com> wrote:
>
> Hello Guys,
>
> I'm running Bluez 3.12 and doing a little bit of file transfer over OBEX
> push and seem to get considerably lower transmission speeds than when i'm
> transmitting from my windows system using the windows stack. For instance,
> when transmitting a 40kb file from my linux system using bluez the file will
> take several seconds to transfer from acceptance of the invitation, however,
> when using the same hardware on my windows box, it will transfer almost
> immediately, with no noticeable delay, this speed difference becomes even
> more apparent when dealing with larger files.
>
> I'm sure i've read in the past this is quite common when using the linux
> stacks, is that right? is there any way to make a marked improvement? I'm
> running bluetooth 2 with EDR capabilities, on a CSR chip.
>
> Thanks guys,
>
> Rob
>
> ------------------------------
> Are you the Quizmaster? Play BrainBattle with a friend now!
> <http://specials.uk.msn.com/brainbattle>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
[-- Attachment #1.2: Type: text/html, Size: 2896 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- 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
next prev parent reply other threads:[~2007-08-20 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:19 [Bluez-users] Improving Transmission Speeds Robert Rawlins
2007-08-20 14:02 ` siddhant tewari [this message]
2007-08-20 14:35 ` Loreno Oliveira
-- strict thread matches above, loose matches on Subject: below --
2007-08-20 14:52 Robert Rawlins
2007-08-24 12:22 ` 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=57c68ddc0708200702ycd697fbx5911b08fb5956251@mail.gmail.com \
--to=siddhant.tewari@gmail.com \
--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