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

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

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

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

Gentlefolks, It seems that tension is rising for no good reason. Let's leave this be before things get out of hand. 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.

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

Just made a new test in the office, where I'm surrounded by an ocean of bluetooth devices. Both when using bluetoothctl | scan on and when using the Bluetooth page of the Settings app, tons of neighbouring devices are detected, so the bluetooth stack itself seems functional. But requesting to connect to the laptop still times out. I've also compared the output of bluetoothctl | show on the Quintus (Noble) and on the Pixel (Focal), but I've not noticed any difference there that seemed significant.

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!

Thank you again for this app! If I can draw attention to one detail (I don't want you to be overwhelmed with requests): The app somehow refreshes itself at a few seconds interval. That makes that, while I scroll down the list of messages in order to look for an older conversation, suddenly the app takes me back to the top. I think the same thing happens inside a conversation when there is a long message and I click on "read more" - after a few seconds the message collapses again. I opened an issue for it: https://github.com/brennoflavio/greenline/issues/4 Again, a big thank you!