Re: understanding/troubleshooting gnokii

[Roberto Verzola]

Thanks for the suggestions, Raphael. We train rice farmers on a
new method called system of rice intensification (SRI). There's lots of
materials about it on the Web.

My config files (one per phone) worked very well for a year so I don't
think they are the problem. But I'll turn debug on, as you suggested.

Here's the main part the config for one phone. Other phones simply have
a different port id.

[global]
port = 18:86:ac:60:5e:98
model = series40
initlength = default
connection = bluetooth
use_locking = yes
serial_baudrate = 19200
smsc_timeout = 10

I'll also try the rest of your suggestions and report back. Thanks and
greetings,

Roberto


On Wed, 10 Jun 2015 23:26:05 -0300
Raphaël <address@hidden> wrote:

> On Thu, Jun 11, 2015 at 09:26:52AM +0800, Roberto Verzola wrote:
> > Specifically, I'd like to understand what other software must work,
> > aside from gnokii.
> 
> 1) look at the debug output adding such a section to
> ~/.config/gnokii/config
> > [logging]
> >   debug = on
> 
> 
> 2) The "port = " stanza you specified in the configuration file
> clearly refers either to a device in /dev/ either to a bluetooth
> address. In the first case kernels modules come into play.
> In the second case it's about bluez (hcitool / hciconfig).
> 
> Ensure the bluez daemons runs.
> Then I'd advise to start with a simple:
> $ l2ping [bt:mac:add:re:ss]
> Then:
> $ sdptool browse [bt:mac:add:re:ss]
> If both succeeds, then run gnokii in debug mode and look closely at
> the output.
> 
> You may want to ensure that the configuration section is correct and
> that you specified it using the --phone option.
> 
> Later may also check that you don't have issue with device association
> (like pin entering on phone side).
> 
> Hope this help.
> 
> 
> Out of curiosity what are these farmers producing?
> 
> _______________________________________________
> gnokii-users mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/gnokii-users
>