@Rondarius Nice! Awesome to hear! I had seen others comment not getting their USB ports to work within Virtualbox (and I also had some trouble despite trying to configure it to passthrough). Great to know it was possible for you! I don't know why Virtualbox couldn't work with my USB (maybe I didn't have passthrough properly configured) and that is why I was going to try KVM/QEMU as another option.

@PierreM said: est-il nettement plus performant que le 4 pour la réception GSM ? Ça je n'en ai aucune idée je n'ai eu que le Fairphone 5 et je n'ai aucun problème de réception réseau avec. il n'est plus commercialisé par Fairphone car c'est maintenant le 6 et d'après ce que j'ai vu, Ubuntu Touch n'est pas encore "installable" dessus. Tu le trouves encore neuf à plusieurs endroits notamment chez ce gafam, je viens aussi d'en acheter un bleu d'occasion (350€) pour ma nièce en quasi parfait état, sur Leboncoin, où je venais de rater une affaire avec un bleu neuf à 400€... Je ne parle ici que du modèle 8/256Go, le 6/128 aussi tu le trouve encore neuf, et moins cher, mais je pense que 6Go c'est limite pour une utilisation à long terme. @domubpkm ce que fait volla est très bien, d'une pour la trésorerie de UBPorts, d'autre part pour aider à diffuser Ubuntu Touch. En revanche je pense qu'ils sortent trop de modèles, à peine le quintus sorti on a déjà le plignus, ensuite le support à long terme, logiciel et matériel, la facilité et donc le droit à la réparation, la garantie de 5 ans, c'est ce qui m'a fait me tourner vers Fairphone.

@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

@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

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?

@UBportsNews Is 24.04-2 supposed to be ready for click packages based on Qt 6 out of the box, i.e. without any Qt 6 related install_lib entries in clickable.yaml? If so, the clickable docker images should probably be adapted to contain a Qt 6 dev environment (but this might have to be discussed with the clickable maintainers). And a question regarding the lomiri-ui-toolkit snap: Any plans/timeline for lomiri-ui-toolkit-core26? DeltaTouch would really profit from Qt >= 6.6, but snap based on core24 only offers 6.4.

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.