> On 14 April 2017 at 23:15 Aleksander Morgado <aleksan...@aleksander.es> wrote: > > On Fri, Apr 14, 2017 at 4:57 PM, Colin Helliwell > > <colin.helliw...@ln-systems.com> wrote: > > > Might have hung this off the wrong thread, but it's along the same lines. > > I've just noticed that whilst the mmcli status now decodes the operator, > > the --sim status doesn't: > > > > # mmcli -m 0 > > ... > > 3GPP | imei: '358606050452806' > > | enabled locks: 'none' > > | operator id: '23415' > > | operator name: 'vodafone UK' > > | subscription: 'unknown' > > > > | registration: 'home' > > > > ------------------------- > > ... > > > > # mmcli -m 0 --sim=0 > > > > SIM '/org/freedesktop/ModemManager1/SIM/0' > > > > ------------------------- > > Properties | imsi : '234159108784146' > > | id : '89441000301658713096' > > | operator id : '23415' > > | operator name : 'unknown' > > Could you gather debug logs so that we can see whether this is due to > the string being wrongly decoded or just not provided by the SIM? >
Yep, it was something I spotted late on yesterday and fired in in case it was a quicky. At first I thought they both would have been coming from the same source command/response, though when I looked at the code quickly it was seeming perhaps not (which your comment also suggests). - I'll try to dig into it further today. _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
