07-13-2022, 02:22 PM
(07-12-2022, 11:40 PM)jyoung Wrote: I installed ModemManager, and I tried the AT commands anyway without putting ModemManager in debug mode. It was able to detect a large number of queued messages, and purge them using the instructions on that thread. I have since received some texts. Maybe the issue with this method only working in debug mode has been solved?
However, there's a button in ModemManager to 'activate' the modem which I seem to need to click/press every time I restart the phone, otherwise texts don't come through. That seems weird, and certainly inconvenient.
Do I actually need ModemManger to use the AT commands with mmcli?
If you're running Mobian, ModemManager is already installed and running as a service. mmcli is part of that package and is a way to interact with ModemManager (mm) via the "command line" (cli).
It sounds like maybe you installed ModemManagerGUI. It crashes any time I've tried to use it so I can't say anything useful about it. It is not a required component. I don't know if it's just doing the same thing as "mmcli -m any --messaging-delete-sms=?" or if it truly removing stuck messages from the modem like the AT command will. Did my 4 step procedure work?
The recent-ish MM change to require debug mode for processing AT commands via mmcli was intentional, to close a security hole, so I doubt we'll see any change there.