All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: SAT support in oFono
Date: Thu, 27 Jan 2011 10:11:23 -0600	[thread overview]
Message-ID: <4D41992B.5020002@gmail.com> (raw)
In-Reply-To: <4D419345.9080505@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]

Hi Philippe,

> We have checked with Jeewaka what are the conditions related to the STK
> events 'User activity', 'idle screen available' and 'language selection'.
> It appears that whatever is the release, once the device is supporting a
> display and a keypad, those events are mandatory for GCF.
> 

Yes indeed that is what the spec says, but pretty much all smart phone
platforms have ignored these and still managed to pass GCF.  I wonder
how they do that?

> The event "Browser termination" is also mandatory if the terminal
> supports class c.
> 

Same with this one.  On a modern platform you use the browser all the
time for stuff unrelated to the SIM.  Do you really expect that someone
will modify Mozilla / WebKit / whatever to send these reports?

> So, it means that we need to monitor some user activity (e.g. a
> key-press, removal of key-lock) and detects when the terminal can
> display a text of normal priority (commonly when the homescreen is on
> foreground)

Think about this one in the context of Meego.  This information is
simply not available.  We're running on a linux desktop, nobody really
knows whether one application is hiding another one or whether the user
is generating events or not.

> For the language selection, we need to inform the UICC when the terminal
> changes the currently used language.
> Finally, for the "Browser termination", we need to inform when  the
> browser is terminated either by the user action or by an error.
> 
> Basically, we could think that this monitoring could be handled by the
> STK agent. But in this case, we need to introduce a method in the STK
> dbus interface to broadcast/notify events to ofono. Also we need of
> course to support the Setup Event List proactive command.
> 
> To start, I propose to introduce those events and the Setup Event List
> command in the TODO file.

Try coming up with these APIs first, if you find them turning into a
disaster area then it should give you a good indication of how likely
they are to be accepted.

Regards,
-Denis

  reply	other threads:[~2011-01-27 16:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  8:44 SAT support in oFono Lasse.Kunnasluoto
2011-01-21  9:12 ` Jeevaka.Badrappan
2011-01-21 15:36   ` Andrzej Zaborowski
2011-01-21 16:13 ` Denis Kenzior
2011-01-24  7:15   ` Lasse Kunnasluoto
2011-01-24 10:14     ` Aki Niemi
2011-01-24 10:53       ` Marcel Holtmann
2011-01-24 10:49     ` Marcel Holtmann
2011-01-24 11:17       ` Jukka Saunamaki
2011-01-24 14:43       ` Lasse Kunnasluoto
2011-01-24 15:10         ` Marcel Holtmann
2011-01-27 15:46           ` Philippe Nunes
2011-01-27 16:11             ` Denis Kenzior [this message]
2011-01-24 14:58       ` Philippe Nunes

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=4D41992B.5020002@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.