Hi jupiter,
On Fri, Aug 2, 2019 at 12:46 PM JH wrote:
>
> Hi Giacinto, thanks for your response.
>
> On 8/2/19, Giacinto Cifelli wrote:
> > Hi jupiter,
> > most likely the network dropped the context without signaling.
> > What kind of modem is it? And would you know also the chipset?
>
> It is
Hi Denis,
Den fre 2 aug. 2019 kl 13:39 skrev Denis Kenzior :
> Hi Richard,
>
> > > + gprs->netreg_status = -1;
> > > gprs->used_pids = l_uintset_new(MAX_CONTEXTS);
> > >
> >
> > Wouldn't changes to gprs.c be sufficient, without touching netreg.c?
> >
> >
> > No
Hi Denis,
Den fre 2 aug. 2019 kl 13:04 skrev Denis Kenzior :
> Hi Richard,
>
> On 8/1/19 6:48 AM, richard.rojf...@gmail.com wrote:
> > From: Richard Röjfors
> >
> > Previously the valid "unknown" registration status was set
> > during startup, but its a bit problematic for gprs.
> > There might
Hi Richard,
> + gprs->netreg_status = -1;
> gprs->used_pids = l_uintset_new(MAX_CONTEXTS);
>
Wouldn't changes to gprs.c be sufficient, without touching netreg.c?
No unfortunately not. gprs reads the netreg status when it attaches to
the atom. Which would be
Hi Giacinto, thanks for your response.
On 8/2/19, Giacinto Cifelli wrote:
> Hi jupiter,
> most likely the network dropped the context without signaling.
> What kind of modem is it? And would you know also the chipset?
It is uBlox SARA-R4 chipset, did you mean it could be caused by weak
LTE
Hi Richard,
On 8/1/19 6:48 AM, richard.rojf...@gmail.com wrote:
From: Richard Röjfors
Previously the valid "unknown" registration status was set
during startup, but its a bit problematic for gprs.
There might be cases where a LTE context is activated
before netreg is finished updating its