Ulrich Mohr (9f385e8b) at 04 Dec 12:30
Ulrich Mohr (5ed79518) at 18 Jan 11:17
Thank you for the reminder. I did the rework as proposed (quite a while ago, but retested and pushed it last week ;-) )
Thank you for the reminder. I did the rework as requested (quite a while ago, but retested and pushed it last week ;-) )
Ulrich Mohr (ce727ba6) at 09 Dec 09:52
mbimcli: Add sms functionality
Ulrich Mohr (9eb7e141) at 09 Dec 07:55
mbim-broadband-modem, qmi-shared: Fallback from qmi uim service on...
... and 278 more commits
Ulrich Mohr (ba650c06) at 09 Dec 07:48
mbim-broadband-modem, qmi-shared: Fallback from qmi uim service on...
When using qmi uim service from mbim broadband modem, a fallback from using qmi uim service to normal mbim operations is done every time a call to qmi_set_primary_sim_slot fails. But this may fall for various reasons, and a fallback only makes sense when the device does not support that call
Ulrich Mohr (a4529e73) at 26 Jul 10:45
mbim-broadband-modem, qmi-shared: Fallback from qmi uim service on...
... and 335 more commits
This adds a new group for sms functionality with three new functions:
Ulrich Mohr (8d59369a) at 25 Jul 13:37
Ulrich Mohr (8d59369a) at 25 Jul 12:44
mbimcli: Add sms functionality
Ulrich Mohr (b103d7a5) at 25 Jul 12:38
mbimcli: Add sms functionality
When mbim uses the qmi uim service to set the primary sim slot, and that call to mm_shared_qmi_set_primary_sim_slot
fails, there is an unconditional fallback to the "normal" mbim way to set the primary slot. But mm_shared_qmi_set_primary_sim_slot
returns an error for various reason, e.g. if the slot to switch to is already active.
Instead, the mbim implementation should only do a fallback when the qmi call is unsupported. I attach a proposal for a patch 0001-mbim-broadband-modem-qmi-shared-Fallback-from-qmi-ui.patch. If this patch is ok, I will do a merge request for it.
Seen with Telit LE910C1-EU, ModemManager 1.19.0 with the patch from this merge request: !828
I send a SMS and store it after sending using mmcli:
mmcli -m any --messaging-create-sms="text='Hello world',number='+49XXXXXXXX'"
Successfully created new SMS: /org/freedesktop/ModemManager1/SMS/1
root@...:~ mmcli -s 1 --send
successfully sent the SMS
root@...:~ mmcli -s 1 --store
The last command does not return because modem manager crashed: log-sms-store-after-send
This issue has been seen with Telit LE910C1-EU, ModemManager 1.19.0, MBIM Interface (and on ModemManager 1.8.0 with a UBlox Toby L210, RNDIS Interface -- but I don't have a log for that)
It seems that (some?) MBIM devices store the message directly when trying to send it. No MBIM_CID_MESSAGE_STORE_STATUS
notification is received in this case (at least on the modem I got)
If I (mis-)use the message reference returned by the send command as sms storage index though, everything works correctly (for the LE910C1-EU modem).
But I think that it is an invalid assumption that the message reference equals the message store index(?) But how do I get the storage index correctly after sending a message?
I see this issue too on an telit LE910C1-EU using mbim. Any news on this?
I tried to track it down and found that the sms does not get deleted because the mm-sim-mbim thinks the SMS is not stored after sending. In mm-sim-mbim.c:delete_next_part
: mm_sms_part_get_index
returns SMS_PART_INVALID_INDEX
and therefore no delete command is sent to the modem.
From what I understand, modemmanager should know that an SMS is stored by getting a notification from the modem that an SMS has been written to flash. But I can't see such a notification in the log file log-no-sms-delete.
Looks a little bit related to theses issues: https://lists.freedesktop.org/archives/libmbim-devel/2013-June/000055.html https://lists.freedesktop.org/archives/modemmanager-devel/2018-May/006415.html
Any ideas how to dig further?
Ulrich Mohr (249e46a7) at 14 Jul 11:52
Ulrich Mohr (249e46a7) at 14 Jul 11:37
mbim: Make use of uim qmi service if available
... and 1 more commit