On 13/05/16 17:15, Carlo Lobrano wrote:
> Inverted steps UPDATE_LOCK_INFO_CONTEXT_STEP_RETRIES and
> UPDATE_LOCK_INFO_CONTEXT_STEP_AFTER_UNLOCK.
>
> Soon after the unlock, the SIM can be busy and
> loading unlock retries might fail.
>
> When implemented, let run "after unlock" logic before any ot
On Thu, 2016-06-30 at 16:16 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 6:16 PM, Dan Williams wrote:
> >
> > On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
> > >
> > > On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano > > m>
> > > wrote:
> > > >
> > > >
> > > > Hi, has
On Wed, Jun 1, 2016 at 6:16 PM, Dan Williams wrote:
> On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
>> On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano
>> wrote:
>> >
>> > Hi, has this change already merged?
>> Not yet; IIRC Dan suggested to merge it after releasing 1.6.0.
>
> Yeah, I
On Wed, 2016-06-01 at 16:48 +0200, Aleksander Morgado wrote:
> On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano
> wrote:
> >
> > Hi, has this change already merged?
> Not yet; IIRC Dan suggested to merge it after releasing 1.6.0.
Yeah, I did suggest that, because I thought it was quite a large
(tho
On Wed, Jun 1, 2016 at 4:34 PM, Carlo Lobrano wrote:
> Hi, has this change already merged?
Not yet; IIRC Dan suggested to merge it after releasing 1.6.0.
I'm targeting to review the QMI over MBIM integration during these
next 2 weeks, which is the only thing blocking us to release a 1.6.0.
--
Hi, has this change already merged?
On Fri, 13 May 2016 at 20:05 Aleksander Morgado
wrote:
> On Fri, May 13, 2016 at 5:15 PM, Carlo Lobrano
> wrote:
> > Inverted steps UPDATE_LOCK_INFO_CONTEXT_STEP_RETRIES and
> > UPDATE_LOCK_INFO_CONTEXT_STEP_AFTER_UNLOCK.
> >
> > Soon after the unlock, the SI
On Fri, May 13, 2016 at 5:15 PM, Carlo Lobrano wrote:
> Inverted steps UPDATE_LOCK_INFO_CONTEXT_STEP_RETRIES and
> UPDATE_LOCK_INFO_CONTEXT_STEP_AFTER_UNLOCK.
>
> Soon after the unlock, the SIM can be busy and
> loading unlock retries might fail.
>
> When implemented, let run "after unlock" logic
Inverted steps UPDATE_LOCK_INFO_CONTEXT_STEP_RETRIES and
UPDATE_LOCK_INFO_CONTEXT_STEP_AFTER_UNLOCK.
Soon after the unlock, the SIM can be busy and
loading unlock retries might fail.
When implemented, let run "after unlock" logic before any other step in
update lock info, when SIM is not locked t
