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

Perrete said: @nogoogle I have a similar issue, gps is no longer detected. It happend to me after installing Navius navigation app. But I'm not entirely sure if the app is responsable for my GPS dying. I would really apreciate assistance here, since the only option I see is reflasing and I would like to avoid that. I can confirm the app broke my gps.

GPS broke after installing Navius. test_gps returns *** setup signal handler *** get gps interface *** GPS interface not found Bye! It's such a shame, since the app seemed promising. I have a feeling this is going to be a challenge to fix, I'll keep you posted. If there is any aditional info I could provide to help resolve the issue or prevent this problem from affecting anyone else please tell me. Device: Fairphone 5 Ubuntu touch version: 24.04-1.3 Navius GPS version: 1.0.4

@turtle_racer Thanks for the Answer. I already have the basics of UbuntuTouch on my phone. The installation always stops at the last point "Flash"... could this be related to a correct USB connection? Since the mobile phone's controls work from the Linux PC via Terminal and ADB, the question is whether the USB connection is lost? Fastboot Mode PROD_NAME = lito, VARIANT = SM_ UFS, SERIALK NR = BA596ED6, SECURE BOOT = YES, DEVICE STATE = UNLOCK Attached are the steps one after the other that I do with the software on the PC (UBports Installer) From picture 2 the USB connection is gone ? and in picture 3 "Fastboot" I select the item "Reboot to Bootloader" and am in FASTBOOT MODE! But without USB connection. Even if I unplug and replug the cable, USB won't connect! Picture 1 [image: 1782647145317-ut_1.png] Picture 2 [image: 1782647171405-ut_2.png] Picture 3 [image: 1782647193730-ut_3.png] Here is the entire error_line: Error: fastboot: flash :error Error: Flashing failed : {"error":{"code":1}, "stderr":"FAILED (remote: 'Flashing is not allowed for Critical Partitions')fastboot: error: Command failed"}

@kristatos yes however logging happens at the generic journal level, there is no prefix to filter on. Entries are listed under 'aa-exec' and usually include the app name (ratatoskr) in the listed paths, you can try journalctl -b | grep ratato There is also logging done by obex that you can list using systemctl --user -e -u obex

@PierreM Bonjour PierreM. A titre d'info, https://volla.online/en/volla-phone-plinius/ . Voilâ un smartphone tout récent qui supportera dans le temps les futurs développement d'UT. C"est aussi un investissement, mais pour un smartphone avec UT préinstallé, tu pourras si nécessaire joindre les développeurs de Volla. https://devices.ubuntu-touch.io/device/ansuz/release/noble/

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.

@sambk Have you had any luck?

Those still requiring a token after converting to the global ROM, can you check if the boot loader image flashed? Maybe try flashing it manually. Ruben says it should be called LK.IMG Ruben thinks it might not have flashed, and reflashing it might unlock it without token.

@777X yea i am using localsend now and then, its a nice clean application if it works xD