<div dir="ltr">Hi Aleksander, hoping to ask another favor on this same thread. You helped me fix profile [1] which worked perfectly (thanks again), but the device recently lost connection and tried to re-establish after reset where it seems to be trying to connect to profile [4] and recycling through the same bearer increase loop. I say this because in mmcli -m 0, the access tech: umts which looks like it was my profile [4], not profile [1]. Is there a way to force it to connect to a specific profile at boot? If not, how do we manually force to connect to the correct profile? Logs below.<div><br><div>Thanks!<br><div><br></div><div>=============================================================<br> Welcome to balenaOS<br>=============================================================<br>root@325da06:~# mmcli -m 0<br> -----------------------------------<br> General | dbus path: /org/freedesktop/ModemManager1/Modem/0<br> | device id: [REDACTED]<br> -----------------------------------<br> Hardware | manufacturer: QUALCOMM INCORPORATED<br> | model: QUECTEL Mobile Broadband Module<br> | firmware revision: EG25GGBR07A08M2G<br> | carrier config: Commercial-TMO_VoLTE<br> | carrier config revision: 05010505<br> | h/w revision: 10000<br> | supported: gsm-umts, lte<br> | current: gsm-umts, lte<br> | equipment id: [REDACTED]<br> -----------------------------------<br> System | device: /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2<br> | drivers: option1, qmi_wwan<br> | plugin: quectel<br> | primary port: cdc-wdm0<br> | ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB2 (at), wwan0 (net), <br> | ttyUSB1 (gps), ttyUSB3 (at)<br> -----------------------------------<br> Numbers | own: 15[REDACTED]18<br> -----------------------------------<br> Status | lock: sim-pin2<br> | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (10), sim-puk2 (10)<br> | state: connecting<br> | power state: on<br> | access tech: umts<br> | signal quality: 49% (recent)<br> -----------------------------------<br> Modes | supported: allowed: 2g; preferred: none<br> | allowed: 3g; preferred: none<br> | allowed: 4g; preferred: none<br> | allowed: 2g, 3g; preferred: 3g<br> | allowed: 2g, 3g; preferred: 2g<br> | allowed: 2g, 4g; preferred: 4g<br> | allowed: 2g, 4g; preferred: 2g<br> | allowed: 3g, 4g; preferred: 4g<br> | allowed: 3g, 4g; preferred: 3g<br> | allowed: 2g, 3g, 4g; preferred: 4g<br> | allowed: 2g, 3g, 4g; preferred: 3g<br> | allowed: 2g, 3g, 4g; preferred: 2g<br> | current: allowed: 2g, 3g, 4g; preferred: 4g<br> -----------------------------------<br> Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5, <br> | utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, <br> | eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19, <br> | eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39, <br> | eutran-40, eutran-41, utran-19<br> | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5, <br> | utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, <br> | eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19, <br> | eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39, <br> | eutran-40, eutran-41, utran-19<br> -----------------------------------<br> IP | supported: ipv4, ipv6, ipv4v6<br> -----------------------------------<br> 3GPP | imei: [REDACTED]<br> | operator id: 310260<br> | operator name: T-Mobile<br> | registration: home<br> -----------------------------------<br> 3GPP EPS | ue mode of operation: csps-1<br> -----------------------------------<br> SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0<br> -----------------------------------<br> Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/3<br></div><div><br></div><div>root@325da06:~# journalctl -u ModemManager<br></div><div>May 26 01:59:00 325da06 ModemManager[1401]: [modem0/bearer17] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] state changed (connecting -> registered)<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0/bearer17] connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect started...<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state (4/8): wait to get fully enabled<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state (5/8): register<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state (6/8): bearer<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] simple connect state (7/8): connect<br>May 26 01:59:00 325da06 ModemManager[1401]: [modem0] state changed (registered -> connecting)<br>May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] couldn't start network: QMI protocol error (14): 'CallFailed'<br>May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] call end reason (1016): gsm-wcdma-activation-reject<br>May 26 01:59:10 325da06 ModemManager[1401]: [modem0/bearer18] verbose call end reason (6,31): [3gpp] activation-reject<br>May 26 01:59:11 325da06 ModemManager[1401]: [base-manager] couldn't check support for device '/sys/devices/platform/soc/3f300000.mmcnr/mmc_hos><br>May 26 01:59:11 325da06 ModemManager[1401]: [base-manager] couldn't check support for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/><br>May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] couldn't start network: QMI protocol error (14): 'CallFailed'<br>May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] call end reason (1016): gsm-wcdma-activation-reject<br>May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] verbose call end reason (6,31): [3gpp] activation-reject<br>May 26 01:59:22 325da06 ModemManager[1401]: [modem0/bearer18] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'<br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 18, 2021 at 8:36 AM Christopher Penney <<a href="mailto:mrpher@gmail.com">mrpher@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Makes sense. I guess I could always automate with a boot script.</div><div dir="auto">Thanks again.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 18, 2021 at 8:19 AM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey,<br> <br> On Tue, May 18, 2021 at 12:47 PM Christopher Penney <<a href="mailto:mrpher@gmail.com" target="_blank">mrpher@gmail.com</a>> wrote:<br> ><br> > Wow, it worked! Thank you VERY VERY much. Turns out the problem was exactly that; the default profile was incompatible with IoTDataWorks default APN.<br> > You really saved the day (week, months really) thanks again.<br> ><br> <br> Glad it worked!<br> <br> > I'll let the Balena team know about the default versions and the fix in case others run into the same problem.<br> ><br> > Meantime, one more favor to ask - is there a programmatic way to clear that default profile at boot rather than have to do it manually on each new device we provision?<br> ><br> <br> No, there is no such thing right now. ModemManager won't do any<br> "automatic" configuration of this kind, if there are profile changes<br> to be done, they should be requested by the user.<br> <br> -- <br> Aleksander<br> <a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a><br> </blockquote></div></div>-- <br><div dir="ltr">Sent from my phone pardon the typos</div> </blockquote></div>