From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: check if lock is locked after code input attempt
Date: Tue, 25 Jan 2011 14:09:25 -0600 [thread overview]
Message-ID: <4D3F2DF5.7060408@gmail.com> (raw)
In-Reply-To: <1295969667.21031.209.camel@jussi-desktop>
[-- Attachment #1: Type: text/plain, Size: 2703 bytes --]
Hi Jussi,
On 01/25/2011 09:34 AM, Jussi Kangas wrote:
>
> Hi, Denis.
>
>> So I'm mostly happy with this approach except that ofono_modem_reset is
>> too big of a hammer to use here. We need something that drops us back
>> to pre-sim state without having to re-power on the device (which is what
>> reset does).
>>
>> Can you try using sim_inserted / sim_removed or maybe even be smarter
>> and do 90% of what sim removal does but without affecting information
>> which is already read. So things like EFiccid, EFpl/EFlp, EFecc, etc.
>>
>> Regards,
>> -Denis
>
> Dropping back to pre_sim is easy if I just call modem_change_state
> directly and not through ofono_modem_reset. Problem with that approach
> is how to come back to online state after PUK has been given without
> effort from client. Calling of ofono_modem_set_powered from
> ofono_modem_reset enables the situation where Ofono comes back online by
> itself after unblocking the pin.
>
> Original solution made by Marit did pretty much what u sound to be
> looking for now. In original solution ofono get's network "denied" state
> but all the APIs stay up since modem does not go to PRE_SIM state. But
> if client goes and tries to retrieve something from network or sim it
> get's error. And when PUK was given system went back online nicely and
> without any extra pushing from client side.
>
> So why PRE_SIM state? I suppose you are worried that user goes under
> different cell or network during denied state and ofono does not read
> all changed information? Or ofono client reads some cached information
> totally unaware that it's not online anymore? I haven't gone walking
> around with this thing to see how well it get's the new info when it
> returns from denied state to online in different network or cell so
> there might something.
My main concern here is that we do not expose functionality that is
actually not available. That confuses the applications. It might also
be that your SIM PUK state is semi-permanent (e.g. you don't know the
PUK, and being on hold with your operator makes you shudder)
So we should simply remove all the atoms that are not relevant and
'forget' all the information that is not available if the SIM PIN is not
known.
>
> Playing with sim inserted sim removed states is plain wrong to me: What
> we have here has nothing to do with sim's presence. I have to
> investigate the sim remove functionality more before I can say for sure
> if there is something that could be reused.
I agree that sim_inserted is not quite the right approach. Re-using
parts of it would definitely be the right direction.
Regards,
-Denis
prev parent reply other threads:[~2011-01-25 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 11:34 [PATCH] sim: check if lock is locked after code input attempt Jussi Kangas
2011-01-24 22:32 ` Denis Kenzior
2011-01-25 15:34 ` Jussi Kangas
2011-01-25 20:09 ` 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=4D3F2DF5.7060408@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.