My goodness, thanks again! Genuinely thanks for your guidance on this. It is hugely appreciated.

I actually went and manually downloaded the partition images for 16.04 and (carefully) extracted them on the phone and that worked also. I'm now happily running UBports 16.04 development with Anbox. I can't believe what I'm seeing. What the UBports team has achieved is amazing!

@tomoqv Ah, magic! That worked perfectly, thanks. Basically all applications I've tried have worked so far which is awesome. Would you happen to know the status for keyboard interactions? Are you aware of a way to get the onscreen Ubuntu keyboard to send keystrokes to the running Anbox application?

By the way, the code formatting is done using standard Markdown syntax. So, if I wanna display some Python code, like this:

a = 1

then I just write some Markdown code like this:

```Python
a = 1
```

@matteo Magic, thanks for that suggestion. Anbox was installable using the development channel without the need to flash a kernel for it separately, as you guessed. Regarding your Wi-Fi experience, I am not experiencing any Wi-Fi problems for native applications running while Anbox is running or for Anbox applications. For you and any others reading, the following UBports and Anbox versions were those I observed as being compatible:

I started with the little BQ Aquaris E4.5 and have had a MEIZU PRO 5. I am considering getting my hands on one of the latest Fairphones or a PinePhone or maybe the F(x)tec Pro1 X.

I'd like whatever device I opt for to be likely to be supported for a good while. I'm particularly keen on support for WayDroid/Anbox and running standard X11 applications. I would have been quite happy continuing to use the Aquaris E4.5, but development of Anbox for it kinda ended so I migrated to the MEIZU PRO 5.

How might you guess at the current degree of support for a particular device, or how might you gauge the likely support of a particular device into the future? So, for example, how might you answer the question of whether it is the Fairphone 4 or the F(x)tec Pro1 X that'll likely still be supported with the latest UBports-related developments 5 years from now?

Probably not perfect, but maybe a bit better than otherwise. Gets one from Android MEIZU PRO 5 to Ubuntu Touch MEIZU PRO 5 with Anbox. Caveats about bricking phone and all that.

https://github.com/wdbm/TFLOSSH/blob/master/turbo.md

Go n-éirí leat!

Mar sin! I've got my 16.05 PRO5 here and I'd love to start throwing what are essentially PyQt5 Python programs at it. Not looking for perfection, just some basic functionality with a window appearing, buttons, that sort of jazz, lotsa nice Python happenings in the backgrounde. Now, much as I'd like pure Python, in the world of Ubuntu Touch I see the push towards QML and pyotherside, well ok.

So, I've been scurrying about trying to install pyotherside (version 1.4) and finding myself meddling with qmlscene (qmlscene: could not find a Qt installation of '' blargh!). I'm happy to dive into proper QML but at this point would be happy with a simple Python "hello world" printout appearing in a window on an Ubuntu Touch device. Could someone guide me to completion on how to accomplish this?

qtchooser -list-versions gives me the following:

4
5
qt4-arm-linux-gnueabihf
qt4
qt5-arm-linux-gnueabhif
qt5

I have a small program like this:

// hello.qml
import QtQuick 2.0
*import io.thp.pyotherside 1.4

Rectangle {
    width: 640; height: 480
    color: "#E95420"
    Label { id: label; text: "Nothing here yet" }
    MouseArea {
        anchors.fill: parent
        onClicked: {
            py.addImportPath(Qt.resolvedUrl("."));
            py.importModule("hello", function(){
                label.text = call_sync("hello_world");
            });
        }
    }
*   Python { id: py }
}

# hello.py

def hello_world():
    return "Hello from Python!"

When I run qmlscene hello.qml (or similar) I get a bunch of Mir-related gibberish, excerpts of which are:

[QPA QMirClientClientIntegration: connection to Mir server failed.

Mir returned "Failed to connect: not accepted by server"

That sorta shite.

So, what've ya got for me, ma expert and extremely leet boos?

@matteo Magic, thanks for that suggestion. Anbox was installable using the development channel without the need to flash a kernel for it separately, as you guessed. Regarding your Wi-Fi experience, I am not experiencing any Wi-Fi problems for native applications running while Anbox is running or for Anbox applications. For you and any others reading, the following UBports and Anbox versions were those I observed as being compatible:

Hey all. I'm trying to install Anbox on my PRO 5 and am running into a problem with anbox-tool install. I'd welcome any illumination, perhaps information on compatible versions of UBports and Anbox for the PRO 5.

I've got UBports 16.04 (OTA-11, stable) and anbox-boot-turbo-test.img flashed (as described here). When I attempt to install Anbox with anbox-tool install, I am presented with a Python error that concludes with the following:

json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Does anyone happen to have any ideas on what is going wrong and how I might get the latest possible Anbox running on the device?

I attempted to install anbox-ubuntu-touch on UBports 16.04 (20200107, devel) but it did not appear to be available.

Hey there. Until a recent build of UBports 16.04 LTS, the camera was working beautifully on this MEIZU PRO 5 here, taking and saving pictures. In recent builds, including this current UBports OS Image Part 2018-12-08-31252, the camera application opens and displays live images as normal, but on taking a picture it displays the following error message:

Capture failed
Restarting your device might fix the problem.

This is the case for all of taking front-facing or back-facing photographs or videos. I've tried the obvious of restarting without success. Can anyone guess at what might be wrong or how this might be fixed? I'd appreciate any guesses or tips.

In case it is somehow related, I have been running Antox with success and this has also broken recently (wherein it just crashes on launch).

Otherwise things seem to be working well and I commend the hard efforts of the developers.

I'd like to try using my little Aquaris E4.5 as a locator beacon for my bicycle, whereby it pings me if it detects that it is being moved. So, I would like to try getting its GPS location in a Python script running on the phone. Is there some way to do this? I saw on Android there is something like this that could be consulted:

adb shell dumpsys location

@tomoqv Ah, magic! That worked perfectly, thanks. Basically all applications I've tried have worked so far which is awesome. Would you happen to know the status for keyboard interactions? Are you aware of a way to get the onscreen Ubuntu keyboard to send keystrokes to the running Anbox application?

By the way, the code formatting is done using standard Markdown syntax. So, if I wanna display some Python code, like this:

a = 1

then I just write some Markdown code like this:

```Python
a = 1
```

Hey there

I'm new to Anbox but am thinking about this as well. As far as I can figure, some APKs are at the directory ~/anbox-data/rootfs/system/app. So, for example, the path of the Android Calendar application is as follows:

/home/phablet/anbox-data/rootfs/system/app/Calendar/Calendar.apk

I had figured on changing to that directory, creating a directory for a new application and then adding its APK to that new directory. I'm not sure how to kill Anbox properly, but the following steps seem to work somewhat:

sudo apt install psmisc
killall anbox

Having "killed" Anbox I want to create a new directory for an application and add the application, in a way like the following:

mkdir /home/phablet/anbox-data/rootfs/system/app/Funkytunes
cd /home/phablet/anbox-data/rootfs/system/app/Funkytunes
wget https://github.com/funkyg/funkytunes/releases/downlad/0.2.1/funkytunes-0.2.1.apk
chmod 755 funkytunes-0.2.1.apk

However, when I attempt to do this, I am told that the filesystem of Anbox is read-only:

phablet@ubuntu-phablet:~/anbox-data/rootfs/system/app$ touch Funkytunes
touch: cannot touch 'Funkytunes': Read-only file system

I'm not sure how to go past this. Any ideas?

My goodness, thanks again! Genuinely thanks for your guidance on this. It is hugely appreciated.

I actually went and manually downloaded the partition images for 16.04 and (carefully) extracted them on the phone and that worked also. I'm now happily running UBports 16.04 development with Anbox. I can't believe what I'm seeing. What the UBports team has achieved is amazing!