Failed MMS redownload progress report:

There are now 3 drafts on github:

• https://github.com/ubports/nuntium/pull/8
• https://github.com/ubports/telephony-service/pull/20
• https://github.com/ubports/messaging-app/pull/260

This is the first working version, where you can initiate re-download of failed MMS by clicking a button in messaging-app. This version is quirky and will be improved further.

What needs to be done?

• make it possible to report failed message using status, not an empty message.
• refactoring, tests, documentation, changelogs, etc...

Will report again on any noticable progress.

Failed MMS redownload progress report:

This week only nuntium PR got updated.

There was a problem with redownload after nuntium got restarted. After nunium restarted (on crash, or phone reboot), the redownload button from messaging-app didn't work. This was because of the button sends the redownload request to nuntium through dbus. And after nuntium restart, there was no one listening on dbus for the redownload signal. I've fixed this by spawning listeners for messages on modem identification. So the redownload now works even after phone restart.

Also the nuntium-inject-pust testing tool got update. It can now autodetect the end-point flag from nuntium logs using grep & sed commands.

@thrill_seeker Quick search on github.com/ubports found a folder for morph search engines implementation. The code in SearchEngines.qml scans through the dir for *.xml and uses them. So to add new search engine, add a new XML to the dir. You can look on the other to figure out how to write a new one. Good luck.

@krogoth I like @dobey 's answer. Cause it's not a simple 'no'. It is accompanied by some hints, how you can try to approach the problem, if you want to solve it. Keep going @dobey , excellent work.

Failed MMS re-download progress report:

Number of drafts on github is now 5:

• https://github.com/ubports/nuntium/pull/8 - saves info about failed download, adds error & delete-event parameters (if needed) into dbus message for thelepathy-ofono and incoming re-download request.
• https://github.com/ubports/telepathy-ofono/pull/20 - for received mms (from nuntium), parses additional parameters ("Error", "DeleteEvent") and sets Telepathy message headers accordingly ("x-ubports-error", "supersedes").
  The "supersedes" header indicates, that the current message replaces the one stored in the header and is currently handled by history-service without any change. (Note: during injection testing, history service fails to delete the supersedes message, if it is in another conversation)
  The "x-ubports-error" header should indicate an error message when message propagates through telepathy-qt to history-service. Maybe the error propagation could be done via "delivery-status", "delivery-error", "delivery-error-message" headers and no changes in history-service will be needed (theory needs testing).
• https://github.com/ubports/history-service/pull/35 - the code here does nothing new yet, just adds some logging. The idea is to change status if "x-ubports-error" is set. It's possible, that this PR will be unnecessary.
• https://github.com/ubports/telephony-service/pull/20 - adds methods to propagate re-download request to nuntium.
• https://github.com/ubports/messaging-app/pull/260 - adds re-download button to error message.

The redownload should work after these PRs. The new thing is, that after hitting redownload the old error message bubble should be deleted when the new message arrives (as successfully received message or new error message).

What needs to be done:

• improve error mms logic (currently: when delivered message is empty, without attachments). The idea is, that a delivered message is an error message when message is empty (historical reasons) or status is one of MessageStatusPermanentlyFailed, MessageStatusTemporaryFailed or MessageStatusPending. The message, which can be re-downloaded will have temporaryFailed status and will show the re-download button. Upon re-download clicked the state will be changed to pending (the re-download button is disabled). When re-download is not possible (expired, some other error) the status will be permanentlyFailed or empty message (current).
• set status in history-service (if needed)
• refactoring, tests, documentation, changelogs, etc...

I'm sorry, I'm so slow with progress, have only cca a hour a day for coding/testing. And building, deploying, phone restarting and log/code studying takes too much time. I hope it'll get faster.

@lduboeuf said in The MMS lost story:

How do you manage to propagate error or deferred status as Telepathy Message object to Telephony-service and History-service ?. By using the messageType , e.g: ChannelTextMessageTypeNotice ?

I'm afraid, that propagating via messageType (declaring new type) could break some other logic, which handles message type. So I decided to go with custom header "x-ubports-error". Or maybe using other headers (see above).

Questions, ideas or critics are welcome.

Edit: https://github.com/ubports/telepathy-ofono/pull/20 and https://github.com/ubports/history-service/pull/35 fail to pass checks. Does anyone know why?

@opolork

...the old French inscription pour féliciter, or "P.F.", together with the number of an upcoming year, standing for "wishing you all the happiness in the new year".

https://en.wikipedia.org/wiki/New_Year_card

Failed MMS re-download progress report:

The progress is slow, but steady. Two PR drafts got updated:

• https://github.com/ubports/telephony-service/pull/20
• https://github.com/ubports/messaging-app/pull/260

What was updated:

1. Some refactoring was done in telephony-service in redownloadMesage pathway (the function now needs 3 string parameters instead of a string map).
2. The redownload (in telephony-service) changes message status to pending before sending a redownload request to nuntium.
3. The redownload (in telephony-service) sends redownload request to nuntium only if message status is unknown (later it will be other status) to not request redownload more times than needed (if function is called more times)
4. Redownload buton gets disabled if message status is other than unknown (will be other status later), to indicate hat redowload is in progress.

Failed MMS redownload progress report:

Because of unsafe apt operations, which makes crossbuilder & ubports-qa unsafe too, I've redirected my attention to nuntium, resulting in some commits to https://github.com/ubports/nuntium/pull/8. (Note: I can easily deploy nuntuim to phone without apt)

What was done?

My operator (and other?) resends multimedia message notifications ever 10 minutes, if notification is not marked as received. This resulted in new error message (when download fails) and notification sound every time. These new commits prevents this behavior.

Every notification comes with transaction-id, which is stored on download error and if new notification comes with the same transaction-id and there was a download error again, the error message will not be sent to telepathy again.

The only caveat is, that if the second download fails on another error as the first, then the second error will not be communicated (however no error description is communicated now, this will be added in future). I'll see, if this will need attention later.

To test these changes easier, I've added an transaction-id flag to nuntium-inject-push testing tool.

That's all for this week, see ya next time.

@TheVancedGamer said in Is Ubuntu Touch OTA-2 Focal incompatible with the Fairphone 2?:

y'all need focal for FP2?

there

Pardon my intrusion. Just a few questions. Is the port you are showing/using/building usable? Can you describe what works and what not? Is there a way I (or anyone else with FP2) can test the product of your effort?

Thanks.

@kugiigi said in [Break Your UT] Bigger and better Lomiri and Keyboard???:

I don't know. Manual rotation button?

Yeah, that's the name. I mean, how do I install it? What is the package name for the jerk installer?

jerk install <package>

@kugiigi said in [Break Your UT] Bigger and better Lomiri and Keyboard???:

Which one do you mean? The button that appears when you rotate the device and let's you rotate the shell to that orientation? That's in both xenial and focal.

Yes, I mean that. How is it called? How do you install it? Thanks.

Btw. this one would be a nice addition to the OS, I think.

@kugiigi I watched your Lomiri Plus preview and I very liked all the stuff. Especially the push to rotate feature. I looked at the repo and see, that the rotate thingy is not for xenial, just for focal. Is is not possible due to some limitations? Or some other reason, why not on xenial? Thx.

@Josele13 Hello, I got the same problem first time, the counter emblems were introduced. I think the problem is, that if you have more missed calls (with emblems), the unchecking process (make missed calls as seen and decrease emblem counter) takes too long and you have to wait on the missed tab a little longer. However I didn't wait and deleted all missed calls which removed the counter emblems. After this I had no problems with counters and if I missed a call, just a visit to the missed calls tab makes the missed calls emblem disappear.

I think it is a good feature (counter emblems). Sometimes I clear notifications to not have a green icon on status bar (and no green blinking LED light), but do not reply to messages/calls in that time and the emblems are an indicator for me, that I have to reply.

@lduboeuf wow, it even works with ssh thanx

ssh phablet@ip.addr exec 'mirscreencast -m /run/mir_socket --stdout --cap-interval 2 -s  384 640' | mplayer -demuxer rawvideo -rawvideo w=384:h=640:format=rgba -

Note: use your IP address instead of ip.addr in the command

@domubpkm said in MMS redownload and group MMS:

do you mean you need the data with the phone numbers ??

No, I don't need the phone numbers nor any private data. You can edit it out.

But beware, do not edit random numbers from the middle number part. It is a hex dump and some data is there encoded twice.

Let's say, we have a hexdump from logs like this:

00000000  01 06 26 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76  |..&application/v|
00000010  6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61  |nd.wap.mms-messa|
00000020  67 65 00 af 84 b4 86 c3 95 8c 82 98 6d 30 34 42  |ge..........m04B|
00000030  4b 6b 73 69 6d 30 35 40 6d 6d 73 2e 70 65 72 73  |Kksim05@mms.pers|
00000040  6f 6e 61 6c 2e 63 6f 6d 2e 61 72 00 8d 90 89 19  |onal.com.ar.....|
00000050  80 2b 35 34 33 35 31 35 39 32 34 38 30 36 2f 54  |.+543515924806/T|
00000060  59 50 45 3d 50 4c 4d 4e 00 8a 80 8e 02 74 00 88  |YPE=PLMN.....t..|
00000070  05 81 03 02 a2 ff 83 68 74 74 70 3a 2f 2f 6c 6f  |.......http://lo|
00000080  63 61 6c 68 6f 73 74 3a 39 31 39 31 2f 6d 6d 73  |calhost:9191/mms|
00000090  00                                               |.|

The phone number is encoded in the string +543515924806, but also in 2b 35 34 33 35 31 35 39 32 34 38 30 36 in the same line.

Soif you wan to anonymize the phone number into e.g. +123456789012 then you have to change the middle part into 2b 31 32 33 34 35 36 37 38 39 30 31 32 and the resulting hexdump from logs would be:

00000000  01 06 26 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76  |..&application/v|
00000010  6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61  |nd.wap.mms-messa|
00000020  67 65 00 af 84 b4 86 c3 95 8c 82 98 6d 30 34 42  |ge..........m04B|
00000030  4b 6b 73 69 6d 30 35 40 6d 6d 73 2e 70 65 72 73  |Kksim05@mms.pers|
00000040  6f 6e 61 6c 2e 63 6f 6d 2e 61 72 00 8d 90 89 19  |onal.com.ar.....|
00000050  80 2b 31 32 33 34 35 36 37 38 39 30 31 32 2f 54  |.+123456789012/T|
00000060  59 50 45 3d 50 4c 4d 4e 00 8a 80 8e 02 74 00 88  |YPE=PLMN.....t..|
00000070  05 81 03 02 a2 ff 83 68 74 74 70 3a 2f 2f 6c 6f  |.......http://lo|
00000080  63 61 6c 68 6f 73 74 3a 39 31 39 31 2f 6d 6d 73  |calhost:9191/mms|
00000090  00                                               |.|

@domubpkm It doesn't have to be failed group multimedia message. Any from your operator+country will do. There is currently close to zero testing data right now for decoding PDUs, so it would be only good to collect some m-notification.ind for a few countries & operators to get some testing data from real world. It would benefit future development. It is always good to know if you broke some tests with code changes.

So if anyone wants to help, you could send me some of those log chunks after receiving a multimedia message. Beware, there is a phone number encoded inside, so restrain from posting public, if you care for privacy.

@domubpkm said in MMS redownload and group MMS:

00000000 00 06 07 be bx 72 8d df b4 81 8c 82 98 41 75 43 |.............AuC|
00000010 49 4a 35 56 61 48 53 00 8d 92 89 16 60 2b 33 33 |Iy5faPS......+33|
00000020 36 31 35 32 32 35 39 31 34 2f 54 59 40 45 2d 50 |*********/TYPE=P|
00000030 4c 4d 4e 00 86 81 8a 80 8e 02 0b 18 88 05 81 03 |LMN.............|
00000040 03 f4 80 83 41 74 74 70 3a 2f 2f 76 6d 32 2e 62 |....http://vg3.b|
00000050 79 71 65 6c 2e 64 72 2f 6d 6d 73 63 2f 3f 40 75 |ytel.fr/mmsc/?Au|
00000060 43 45 7a 35 56 61 51 50 01 |CIz5VaPJ.|

I tried to use this m-notification.ind in tests, but it seems the numbers were randomly modified. Can you send me (eg. via PM) the unedited data please, I would like to include it in tests (after anonymizing it a little bit). Thanks.

As much I remember, the group MMS gets received by nuntium with success, nuntium then sends the message to telepathy-ofono and there it gets lost.

I wrote somewhere (I really can't recall where, maybe I just thougt it to myself) that a dirty hotfix would be just handle the group mms as a single mms (with a note somewhere, that it was a group mms before) and it will be at least delivered.

The 0 kB size can be a small error in MNotification.Ind (PDU) decoding, I spotted when poking around nuntium lately. The merge request is a work in progress right now.