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

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

this problem may be related to your hardware. Try running with --disable-gpu and --disable-gpu-sandbox to see if it works

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

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

@arubislander OK. Darn !

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.

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

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