All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RfC] Retry registering packet radio to home PLMN when available.
Date: Mon, 26 Oct 2009 19:06:58 -0500	[thread overview]
Message-ID: <200910261906.58614.denkenz@gmail.com> (raw)
In-Reply-To: <1256577664-4459-1-git-send-email-andrew.zaborowski@intel.com>

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

Hi Andrew,

So I took this patch and the two earlier patches and applied them.  Thanks.

> Instead of setting DataConnectionManager.Powered to false after
> failed attempts to register to home PLMN with packet radio when
> RoamingAllowed is false, wait for the home PLMN to become available
> retrying everytime the circuit switched radio manages to register
> to home PLMN.  The downside is if the circuit switched radio is off,
> we wait indefinitely.

So I decided to simplify things even further.  Before we can attach we must be 
registered to the network (e.g. COPS issued), otherwise attach fails.  Since 
we need netreg for this anyway, we might as well always rely on netreg's 
registration status to base our attach / detach decisions on.

To me this seems to be the most sensible way to approach this.  However, this 
assumes that the modem can't be registered on netreg and roaming on gprs.

It also might break down in low-signal conditions where packet radio has 
signal but circuit-switched radio doesn't (which is interesting case where 
COPS reports an operator, CGREG shows registered, but CREG shows unregistered)

Comments?

Regards,
-Denis

  reply	other threads:[~2009-10-27  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 17:21 [RfC] Retry registering packet radio to home PLMN when available Andrzej Zaborowski
2009-10-27  0:06 ` Denis Kenzior [this message]
2009-10-28  7:30   ` Andrzej Zaborowski
2009-10-28 21:21     ` 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=200910261906.58614.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.