Modem Issues - Please Help!

spacemanspiffy · August 8, 2026, 6:54pm

I think my modem may have died yesterday, but would appreciate some help diagnosing/troubleshooting.
I plan to email support@puri.sm, but I figure it’s the weekend and asking here might get a quicker response before Monday.

OS: Crimson, up to date
Carrier: Mint Mobile in the northeast USA
Modem: BM818-A1

To sum it up, my phone hasn’t been able to get solid cell connection for about 24 hours now. (Except for about 2 minutes while on a drive to receive an MMS, then gone again).
It seems to have problems connecting to Mint, and instead of saying T-Mobile in the Quick Settings, the carrier keeps switching between AT&T and Verizon every few minutes. Sometimes it says the carrier “331 003” or something like that.

I was able to get through to a Mint Mobile rep on the phone, and they decided the reason it stopped working was because T-Mobile is taking down 2G towers and they said the L5 only supports 2G. I mentioned to them that their info might be a bit out of date.

Anyways, here’s what I’ve tried with the phone:

Multiple reboots and removal/re-insert of battery, as well as HKS switching and SW switch toggling.
Powering off the phone, removing the SIM, waiting a bit, reinserting, restarting.
I tried pushing in the connections on the wires on the modem. They seemed fine to begin with, however.
Changing my APN in GNOME Settings to Mint / Wholesale. It had defaulted before to I think wireless.dish.com or something similar. I’ll probably change this back.
GNOME Settings modem info lists:
- Carrier: Whatever my phone decides it wants to connect to at that moment
- Network type: lte
- Signal strength: 41% (in my basement typing this)
- Network Status: Roaming (probably due to it saying I’m on VErizon at this second)
- Manufacturer: Qualcomm
- Model: 0
- Firmware Version: MPSS.JO.2.0.2.c1.1-00032-9607_GENSS_PACK-1.351938.1 …
dmesg and journalctl have some scary stuff that makes me worry my modem is indeed a goner. Here is journalctl -f after powering the modem on from HKS off. It connected to T-Mobile first, sat for a few minutes, then switched to say AT&T around the Aug 08 14:52:32 timestamp.

Aug 08 14:50:32 voyager systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Aug 08 14:50:32 voyager systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Aug 08 14:50:32 voyager NetworkManager[542]: <info>  [1786215032.2787] manager: rfkill: WWAN now enabled by radio killswitch
Aug 08 14:50:37 voyager systemd[1]: systemd-rfkill.service: Deactivated successfully.
Aug 08 14:50:38 voyager kernel: usb 1-1.2: new high-speed USB device number 9 using xhci-hcd
Aug 08 14:50:39 voyager kernel: usb 1-1.2: New USB device found, idVendor=2020, idProduct=2060, bcdDevice= 0.00
Aug 08 14:50:39 voyager kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Aug 08 14:50:39 voyager kernel: usb 1-1.2: Product: Qualcomm CDMA Technologies MSM
Aug 08 14:50:39 voyager kernel: usb 1-1.2: Manufacturer: Qualcomm, Incorporated
Aug 08 14:50:39 voyager kernel: usb 1-1.2: Device is not authorized for usage
Aug 08 14:50:39 voyager usbguard-daemon[665]: uid=0 pid=585 result='SUCCESS' device.rule='block id 2020:2060 serial "" name "Qualcomm CDMA Technologies MSM" hash "1E5MUAqBN4Iq7aIBy9C66mfhsybxqVMgqb0Zo2g0vPw=" parent-hash "vcQCvo7og/OsiyjGJkBpBhxttJR/CC2E95j94p5kh0I=" via-port "1-1.2" with-interface { ff:ff:ff ff:ff:ff ff:ff:ff ff:fe:ff ff:ff:ff } with-connect-type "not used"' device.system_name='/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2' type='Device.Insert'
Aug 08 14:50:39 voyager kernel: option 1-1.2:1.0: GSM modem (1-port) converter detected
Aug 08 14:50:39 voyager kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
Aug 08 14:50:39 voyager kernel: option 1-1.2:1.1: GSM modem (1-port) converter detected
Aug 08 14:50:39 voyager kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
Aug 08 14:50:39 voyager kernel: option 1-1.2:1.2: GSM modem (1-port) converter detected
Aug 08 14:50:39 voyager kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
Aug 08 14:50:39 voyager kernel: option 1-1.2:1.3: GSM modem (1-port) converter detected
Aug 08 14:50:39 voyager kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
Aug 08 14:50:39 voyager kernel: qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device
Aug 08 14:50:39 voyager kernel: qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.4.auto-1.2, WWAN/QMI device, e2:c5:9d:ab:e3:53
Aug 08 14:50:39 voyager kernel: usb 1-1.2: authorized to connect
Aug 08 14:50:39 voyager usbguard-daemon[665]: uid=0 pid=585 result='SUCCESS' device.system_name='/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2' target.new='allow' device.rule='block id 2020:2060 serial "" name "Qualcomm CDMA Technologies MSM" hash "1E5MUAqBN4Iq7aIBy9C66mfhsybxqVMgqb0Zo2g0vPw=" parent-hash "vcQCvo7og/OsiyjGJkBpBhxttJR/CC2E95j94p5kh0I=" via-port "1-1.2" with-interface { ff:ff:ff ff:ff:ff ff:ff:ff ff:fe:ff ff:ff:ff } with-connect-type "not used"' target.old='block' type='Policy.Device.Update'
Aug 08 14:50:39 voyager usbguard-daemon[665]: Ignoring unknown UEvent action: sysfs_devpath=/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2 action=change
Aug 08 14:50:39 voyager mtp-probe[8157]: checking bus 1, device 9: "/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2"
Aug 08 14:50:39 voyager mtp-probe[8157]: bus: 1, device: 9 was not an MTP device
Aug 08 14:50:39 voyager mtp-probe[8159]: checking bus 1, device 9: "/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2"
Aug 08 14:50:39 voyager mtp-probe[8159]: bus: 1, device: 9 was not an MTP device
Aug 08 14:50:41 voyager ModemManager[649]: <info>  [device /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2] creating modem with plugin 'broadmobi' and '6' ports
Aug 08 14:50:41 voyager ModemManager[649]: <info>  [base-manager] modem for device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2' successfully created
Aug 08 14:50:42 voyager ModemManager[649]: <warn>  [modem5] couldn't query SIM slots: QMI protocol error (94): 'NotSupported'
Aug 08 14:50:42 voyager ModemManager[649]: <warn>  [modem5/sim5] couldn't load GID2: Couldn't read data from UIM: QMI protocol error (16): 'NotProvisioned'
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] state changed (unknown -> disabled)
Aug 08 14:50:42 voyager mmsdtng[754]: New Object with Messaging feature found, Adding...
Aug 08 14:50:42 voyager NetworkManager[542]: <info>  [1786215042.4328] manager: (cdc-wdm0): new Broadband device (/org/freedesktop/NetworkManager/Devices/12)
Aug 08 14:50:42 voyager NetworkManager[542]: <info>  [1786215042.4390] device (cdc-wdm0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 08 14:50:42 voyager NetworkManager[542]: <info>  [1786215042.4406] device (cdc-wdm0): modem state 'enabling'
Aug 08 14:50:42 voyager NetworkManager[542]: <info>  [1786215042.4456] device (cdc-wdm0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] state changed (disabled -> enabling)
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] power state updated: on
Aug 08 14:50:42 voyager gnome-calls[1157]: Failed to get 3gpp location service: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.WrongState: Cannot get location: device not yet enabled
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] state changed (enabling -> enabled)
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (unknown -> registering)
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (registering -> home)
Aug 08 14:50:42 voyager ModemManager[649]: <info>  [modem5] state changed (enabled -> registered)
Aug 08 14:50:45 voyager systemd[1]: systemd-timedated.service: Deactivated successfully.
Aug 08 14:51:07 voyager gnome-calls[1157]: Could not query call waiting status: Timeout was reached
Aug 08 14:51:31 voyager systemd[1]: pcscd.service: Deactivated successfully.
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.1649] policy: auto-activating connection 'Mint' (ae71c70d-3250-4678-b70e-c9c3aafd4892)
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.1692] device (cdc-wdm0): Activation: starting connection 'Mint' (ae71c70d-3250-4678-b70e-c9c3aafd4892)
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.1702] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect started...
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect state (6/10): register
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect state (7/10): wait to get packet service state attached
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect state (8/10): bearer
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect state (9/10): connect
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] state changed (registered -> connecting)
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17] QMI IPv4 Settings:
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17]     address: 33.220.240.182/30
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17]     gateway: 33.220.240.181
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17]     DNS #1: 10.177.0.34
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17]     DNS #2: 10.177.0.210
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17]        MTU: 1500
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17] couldn't start network: QMI protocol error (14): 'CallFailed'
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17] verbose call end reason (3,1110): [cm] (null)
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5/bearer17] reloading stats is supported by the device
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] state changed (connecting -> connected)
Aug 08 14:51:33 voyager ModemManager[649]: <info>  [modem5] simple connect state (10/10): all done
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3711] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3754] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3807] modem-broadband[cdc-wdm0]: IPv4 static configuration:
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3808] modem-broadband[cdc-wdm0]:   address 33.220.240.182/30 brd* 33.220.240.183 lft forever pref forever lifetime 8348-0[0,0] src wwan
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3809] modem-broadband[cdc-wdm0]:   gateway 33.220.240.181
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3809] modem-broadband[cdc-wdm0]:   DNS 10.177.0.34
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3809] modem-broadband[cdc-wdm0]:   DNS 10.177.0.210
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.3810] modem-broadband[cdc-wdm0]:   MTU 1500
Aug 08 14:51:33 voyager NetworkManager[542]: <warn>  [1786215093.3811] device (cdc-wdm0): retrieving IP configuration failed: modem IP method unsupported
Aug 08 14:51:33 voyager systemd-resolved[509]: wwan0: Bus client set default route setting: no
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.4274] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Aug 08 14:51:33 voyager systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.5181] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.5187] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 08 14:51:33 voyager NetworkManager[542]: <info>  [1786215093.5203] device (cdc-wdm0): Activation: successful, device activated.
Aug 08 14:51:43 voyager systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 08 14:51:57 voyager phosh[1039]: Moved 'org.gnome.Calls.desktop' to transient systemd unit
Aug 08 14:51:57 voyager systemd[697]: Started app-gnome-org.gnome.Calls-8303.scope - Application launched by phosh.
Aug 08 14:51:59 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (home -> registering)
Aug 08 14:51:59 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (registering -> home)
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (home -> unknown)
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5] network reject indication received
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   service domain: ps
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   radio interface: lte
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   reject cause: ue-identity-not-derived-by-network
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (unknown -> registering)
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (registering -> roaming)
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] state changed (connected -> disconnecting)
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] state changed (disconnecting -> registered)
Aug 08 14:52:32 voyager NetworkManager[542]: <info>  [1786215152.1153] device (cdc-wdm0): state change: activated -> failed (reason 'modem-no-carrier', sys-iface-state: 'managed')
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5/bearer17] connection #1 finished: duration 58s, tx: 0 bytes, rx: 0 bytes
Aug 08 14:52:32 voyager NetworkManager[542]: <warn>  [1786215152.1214] device (cdc-wdm0): Activation: failed for connection 'Mint'
Aug 08 14:52:32 voyager NetworkManager[542]: <info>  [1786215152.1251] device (cdc-wdm0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 08 14:52:32 voyager systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Aug 08 14:52:32 voyager NetworkManager[542]: <info>  [1786215152.2067] policy: auto-activating connection 'Mint' (ae71c70d-3250-4678-b70e-c9c3aafd4892)
Aug 08 14:52:32 voyager NetworkManager[542]: <info>  [1786215152.2086] device (cdc-wdm0): Activation: starting connection 'Mint' (ae71c70d-3250-4678-b70e-c9c3aafd4892)
Aug 08 14:52:32 voyager NetworkManager[542]: <info>  [1786215152.2089] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] simple connect started...
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] simple connect state (6/10): register
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] simple connect state (7/10): wait to get packet service state attached
Aug 08 14:52:32 voyager systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5] network reject indication received
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   service domain: cs-ps
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   radio interface: lte
Aug 08 14:52:32 voyager ModemManager[649]: <warn>  [modem5]   reject cause: roaming-in-location-area-not-allowed
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (roaming -> searching)
Aug 08 14:52:32 voyager ModemManager[649]: <info>  [modem5] state changed (registered -> searching)
Aug 08 14:52:42 voyager ModemManager[649]: <info>  [modem5] simple connect started...
Aug 08 14:52:42 voyager ModemManager[649]: <info>  [modem5] simple connect state (4/10): wait to get fully enabled
Aug 08 14:52:42 voyager ModemManager[649]: <info>  [modem5] simple connect state (5/10): wait after enabled
Aug 08 14:52:42 voyager systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 08 14:52:42 voyager ModemManager[649]: <info>  [modem5] simple connect state (6/10): register
Aug 08 14:52:59 voyager ModemManager[649]: <info>  [modem5] 3GPP registration state changed (searching -> unknown)
Aug 08 14:52:59 voyager ModemManager[649]: <info>  [modem5] state changed (searching -> enabled)

amarok · August 8, 2026, 10:19pm

Possibly a network outage:

(I think those times are in Pacific Time, since I’m accessing that site from California.)

spacemanspiffy · August 8, 2026, 11:38pm

I thought this, too, but my SOs Android phone is working just fine.

spacemanspiffy · August 9, 2026, 1:47am

I figured out a solution, huge relief.

Maybe there is some merit to what the Mint tech said about 2G getting shut down.

I tried changing the Network Mode to 4G only, and my troubles seem to be gone.

Maybe a change was made in the T-Mobile network in my area.

Good to have my modem back after a day and a half of downtime.

JR-Fi · August 9, 2026, 7:21am

Wasn’t Mint using T-mobile networks? From their web page: “As of August 3, 2026, T-Mobile’s 2G GSM network will be retired.” https://www.t-mobile.com/support/coverage/t-mobile-network-evolution

Sunsetting of most 2G networks has been a topic in these forums for years…

spacemanspiffy · August 10, 2026, 6:19pm

I think I spoke too soon.

SMS/MMS works.
Mobile data works.
Calls (incoming and outgoing) fail.

Here is what I see in the logs when trying to make an outbound call:

Aug 10 14:18:26 voyager systemd[689]: Started dbus-:1.6-org.gnome.Contacts@1.service.
Aug 10 14:18:26 voyager ModemManager[638]: <info>  [modem1/call8] user request to start call
Aug 10 14:18:26 voyager ModemManager[638]: <info>  [modem1/call8] call state changed: unknown -> dialing (outgoing-started)
Aug 10 14:18:26 voyager ModemManager[638]: <warn>  [modem1/call8] couldn't start call: Couldn't create call: QMI protocol error (13): 'NoNetworkFound'
Aug 10 14:18:26 voyager ModemManager[638]: <info>  [modem1/call8] call state changed: dialing -> terminated (unknown)
Aug 10 14:18:27 voyager gnome-calls[1220]: Error starting outgoing call MM call '/org/freedesktop/ModemManager1/Call/8': GDBus.Error:org.freedesktop.libqmi.Error.Protocol.NoNetworkFound: Couldn't create call: QMI protocol error (13): 'NoNetworkFound' (domain: g-io-error-quark [36])

I’m not sure what else to do. I tried with 3G and 2G enabled again but just got the same issues I did as before.
VoLTE is enabled per BM818 Tools.

I know there are others using Mint and T-Mobile here… anyone else having problems?

JR-Fi · August 10, 2026, 7:54pm

Check also mmcli -m any. That, 'NoNetworkFound' is pretty direct hint, though - it’s not finding a network it likes or can connect.

spacemanspiffy · August 10, 2026, 7:56pm

  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/0
           |               device id: 145716d5bb80219e4b017b59d4a420b1cfd590e2
  -----------------------------------
  Hardware |            manufacturer: QUALCOMM INCORPORATED
           |                   model: 0
           |       firmware revision: MPSS.JO.2.0.2.c1.1-00032-9607_GENNS_PACK-1.351938.1  1  [Nov 26 2020 02:00:00]
           |          carrier config: ROW_Generic_3GPP
           | carrier config revision: 05010822
           |            h/w revision: 10000
           |               supported: gsm-umts, lte
           |                 current: gsm-umts, lte
           |            equipment id: ***************
  -----------------------------------
  System   |                  device: /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
           |                 drivers: qmi_wwan, option
           |                  plugin: broadmobi
           |            primary port: cdc-wdm0
           |                   ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (at), ttyUSB2 (at), 
           |                          ttyUSB3 (at), wwan0 (net)
  -----------------------------------
  Numbers  |                     own: ***********
  -----------------------------------
  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (10), sim-puk2 (10)
           |                   state: connected
           |             power state: on
           |             access tech: lte
           |          signal quality: 41% (recent)
  -----------------------------------
  Modes    |               supported: allowed: 2g; preferred: none
           |                          allowed: 3g; preferred: none
           |                          allowed: 4g; preferred: none
           |                          allowed: 2g, 3g; preferred: 3g
           |                          allowed: 2g, 3g; preferred: 2g
           |                          allowed: 2g, 4g; preferred: 4g
           |                          allowed: 2g, 4g; preferred: 2g
           |                          allowed: 3g, 4g; preferred: 4g
           |                          allowed: 3g, 4g; preferred: 3g
           |                          allowed: 2g, 3g, 4g; preferred: 4g
           |                          allowed: 2g, 3g, 4g; preferred: 3g
           |                          allowed: 2g, 3g, 4g; preferred: 2g
           |                 current: allowed: 4g; preferred: none
  -----------------------------------
  Bands    |               supported: pcs, g850, utran-4, utran-5, utran-2, eutran-2, eutran-3, 
           |                          eutran-4, eutran-5, eutran-12, eutran-13, eutran-17, eutran-25, 
           |                          eutran-26, eutran-41, eutran-66
           |                 current: pcs, g850, utran-4, utran-5, utran-2, eutran-2, eutran-3, 
           |                          eutran-4, eutran-5, eutran-12, eutran-13, eutran-17, eutran-25, 
           |                          eutran-26, eutran-41, eutran-66
  -----------------------------------
  IP       |               supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP     |                    imei: *******************
           |           enabled locks: fixed-dialing
           |             operator id: 310260
           |           operator name: T-Mobile
           |            registration: home
           |    packet service state: attached
  -----------------------------------
  3GPP EPS |    ue mode of operation: csps-1
           |     initial bearer path: /org/freedesktop/ModemManager1/Bearer/0
           |  initial bearer ip type: ipv4v6
  -----------------------------------
  SIM      |        primary sim path: /org/freedesktop/ModemManager1/SIM/0
  -----------------------------------
  Bearer   |                   paths: /org/freedesktop/ModemManager1/Bearer/1

JR-Fi · August 10, 2026, 8:10pm

You have only 4G allowed. Any change, if you allow all (or at least 3G too)? It’s the only thing that caught my eye. If your phone previously used 2G, you may not have been aware, just how dependent it was of it for some reason.

spacemanspiffy · August 10, 2026, 9:07pm

If i try 3G, 4G (Preferred), I get issues similar to the ones in my initial post.

gondolyr · August 10, 2026, 9:13pm

A 41% signal strength/quality is not very good. I have seen the Librem 5 drop calls even on signal strength of around 65% so I would expect seeing 3 bars or higher of service to be what is needed.

Try moving elsewhere for a better signal if possible. My Librem 5 falls over more often than not when I am indoors.

spacemanspiffy · August 11, 2026, 12:22pm

Thanks, but I don’t think so. I tried while outside with 70% signal and it made no difference.

For now, I am back on Android until I can figure this out, if I can… I moved my SIM over last night since I need a phone to work.

Holy crap I am inundated with notifications about useless crap. Samsung ads, “Montly App Recommendations”, notifications that cannot go away. It’s making my eye twitch.

Also, apparently it’s forcing me to use the new Google Messenger for SMS. Does anyone know a decent third party Android SMS client I can use instead? Edit: Trying out this “Simple SMS Messenger” I found in F-Droid.

amarok · August 11, 2026, 2:23pm

Fossify Messages is popular in degoogled Android forums.

A couple of Samsungs now have custom ROMs available that enable a new experimental IMS/VoLTE. (Previously, no Samsung running a custom ROM could implement VoLTE, due to Samsung’s policy of keeping their IMS stack closed… an obvious problem if there is no 2G or 3G left to carry phone calls. So things are looking up for at least some Samsung models.)

JR-Fi · August 11, 2026, 5:51pm

Curious. Some things to consider. MM and the modem see the network, meaning that part of the way works - antenna, network etc., so mostly not hardware issue, unless you got that unexpected short too. Any modem hardware issue would need a replacement modem. If it’s a network issue (that the 2G previously "masked from you), you’d need an alternative modem or maybe you could get some results if you go to a different area and try some other network than Mint (if there is any that works [without 2G] and is available). A shorted modem that has a visible mark and some blue smoke would be the easiest to diagnose but there can be something wrong even without any visible marks. Of these two alternatives I think the timing in relation to 2G seems too much of a coincidence. From there, towards the other end of the links in the chain of technology, the third alternative to look into is the software, if/what has changed. [Edit to add: LTE/data seems to often work even if “phoneline” doesn’t (did it here too?). A workaround could be to use SIP calls via data.]

In a bigger picture: there should be a process to troubleshoot phone issues. Not just with Librem 5 but all linux phones. There are so many links in the tech stack that need to work but it’s bit much to ask that a single user could fathom them all. Yet, this is and should be logical and there should be some straight forward methods to create a flowchard to rule out stuff and point to right direction. There should be a list of commands that gather all relevant information from all the different logs and sources - an presents them in a readable way (GUI and terminal/txt). I’m pretty sure all the different linux HW/SW/OS platforms could benefit from this. Seem kinda amazing that there isn’t a community app/tool that tells user about the health of their telephone connection (from audio to calling to modem software to modem to network to ISP…) and maybe even offer some test call functions somehow.

irvinewade · August 11, 2026, 11:16pm

Why not go one step further and actually diagnose the problem? (half serious)

If you have a flowchart and access to all the information, a computer can follow the troubleshooting flowchart better than most humans.

I think there is a generic software architecture problem in most software, namely that errors get lost in the stack and lost in translation. What starts off as a clear and explicit failure at some very low level in the software stack, sooner or later, as it flows up the software stack, becomes bland and difficult to attribute to a specific cause (and, in the occasional really bad scenario, dropped completely i.e. not noticed by the software at the higher level because some status doesn’t get checked at all). (This is the advantage of the exception throw model of error handling.)

This is doubly so with a blackbox modem, as found on most phones, where the lowest levels are intentionally obscured.

carlosgonz · August 12, 2026, 1:01pm

I have Android on so many sony xperia devices and android work really nice even with google things. It feel like i control android like phosh. However android on samsung, or any other device android it feel superevil and spyer.

Sony still not released android 17, but from last sony release android 16 sony reduced custom sony code and custom android code to xperia device making android superclean to xperia.
ATM i waiting sony to release pure android 16 without sony and google code to xperia compatible device plus gnulinux 6.6 open driver. Sony claim rooted android 16 by default in this release, but i still dont know it and test, i already try to compile to testing however this source code asking for gnulinux 6.6 which is not available yet. This compilation it is more then 100GiBs making OOM Killer on 25Gibs RAMs, as some issues.

I do not know other android vendor like sony. I am a real sony fan from sony ericsson.

It may try t-mobile contract sim, as looking to support more bands.
My sony murray get 5G only with t-moble contract, however t-mobile connect(prepay) do not get 5G.

It looks the modem has IMS registered issue. Enabling VoLTE does not mean success to ims register.

Even if you got v.o.l.t.e work we still have issues to v.o.l.t.e sound profile, same to ringtone as lacking a profile too.
Even i wanted a discrete ringtone speaker on Librem5 to make real ringtone experience.

Edit: I know too that pmos is working something in this area calls but i unclear a.t.m and i fully untrust pmos.
Also i know superhero s.krzyszkowiak improved L5 sound driver, however this does not mean a discrete L5 volte profile output.

Real Ringtone has the power to quick enable MOODs for calls experience and more.