continuing MMS issues.

domubpkm

@fizz it is nuntium and not numtium as you wrote i think.

Fizz

@domubpkm
Doh! You're right. Thanks.

I have it installed now. At the end of the install, i got a warning that it failed to remount root filesystem, and a warning to consider rebooting. I'm thinking (hoping) that is normal, so i've rebooted the phone.

I will let everyone know how it's going a bit later today. Thanks!

-Fizz

Fizz

So after the reboot, my messaging list seems to indicate that i sent a blank message to a previously used number (one i know, but not on my contacts list) essentially at the same time it was rebooting. I've no idea if it actually sent an empty message, it's just how it looks in my message history. That number / message was not previously in my history, and i certainly just didn't enter it myself.

I had my wife send me a test image, and unfortunately, the behavior seems to be exactly as it was before-
"Could not fetch the MMS message. Maybe the MMS settings are incorrect or cellular data is off?".

She's off to work now, so any more tests i'll have to do later this evening.

-Fizz

domubpkm

@fizz When I was testing MMS, I happened to send MMS to myself. Maybe it could be useful in your tests.

jezek

@fizz I'm sorry the fix didn't work for you. Feel free to go back to stable.

It would be helpful that you provide a ~/.cache/upstart/nuntium.log contents for debug purposes.

Restart your phone. That should clear the log file.
Let somebody send you an MMS (and/or try to send one to yourself).
Locate the log file and copy its content here via some file sharing service (pastebin, gist). DON'T FORGET to redact the log file, the phone number of the sender is somewhere there. Replace the digits if you don't want to expose them to the internet.

Fizz

@jezek
It seems this update has caused some other issue as well- whenever i try to restart the phone, it takes much longer than before.

It actually seems to reset in the middle of the reboot: i see the black UBPorts screen, and then the Magenta screen. But then it goes black and i see the black UBPorts screen again, and then Magenta, and finally to the login page. The whole process takes several minutes.

So after i get this log for you, i think i'll go back to the stable version. How do i uninstall the rc version and go back to the current stable version?

(I presume you want the log from the rc version, but if you want the log from the stable i can do that.)

-Fizz

Fizz

@jezek
OK, i restarted the device (this time it seemed to reset about 4 times before getting to the login screen). My wife sent me a test image.

Fwiw, i've noticed that with this modified version i get two simultaneous notifications from the OS, but not two messages.

Below is the nuntium log. This is from the rc version.

2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/a5728be444eb482c049065fe7a174b4b is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/a5728be444eb482c049065fe7a174b4b is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/19a20cf5fb944b2e7020be1f2f15e70f is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/19a20cf5fb944b2e7020be1f2f15e70f is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/b6fd22c5584043e4d8ab25ba710e5a70 is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/b6fd22c5584043e4d8ab25ba710e5a70 is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/05f03fa368fd6c583f3773bdecf7f685 is not responded and not expired, not deleting.
2022/11/28 19:13:31 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/28 19:13:31 Message /org/ofono/mms/302610917674682/05f03fa368fd6c583f3773bdecf7f685 is not responded and not expired, not deleting.

Now, how do i go back to the previous (stable) version? sudo ubports-qa uninstall PR_nuntium_18 would leave me with no messenger at all, wouldn't it?

-Fizz

wally

Flashing the device using the installer would remove the changes to nuntium and put you back on Stable channel in one swoop. Just select Stable and make sure not to click the button to wipe the device clean. Then it comes back just as it was.
Last night I botched my install of Jezek's fix - it froze/disconnected halfway through. Couldn't remove it or redo the install, and I wound up having to flash the device. So I can vouch for that working, and it shouldn't take much longer than reverting nuntium and switching to Stable separately.
I'd have guessed that you could also use the command that you typed, except with "remove" in place of "uninstall", to revert to how nuntium was before, but I don't know nearly enough about that to say so with confidence.

wally

More broadly, sorry to hear of your MMS woes Fizz. It's definitely pretty essential here in Canada, though my impression is that North America's a bit abnormal in that, and UT's not really working as a normal phone in USA since they dropped 3G.

Wish I had better ideas to help, but it seems like you've ticked the boxes that I was aware of.

I have an MMS issue myself, but it seems distinct from yours. Mine works day to day, then I'll just stop receiving MMS entirely with no notification whatsoever. People will send an image and I'll have no idea. But day to day my MMS works (Oneplus 5, Telus network [Public Mobile]), it just breaks sometimes. Dunno what causes it. I've found a strange, roundabout way of fixing it once I realize it's broken, linked in case anyone else has this issue.
https://forums.ubports.com/topic/8145/mms-status-on-the-oneplus-5-cheeseburger/3

Too early to say whether the Jezek nuntium update will fix my issue, but I'm hopeful. In any case, thanks sincerely for your work on this Jezek!

I second the suggestion of texting images to oneself as a means of testing MMS. Works for me.
Good luck, Fizz.

Fizz

@wally
Well i did the "remove" rather than "uninstall", and i think it worked... The removal process proceeded, and after a reboot i still have messenger. So i think i'm back to the stable version.

I too thank Jezek for his work on this. Hopefully he can find the root cause of the issue.

-Fizz

lduboeuf

@wally i think you can create a new issue ticket for this or comment on the multiple current ticket for MMS.
There is so many possible root cause to make this happen, hope on Focal there will be a better APN setting support. Jezek's work should also provide better debug logs, so always add logs please with your ticket.
also the syslog ( cat /var/log/syslog ) can help but personal datas there also i guess.

wally

Yeah, in retrospect, my own issue may have been a cumbersome thing to add to this thread. Thanks for the suggestions Lionel. I've been meaning to make time to look into issue tickets / bug reports. Unless I learn to code, seems like the other thing I can do to help the cause beyond donating.
Y'all are excellent, all you folks who keep this thing working and improving! Thanks.

Fizz, I believe you'll still be on the Release Candidate version of the operating system, just with a reverted nuntium. Maybe you know that, but when you mentioned "stable", I thought it was worth mentioning, Stable being being the name of the least frequently updated / safest OS channel. I find RC pretty reliable though.

Fizz

@wally
OK, here's the timeline of my updates...

I was on OTA-23, on the stable channel. I updated to OTA-24, again stable, and tried out the MMS issue.

When MMS was still not working, i posted here. I switched to the RC channel, but i did not update anything through the updater. All i did was run the sudo ubports-qa install PR_nuntium_18 to install the new nuntium.

So at this point, to my knowledge, i was on OTA-24 stable but with the RC version of nuntium.

I did my tests, reported here, and then ran sudo ubports-qa uninstall PR_nuntium_18. So i should be back on OTA-24 with the current stable version of nuntium.

Correct? Or have i done something that invalidates my earlier tests?

-Fizz

jezek

@fizz You have to switch to rc channel and then download and install the new version via settings update. Then reboot and after that install the ubports-qa. Then reboot and try to receive an MMS. Then, when the error happens, paste the nuntium log file. It should look something like this:

2022/07/09 23:09:02 Using session bus on :1.2
2022/07/09 23:09:02 Registered :1.2 on bus as org.ofono.mms
2022/07/09 23:09:02 Using system bus on :1.42
2022/07/09 23:09:02 Initializing modem /ril_1
2022/07/09 23:09:02 Initializing modem /ril_0
2022/07/09 23:09:09 Received GetServices()
2022/07/09 23:09:10 Using session bus on :1.45
2022/07/09 23:09:10 Registered :1.45 on bus as org.ofono.mms
2022/07/09 23:09:10 Using system bus on :1.66
2022/07/09 23:09:10 Initializing modem /ril_1
2022/07/09 23:09:10 Modem online: true
2022/07/09 23:09:10 Initializing modem /ril_0
2022/07/09 23:09:10 Push interface state: true
2022/07/09 23:09:10 Modem online: true
2022/07/09 23:09:10 Registering agent for /ril_0 on path /nuntium and name :1.68
2022/07/09 23:09:10 Identity added 231014453153205
2022/07/09 23:09:10 Agent Registered for /ril_0 on path /nuntium
2022/07/09 23:09:10 Service added /org/ofono/mms/231014453153205
2022/07/09 23:09:10 Initializing 2 messages from storage
2022/07/09 23:09:10 Message b3cf18494ac5b728493d606e4ab156ac is not an incoming message. State: draft
2022/07/09 23:09:11 Message 34049fe83ca2115aa1a5a72296939dc7 is not an incoming message. State: draft
2022/07/22 10:41:14 Received ReceiveNotification() method call from 851
2022/07/22 10:41:14 Push data
00000000  00 06 07 be af 84 8d f7  b4 81 8c 82 98 41 39 6e  |.............A9n|
00000010  44 31 45 5f 4a 79 54 55  51 31 65 66 33 75 00 8d  |D1E_JyTUQ1ef3u..|
00000020  92 89 19 80 2b 34 32 31  39 30 35 34 38 39 32 31  |....+00000000000|
00000030  38 2f 54 59 50 45 3d 50  4c 4d 4e 00 86 81 8a 80  |8/TYPE=PLMN.....|
00000040  8e 03 02 4d 7d 88 05 81  03 01 43 70 83 68 74 74  |...M}.....Cp.htt|
00000050  70 3a 2f 2f 32 31 33 2e  31 35 31 2e 32 35 30 2e  |p://213.151.250.|
00000060  32 38 3a 31 30 30 32 31  2f 6d 6d 73 63 2f 3f 41  |28:10021/mmsc/?A|
00000070  39 6e 44 31 45 5f 4a 79  54 55 51 31 65 66 33 75  |9nD1E_JyTUQ1ef3u|
00000080  00                                                |.|
2022/07/22 10:41:14 Pushed transaction ID (A9nD1E_JyTUQ1ef3u) is in undownloaded pointing to UUID: 667cd568ee5213abe31a2ba9894565b9
2022/07/22 10:41:14 Changing recieved date to the first push date: 2022-07-22 09:41:15.003349952 +0200 CEST
2022/07/22 10:41:14 Trying to set Active property to true for context on true /ril_0/context3
2022/07/22 10:41:14 Cannot set Activate to true (try 1/3) interface on /ril_0/context3: org.ofono.Error.NotAttached: GPRS is not attached
2022/07/22 10:41:16 Cannot set Activate to true (try 2/3) interface on /ril_0/context3: org.ofono.Error.NotAttached: GPRS is not attached
2022/07/22 11:48:04 Cannot set Activate to true (try 3/3) interface on /ril_0/context3: org.ofono.Error.NotAttached: GPRS is not attached
2022/07/22 11:48:06 Failed to activate for /ril_0/context3 : failed to activate context
2022/07/22 11:48:06 Cannot activate ofono context: no context available to activate
2022/07/22 11:48:06 Message or handling error for MNotificationInd with TransactionId: "A9nD1E_JyTUQ1ef3u" was already communicated by UUID: "667cd568ee5213abe31a2ba9894565b9"
2022/07/22 11:48:06 Message 9c1a440fb05d30b49e9c2256c3ca7515 was removed from storage
2022/07/22 14:07:50 Received unknown method call on org.ofono.mms.Message MarkRead
2022/07/22 14:07:50 Message /org/ofono/mms/231014453153205/667cd568ee5213abe31a2ba9894565b9 is not responded and not expired, not deleting.

Note, that i redacted the phone number in the Push data. The log you provided was missing the application start ant the Received ReceiveNotification() part.

Also it would be a big help when you write your steps you made while testing and collecting logs. Something like:

Switched to rc channel , via setting -> updates -> updates-setting.
Downloaded and installed update. The phone restarted.
Installed the qa using command sudo....
...

Thank you.

Fizz

@jezek
Roger that, will do. I thought i had to be on the rc channel to get nuntium only- didn't realize i needed the whole OS on the rc version.

For the record, the log file that i attached was the entire log file- there was literally nothing else in it. But that's all moot now anyways.

Will post again once i've run through all those steps.

-Fizz

Fizz

OK, here's what happened... I did this in steps. First i installed the RC version of the OS, and tried to receive a mms. Then i installed nuntium_18 and tried again.

System Setting > Updates > Changed to RC > downloaded "version 145" (435.2MB)

The system / installed / restarted itself

Had a text-image sent to me. I received a single notification (this is relevant later). I received the usual error message.

Retrieved log (see below):

2022/11/30 12:59:39 Received ReceiveNotification() method call from 44600
2022/11/30 12:59:39 Push data
00000000  00 06 29 1f 22 61 70 70  6c 69 63 61 74 69 6f 6e  |..)."application|
00000010  2f 76 6e 64 2e 77 61 70  2e 6d 6d 73 2d 6d 65 73  |/vnd.wap.mms-mes|
00000020  73 61 67 65 00 81 84 af  84 8d 01 00 8c 82 98 39  |sage...........9|
00000030  61 30 37 34 61 39 32 61  65 61 35 36 66 31 32 36  |a074a92aea56f126|
00000040  37 35 35 65 61 65 63 2d  31 00 8d 92 89 1a 80 18  |755eaec-1.......|
00000050  ea 2b 31 35 31 39 38 35  39 30 35 34 37 2f 54 59  |.+10000000000/TY|
00000060  50 45 3d 50 4c 4d 4e 00  96 00 8a 80 88 05 81 03  |PE=PLMN.........|
00000070  09 3a 7d 86 81 83 68 74  74 70 3a 2f 2f 6d 6d 73  |.:}...http://mms|
00000080  63 32 2e 67 65 74 2e 62  65 6c 6c 2e 63 61 2f 63  |c2.get.bell.ca/c|
00000090  6c 6f 75 64 6d 6d 73 63  3f 6c 3d 61 65 65 63 34  |loudmmsc?l=aeec4|
000000a0  35 38 35 61 66 38 64 39  34 65 65 39 34 34 34 31  |585af8d94ee94441|
000000b0  31 66 61 2d 31 00 8e 03  04 9a 4f                 |1fa-1.....O|
2022/11/30 12:59:39 Trying to set Active property to true for context on true /ril_0/context2
2022/11/30 12:59:40 Download issues: org.freedesktop.DBus.Error.InvalidArgs: Invalid URL: ''
2022/11/30 12:59:40 Trying to set Active property to false for context on false /ril_0/context2
2022/11/30 12:59:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 12:59:56 Message /org/ofono/mms/302610917674682/2d50b77dfa31fa85e12d8f74af4d170c is not responded and not expired, not deleting.

where i replaced the phone number with 0000000000.

Next, I attempted to install nuntium 18 via "sudo ubports-qa install PR_nuntium_18" through terminal

I am not sure it installed properly, the last few lines of the process says:

W: No sandbox user '_apt' on the system, can not drop priveleges
Reading pack lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mount: / is busy
WARNING:ubports-qa:Failed to remount root filesystem read-only.
WARNING:ubports-qa:Please consider rebooting your device.
INFO:ubports-qa:You can remove the repository by running 'sudo ubports-qa remove PR_nuntium_18'

So did it install or not? (Things behaved differently, so something surely is different.)

Going on the assumption that it worked, i rebooted the device.

Received a black screen for a very long time... ~5 minutes. I could tell the backlight was on, but the screen was black. Finally i decided to force restart. I saw the Nexus5 screen, then the magenta UbuntuTouch loading page. Then it went black and seemed to reboot again. Finally i made it to the desktop.

Had a text-image sent to me. I received two notifications on the desktop (was only one notification per message before). (This is what happened earlier after i installed nuntium_18. Something about that install causes multiple notifications, even when not MMS.) And i still get the same error message.

Retrieved the new log file (see below):

2022/11/30 13:19:13 Received ReceiveNotification() method call from 44600
2022/11/30 13:19:13 Push data
00000000  00 06 29 1f 22 61 70 70  6c 69 63 61 74 69 6f 6e  |..)."application|
00000010  2f 76 6e 64 2e 77 61 70  2e 6d 6d 73 2d 6d 65 73  |/vnd.wap.mms-mes|
00000020  73 61 67 65 00 81 84 af  84 8d 01 00 8c 82 98 30  |sage...........0|
00000030  31 31 33 34 39 35 32 61  38 36 66 31 38 65 39 66  |1134952a86f18e9f|
00000040  37 64 34 62 63 61 33 2d  31 00 8d 92 89 1a 80 18  |7d4bca3-1.......|
00000050  ea 2b 31 35 31 39 38 35  39 30 35 34 37 2f 54 59  |.+10000000000/TY|
00000060  50 45 3d 50 4c 4d 4e 00  96 00 8a 80 88 05 81 03  |PE=PLMN.........|
00000070  09 3a 7e 86 81 83 68 74  74 70 3a 2f 2f 6d 6d 73  |.:~...http://mms|
00000080  63 32 2e 67 65 74 2e 62  65 6c 6c 2e 63 61 2f 63  |c2.get.bell.ca/c|
00000090  6c 6f 75 64 6d 6d 73 63  3f 6c 3d 30 31 31 33 34  |loudmmsc?l=01134|
000000a0  39 35 32 61 38 36 66 31  38 65 39 66 37 64 34 62  |952a86f18e9f7d4b|
000000b0  63 61 33 2d 31 00 8e 03  02 3c e5                 |ca3-1....<.|
2022/11/30 13:19:13 Mediator /ril_0 is handling a MNotificationInd with UUID: 0fa9a1efa5d39d0fbeb67cc2a3994d30
2022/11/30 13:19:13 Trying to set Active property to true for context on true /ril_0/context2
2022/11/30 13:19:13 Download issues: org.freedesktop.DBus.Error.InvalidArgs: Invalid URL: ''
2022/11/30 13:19:13 Trying to set Active property to false for context on false /ril_0/context2
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/a5728be444eb482c049065fe7a174b4b is not responded and not expired, not deleting.
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/19a20cf5fb944b2e7020be1f2f15e70f is not responded and not expired, not deleting.
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/b6fd22c5584043e4d8ab25ba710e5a70 is not responded and not expired, not deleting.
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/05f03fa368fd6c583f3773bdecf7f685 is not responded and not expired, not deleting.
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/2d50b77dfa31fa85e12d8f74af4d170c is not responded and not expired, not deleting.
2022/11/30 13:19:56 Received unknown method call on org.ofono.mms.Message MarkRead
2022/11/30 13:19:56 Message /org/ofono/mms/302610917674682/0fa9a1efa5d39d0fbeb67cc2a3994d30 is not responded and not expired, not deleting.

I hope i have everything you need there, and that i've been clear in exactly what i've done. Let me know if you need anything else.

-Fizz

jezek

@fizz said in continuing MMS issues.:

I hope i have everything you need there, and that i've been clear in exactly what i've done. Let me know if you need anything else.

You did good. I have everything I need. It seems, that the bug is somewhere in the downloader and the ubports-qa fix does nothing there. Feel free to go back to stable.

What I see In booth logs and is relevant is this line:

Download issues: org.freedesktop.DBus.Error.InvalidArgs: Invalid URL: ''

which is kind of strange, because it says, the URL is blank although I clearly see the url in the push data:

00000070  09 3a 7e 86 81 83 68 74  74 70 3a 2f 2f 6d 6d 73  |.:~...http://mms|
00000080  63 32 2e 67 65 74 2e 62  65 6c 6c 2e 63 61 2f 63  |c2.get.bell.ca/c|
00000090  6c 6f 75 64 6d 6d 73 63  3f 6c 3d 30 31 31 33 34  |loudmmsc?l=01134|
000000a0  39 35 32 61 38 36 66 31  38 65 39 66 37 64 34 62  |952a86f18e9f7d4b|
000000b0  63 61 33 2d 31 00 8e 03  02 3c e5                 |ca3-1....<.|

BTW... I vaguely remember crossing this kind of error... [did some search]... And I'm right I saw it during my work on MMS re-download and there was an issue made that time. I'll add a link to this thread there.

I recall to try to figure it out back then, but I could't replicate the bug on my device. I'll try to debug it with your push data, but don't get your hopes up. What can't be replicated is nearly impossible to fix (for me).

Fizz

@jezek
Thanks for your work on this. I noticed something that may or may not be important.

In the push data it refers to mmsc2.get.bell.ca . Should that be matching anything in my apn settings? I don't see anything in my apn settings with that url.

Maybe it means nothing, but i just noticed so thought i'd mention, just in case it was important.

As a reminder (again in case it helps), i'm using a Nexus 5 and am on Virgin Canada's network. The apn settings are the default ones (whatever it decided when i installed the OS). We tried tweaking those in the past but it never helped.

-Fizz

lduboeuf

Hi all, if anyone still having that " Invalid URL: '' issue (https://gitlab.com/ubports/development/core/nuntium/-/issues/14), i've tried to work around it.
test could be done on 20.04, devel: sudo ubports-qa install focal_-_PR_nuntium_25