Re: [MM] [PATCH] iface-modem-3gpp: handle non-deferrable registration state updates

[Ben Chan <benchan chromium org>]

+Dan

On Tue, Apr 30, 2013 at 1:03 PM, Ben Chan <benchan chromium org> wrote:

Hi Aleksander / Dan,

Would a transition from 'registered' to 'idle'/'searching' considered a 'service' loss from the connection manager's perspective (e.g. the service disappears and then reappears in connection manager)?  In practice,  a +CEREG change may not necessarily mean that the service disappears. But I guess such a glitch can be smoothed out in the connection manager layer instead of the modem manager layer. I'm happy to update the logic as suggested if that's the expected behavior.

Thanks,

Ben

On Tue, Apr 30, 2013 at 5:23 AM, Aleksander Morgado <aleksander lanedo com> wrote:

Hey Ben,

Resurrecting old patch...

On 05/03/13 03:37, Ben Chan wrote:
> This patch changes MMIfaceModem3gpp to differentiate between deferrable
> and non-deferrable 3GPP registration state updates. Periodic or
> unsolicited registration state updates are deferrable, while internal
> updates, e.g. due to modem being disabled, are non-deferrable.

I think that we should *not* defer the registration state update unless
the modem was connected. This is, if the modem goes from registered to
idle or searching, that update must be published in the interface right
away. What do you think? Are you able to update the logic like that?

--
Aleksander