Phosh won't receive SMS messages

I have the same issue on my pinephone, with PM OS edge, Phosh, running modem-manager 1.16.2-r1.

I tried my – not up to date – pinephone with Manjaro Arm, Phosh, which uses the "modemmanager-pp" package in version 1.14.8-3. After booting I received all my sms on this phone back to 28th of February.

I saw a reddit thread today which describes the same issue with Mobian (the mobile version of Debian). Somebody linked a wikipage from pine64, with the advise to delete the received sms with the ModemManager https://wiki.pine64.org/wiki/PinePhone_FAQ#The_phone_does_not_receive_SMS

But your issue seems to be different, as there are no received sms listed. My pinephone shows 29 received SMS with the command you posted above.

By Ralf Niederhammer on 2021-03-05T14:27:33

Do you have any special character or emoji in one of your text messages? See #861 (closed)

By Dylan Van Assche on 2021-03-05T14:27:33

I don't. I ran ModemManager with a --debug option and it appears to somehow react to texts being sent to it, but I don't understand these logs at all. Could as well be some periodic network check. There are no warnings nor errors.

By furtarball on 2021-03-05T15:05:27

Actually, my other phone receives them some time after I put the simcard in it, so ModemManager probably doesn't receive them at all.

By furtarball on 2021-03-05T15:21:43

Did you ever upgraded the modem firmware, if so, which version?

By Dylan Van Assche on 2021-03-05T17:41:45

Before I flashed pmOS, Android said the modem version was A500FUXXU1CPH3. It might have been upgraded at some point, since the Android version was 6.0.1 and this model shipped with 4.4.4.

By furtarball on 2021-03-06T09:25:27

Well, I have only a PinePhone, but I'm not sure about the samsung-a5ulte. According to the device wiki, @Minecrell and @minlexx at least have these devices.

By Dylan Van Assche on 2021-03-06T15:55:18

I've had the same issue on Motorola Harpia XT1602. I could send SMS but not receive them. OS version was 20210216 from images.postmarketos.org. mmcli showed nothing on the modem. I sent the sms from my other phone, and I can be sure there were no emojis or other non-ascii characters. As soon as I reflashed lineageOS, the messages arrived within a minute or so.

By Irihapeti on 2021-03-07T21:40:27

Did you run any upgrades? And if so, how, via command-line or via GNOME Software?

The mentioned image had the postmarketOS version of the package (as it should be):

https://builds.sr.ht/~postmarketos/job/427405#task-img_mainline_modem-558

(177/512) Installing modemmanager (9999-r2)
(178/512) Installing modemmanager-openrc (9999-r2)

By Oliver Smith on 2021-03-07T21:40:27

Thank you for your reports, @furtarball, @nieral and @Irihapeti!

I've just sent several SMS to my PinePhone with up-to-date postmarketOS edge, but I can't reproduce the problem :\

Sent while not suspended
Sent while suspended (phone woke up: screen flashed briefly; I unlocked it and after ~10s the SMS arrived)
Sent one SMS with emoji and another one without emoji afterwards
- The one with emoji did not arrive (bug #861 (closed)), but the other one did

@nieral wrote:

I have the same issue on my pinephone, with PM OS edge, Phosh, running modem-manager 1.16.2-r1.

I tried my – not up to date – pinephone with Manjaro Arm, Phosh, which uses the "modemmanager-pp" package in version 1.14.8-3. After booting I received all my sms on this phone back to 28th of February.

Oh, I see the problem! Alpine's version of modemmanager (currently 1.16.2-r2) is installed on your system, instead of the postmarketOS one ("9999-r2", which is 1.14.8 as seen in the APKBUILD).

I wonder how that happened, maybe a similar issue to (#694 (closed))? I'm looking into it, will post further details once I found out more.

(We should really get apk logging going, created #1005 (closed) for that.)

By Oliver Smith on 2021-03-07T22:13:11

APKINDEX details for the package in pmOS / alpine:

postmarketOS version:

pmbootstrap apkindex_parse APKINDEX.bdd0d494.tar.gz modemmanager
{
    "modemmanager": {
        "pkgname": "modemmanager",
        "version": "9999-r2",
        "arch": "aarch64",
        "origin": "modemmanager",
        "timestamp": "1606679685",
        "depends": [
            "so:libc.musl-aarch64.so.1",
            "so:libgio-2.0.so.0",
            "so:libglib-2.0.so.0",
            "so:libgmodule-2.0.so.0",
            "so:libgobject-2.0.so.0",
            "so:libgudev-1.0.so.0",
            "so:libintl.so.8",
            "so:libmbim-glib.so.4",
            "so:libmm-glib.so.0",
            "so:libpolkit-gobject-1.so.0",
            "so:libqmi-glib.so.5"
        ],
        "provides": [
            "cmd:ModemManager",
            "cmd:mmcli"
        ]
    }
}

alpine version:

pmbootstrap apkindex_parse APKINDEX.b53994b4.tar.gz modemmanager
{
    "modemmanager": {
        "pkgname": "modemmanager",
        "version": "1.16.2-r2",
        "arch": "aarch64",
        "origin": "modemmanager",
        "timestamp": "1614896135",
        "depends": [
            "so:libc.musl-aarch64.so.1",
            "so:libgio-2.0.so.0",
            "so:libglib-2.0.so.0",
            "so:libgmodule-2.0.so.0",
            "so:libgobject-2.0.so.0",
            "so:libgudev-1.0.so.0",
            "so:libintl.so.8",
            "so:libmbim-glib.so.4",
            "so:libmm-glib.so.0",
            "so:libpolkit-gobject-1.so.0",
            "so:libqmi-glib.so.5",
            "so:libqrtr-glib.so.0"
        ],
        "provides": [
            "cmd:ModemManager",
            "cmd:mmcli"
        ]
    }
}

By Oliver Smith on 2021-03-07T22:13:11

I'm looking at !1931 right now, which will drop the fork anyway... but my postmarketOS time is up for today

So in conclusion, I'm not sure yet what happened here, it might be more than one issue. The Alpine package being installed instead of the pmOS package is definitively unexpected, but I'm not sure if it should have lead to SMS missing or not. We'll drop the pmOS specific fork soon, but that might only work properly with the eg25-manager configs for the pinephone in !1931. (@dylanvanassche?)

And all of that does not explain at all why it does not work with motorola-harpia, apparently there wasn't even the "wrong" modemmanager package installed. For harpia, it only seems obvious that modemmanager did not work, but ofono (Plasma Mobile) did.

CC @Minecrell, maybe you have additional insights here.

By Oliver Smith on 2021-03-07T22:35:36

Oh, I see the problem! Alpine's version of modemmanager (currently 1.16.2-r2) is installed on your system, instead of the postmarketOS one ("9999-r2", which is 1.14.8 as seen in the APKBUILD).

I checked that again. 1.16.2-r2 is installed next to modemmanager-9999-r2 (at least this is what apk info modemmanager* says).

But I was able to solve my problem by following the solution on pine64' wiki (see link above) and deleting the saved sms with $ sudo mmcli -m 3 --messaging-delete-sms=XX (xx is the number of sms saved by modemmanager which is shown via mmcli - m 3 --messaging-list-sms)

Thank you anyway! I really appreciate the fast response on gitlab by you and the other developers.

By Ralf Niederhammer on 2021-03-08T08:54:37

And all of that does not explain at all why it does not work with motorola-harpia

And samsung-a5ulte, mind you. This is the exact same problem I have, my modemmanager is on version 9999, too. I forgot to mention it up in the initial report, but SMS sending and calls (maybe besides some pulseaudio shenanigans, but that's a topic for another issue report) work just fine.

By furtarball on 2021-03-08T10:28:04

(at least this is what apk info modemmanager* says).

apk info is a "lie", it lists all available packages in repo; use apk list -I modemmanager\*

By Alexey Min on 2021-03-08T18:05:17

Ok. I misunderstood "installed size"... apk list shows only modemmanager-9999-r2 and modemmanager-openrc-9999-r2. Monday, 08 March 2021, 07:05PM +01:00 from Alexey Min gitlab@mg.gitlab.com :

By Ralf Niederhammer on 2021-03-08T21:20:01

Oh, getting apk to display the installed versions is indeed not so intuitive. I've added it to the cheat sheet (which gets linked to when logging into SSH for the first time nowadays):

https://wiki.postmarketos.org/wiki/Terminal_cheat_sheet#Package_management

By Oliver Smith on 2021-03-09T21:59:29

added ui-phosh + 1 deleted label

Thanks for all the additional data points!

Let me summarize:

not an issue: the alpine version of modemmanager did not get installed instead of the pmOS one
we have two issues:
- pinephone: modemmanager lists messages in the queue, it's the problem from here and deleting the messages works as explained in the wiki article.
  - so it's a duplicate of #731
samsung-a5ulte / motorola-harpia: messages don't even make it into the queue of modemmanager, while they are received fine with ofono

So let's make this issue about the latter.

To move this forward, I suggest looking into modemmanager logs / poking around with CLI utils to see what's going on.

@aleksander0m, as modemmanager upstream, do you have a more detailed advice / what to look for?

EDIT: I'm removing the regression label, since I didn't see any report that this worked on the devices in question before. Please correct me if that's wrong.

EDIT2: related: WIP modemmanager update: !1966

By Oliver Smith on 2021-03-09T23:36:12

added device-motorola-harpia device-samsung-a5 type::bug labels and removed 1 deleted label

samsung-a5ulte / motorola-harpia: messages don't even make it into the queue of modemmanager, while they are received fine with ofono

@ollieparanoid haven't seen MM debug logs for that issue, do you have any?

By Aleksander Morgado on 2021-03-10T10:49:11

I saved logs that were printed seconds after I sent a text to my a5ulte. Is there any identifying info I should redact?

By furtarball on 2021-03-10T12:06:59

If you're worried about making info public, you can send them to me directly by email, or otherwise open a new bug here https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues flagging it as "confidential" so that only maintainers can check the contents

By Aleksander Morgado on 2021-03-10T16:10:06

Slightly off topic, but I think having a new MM log option to automatically get rid of all personal info wouldn't be a bad idea: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/334

By Aleksander Morgado on 2021-03-10T16:15:16

OK, sent, let me know if they're safe to be published or if you need more.

By furtarball on 2021-03-11T15:10:51

@furtarball got your logs. What you're receiving is a "Transfer Route MT Message", and MM doesn't currently handle those well. There's some work/discussion ongoing here https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/257 and at some point we'll get it implemented. You're not receiving a normal SMS message though, the transfer route MT messages are usually MMS indications that need to be handled differently.

By Aleksander Morgado on 2021-03-11T19:12:48

I sent @aleksander0m more logs after trying to receive texts from two pre-2010 phones and the same one from before. They were all very different. He said none of them indicate that an SMS message is being received.

What are they, then? Is the modem talking to the network completely incorrectly and misunderstanding the data it receives?

By furtarball on 2021-03-15T07:42:24

What are they, then?

@furtarball one of the messages you posted was a signal quality indication, another one a WDS indication reporting channel active & then dormant, and another one was an indication reporting registration status. None of those are new SMS indications.

Is the modem talking to the network completely incorrectly and misunderstanding the data it receives?

No. Those are indications you would normally receive even without any SMS being received.

Maybe the SMS messages are not being notified via QMI WMS indications and are only notified via AT URCs? Would you be able to get some ofono logs to see how they're processed? We added a change in MM recently to enable both WMS+AT indications for SMS messages, not just one or the other, maybe that could help you. @dylanvanassche is that change ported to postmarketos?

By Aleksander Morgado on 2021-03-15T08:29:06

@aleksander0m That patch was part of !1931 but I removed it as it was not needed. Currently, we are on 1.16.2 which doesn't include the patch.

By Dylan Van Assche on 2021-03-15T08:34:57

Would you be able to get some ofono logs to see how they're processed?

Uhh… how exactly? None of the ways to get a log out of ofono I was able to find work on postmarketOS. Is monitor-ofono from ofono-scripts good enough? It outputs nothing besides the contents, date, and sender of a message.

By furtarball on 2021-03-15T19:03:41

I have absolutely no idea how to do that, was hoping anyone here would know :)

By Aleksander Morgado on 2021-03-16T08:31:44

Uhh… how exactly? None of the ways to get a log out of ofono I was able to find work on postmarketOS.

You can sudo rc-service ofono stop and then start it in debug mode like sudo ofonod --debug --nodetach. The output isn't as nice as the one from ModemManager though :)

By Minecrell on 2021-03-17T16:00:43

@aleksander0m I have a similar issue on my bq-paella, not sure why @Minecrell don't have this issue (maybe because paella bought for less than a pizza price are perfectly working :-P).

By default my paella modem has this storage settings for SMS:

+CPMS: "ME",0,11,"ME",0,11,"SM",0,10

With this configuration, if someone sends me an SMS I can see from debug logs that I receive it as Transfer Route MT Message and it doesn't shows up in Phosh.

BUT! By changing the defaults storages for SMS to:

+CPMS: "MT",0,11,"MT",0,11,"MT",0,11

with sudo echo 'AT+CPMS="MT","MT","MT"' | sudo atinout - /dev/modem-at - I then receive SMS correctly. I can send you logs for both the storage settings if you need them.

By Jonathan Albrieux on 2021-03-20T19:18:16

I have a similar issue on my bq-paella, not sure why @Minecrell don't have this issue (maybe because paella bought for less than a pizza price are perfectly working :-P).

Usually I don't run GUIs and to be honest I'm not sure I ever tested receiving SMS. I was happy enough when sending SMS worked, eventually voice calls had audio and at some point I managed to get mobile data working :)

By Minecrell on 2021-03-20T19:18:15

sudo echo 'AT+CPMS="MT","MT","MT"' | sudo atinout - /dev/modem-at -

This returns:

fopen(/dev/modem-at) failed: Invalid argument

What do I do? /dev/modem-at does exist.

By furtarball on 2021-03-21T13:47:31

Have you stopped modemmanager service before running the command?

By Jonathan Albrieux on 2021-03-21T13:53:53

Oh, right! Now it works! Thank you!

By furtarball on 2021-03-21T14:47:49

@furtarball Curious, with "it works" do you mean the command works, or does this also help you to receive SMS on a5ulte?

By Minecrell on 2021-03-21T14:56:02

@Minecrell I mean that the Chats app finally receives texts as it should, both new and previously unreceived.

By furtarball on 2021-03-21T14:58:05

I mean that the Chats app finally receives texts as it should, both new and previously unreceived.

Great!

@aleksander0m Do you have an idea why this magic AT command helps, and if we should do it automatically in ModemManager? (Also, maybe there is an alternative QMI command for it?)

By Minecrell on 2021-03-21T15:02:58

@aleksander0m Do you have an idea why this magic AT command helps, and if we should do it automatically in ModemManager? (Also, maybe there is an alternative QMI command for it?)

This may be a bug in the MM logic actually:

The QMI modem by default will support 2 different storages: ME (modem) and SM (SIM), see messaging_load_supported_storages_finish() in mm-broadband-modem-qmi.c.
Then, in the mm-iface-modem-messaging.c enabling procedure there is a case ENABLING_STEP_STORAGE_DEFAULTS step, which selects one default storage that will be used for storing, using get_single_default_sms_storage() or get_best_initial_default_sms_storage() (I'd say the second).
With that default storage, set_default_storage() is called, which in the QMI modem it defaults to messaging_set_default_storage() in the mm-broadband-modem-qmi.c source.
That method uses qmi_client_wms_set_routes() to configure settings for Class 0 (flash) and Class 1 (regular) SMS messages. Same settings for both: action QMI_WMS_RECEIPT_ACTION_STORE_AND_NOTIFY in the storage given by the mm_sms_storage_to_qmi_storage_type() conversion.
Following that flow, I would have said that the set_routes() message should have configured QMI_WMS_STORAGE_TYPE_NV as storage for the received SMS, which would have been equivalent to configuring ME as mem3 in the AT+CPMS command, but now I'm not sure if there's some issue in this flow.

If anyone wants to go over all the steps to review them one by one, that would be nice.

By Aleksander Morgado on 2021-03-22T08:37:15

added device-bq-paella label

This issue seem to have been solved somehow, at least on a5lte. I no longer have to use the sudo echo 'AT+CPMS="MT","MT","MT"' | sudo atinout - /dev/modem-at - workaround, text messages are received without it

By Henrik Grimler on 2021-06-17T09:13:33

Not sure if anything changed recently though

By Minecrell on 2021-06-17T09:13:32

Yeah, I am not sure when it might have been fixed, it definitely did not work in middle of April. Since then (on the occasions I have used the device with a sim card) I have run the workaround out of habit on boot, so any update in the last two months could have fixed it

Could someone else check if receiving texts with phosh seem to work, or if it is still broken?

By Henrik Grimler on 2021-06-17T09:30:31

It does work for me now.

By furtarball on 2021-06-19T11:57:36

I don't understand why it is fixed now but if everyone reports that it is fine now I'll close this until someone comments here otherwise again. :)

By Minecrell on 2021-08-16T13:56:56

closed

Phosh won't receive SMS messages

Describe your issue

What's the expected behaviour?

What's the current behaviour?

How to reproduce your issue?

What device are you using?

On what postmarketOS version did you encounter the issue?

On what environment did you encounter the issue?

Phone environments

Other

How did you get postmarketOS image?

What's the build date of the image? (in yyyy-mm-dd format)

Additional information

Child items 0

Activity