> Maybe it wouldn't be a bad idea to keep track of which operations may > fail due to SIM being busy, and perform automatic retry later if we > get that specific error, something like that.
If the information can be updated later and it's not needed soon, it's a good idea. On Fri, 17 Mar 2017 at 12:00 Aleksander Morgado <aleksan...@aleksander.es> wrote: > On Fri, Mar 17, 2017 at 11:39 AM, Carlo Lobrano <c.lobr...@gmail.com> > wrote: > > Well, before "#QSS: 3" you can expect some errors accessing the SIM, but > > it's not forbidden, and in fact we got some errors sometimes, like "SIM > > Busy" > > That was exactly what I wanted to avoid with my patch, because > ModemManager does a lot of reading just after SIM-PIN unlock, and if > the operations fail they're not retried anymore. But waiting up to 35s > is way too much I'd say... > > Maybe it wouldn't be a bad idea to keep track of which operations may > fail due to SIM being busy, and perform automatic retry later if we > get that specific error, something like that. > > -- > Aleksander > https://aleksander.es >
_______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel