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

@domubpkm Haha, yes, this way we never get a new release. No, thanks for that. Without testers and issues the errors stay. I did drop the created date, something is funny about that. And I think its not that important to add.

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!

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.

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

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.

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!

@sixwheeledbeast I guess what I was pointing more toward is that there are situations or people that need a more predictable control panel. To be clear, I like the panel and the one hand scrolling. Its gorgeous to look at and most of the time its convenient. But it does mean that it is not good in emergencies. For example: say I urgently need to: Turn on wifi. I know to flick down just right of the camera notch, and the toggle is reliably about halfway down the page. access system settings. I try to flick down from the right top corner but what page I land on is a bit of a lottery. I then need to scroll to adust the pagu before I can do what I need. It is even worse for the items to the far left on the menu.

Sorry for bringing up a 4-year-old post. I tested three Pixel 3a devices (RC 1.3). I noticed exactly the same battery drain issues described here. Have any solutions been found for this yet?

@nbdynl Directly donating money is always an option but I did try this last year and I got very little engagement from the community. I had asked for a 'promise to donate' rather than sending the money to anyone so there was effectively no risk for the donors as they would donate to the winner directly. When I asked for people to dedicate time or effort to create a reward (images, logos, etc), I got much more engagement. This is great but it can't scale well if you want to get more than 5 people contributing to the reward.

@RJDan here is a link to the last (2023) post done by a NodeBB member about it.

@projectmoon exactly i dont mind confinement anymore as i used complain because i didnt understand now i do and i see ALOT of missing api thats why i made "workspace" --->still needs lots of testing but i have to say im not happy having to make a workaround solution ....as it kinda breaks the whole design point ..

@messayisto said: You can set this individually in Dekko -> options. Go to Identities -> Signature Thank you for the tip. And I realise that, using the method you’ve described, it can be done with Mailo, for example, which is an app available in the UT Open Store...

Hi @danfro, I just wanted to point out that someone has to take on the task of porting it; it’s a huge undertaking, and there’s a chance it might not work out in the end. And, who here is willing to do the groundwork and look up the author’s questions? Greetings Mario

Now the led notification issue has been resolved, it’s working 99% of the time… and this could be fixed on the device list for the OnePlus 5T Thanks to everyone who worked on this.