@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 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.

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.

@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.

For those who use crossbuilder for development, the ssh deployment pull request has just been issued. It allows you to deploy your code to device via ssh (wi-fi) instead of adb (cable), using the --ssh option.

Feel free to test, complain and/or enjoy.

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.

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 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

Hello, today I updated to new RC (v146) and after restart all the contacts were gone. Except a few (5-6). When reverted back to stable, all the contacts were back again.

Has anyone experienced this?

Thanks.

@ogogon said in How to transfer configuration and data to another phone?:

Unfortunately, I did not find the content of my SMSs in the history.sqlite database, only a huge number of very strange links.
I think you are confusing something...

The messages are in text_events table. This is what my phone returns if asked for last text message (text & numbers redacted):

phablet@ubuntu-phablet:~$ sqlite3 .local/share/history-service/history.sqlite 
SQLite version 3.11.0 2016-02-15 17:29:24
Enter ".help" for usage hints.
sqlite> select * from text_events order by eventId desc limit 1;
ofono/ofono/account0|+401901123456|2022-05-16T20:12:57+0200-18|+401901123456|2022-05-16T18:12:57.000Z|0|This is the redacted text of the message.|0|0|||0|2022-05-16T18:12:57.000Z
sqlite> 

@kugiigi said in How to manually change the screen orientation ?:

@jezek I created a separate repo. Check the ManualOrientation under Lomiri.

Thank you.

@kugiigi said in How to manually change the screen orientation ?:

@ub I was able to create a patch where if rotation is locked, it'll switch to portrait when unlocked, it'll switch to landscape. You can try the script I created (https://github.com/kugiigi/jerk-installer) to easily install and uninstall it or I can provide you the single QML file for it. Not yet sure where to put the files though. If you have telegram, I can send them to you.

Put it somewhere public (in jerk-installer/sample-packages?) please. Last week I thought such feature (manualy rotate screen if rotation is locked) would be great for me. I now I read you made something similar. I would like to try it too.

Thanks.

@lduboeuf said in Test alternative pin code prompt - system settings integration:

and i've already tested random digits, it is more annoying than helpful, it takes too long to find your digits ...

Pardon my intrusion. Maybe they don't have to be random, they can be rotated by random places (the order will be preserved), have you tried that?

But I agree, that can wait.

@fizz Hello, I've been able to make a test using the approach described above. The test was done in stable channel (OTA-22) after reboot and the commands have been punched via ssh.

1. I sent myself a testing multimedia message via the nuntium-inject-push testing helper tool.

   phablet@ubuntu-phablet:~$ sudo ./nuntium-inject-push -s +421908353517 --sender-notification +421908353517 --transaction-id test-wget --error-activate-context=1
   [sudo] password for phablet: 
   No end-point flag provided, trying to retrieve end-point from nuntium logs in: /home/phablet/.cache/upstart
   Using endpoint: ":1.55"
   Creating web server to serve mms
   Denial count: 0
   

   The notification was delivered to messaging-app
   

2. I looked at the ~/.cache/upstart/nuntium.log

   phablet@ubuntu-phablet:~$ tail .cache/upstart/nuntium.log
   00000060  39 30 38 33 35 33 35 31  37 2f 54 59 50 45 3d 50  |908353517/TYPE=P|
   00000070  4c 4d 4e 00 8a 80 8e 02  74 00 88 05 81 03 02 a2  |LMN.....t.......|
   00000080  ff 83 68 74 74 70 3a 2f  2f 6c 6f 63 61 6c 68 6f  |..http://localho|
   00000090  73 74 3a 39 31 39 31 2f  6d 6d 73 3f 65 72 72 6f  |st:9191/mms?erro|
   000000a0  72 2d 61 63 74 69 76 61  74 65 2d 63 6f 6e 74 65  |r-activate-conte|
   000000b0  78 74 3d 31 00                                    |xt=1.|
   2022/03/11 18:10:19 This is a local test, skipping context activation and proxy settings
   2022/03/11 18:10:19 Forcing debug error: main.downloadError{standartizedError:main.standartizedError{error:"error-activate-context", code:"x-ubports-nuntium-mms-error-activate-context"}}
   2022/03/11 18:10:31 Received unknown method call on org.ofono.mms.Message MarkRead
   2022/03/11 18:10:31 Message /org/ofono/mms/231014453153205/cb2e5a6911b100a99a13927694308474 is not responded and not expired, not deleting.
   

   and extracted the message UUID cb2e5a6911b100a99a13927694308474 and download link http://localhost:9191/mms.
   (Note: in the log there is "?error-activate-context=1" in the url. This is a testing string specific for the nuntium-inject-push tool and I know it's safe to remove. In real world usage use the whole link)

3. I downloaded the message content with wget using the download link into the storage as <UUID>.mms

   phablet@ubuntu-phablet:~$ wget -O - http://localhost:9191/mms > ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.mms
   --2022-03-11 18:23:50--  http://localhost:9191/mms
   Resolving localhost (localhost)... ::1, 127.0.0.1
   Connecting to localhost (localhost)|::1|:9191... failed: Connection refused.
   Connecting to localhost (localhost)|127.0.0.1|:9191... connected.
   HTTP request sent, awaiting response... 200 OK
   Length: 3405 (3,3K) [application/octet-stream]
   Saving to: ‘STDOUT’
   
   -                                      100%[=========================================================================>]   3,33K  --.-KB/s    in 0s      
   
   2022-03-11 18:23:50 (79,2 MB/s) - written to stdout [3405/3405]
   

   And checked, if there is the file in the storage folder. (Note: I've also appended, what the files look like.)

   phablet@ubuntu-phablet:~$ ls -l ~/.local/share/nuntium/store/
   total 8
   -rw------- 1 phablet phablet  653 mar 11 18:10 cb2e5a6911b100a99a13927694308474.db
   -rw-rw-r-- 1 phablet phablet 3405 mar 11 18:23 cb2e5a6911b100a99a13927694308474.mms
   
   phablet@ubuntu-phablet:~$ head -c 200 ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.mms 
   ���test-wget���abcdefghipqrrst�TZ�7��+421908353517/TYPE=PLMN��application/smil�<smil>/�+pplication/smil�smil.xml�smil.xml�"<smil><smil>   <head>     <layout>         <region id="Image
   
   phablet@ubuntu-phablet:~$ head ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.db
   {"Id":"test-wget","State":"notification","ContentLocation":"http://localhost:9191/mms?error-activate-context=1","SendState":null,"ModemId":"231014453153205","MNotificationInd":{"MMSReader":null,"UUID":"cb2e5a6911b100a99a13927694308474","RedownloadOfUUID":"","Received":"2022-03-11T18:10:19.122527716+01:00","Type":130,"Version":144,"Class":128,"DeliveryReport":0,"ReplyCharging":0,"ReplyChargingDeadline":0,"Priority":0,"ReplyChargingId":"","TransactionId":"test-wget","ContentLocation":"http://localhost:9191/mms","From":"+421908353517/TYPE=PLMN","Subject":"","Expiry":"2022-03-13T18:10:18.122527716+01:00","Size":29696},"TelepathyErrorNotified":true}
   

4. I edited the ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.db file and changed the State to "downloaded" and TelepathyErrorNotified to "false".

   phablet@ubuntu-phablet:~$ sed -i 's/"State":"notification"/"State":"downloaded"/' ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.db 
   phablet@ubuntu-phablet:~$ sed -i 's/"TelepathyErrorNotified":true/"TelepathyErrorNotified":false/' ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.db 
   phablet@ubuntu-phablet:~$ head ~/.local/share/nuntium/store/cb2e5a6911b100a99a13927694308474.db
   {"Id":"test-wget","State":"downloaded","ContentLocation":"http://localhost:9191/mms?error-activate-context=1","SendState":null,"ModemId":"231014453153205","MNotificationInd":{"MMSReader":null,"UUID":"cb2e5a6911b100a99a13927694308474","RedownloadOfUUID":"","Received":"2022-03-11T18:10:19.122527716+01:00","Type":130,"Version":144,"Class":128,"DeliveryReport":0,"ReplyCharging":0,"ReplyChargingDeadline":0,"Priority":0,"ReplyChargingId":"","TransactionId":"test-wget","ContentLocation":"http://localhost:9191/mms","From":"+421908353517/TYPE=PLMN","Subject":"","Expiry":"2022-03-13T18:10:18.122527716+01:00","Size":29696},"TelepathyErrorNotified":false}
   

5. I restarted nuntium (should be the same as restarting the phone)

   phablet@ubuntu-phablet:~$ initctl --user restart nuntium
   nuntium start/running, process 10665
   

6. There is the message instead of notification in the messaging app.
   

Here you can see the relevant logs produced in this test for comparsion.

For the record, I've also encountered a case, where the message was not delivered to messaging-app after restart, but it was due to bad wget usage, which produced an empty .mms file. So maybe if the file is somehow faulty, the message is not shown. This needs more investigation.

@fizz said in MMS success and failure:

Actually, the .db State is now "received" (not my doing). TelepathyErrorNotified is still "false".

The "received" state means that the messege was forwarded to messaging-app, which is strange that it is not there. But more strange is, that I don't see any error in loggs, so the message should ended in "responded" state. As I said I have to test this approach on my phone.

Thank you for answering my questions. I'll write you, when I know more.

@fizz Hmm. I'm not smarter from the log. I'll have to test by myself. I'll come back to you.I hope it'll be soon.

Meanwhile, please, could you write me, what is the state of the message .db, you have modified? Is it still "downloaded" and is the telepathy notified field still false? Thanks.

@fizz Can you post, or PM me the ~/.cache/upstart/nuntium.log, please?

another workaround is to copy to clipboard an empty string, or just a dot or something meaningless.