@klh Wow! Cool that you tried. For me it seems to happen mostly on first use shortly after a reboot so far, but it did happen one time many hours after the last reboot too.

@sixwheeledbeast said: audio/video calls If this is high priority for you, you might want to give DeltaTouch a try. Earlier this weekI tried a videochat with a friend who was using DeltaChat on /e/OS, and it worked fine.

@pparent ok, je vais essayer. Mais je rentres que Dimanche chez moi. Je ferai un retour.

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

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

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

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

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

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

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

@PhAndersson I have just switched my phone back to 24.04-1.3 and obex is definitely started automatically.

@Vlad-Nirky No, the quota limit is the number of unlocking request per day that Xiaomi approves. I read somewhere that it was set to 2000 requests per day. It seems that millions of people are waiting till midnight in Beijing, because the limit is reached instantaneously. However, according to what is written in the Xiaomi community app this procedure, and hence the limit, is for devices running HyperOS. In my case I am running MIUI12. EDIT: I read contradictory info about the number of devices one can unlock, but this is the first and only one I want to unlock.

@dl8aax said: @Vlad-Nirky said: Could you give some more details about the database to be backed up? Which application is it for? I'm creating the database with: var db = LocalStorage.openDatabaseSync("MienImmen", "1.0", "", 1000000); Because there's also important data, I want to back up the database and import it to my PC. Swapping the database is less error-prone than exporting and importing individual tables. There are approximately 40 tables. App databases are stored under the app namespace, e.g if your app is called "abd.xyz", you should either find it in ~/.local/share/abd.xyz or under ./config/abd.xyz

@gpatel-fr phablet@ubuntu-phablet:~$ uname -r 5.4.289-qgki-gcfce8884187a

@skipperkeith hello again, i have successfully installed waydroid: i installed waydroid helper from the openstore selected 'install waydroid' this time the download finished without incident (my earlier failures might have resulted from my mobile data hotspot's variable moods) messages were obvious and showed success but... once installed and opened in landscape mode, the screen was oddly divided and flashed the word 'waydroid' in a corner. not functional at all. finally... restarting the tablet in portrait mode, waydroid loaded, with the good old lineage boot graphics, and my ubuntu touch tablet became an android 'phone.' i'm typing this within duckduckgo browser (from aurora store) installed in lineage os running android14 in waydroid on the ex-android11 lenovo tablet, with its new base os - ubuntu touch - only a swipe away. brilliant! so far, performance is pretty good! even the windy (weather) app, with its impressive graphic displays, is perfectly usable. duckduckgo now syncs itself with my mac and android versions. great things seem possible, but i won't rush to load it up with apps like a new 'phone.' i'm impressed! waydroid helper is only one method of installing waydroid, but is also useful for stopping a waydroid session, and more. here's hoping my experience at least encourages you, and maybe others too. cheers, KJU

@gpatel-fr I guess, when all will be ready, that Ratchanan will give the go to use QT6 in clickable with the next framework as he did for 24.04.

@Lazarus2026 wel yea seems like, but i see you have one support porter already xD. its a pity, i am not a developer aswell, and i do feel like it is a great experience doing one sometime... but i dont think anyone can do that without the device. there is plenty of help and support once you read the porting document because i believe porters do help eachother...

The behaviour of the Quintus seems related to this Gitlab issue: Bluetooth sometimes in a state where not all paired devices are listed and can be connected