Just FYI, the credit is not mine but goes to my brother - his nick is zub, mine is not :). Unfortunately I lack the deeper knowledge necessary for such things. All I did was that I upgraded it to work with clickable (already on the original repo) and to run on 16.04 (apparently the apparmor framework update is still not there, but whatever).

Regarding the SDL2 clickable template it doesn't sound as a bad idea though. However I really can't spend the time on it now :(. And the second thing is that SDL is no longer supporting Mir and new stuff may require newer SDL. So the question is whether this is useful. With Unity 8 and Mir upgrades (now on Edge) Wayland-enabled stuff should start working. So it would probably be better to start from scratch and take a look at how to compile SDL apps with Wayland. And I suspect that will be much more documented and a more streamlined experience.

Sadly Mir didn't turned out the way I was hoping it would ... it is a nicely written code on par with the latest standards as that's how Canonical rolls but that's probably not what the general Linux community wants :(.

Some of you may find these demos usable:
https://gitlab.com/zub2/SDLDemo
https://gitlab.com/zub2/MirGLESDemo

However with the Mir upgrade things should become a bit easier as regular Wayland-compiled SDL stuff should start working there. That is if I understand it correctly.

I have MX4 myself and never had any of these issues. Fastboot is a bit broken making UBports installer useless.

Anyway, based on the thread I suppose you can access filesystem using the USB cable, so the data flow is probably ok. Some cables can be problematic and could possibly cause this kind of issues. Could you try a different USB cable?

Nonetheless if you could run the installation on an Ubuntu desktop it would simply things a bit:

• Boot to fastboot mode (hanging on the message you mentioned is correct) and install recovery using fasbtoot flash recovery path/to/recovery-arale.img - you can download it from here: http://cdimage.ubports.com/devices/recovery-arale.img
• Once flashed reboot to recovery ... again, it will not say much ... there will only be an ubuntu logo with a background displayed.
• Install the ubuntu-device-flash package if it is not installed already.
• • Perhaps by adding this repo if you are on bionic (Ubuntu 18.04) running this code: sudo add-apt-repository http://repo.ubports.com and then apt install ubuntu-device-flash.
• • or just get the package manually https://repo.ubports.com/pool/bionic/main/g/goget-ubuntu-touch/ubuntu-device-flash_0.35+ubports+0~20181221200828.5~1.gbpd7daaa_amd64.deb and install it - fixing possible apt issues in case they appear by apt -f install then.
• Flash Ubuntu Touch to the device: ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/stable ... which will keep the old data or alternatively add --wipe option to clear old data making this a clean install.

Sadly this is the default behaviour for Terminal and as @guru says it has been present ever since UT has a Terminal (and suspends inactive apps, not sure which was first). But it makes it quite useless on many occasions so if I could vote I would vote for preventing Terminal suspension by default.

Of course UT Tweak Tool is a way to "fix" this but it is kind of expected that people would want to run tools in Terminal even when the app is not on focus.

@jezek Well, you would need to find the partition table of you phone to find the correct partition to flash the image to.

Not sure what would happen if the boot logo image was incorrect, it would work nonetheless (with a black screen) or perhaps it would brick the phone and you would have to reflash the correct image using fastboot then ... something like fastboot flash logo splash.img (the command may not work at all or could be different depending on the device).

And if you flash it to a wrong partition there is a great chance of bricking the phone.

@jezek You should be able to write the correct partition image (could be called e.g. "logo.img") using dd command right on the device but in order to do that you would have to have that image prepared already.

This is however very much device specific: https://forum.xda-developers.com/android/software-hacking/guide-how-to-create-custom-boot-logo-t3470473 so you would ideally have to check the correct instructions for you phone. And I expect such thing (if the XDA instructions do not recommend a Windows executable) would be doable on a phone as well but it would certainly not be the most comfortable way to deal with it.

@Flohack Thank you. Sadly I don't have that device for something like 2.5 years but am very happy it got fixed. Nice work :).

@Stefano I had Nexus 7 2013 deb and tasemnice was the only server that provided fully working Nexus 7 deb images. I've had Ubuntu Touch installed there both in dualboot mode as well as the only system present over the years and never experienced any WiFi issues. When tasemnice stopped working, I also tried UBports image from Nexus 7 flo on the device and it was also working fine in this perspective. So I've never seen this issue myself.

From what you say though it could mean the build was done differently when tasemnice was still active. But maybe you would have experienced the same issue with official Canonical images back then.

@Stefano Hm, this doesn't make sense then. If it works with Android sending to manufacturer is certainly not an option here. If that's the case then it would mean the EFS doesn't get destroyed but rather Ubuntu Touch has issues reading it.

@UniSuperBox Would there be a way for users to debug this somehow? It would be great if this thing could be solved as it seems to be recurring quite often in the forums/on github.

@UniSuperBox Yup :(, but it is not the first time I've experienced something like that. Last year when Xenial was still pretty much testing it (devel) also didn't work on arale for some time.

Edit: Oh, it was something else: https://forums.ubports.com/topic/901/xenial-ui-constantly-freezing-at-least-on-mx4 + https://github.com/ubports/ubuntu-touch/issues/434
In that case this is a new thing for me