@zubozrout Oh I see, that's sad. Mine is now used just for a single app or purpose so it doesn't have much apps on it and I don't get the crashes. In fact, I love that it lasts about a week (without sim and wifi off)

If you build your app on a PC with your build of SDL, does it work under wayland/weston? That's probably a good place to start debugging. Once that's working, if you have a 16.04 VM set up with unity8 installed, I would build an x86 version of the click, install it in the VM, and see what works. Once both of those are working, it should also work on phones/tablets, once the remaining bits to get wayland clients working there are done.

I was wondering what was going on here: apt -o Dir::Cache::Archives=/home/phablet/anbox install anbox-ubuntu-touch On Telegram zubozrout explained that : "Well all it does if I parse it right is that it downloads the packages to a specified folder instead of the cache folder on the root filesystem (if you pick a folder in your home for instance) and then installs it from there. So it may not help if the rootfs is too full since the installed files end up where they should anyway but it saves a small part needed for the actual download which may allow you to install it."

Ok, it turned out my issue was that the old Ubuntu SDK project had the following line set in the Transport/Transport.pro file: desktop_file.files = $$OUT_PWD/*.desktop which turned out to work fine for vivid but for xenail the desktop file was missing from the final click package. So if anyone bumps into the similar issue you may try changing the above glob with a full path like this: desktop_file.files = $$OUT_PWD/Transport.desktop Once done the build project should be working (exacutable) on Xenial. Thank you @dohbee for helping me so much with this.

@advocatux Thanks for your report. So i will wait...

@marathon2422 Oh, no at all. I understand that what I've installed is not recommended for daily use. I was just curious whether the issues I've mentioned are also present on other devices as well. In any case the fact 16.04 is available for MX4 I haven't even hoped for is a good enough reason for me to at least play with it for a few days :). And since I've been mostly on Android after Canonical decided not to continue with the project I've found a really easy way to dualboot between both systems: https://iubuntu.cz/dualboot-mx4.html so I plan to keep 16.04 and add Android as another option once I install it again.

@advocatux Thanks!

Thanks @fulvio, it's working for me now.