@brenno.almeida Thanks a lot for this great app! I get the impression—purely subjective, mind you—that the app uses quite a bit of power. Do you think it would be possible to add an option in the settings to set the refresh rate for new messages (or even to stop it unless I check manually)? Or am I mistaken? What do you think?

Buddy, is anyone already working on this device? What’s still missing, and how can I help?

Hi, I started two days ago to unlock my poco x3 nfc No problem for the firsts steps for me I already had an account bcs my previois phone was a Xiaomi (used in france with classical android/miui, account region in France) So I linked this account, and with the python "miunlock" package (on my personal Linux Mint computer), I passed all the first steps with no problem (I also have a french sim card with data, sms, mms, calls) I'll give news next week after the regular 168h required on my phone

@Persinto Wait, that's for porting (= creating installation files for a so far unsupported device), not for installing. Is porting what you are wishing to do? It's not clear to me because you haven't mentioned porting at all.

Glad I could help, and good luck on your installation!

is there a way to move to the stable channel? in the settings & wiki i can only find the daily channel..

@Moem said: I will repeat what I've said elsewhere: I will bring this subject to the table in the next meeting of the Board of Trustees. That's what I can do and I'll do that. Until a possible workaround is found, it seems appropriate to notify users of the installer. I have therefore created the following ticket: https://github.com/ubports/ubports-installer/issues/4565 Since other countries may also be affected, it would be helpful to know which ones. I have therefore created the following thread: https://forums.ubports.com/topic/12291/internet-access-restriction-for-ubports-installer-list-your-country That's what I can do, and I did it

OK, yet another test. I just tried connecting the Quintus to my main UT phone (the Pixel 3a, Focal). during discovery, the Pixel appears in the list of neighbouring devices on the Quintus (and the Quintus on the Pixel) when I tap the Pixel in the list on the Quintus, I'm asked to confirm the PIN on both devices, which I did the Pixel then moves to the "Paired devices" section on the Quintus, shows connected for a few seconds then returns to "disconnected" on the Pixel, it remains in the list of neighbouring devices (and a notification is re-issued for the last received SMS, which was left unread) Tapping the Pixel then tapping "connect" causes the following: the Pixel shows as connected for a few seconds on the Quintus, then it returns to its "disconnected" state nothing changes on the Pixel on the Bluetooth settings page, but a notification is re-issued for the last received SMS (strange, I know, but I got that same behaviour twice).

Yesterday all of our SIP in Germany stated, that they will shutdown MMS at the end of June. So it's important to have an alternative as RCS for people who need this kind of service.

@domubpkm I had to move the number back into the info string. Some translators raised issues that the separate number breaks translation in their language. So we are using this "<b>%1</b> files found, swipe an entry for file info and delete options" variation now. Still translatable and a bold number. Not perfect but should work.

@AntiMS The experimental Halium 12 build has two reports of succesfull VoLTE - both originating and receiving (non US), and several one way only calls with or without audio. I personally have tried it with all three US networks. Verizon has trouble, but with both T-Mobile and AT&T networks you can receive calls with audio in both directions. However, making a call fails and the dialer hangs. Logs were sent to the porter, and it is suspected that this is an ipv6 vs ipv4 issue. We can help you more efficiently if you join the ubports NA Issues Telegram channel.

@uxes It's a feature, taken from the click documentation: 4.3.2 Specification • Only system packages (i.e. .debs) may declare hooks. Click packages must be declarativeinclude code executed outside AppArmor confinement, which precludes declaring hooks.

I found the reason for my increased battery drain when using Wi-Fi. On January 26, 2026, I installed an app called "UB Connect" from the OpenStore. ubconnect I uninstalled it shortly after. The app wasn't uninstalled cleanly, and a ubconnect.daemon.service remained in the system. Whenever Wi-Fi was turned on, this daemon would automatically start, but it failed because the app was missing. This prevented Ubuntu Touch from going into power-saving mode after the screen was turned off. After uninstalling and deleting all leftover files from the ubconnect app, Ubuntu Touch goes back into power-saving mode with Wi-Fi on, and the battery consumption is minimal like with mobile data.

One last update to the links in the original post. There is now sound/music with an option to turn it off. Hope you enjoy it! Not getting any more feedback, so I presume there are no more bugs? If I don't hear anything else I will release it to the open-store in the next day or two. Thanks for testing!

@gpatel-fr I just tested it now with sms and it works - it uses the new selected Meesage sound. So it is only for notifications from apps (like Dekko, Greenline) that the Message sound is not updated unless a reboot. It starts to sound more like a bug?

@mihael tested with dekko. I think it's a bug, it don't seem logical that silent mode mutes the rings but not the messages.