MC7710 "forgetting" RAT

Aleksander Morgado aleksander at
Tue Feb 4 00:41:10 PST 2014

On Tue, Feb 4, 2014 at 9:06 AM, Martin Anderseck
<Martin.Anderseck at> wrote:
> Hi Alexander,
> Thank you (once more) for your quick response.
> modemmanager-devel-bounces at wrote on 03.02.2014
> 19:29:20:
>> ModemManager doesn't automatically set either bands or allowed modes
>> (e.g. 2G/3G/4G preference). Those changes are only done if the user
>> requests them (e.g. through --set-allowed-modes or --set-current-bands
>> in mmcli).
> Okay, but usually the setting should remain in the modem until I change it
> via mmcli or AT commands, I think.
>> When using mmcli to do those changes, and if the modem is
>> handled with QMI, ModemManager will use QMI itself to perform those
>> changes (e.g. no AT!SELRAT command).
> Always nice to have a QMI alternative :-)
>> If you can gather debug logs of ModemManager when the issue happens we
>> could try to know what could be really happening.
> I have gathered a log and attached it to this mail. As you say that
> ModemManager doesn't do anything related to this automatically unless it
> is asked to I guess it is a firmware issue and the modem already comes up
> with this broken setting.

Weird, it keeps saying "registration_state =
'not-registered-searching'". Can you run "mmcli -m 0 --3gpp-scan"?

More information about the ModemManager-devel mailing list