@moem All though the app doesn't run 100% on 2.x at the moment, I use it to check messages whenever my Signal bridge is a bit under the weather. It always starts after a couple of tries. I am so grateful for all the effort you put into this, @pparent , thank you!

@kristatos Gute Nachrichten! Ich habe festgestellt, dass ich die Bluetooth Verbindung mit dem Autoradio in den UT-Bluetooth Einstellungen mit dem Entfernen Button gar nicht wirklich löschen kann. Ich habe dann nach anderen Möglichkeiten gesucht, um die Verbindung zu entfernen. Mit diesen Befehlen habe ich die Verbindung entfernen können. $ bluetoothctl $ devices $ remove MAC_ADDRESS Danach habe ich das Pixel 3a neu gestartet und versucht eine Bluetooth Verbindung mit dem car-audio herzustellen. Diesmal hat es beim ersten Versuch geklappt. Sounds good! Die Funktionalitäten mit Anrufen und Adressbüchern habe ich noch nicht getestet. Hat für mich aber nur eine untergeordnete Priorität. Ich vermute, dass der erste Verbindungsversuch vor Wochen gescheitert war, aber noch irgendwelche Konfigurationseinträge eine neuerliche Koppelung verhinderten. Erst durch die saubere Entfernung der korrupten Verbindung und einen Neustart konnte eine neuerliche Verbindung erfolgen. Vielen Dank für deine optimistischen Antworten. Sonst wäre ich vermutlich nicht mehr bei dem Regen zum Parkplatz gelaufen. Und morgen hätte ich wieder die Kabelverbindung angestöpselt. (wie in den 80ger Jahren)

Ok. Like I uinstall my debian for lmde, I will try laaaaater. It is possible that I have a probleme with the gpu driver : I try to solve it in lmde.

@developerbayman to be honest, neither you nor I know what the community would or wouldn't mind. I am somewhat confused though, you appreciate that there are no adds, yet you wonder why there aren't any. If you can mention any product or service that has increased user satisfaction by including adds, then maybe we can have that conversation.

@oldbutndy said: As long as everything it generated was open source, so it could be reviewed. Otherwise, unsafe. The problem is, that there is no way to tell. We don't know what the AI was trained on. So we can't know if what it reproduces is in violation of any licenses, proprietary or otherwise.

@arubislander OK. Darn !

@Bolly Not harsh at all. But we had to go through the process of warning the user and seeing where things went. Where they went warranted intervention. The situation has now been dealt with and we have posted our stance on the matter going forwards.

Is it worth considering starting again? Installing the correct Fairphone Andriod version listed on the ubuntu-touch website and following the install procedures for 24.04 stable? I have none of the issue you mentioned in your multiple threads with my fp5. The only outstanding issue is the fingerprint reader for me at the moment on stable.

I agree with Cibersheep here. It's not part of the OS design to have a global back button like Android and not a requirement due to the edge OS controls. Yes the in-app back being top left is awkward positioning for one handed use but I would find it more annoying that a window was closed/disappeared by accident from some other inconsistent close or back positioning. I'm not against a top swipe for back on top of the standard style back, like in openstore Timer app but really following the development guidelines and being consistent between all apps is the important thing.

Thanks for the tip @OtaDr , but it looks like I have a corrupted FASTBOOT (black screen).

@k.nacke im finally back with the tablet, can you teach me how to port a device

i am doing a app for this in the future called pysync ...i may rename it for UT ...hmmm UT-sync?? .....the app is built but very broken right now and not a priority ...it will do the same thing as syncthing ...well i hope anyways UT design can throw a wrench into things

@Escain this is precisely what i am experiencing as well on fp5! @devs please fix!

@Moem said: @oldbutndy Sorry, no idea! I would hope that someone looking for information would get their info at the source: our webpage. Not an AI summary that may or may not be correct. I may be oldfashioned... but I always try to look for the original source. Agreed, but I restarted my search 2025 December via Google and I know I also read the UT device page (because I made a spreadsheet then, comparing the top choices, and included details such as wireless ext display). I don't remember device page clearly saying VoLTE not working, main developer carrier NOT using VoLTE, and therefore low likelihood of P3A XL ever getting good VoLTE, and no native VOIP app for current UT release. So, I ordered the 3A XL, installed UT (great easy process, but it IS easy on an unlocked Pixel, and I had already been through similar process with LineageOS, on P XL, and 4XL.) I also don't remember in early December, whether Nord N10 5G was yet working for VoLTE, but by late that month I got replies to forum questions suggesting I try it (since 1 person had it working in USA on T-Mobile). That meant 'possible', at least. (so, I bought 1 !) All I am trying to say here is we need to keep striving to make sure the main UT landing pages are accurate, especially for critical details: examples (1) do any device pages clearly state that some highly promoted devices are missing bands required by some carriers in some countries ? or (2) on another brand, if you brick the main board during UT install, you effectively cannot get a part replacement in any country but France (if I understand that thread correctly). Those 2 facts might cut 2 of the MOST recommended options for US purchasers. So, last I checked, Nord N10 5G is not highlighted, but if in USA, and you want a phone that works on VoLTE now, and lasts a bit into the future, Nord N10 5G is the ONLY economical viable option ? If google quick search gets it wrong, and Dive Deeper gets it wrong, but people find UT device page and critical info NOT obvious, and new people waste time & money, isn't that at least partially our fault ? I understand that someone IS doing their best to update the tiny details, on device pages, but I was told that is completely different from adding a sentence to a paragraph on a web page (I did not know that). That is why I tried yesterday to see if I could improve the data that Google fed to people. I hate feeling helpless. I have no idea how to edit a webpage. (and I did not yet bother to ask Google about it.), And, since I am a newbie & keep finding conflicting info all over, I would not want to edit a page unless I was POSITIVE about it. I don't want to make anything WORSE !

@Futura Wow, that's disappointing.

@MarcelloTogg Core merged requests help to see too https://gitlab.com/groups/ubports/development/core/-/merge_requests?scope=all&state=merged

@Kadafi I have a FP5 and the 2FA app you are talking about installs without problem. Maybe it's because I'm on stable while by using daily you are exposing yourself to any fleeting update bug. The usual cause of this problem is network error. Try to download the click by hand using Morph QT6 browser and visiting open-store.io. If you can't download it, either your network is blocking somehow or your install is hosed (I have already warned you against this possibility, I'm still not convinced by your counter-arguments...) If you can, navigate to the resulting file and try to install it from there using the store app.

actually this is been a few months coming