gpatel-fr said: libicudata.so.74 looking a bit more at this issue, this comes from the operating system upgrade: Ubuntu 24.04 comes with libicu74 while 26.04 uses libicu78. Ubuntu 26.04 don't have libicu74, so don't seem to be able to use some binaries built for a previous Ubuntu version. The use of snap in Ubuntu is something of a workaround this problem I guess while click format was designed before the rise of snap/flatpak with their library packages.

@PhAndersson said: Could it somehow be related to the fact that the clock is now reasonably synched? I don't think so, for the following reasons: I did give you the hint about recreating the connection, and I don't have a mediatek device date problems for ssl come from the securing through a certificate infrastructure, that don't make much sense for Bluetooth, whose hacking radius is 10 meters vs 40000 km for standard internet networking updating certificates and certificates lists would be unfeasible for many Bluetooth devices that don't even have an Internet link This said, if you want to try it out, it's easy: just re-enable the qualcomm time service and check again.

Dear @luksus - are you planning to release the Ubuntu Touch 24.04, please? Thank you and I wish you All the Best.

Dank @Sander! Radio NL en Radio BE zojuist geinstalleerd. Als je van klassieke muziek houdt is het Belgische Klara een aanrader.

@Keneda said: plignus plinius

@fischer.poco Yes that is right. You install 10.5.7 with MSM Download Tool, this means that the entire OS is replaced and all data deleted. And then install UT.

@nbdynl Thank you again for your replies. You are right, the app actually works great.

It did NOT break my GPS in fact I'll give you a rundown of what I did to get to my original conclusion. Installed Navius having used my GPS with other apps (like PureMaps) before. Saw Navius not getting a GPS signal even though I was outside for a while (15 to 20 minutes). Saw PureMaps not getting a GPS signal even though I was outside for almost 40 minutes. Then I panicked (since I really need GPS on my daily) and searched for information on how to fix the issue, then I found out about the test_gps command and saw it showed the above message. I tried changing locations, rebooting, taking the battery out, changing update channels and I was seriously considering having to re-flash my phone but I saw a post about someone saying that the test_gps command is unreliable and can miss-report GPS functionality. In the end I moved to a more populated area with better satellite signal (apparently) and I got my GPS working again after a bit of waiting, even though the above command said otherwise (and it still gives me the same output). I feel like I ow the developer an apology . I wish I could edit my original reply. I'll be giving the app a good shot now and share my feedback! But really what is wrong with the test_gps command? Any idea why it works for some people and not in this particular case?

New Release: Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases Github mirror: https://github.com/brennoflavio/greenline/releases You now can translate Greenline for your language, go to UBports translation project and feel free to contribute https://hosted.weblate.org/projects/ubports/greenline/ Many thanks for UBports admins to make this happen. Changelog: Animated stickers now renders correctly Fixed a bug where the name and photo in the notification was not shown correctly Now you can start new chats. Either by inputting a phone number or importing a contact into the app Translation support Progress towards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

@MrT10001 bro you unbrick it with mtkclient

I found a procedure online, restarting snapd, removing locks. That didn't work. Rebooted. Didn't fix it. Manually removed snap in home. Rebooed. Nope. I managed to install again and then remove it. That fixed it.

@Persinto since you want to use it as android phone, then any

@Moem Looks promising, It could be just what I need. Thank you!

@KoJans said: That worked in a few minutes outside. Glad to hear it!

Thanks for the hint. Yes, both work correctly. The physical volume buttons change the playback volume. The system volume slider (volume indicator) also changes the playback volume. Only QMediaPlayer::setVolume() has no audible effect, although the property itself changes correctly. So it looks like the backend ignores the player's volume while still using the system media volume.