Hey > > Please note that the automatic registration you're seeing (+COPS=0) is > > being started because you likely run a Simple.Connect() while the > > modem was disabled (as opposed to running a Modem.Enable() first and > > then a Simple.Connect()). Not saying that running the Simple.Connect() > > while disabled is wrong, but I think it's important to note that MM > > won't ever run +COPS=0 on its own. Regarding the issue itself, ideally > > if the modem is already registered automatically in the home network, > > running +COPS=0 could just be a no-op; if the modem is reporting > > +CEREG: 0 after the +COPS=0, I think we could try to improve the logic > > to avoid having run the +COPS=0 in the first place, either by applying > > those delayed 3GPP registration updates from the previous questions, > > or even running an explicit registration refresh before triggering the > > automatic registration in the Simple.Connect() logic. > > > > I compiled a suggested fix for this here: > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/917 > > Let me know what you think in the merge request discussions :) >
Nice, thanks! Will try to review it in the next following weeks. I need to fix some things in the enabling/disabling sequence, so it may be a good time to include both things together. -- Aleksander
