From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Problem with SIM lock states not showing correctly in Ofono API.
Date: Mon, 21 Feb 2011 09:21:59 -0600 [thread overview]
Message-ID: <4D628317.4010909@gmail.com> (raw)
In-Reply-To: <1298281563.8797.20.camel@jussi-desktop>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Hi Jussi,
On 02/21/2011 03:46 AM, Jussi Kangas wrote:
> Hi,
>
> On Fri, 2011-02-18 at 19:29 +0200, Denis Kenzior wrote:
>
>> I have pushed experimental patch
>> e8553f53376a33504dd18c4d7bb6d6f309973e0a to take care of this. Let me
>> know if this works for you.
>>
>> Regards,
>> -Denis
>
> It seems to be showing the states correctly except in case when you make
> PIN2 blocked using call meter API. If PIN2 goes blocked when using
> callmeter nothing is shown in API. (My patch did not do that either.
> Plan was to fix it in separate patch)
>
Please do. Most modems do not support PIN2 entry via CPIN, and
implement this using a vendor extension. PIN2 / PUK2 support seems to
be a rather recent addition to the specs.
> Another issue is that your patch brings the API:s down when PIN2 goes
> blocked. ( using ChangePin ) That is not correct. Blocked PIN2 does not
> force phone to drop from network and it does prevent the usage of SIM.
>
If your modem reports the PIN2 in CPIN, then yes that is a bug.
> There seems to be also some problem when API shows PUK2 required and PIN
> and PIN2 locked. Reset-pin opens the PUK2 but API does not get the
> response it's looking for and oFono needs to be booted before states are
> showed correctly again. I suspect that's a separate issue however and
> not caused by this patch.
>
I'm having trouble visualizing this one. Can you provide an AT debug
log to illustrate?
Regards,
-Denis
prev parent reply other threads:[~2011-02-21 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 7:56 Problem with SIM lock states not showing correctly in Ofono API Jussi Kangas
2011-02-18 17:29 ` Denis Kenzior
2011-02-21 9:46 ` Jussi Kangas
2011-02-21 15:21 ` Denis Kenzior [this message]
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=4D628317.4010909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox