[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nokia6600 & gnokii troubles with Bluetooth.

From: BORBELY Zoltan
Subject: Re: Nokia6600 & gnokii troubles with Bluetooth.
Date: Tue, 11 Jan 2005 01:45:02 +0100
User-agent: Mutt/1.4.1i


On Fri, Dec 24, 2004 at 08:06:10PM +0100, Talksina wrote:
> I am a new Nokia6600 user; my Linux distribution is a debian sarge running
> with Kernel 2.6.9.
> I have problems, that is, gnokii --identify says Couldn't open GNBUS
> device:, the device is busy.
> Or the resource is temporarily available.
> About gnapplet I don't know if it gets different colours on the display, as
> I am blind...

There's no colours. Just a simple text screen.

> about this, why don't the developer write a tect on there, for example,
> "starting the connection... 30 seconds left...29 left..." etc etc?
> well, let me explain all steps I followed to reach this.
> To make it work, I just followed about all the steps on this howto:
> I compiled these bluetooth modules:
> <M>   L2CAP protocol support
> <M>   SCO links support
> <M>   RFCOMM protocol support
> [*]     RFCOMM TTY support
> <M>   BNEP protocol support
> [*]     Multicast filter support
> [*]     Protocol filter support
> and then installed the bluez-utils by doing apt-get install bluez-utils,
> after, of course, installing the bluetooth driver bluez and so on, and
> compiling gnokii with ./configure --with-bluetooth.
> I didn't specify a directory, because I did not know which is the exact path
> for the libraries.

That's ok.

> Then edited the /etch/bluetooth/hcid.conf and pin.
> hciconfig and hcitool scan gave me correct output, that is, the name of my
>  phone and its ID, and so on.
> Afterwards I skipped the step regarding gnubox, as I am a particular user: I
> am blind, and use a program called Talks
> ( and don't know what gnubox
> is/does, and passed out to the next step, also because I don't know german
> and do not understand quite well which are the options I must use on the
> phone.
> So, I did this:
> sdptool add --channel=3 SP
> then skipped the dund -n --listen --channel 3 --msdun noauth
> pc_IP_address crtscts 115200 ms passage, as I did not have a proper IP
> address, I was without gnubox.
> then:
> rfcomm bind 3 my-phone-ID  2
> and then, echo 0000 > /dev/rfcomm3 (0000 was the pin number) and, finally,
> my TALKS software started to say: enter pin code
> and I entered the code, that's all...
> And there is another problem now, that every reboot I must set everything
> again, as it does not recognize the phone automatically, the rfcomm3 I mean.
> The funny thing is that the phone is seen, that is, 00:60:57:DF:06:A1
> Talksina
> and it finds my PC if I search for a new remote device from the phone!
> Bye, and let me know what to do, if I missed something!

There's no need to setup dund to run gnokii unless you want to use your
phone as a modem.

> Oops...
> the gnokii configuration:
> port = /dev/rfcomm3
> rfcomm_channel = 3
> model = series60
> This: rfcomm_channel should be: 3, 2, or 14 as in documentation
> readme-symbian in docs/ directory?

here's a simple gnokiirc:

port = _bluetooth_address_of_your_phone_
rfcomm_channel = 14
model = series60
connection = bluetooth

You have to set the rfcomm_channel to the same value as you specified
in gnapplet.ini (this file is on your phone, you can use p3nfs to
access it), its value is 14 or 13.

If it still doesn't work, please enable debugging:

debug = on


reply via email to

[Prev in Thread] Current Thread [Next in Thread]