[ILUG] Linux compatible mobile phone

[Martin List-Petersen]

On Sat, 2004-12-04 at 17:14, Timothy Murphy wrote:
> On Saturday 04 December 2004 15:33, Martin List-Petersen wrote:
> 
> > > You also said, if I understood you correctly,
> > > that you could communicate with the phone with Bluetooth
> > > through /dev/rfcomm0 .
> > > I know that is supposed to be possible,
> > > but I've never been able to do it with minicom.
> > > What program do you use for this purpose?
> > > If minicom, what initial string do you use?
> >
> > minicom, simply ATZ will do, or any customer initstring that you wish.
> 
> OK, I just tried minicom, 
> after setting minicom's serial port to /dev/rfcomm0 .
> This is what I get.
> I'm more than willing to believe I've done something stupid ...
> But it shows that for me at least minicom/AT is far from simple to use.
> ==========================================
> Script started on Sat 04 Dec 2004 17:02:13 GMT
> [tim at william ~]$ sudo service bluetooth restart
> Stopping Bluetooth services: ...
> Starting Bluetooth services: ...
> [tim at william ~]$ hcitool scan
> Scanning ...
>  00:02:EE:10:A5:BE gayleard
> [tim at william ~]$ ls -ls /dev/rfcomm0
> ls: /dev/rfcomm0: No such file or directory
> [tim at william ~]$ sudo rfcomm bind 0 $PHONE 1
> [tim at william ~]$ ls -ls /dev/rfcomm0
> 0 crw-------  1 tim root 216, 0 Dec  4 17:04 /dev/rfcomm
> [tim at william ~]$ minicom
> minicom: cannot open /dev/rfcomm0: No such file or directory
> [tim at william ~]$ sudo !!
> sudo minicom
> minicom: cannot open /dev/rfcomm0: Host is down
> [tim at william ~]$ ls -ls /dev/rfcomm0
> 0 crw-------  1 tim root 216, 0 Dec  4 17:04 /dev/rfcomm0
> [tim at william ~]$ exit
> exit

You need to set your rfcomm interface up in /etc/bluetooth/rfcomm.conf
(Debian, might be different if you are on another distribution).

Something like 

rfcomm0 {
  bind yes;
  device 00:11:22:33:44:55;
  channel 1;
}

The channels is dependant on, where your phone provides the rfcomm
serial interface. "sdptool browse 00:11:22:33:44:55" will list all
profiles that your phone has, where 00:11:22:33:44:55 is the bdaddr of
your phone.

"/dev/rfcomm0: No such file or directory" tells me, that you haven't
done that setup yet.

> You need bluettooh, obviously.
> But you don't need to know anything about rfcomm.
> ==========================================
> Script started on Sat 04 Dec 2004 17:12:05 GMT
> [tim at william ~]$ sudo service bluetooth restart
> ...
> [tim at william ~]$ gnokii --identify
> GNOKII Version 0.6.1
> IMEI         : 350841200802729
> Manufacturer : Nokia
> Model        : NPE-4
> Revision     : V 04.20
> [tim at william ~]$ exit
> exit
> Script done on Sat 04 Dec 2004 17:12:40 GMT
> ==========================================

gnokii's bluetooth support might have gotten better, since i last toyed
around with gnokii/bluetooth, so it is just good, if it doesn't need the
rfcomm interface anymore.

I've moved away from Nokia phones, because they are too expensive and
buggy in comparison what you get from other vendors for 2/3 of the
money, so the last BT phone i had was a 6310i and that's nearly 2 years
ago. Also Nokia tends to implement only half or a cripled bluetooth
featureset, like the 7650, where you can't use a headset or handsfree
installation.
 
Slán leat,
Martin List-Petersen
Dublin, Eire 
(contact info on --> http://www.marlow.dk/)