Linux bluetooth development
 help / color / mirror / Atom feed
From: Michael Mauch <michael.mauch@gmx.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Is this list dead? Here is my problem...
Date: Sat, 10 Feb 2007 01:16:53 +0100	[thread overview]
Message-ID: <20070210001653.GE18643@elmicha> (raw)
In-Reply-To: <45CA47A8.5000109@gmail.com>

Xamindar wrote:

> John H. wrote:
> > Yes, it looks as though you do.  Can you do a regular rfcomm connect?
> > What if you use rfcomm1?
> >   
> What is a regular rfcomm connect?  On the console it just gives me errors.
> 
> white-rabbit xamindar # rfcomm
> rfcomm1: 00:12:56:5A:92:59 channel 8 clean
> white-rabbit xamindar # rfcomm connect 1
> Can't create RFCOMM TTY: Address already in use
> white-rabbit xamindar #

You don't want to use "rfcomm connect". You already bound channel 8 on
your phone to /dev/rfcomm1 (probably in rfcomm.conf). That means that
rfcommd is waiting for a program that uses /dev/rfcomm1 like a serial
device.

Just use /dev/rfcomm1 with minicom and try sending some "AT" commands to
your phone, like "ATI", "ATI1" and so on.

In case you're not familiar with minicom: start "minicom -s rfcomm1" and
change the "Serial port setup" -> "Serial Device" to /dev/rfcomm1.
"Save setup as rfcomm1" and "exit from Minicom".

Now start "minicom rfcomm1". If your phone is too slow answering
bluetooth connection and minicom says "cannot open /dev/rfcomm1", just
try it again and again a few times.

If that works, use wvdial, kppp, gkdial or networkmanager to connect
using /dev/rfcomm1 (instead of /dev/modem, /dev/ttyS0).

Regards...
		Michael

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2007-02-10  0:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 17:00 [Bluez-users] Is this list dead? Xamindar
2007-02-07 17:26 ` John H.
2007-02-07 17:27 ` robert
2007-02-07 18:35   ` Marco Pracucci
2007-02-07 19:16     ` [Bluez-users] Is this list dead? Here is my problem Xamindar
2007-02-07 19:27       ` John H.
2007-02-07 19:35         ` Xamindar
2007-02-07 20:06           ` John H.
2007-02-07 21:42             ` Xamindar
2007-02-08  3:50               ` John H.
2007-02-08  4:10                 ` Mahesh T. Pai
2007-02-08  4:18                 ` Xamindar
2007-02-08  5:15                   ` John H.
2007-02-08  6:13                     ` Xamindar
2007-02-08  6:16                       ` John H.
2007-02-08  8:53                         ` Xamindar
2007-02-08 19:09                           ` John H.
2007-02-08 20:03               ` Anssi Saari
2007-02-09 19:59                 ` Xamindar
2007-02-10  0:16               ` Michael Mauch [this message]
2007-02-10 23:02                 ` Xamindar
2007-02-10 23:32                 ` Xamindar
2007-02-07 19:36         ` Xamindar

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=20070210001653.GE18643@elmicha \
    --to=michael.mauch@gmx.de \
    --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