error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.libmbim.Error.Status.MemoryFull: Couldn't send SMS part: MemoryFull'
dpecka at opensuse.org
Fri Aug 10 14:22:12 UTC 2018
I have update. It's weird, I've inserted my SIM card into the phone
with android and indeed, there were some messages on the SIM, so I've
deleted them and now sending and receiving messages works again -
that's the `success story part' .. but what I don't completely
understand is that on the SIM card were something like 10-20 messages,
not more, with usual length, and from linux it has been considered as
a full storage ...
it's weird, I will look this closely and try to investigate that
further if it happens again ..
S Pozdravem / Best Regards
Daniel Pecka - dpecka at opensuse.org
SCSA, SCNA, RHCE, CLP
On Sat, Jul 28, 2018 at 5:24 PM, Aleksander Morgado
<aleksander at aleksander.es> wrote:
>>> The problem is not your system memory; it's the SMS storage inside the
>>> modem the one that is full.
>>> Try to list SMS messages with mmcli --messaging-list-sms, and then
>>> delete the ones you don't want with --messaging-delete-sms=[INDEX]
>> Hello Alex,
>> thanks for your input .. I've forgot to add, that this was the first
>> idea that came into my mind and I've checked that .. mmcli says it's
>> # mmcli -m 1 --messaging-list-sms
>> No SMS messages were found
>> However I doubt that mmcli is querying the SIM memory. According to memory
>> # mmcli -m 1 --messaging-status
>> Messaging | supported storages: 'mt'
>> | default storage: 'unknown'
>> I've tried several otger opts with --store-in-storage=mt but it didn't
>> work .. I think that the last resort that I'm going to try is to
>> insert the SIM into some cell phone and try to check the status of its
>> storage like that .. Will tell you the result ..
> This totally looks like a common issue in MBIM modems, where there is
> no way to select the current SMS storage. I've seen cases where the
> MBIM API works with one storage (e.g. SIM storage) and the device is
> configured to use another by default (e.g. modem storage), so at the
> end one ends up full and hidden to the MBIM API. If your device can
> work with some other protocol (QMI, AT?) then you could try emptying
> all storages using that other protocol.
More information about the libmbim-devel