Re: Nokia 6126 with Ubuntu 6.06 LTS

[Hal Eisen]

Dimitris,

Thanks for the quick response.  I've downloaded, compiled and installed
the 0.6.14 version of gnokii, and updated my rfcomm_channel setting to
15 from inspecting the results of "sdptool browse" and locating the
Nokia PC Suite entry.  Now, when I try to run "gnokii --identify" I get:

        GNOKII Version 0.6.14
        LOG: debug mask is 0x1
        LOG: xdebug mask is 0x1
        phone instance config:
        model: series40
        port_device: 00:11:22:33:44:55
        connection_type: 5
        init_length: 0
        serial_baudrate: 19200
        serial_write_usleep: -1
        hardware_handshake: 0
        require_dcd: 0
        smsc_timeout: 100
        connect_script:
        disconnect_script:
        rfcomm_cn: 15
        sm_retry: off
        Connecting
        Serial device: opening device 00:11:22:33:44:55
        Couldn't open PHONET device: Success
        Error in link initialisation: 1
        Telephone interface init failed: Command failed.
        Quitting.
        Command failed.
        Serial device: closing device

Any ideas?

Hal

On Sun, 2006-10-15 at 10:59 +0300, Dimitris Mandalidis wrote:
> On Sun, Oct 15, 2006 at 12:56:00AM -0700, Hal Eisen wrote:
> 
> > I just received an unlocked Nokia 6126.  I've been trying to connect to
> > it using Gnokii, but without any success.  I can pair with the phone
> > using hcitool, so I know that my BlueZ kernel modules are working, and
> > that my USB bluetooth dongle (D-Link DBT-120) are working.
> > 
> > My .gnokiirc contains:
> > 
> >         [global]
> >         port = 00:11:22:33:44:55
> >         model = series40
> >         connection = bluetooth
> >         use_locking = no
> >         rfcomm_channel = 14
> 
> Try $ sdptool browse 00:11:22:33:44:55 to check which bluetooth channel
> corresponds to 'Nokia PC Suite' (mine is 15 with Nokia 6125).
> 
> >         Sorry, phone has not yet been converted to new style.
> >         Phone.Functions == NULL!
> 
> Update to Gnokii 0.6.14, it's on the FAQs you haven't carefully checked ;)
> 
> D.
>