public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bc90021 <bc90021@bc90021.net>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Treo 650 Oddities
Date: Fri, 29 Jul 2005 20:10:08 -0400	[thread overview]
Message-ID: <1122682209.11983.113.camel@viskulan.tigerhost.net> (raw)
In-Reply-To: <loom.20050728T195337-380@post.gmane.org>

Hi All,

I have three devices:


Dell Desktop, with USB Dongle
Dell Laptop, with USB Dongle
Treo 650 (Verizon)


>>From the desktop, I can see the phone and the laptop.
>>From the laptop, I can see the desktop and the phone.
>>From the phone, I can see the desktop, but not the laptop.

No matter what I do, the phone will not discover the laptop.  It sees
the desktop with no problem.

I've tried switching the dongles, to no effect.  I've tried updating my
BlueZ software, to no effect.  I've tried updating the kernel, to no
effect.

I can't use hcidump to find out what's going on, because it doesn't
register the connection attempt from the phone.  (I tried that with the
desktop, too, with the same effect.)  However, the desktop can
successfully connect to the phone nonetheless, as the laptop should.
(I've backed up the Treo with pilot-xfer, so I know it works.)

The dongle (either one), when in the laptop, will turn to a more solid
blue (as opposed to intermittently flashing), making it look like it is
getting a signal.  I'm never more than three feet from the laptop with
the phone, so range is not an issue.

The kernel versions are the same on the desktop and the laptop.  The
BlueZ software versions are identical (I'm using Gentoo on both).  The
configuration files are the same (literally, I scp'ed them) on the
laptop as they are on the desktop.

Can anyone suggest what to try next?  I'm at a loss here... I want to be
able to use the Treo as a modem for the laptop while I'm on vacation,
but since I can't pair them, I can't do that right now.

Thanks in advance for any and all help.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-07-30  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21  7:14 [Bluez-users] Early failures with Treo 650 David Britton
2005-05-23 10:06 ` Marcel Holtmann
2005-05-24  2:38   ` David Britton
2005-05-24  8:48     ` Marcel Holtmann
2005-05-26  4:43       ` David Britton
2005-05-26  8:16         ` Marcel Holtmann
2005-05-27  2:15           ` David Britton
2005-05-27  7:05             ` Marcel Holtmann
2005-05-28  5:46               ` David Britton
2005-05-28 13:41                 ` Marcel Holtmann
2005-06-02  4:46                   ` David Britton
2005-07-28 18:02                     ` [Bluez-users] " Ken M
2005-07-30  0:10                       ` bc90021 [this message]

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=1122682209.11983.113.camel@viskulan.tigerhost.net \
    --to=bc90021@bc90021.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