Bug 93398 - Operator not updated in mmcli output after --3gpp-register-in-operator call
Summary: Operator not updated in mmcli output after --3gpp-register-in-operator call
Status: RESOLVED MOVED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: mmcli (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Aleksander Morgado
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-16 09:39 UTC by Tore Anderson
Modified: 2018-06-10 09:04 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
MM debug log (64.20 KB, text/plain)
2015-12-16 09:39 UTC, Tore Anderson
Details
Patch. (5.63 KB, patch)
2015-12-21 17:10 UTC, Aleksander Morgado
Details | Splinter Review

Description Tore Anderson 2015-12-16 09:39:23 UTC
Created attachment 120538 [details]
MM debug log

After explicitly changing the operator with mmcli --3gpp-register-in-operator, the output from mmcli doesn't change and keeps showing the old operator. Debug log attached.

What was done after starting MM, was the following:

Verifying that MM's initial idea of the selected operator is correct (at approx 10:31:53):

           |    operator id: '22601'
           |  operator name: 'RO Vodafone RO'
AT+COPS?
+COPS: 1,1,"VF-RO",2 

...it is.

Then I'm changing to Orange:

$ date; mmcli -m 0 --3gpp-register-in-operator=22610
on. 16. des. 10:32:21 +0100 2015
successfully registered the modem

At 10:32:46 mmcli still shows the modem connected to Vodafone:

           |    operator id: '22601'
           |  operator name: 'RO Vodafone RO'

...while the modem itself has figured out it's on Orange:

AT+COPS?
+COPS: 1,1,"ORANGE",0
Comment 1 Aleksander Morgado 2015-12-21 17:10:23 UTC
Created attachment 120626 [details] [review]
Patch.

Any chance you could test the attached patch?
Comment 2 Tore Anderson 2015-12-21 21:31:00 UTC
(In reply to Aleksander Morgado from comment #1)
> Any chance you could test the attached patch?

I'm sorry, but not any time soon - the above message reached me just as I landed in my home country, where I only have access to a single PLMN. So I can't roam freely between them anymore. I might go abroad again in March though, if so I'll test it then.

Tore
Comment 3 Christopher 2017-01-14 16:42:30 UTC
Hi,

I'm having the same problem as described here. I confirmed that the modem is not changing the operator with an external GSM tester / spectrum analyser. The operator change works some times if you wait long after disconnecting the modem and send the change command multiple times.

I would like to try the patch but have absolutely no idea how to apply it and build the software. Can anyone point me to a good step-by-step guide?

Thanks

Christopher
Comment 4 GitLab Migration User 2018-06-10 09:04:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/48.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.