@gpatel-fr Oh, wow, I would have never thought of checking after a restart... Let me just link that here: https://forums.ubports.com/topic/12289/changing-message-sound-requires-restart

@lduboeuf Many thanks for the suggestions & help Actually, when I got the problem, at first I tried removing the whole conversation. Then, I tried sending another SMS to the same contact, which re-created a new conversation, but that SMS got stuck too (spinning wheel), which made me think there was some service lomiri-messaging relied on that was somehow stuck, maybe ofono (pure conjecture on my behalf). Following your sugestion (a few hours later), I tried to delete the blocked message, then again the whole conversation, and then sent another SMS to the same contact and this time, it worked. So AFAIK, problem solved, but I do not know why. I tried to look at the traces by doing a journalctl | grep lomiri-messaging > somefile.txt but I got 2MB worth of traces. I tried to grep -i 'error' or 'invalid' but I do not know exactly what to look for. Lines which appear suspicious to me (but may be completely unrelated) are: juin 02 14:38:27 ubuntu-phablet lomiri-messaging-app[95339]: QSocketNotifier: Invalid socket 19 and type 'Read', disabling... ... juin 04 17:58:56 ubuntu-phablet lomiri-messaging-app[16850]: file:///usr/share/lomiri-messaging-app//MessagesListView.qml:87: TypeError: Cannot read property 'left' of null ... juin 04 12:05:42 ubuntu-phablet lomiri-messaging-app[11099]: error calling result "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.103" (uid=32011 pid=11099 comm="lomiri-messaging-app message:+XXXXXXX" label="lomiri-messaging-app (enforce)") interface="com.lomiri.libertine.Service.OperationsMonitor" member="result" error name="(unset)" requested_reply="0" destination="com.lomiri.libertine.Service" (uid=32011 pid=4480 comm="/usr/bin/python3 /usr/bin/libertined" label="unconfined")" juin 04 12:05:42 ubuntu-phablet lomiri-messaging-app[11099]: lastError - no arguments? ... No sure this is much help. I will experiment again with MMS and post back on this thread if find something useful

@gpatel-fr anyway thanks for your lines and good to know, that the problems with tones is frequently.

@CiberSheep o joy I can post again. don't worry. watching this whole interaction has put me off on sharing here. Ill still be hacking on ubuntu touch but I wont bother you guys anymore.

Hallo Pparent, thanks for the hint

gpatel-fr said: I realize belatedly that I did not think of giving some advice about the problem of returning back to a newer version once the goal of revert to a previous one has been achieved. It would be easy to imagine that it will be easy, but it's not as straightforward as following the usual procedure. When going from 1.1 -> 1.2 -> 1.3, history of these upgrades was recorded. If the phone is rudely returned to 1.1 and the user asks it to update back to 1.2, it will look at this history and conclude 'I have nothing to do !'. So the way to go in this case is to delete all this history in the lower part of the phone screen by swiping to the right and pushing the red trash button for all theses updates, and then the normal update behaviour will be restored back to normal.

@ubuntushop said: Why not just fix the problem.? You mean instantly ? How could that happens ? This sure will be fixed, but be patient, this is not a trivial task to maintain and fix such an OS with so few Devs involved...

Please use pure English on forums, use deepl if you need translation. And avoid double posting. And you should go on Google play site if you search for a number to reach them. I don't know it.

@PhAndersson said: the Pixel is able to get its time from the traditional GSM networ My memory is a bit dim on the subject and it's all hearsay anyway, however I remember I was said otherwise. Sorry to not be more precise however my meter says that I posted 563 posts in 9 months, so I finding precise details in the answers I got in all theses threads is not an attractive proposition. It could be that the Pixel is able to save clock and this ability was lost on more recent phones. @PhAndersson said: use your phone as alarm clock when you travel not sure it's a huge priority - there is an obvious workaround: do not stop your phone during the night.