a bug?

Aleksander Morgado aleksander at aleksander.es
Wed Apr 29 23:50:57 PDT 2015

On Thu, Apr 30, 2015 at 8:40 AM,  <Jean-Pierre.Eckmann at unige.ch> wrote:
> Thanks. The situation here is that there is only one modem, but of course
> wifi etc...

The index number should only apply to modems. So this likely means
that sometimes you end up getting a modem without SIM correctly
detected; which is weird. Which modem device is this?

> of course I can use traial and error to find the true number of teh modem

No the way to go is:
  * List modems to get modem index number.
  * Retrieve modem info.
  * Retrieve sim index number from the modem info.

Are you developing an application using ModemManager as backend? If
so, I'd suggest to use libmm-glib, not mmcli calls.

> I noted thet when the environment asks for the sim code through at popup
> window it does seem to know the right number. Do they do another mmcli
> call in the background or do they do "trial and error"?

There's no mmcli involved there; it all goes through libmm-glib.
Basically, the app will monitor available modems and will synchronize
property values as well in the Modem interface; and among those
properties you'll find the SIM object path (including the SIM index).


More information about the ModemManager-devel mailing list