@wgarcia said: it looks dependent on type of connection and maybe operator? I have a FP5 with Freemobile in France and I don't see this problem. BTW, I have posted on the 26.04 a trick to see the ofono data on which the indicator is based but it did not get much traction, only one person posted a few data and it did not seem that the indicator itself was at fault, it looked as more or less reflecting the underlying ofono data (so something that may depend on the operator or even connection type).

@CyBerT Perhaps some Waydroid logs would be useful at this point?

@sixwheeledbeast said: OMEMO MUC Next major item on the list. All the pieces are present, just need to assemble them correctly. In band registration I consider it lower priority: something for app stable release, but not for alpha -> beta graduation. Although it's a barrier to new users, it's possible to register elsewhere. However, if someone wants to contribute it earlier, hey ho let's go. support multiple accounts Coming soon to a .click near you audio/video calls? Faaaaaaaaaaaaaaaaaaar away. If Libervia is a backend is there a possibly it could be merged into the existing messages app? Anything is possible. But I won't be doing it. I don't know how the Lomiri messaging app is constructed, exactly, and if it's specific to SMS/MMS or not.

@linl OK, it seems there are problems, meaning restrictions from maybe your country (or maybe USA, or both, I don't know where the download servers are hosted), that can prevent installer to download properly. Another topic is already opened about this problem. https://forums.ubports.com/topic/12174/mirrors-for-users-in-russia/21?page=2 I'll merge yours with it. Please be patient, the issue is already known, but UBPorts team don't have much ressources (in any kind) to react like gafams can (but may not), and this may need a new version of installer, servers, mirrors, or whatever. Feel free to read thread and continue here, and maybe go to the russian telegram UBPorts help channel mentioned in previous post.

@brenno.almeida There is also this heart that appeares now when the other person reacted to my text (circled in red) - so I can see now their reaction: [image: 1781726172408-screenshot20260617_225249232.png]

@brenno.almeida said: @projectmoon @amaurydbz we just got the patches released in original Futify. Would you mind checking if the updated store version works for you? Thanks I'm still logged in to regular Futify from long ago. I played a song this morning and it worked. But then I did a search for a playlist, and played it. But it would go through each song for 2 seconds, without actually buffering or playing it.

@Ida_ Thank you very much! Unfortunately, at the moment, this does not help me understand what happens on 24.04-2.x

@KoJans said: Does that mean that I also have to install the fastboot package on my PC? yes sudo apt install fastboot if you use a Debian like distro.

@DJac said: En pratique, l appli est bonnes, mais je n ai pas accès aux messages : La boite de reception ne correspond pas au contenu de celle du site. je n y trouve que les messages 'officiels' de blablacar et aucun des messages de mes passagers. Je serai intéressé de savoir ce que donne l'application sur UT 24.04-2.x si quelqu'un test à un moment ou à un autre! Est-ce que la messagerie fonctionne? ( Ca indiquerai que l'app bénéficie du nouveau moteur Qtwebengine 6 )

@mariogrip FP 5 build 105 serious regression issue on mms ? have confirmed by switching back to 24.04-1.3 stable, can send and receive a mms to an Android phone, switch again to 26.04, failure to send and receive. Astonishingly the Android phone report a failure to send (it has no issue sending to UT 24.04 or another Android phone). I say 'astonishingly' because I had always thought that MMS were asynchronous (the Android phone has RCS disabled) On UT 26.04, trying to send a MMS leads to a spinning blue circle next to the text, spinning that never stops. these tests were done in both cases with wifi OFF (but it don't work better with wifi on) log: sendingmmsfrom2604.txt (I replaced the phone number of the UT phone by 26042604 and the one of the Android phone by 00000000)