From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Ofono - Quering PIN authentication state failed
Date: Tue, 25 May 2010 09:36:44 -0500 [thread overview]
Message-ID: <201005250936.45180.denkenz@gmail.com> (raw)
In-Reply-To: <AANLkTinqHj40b3H0Zjg2ecS_3Ttzb0fqz-2N1Q1KoP-j@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
Hi Naresh,
> Hi All,
>
> I am new to Ofono development but am very interested in checking it out and
> see if I can contribute with something. I have pulled the ofono source and
> am able to build the daemon. I have also been able to connect to the
> AT-Modem interface on /generic (as defined in the modem.conf) file.
It might help to tell us what modem you're using.
>
> Below is the sequence of prints that I get on the daemon terminal after I
> execute enable-modem in another terminal:
>
> sudo ./src/ofonod -n -d 'plugins/*'
> ofonod[8592]: oFono version 0.20
> ofonod[8592]: plugins/atgen.c:atgen_enable() 0x93e9418
> ofonod[8592]: plugins/atgen.c:atgen_pre_sim() 0x93e9418
> ofonod[8592]: Querying PIN authentication state failed
> ofonod[8592]: Querying PIN authentication state failed
Also, please setenv / export OFONO_AT_DEBUG=1 so that we can see the AT chat
log.
> The problem that I have is that I can't see any more interfaces in either
> the /generic or / path. The only interfaces it shows on / is
> org.ofon.Manager. And on /generic it shows org.ofono.Modem and
> org.ofono.SimManager. I saw the SimManager methods and since there is no
> PIN set, I should be able to see further interfaces like VoiceCallManager
> and SmsManager. But I am not able to see that.
It might be that voicecall atom fails its initialization as well, the AT chat
log should help.
Regards,
-Denis
next prev parent reply other threads:[~2010-05-25 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 14:11 Ofono - Quering PIN authentication state failed Naresh Mehta
2010-05-25 14:36 ` Denis Kenzior [this message]
2010-05-26 10:05 ` Naresh Mehta
2010-05-26 16:56 ` Denis Kenzior
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=201005250936.45180.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.