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

@Linus67 said: rm -f ~/.config/systemd/user/ubconnect-daemon.service Thanks to this hint, I knew where to find it and removed it using the file manager. All clear now! The advantage of using the GUI in this case was that it showed me what else lived there. There was another daemon that was no longer needed. So that was helpful.

@AntiMS said: That's especially surprising given that the device page indicates VoLTE isn't supported. Yes, but keep in mind that device pages can (and often will) lag behind reality. They're not automatically updated and sometimes it takes a while.

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