public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "John H." <mistamaila@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] if using bluetooth DUN, how to get best performance?
Date: Tue, 20 Feb 2007 02:44:37 -0600	[thread overview]
Message-ID: <5b9417770702200044k290111f0m880d009c17f6f577@mail.gmail.com> (raw)
In-Reply-To: <45DA6241.8030507@xmission.com>

I am using the moto Q with sprint, and pdanet.  It doesn't work
without pdanet, and pdanet also lets me use it without using the modem
plan.  Is it the pdanet software that may be limiting bandwidth?

On 2/19/07, Brad Midgley <bmidgley@xmission.com> wrote:
> John
>
> > well, when using pdanet's software in xp and usb connection, i got over 800kb/s
> > when using bt dun in XP, i got 160kb/s
> >
> > I am assuming it was roughly the same speed in linux DUN.  I don't see
> > them fixing their software itself to run on linux any time soon, so i
> > am probably stuck with BT DUN as opposed to USB dun in linux, so i was
> > wondering if there was anything i could do.
>
> which phone are you using? do you use pdanet for bt dun or a native dun
> service?
>
> in my experience, pocketpc runs bt dun nowhere near the bluetooth
> bandwidth ceiling. It probably doesn't make any difference if you find a
> phone with bt2.0+edr. Their performance just stinks. The numbers you
> mention are not surprising.
>
> sometimes it crosses the line from poor performance to simply buggy. I
> was consistently locking up the sprint 6700 when using a linux dun
> client. I'm not sure if there's anything we can do from bluez to help
> the situation. I took the phone back.
>
> brad
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-02-20  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  3:02 [Bluez-devel] if using bluetooth DUN, how to get best performance? John H.
2007-02-19  3:51 ` Brad Midgley
2007-02-19 18:13   ` John H.
2007-02-20  2:51     ` Brad Midgley
2007-02-20  8:44       ` John H. [this message]
2007-02-20 23:43         ` Brad Midgley
2007-02-21  2:30           ` John H.
2007-02-21  5:34             ` Brad Midgley

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=5b9417770702200044k290111f0m880d009c17f6f577@mail.gmail.com \
    --to=mistamaila@gmail.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