Re: Re: SIM hot swap with SIM locked

On Mon, May 8, 2017 at 10:33 AM, Carlo Lobrano wrote: > any update on this front? Let me know if you need any help for this Not yet, but not forgotten. I've been adding this task to my weekly TODO task since at least a month, hope to have some time to check it soon... --

Re: Re: SIM hot swap with SIM locked

​ ​​ > Hi Aleksander, > > You'll be able to reproduce it with the two patches attached to this > email. The first is basically the one you proposed for tracing #QSS: 3, > while the latter is a work in progress to fix the problem of sim locked > with some logic to manage QSS transitions and some

Re: SIM hot swap with SIM locked

On Fri, Mar 17, 2017 at 4:55 PM, Carlo Lobrano wrote: > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): --> > 'AT+GCAP' > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '' > mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '+GCAP: >

Re: SIM hot swap with SIM locked

On Fri, Mar 17, 2017 at 2:16 PM, Carlo Lobrano wrote: > Short update that might highlight better the problem. When the Modem is > re-probed after SIM is removed, the "parse_caps_gcap" receives NULL strings, > even if we can see the reply on the logs > > mar 17 14:08:40 D2040

Re: SIM hot swap with SIM locked

Sorry, I made a mistake copying the log in the previous email mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): --> 'AT+GCAP' mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '' mar 17 16:45:15 D2040 ModemManager[3946]: (ttyACM0): <-- '+GCAP: +CGSM,+DS,+FCLASS,+MS,+ESOK' mar 17

Re: SIM hot swap with SIM locked

Short update that might highlight better the problem. When the Modem is re-probed after SIM is removed, the "parse_caps_gcap" receives NULL strings, even if we can see the reply on the logs mar 17 14:08:40 D2040 ModemManager[7410]: (ttyACM0): --> 'AT+GCAP' mar 17 14:08:40 D2040