PySide6 for Android Devices

Note

DISCLAIMER: This guide is unofficial and not affiliated with Qt. Please refer to the Official Documentation about the compiling process for Android.

Taking Qt for Python to Android
Qt for Python v6.8

This Guide is up to date with version:

PySide6 == 6.8.0

Table of contents

• General
• Downloading the Android wheels
• Setup
• Building the Android APK
  • PySide6 modification
  • The final build process
  • Installation of your App
• Errors and solutions
  • RuntimeError
  • C-Compiler can not create executables
  • python package architecture mismatch
  • DeadObjectException
• Building the Wheels (LEGACY)
  • Install dependencies
  • PySide-Setup
  • Building the wheels

Warning

Before proceeding, make sure your app is compatible with either Python3.10.x or Python3.11.x

A general explanation

Android devices can have one of the four architectures: armv7, aarch64, x86_64, i686. You should compile your application for all four of these. This involves using the official pyside6-android-deploy tool, which will automatically sets everything up.

Downloading the Android wheels

Since Qt Version 6.8 Qt published their own Android wheels, which you need for building. I STRONGLY recommend you to download them, instead of compiling your own.

However, if you want to compile them by yourself, you can skip to the LEGACY part.

Here's the link to their public archive: https://download.qt.io/official_releases/QtForPython/pyside6/

And here are the links for every release:

Note

Only the aarch64 and x86_64 versions are available at the moment.

I also compile my own wheels, which you can download in the GitHub releases, although there's no guarantee for them to work!

• PySide6 - aarch64

• PySide6 - armv7

• PySide6 - i686

• PySide6 - x86_64

• Shiboken - aarch64

• Shiboken - armv7

• Shiboken - i686

• Shiboken - x86_64

Setup

When building the .apk you need the Android SDK and NDK. You can install them manually and skip this section, but to make your life a little bit easier, I recommend using Qt's own tool for that purpose.

Dependencies:

Although you do not need all of them, I recommend installing them:

sudo pacman -Syu base-devel android-tools android-udev clang jdk17-openjdk llvm openssl cmake wget git

cd ~/
git clone https://code.qt.io/pyside/pyside-setup
cd pyside-setup 
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
pip install -r tools/cross_compile_android/requirements.txt
python tools/cross_compile_android/main.py --download-only --verbose

Important

Make sure to use the --verbose flag, otherwise it won't show you the License Agreement for the SDK and you won't be able to install the build tools.

After you are finished with this your Android SDK and NDK are in the following directories:

Android SDK: ~/.pyside6_android_deploy/android-sdk
Android NDK: ~/.pyside6_android_deploy/android-ndk/android-ndk-r26b/

Building the Android APK

The buildozer.spec file

Note

Although you do not need this for a base PySide6 application, I still recommend you to read through the following part, because it contains very important things for your Android App.

Buildozer is the tool which generates the .apk file using P4A (Python for Android) as backend. The buildozer.spec file is a configuration file which is generated on Buildozer's first run. It's used to configure the behaviour of your application. For example whether your App should run in portrait or landscape mode and other things. Here's a list of the most important options:

• requirements: The list of all python packages used in your app See Buildozer.spec
• icon.filename: The Icon of your App as a .png or .jpg. Please have a look at Google's Adaptive Icons
• title: Your App name
• version: The version of your application e.g, 1.1
• android.permissions: All permissions your App needs. Have a look at Android Permissions
• package.name: The name of your package, which is the output of buildozer
• package.domain: The unique identifier of your app inside the Android app system
• orientation: The orientation of your app: portrait ->: || or landscape ->: ===

Special Note on charset_normalizer and requests:

If your project uses the 'requests' library or any other library dependent on 'charset_normalizer', ensure to specify the version charset-normalizer==2.1.1 in your requirements, otherwise there will be an architecture mismatch.

PySide6 modification

Unfortunately the pyside6-android-deploy script starts the build proces immediately, without giving you the option to manually review the buildozer.spec file, which is the reason why we need to do a little modification, but don't worry it's easy:

1. Go into your virtual environment to the PySide6 folder (e.g: venv/lib/python3.11/site-packages/PySide6/scripts/)
2. Edit the android_deploy.py file.
3. Search for the line: logging.info("[DEPLOY] Running buildozer deployment")
4. Above this line write this: input("Modify your buildozer.spec now")

When you start building the apk with pyside6-android-deploy the build process will stop at some point, and then you can make adjustments to the buildozer.spec file. After you are done, just press enter the build process, and it will go on using your own options in the requirements.

The final build process

Important

Make sure your script is named main.py

Go into your source directory and type the following:

`pyside6-android-deploy --wheel-pyside=<your .whl file for the architecture> --wheel-shiboken=<your .whl file for your architecture> --name=main --ndk-path ~/.pyside6_android_deploy/android-ndk/android-ndk-r26b --sdk-path ~/.pyside6_android_deploy/android-sdk/

Explanation:

• --wheel-pyside= Here comes your PySide6 wheel which you've downloaded or compiled
• --wheel-shiboken= Here comes your Shiboken wheel which you've downloaded or compiled
• --name= The name of your application
• --ndk-path= The path to your Android NDK (See Setup)
• --sdk-path= The path to your Android SDK (See Setup)

The script will start configuring buildozer and buildozer will start the build process. At the end you will have a .apk file for the specified Android architecture.

Installation (Best practices)

I generally recommend you to use ADB / Fastboot to install, and debug your Android application. Once you understood how it works, it makes your life a lot easier...

1. Go into your system information and tap a few times on your build number

2. Go (or search) into the developer settings

3. Enable USB-Debugging (Or Debugging over W-Lan, but this is a little bit advanced)

4. Install the android-tools on your system:

   • On Arch Linux: sudo pacman -S android-tools
   • On Ubuntu: sudo apt install android-tools-adb android-tools-fastboot
   • On Windows: Imagine using Windows lol

5. Type: adb devices

6. On your device there should be a popup asking for your permission. Click on confirm.

7. Type: adb devices once again and confirm, that you see your device there.

The two magical commands

Install your apk: adb install <path_to_apk_file>
Debug your app: adb logcat --regex "<package.domain>

After your apk was installed, you will see it in your system apps. Click on your app, scroll down and at the very last line it should say something like:

Version 2.1.6
com.digibites.accubattery

The first line is your App version and the second line is your package domain.
After executing the logcat command, you can start your App and you should see a lot of debug messages. In case your app crashes, you can see what went wrong, although the crash report isn't always very helpful...

Note

These instructions are based on my Pixel 7 Pro running Android 14. The steps for you might be different, but in general they are all very similar on all Android devices. If you are stuck somewhere, XDA, Google and StackOverflow are your best friends :D

Errors and (potential) solutions:

• RuntimeError: "You are including a lot of QML files from a local venv..." This error is related to your virtual environment. Make sure your virtual environment is NOT inside your projects' folder. It doesn't matter where it is, but must not be in your projects' folder. For example, if you have your main.py in a folder named my_project, then your virtual environment can't be in this folder!

Create a new virtual environment in a different location and delete your old one with `rm -rf venv .venv` (or whatever you've called it)
This is more an issue from Qt and will hopefully be fixed in a later Qt release, so that you don't need to do this anymore. I know it's confusing.

• c compiler can not create executables Don't worry, this issue most of the time comes because you are using a too high API level. Just go into the path, where it says the C compiler wouldn't be able to create executables and then look inside this directory. You'll find files ending like androidclang33- (or something like that). The highest number which is there is the highest number you can select.

• blah blash blah is for x86_64 architecture not aarch64
  Solution: Search online if the pip package has a verified aarch64 version. If it doesn't prepare for some months of work building the recipes lmao

• DeadObjectException (Couldn't insert ... into...)
  Solution: Could be anything. but possibly one of your imported packages has an issue such as not being available. If you are sure that this is not the case, I would suggest you to make a basic test application which just shows a window and a test label, and you try to import one package by one until it breaks.

Important

I AGAIN want to remind you of using the Java version 17! Java 11 is supported by Gradle and even recommended, but not supported by Qt, and version 21 is supported by Qt, but not by the currently used Gradle version. This may change in the future and I will update it accordingly.

Contributions / Issues

If you see Issues in this guide, or you have something to improve it, feel free to open PRs and Issues. I'll respond to them and try to help you as much as possible. (Only for Arch Linux).

Maybe someone of you can make an alternative readme for other distros. Would be nice :)

Support

I appreciate every star on this repo, as it shows me that my work is useful for people, and it keeps me motivated :)

Legacy (Building the wheels)

Note

Please note, that this won't be maintained as often and that the following part is NOT perfect and may contain some issues. This is made to get you into the right direction, but shouldn't be seen as a perfect tutorial or guide!

Installing Qt

• Log in to your Qt account at Qt
• Download the Qt Online Installer and execute it
• Select "Desktop" and "Android" and install Qt (Should be around ~1.3 Gigabyte downloading)

Install dependencies

Arch Linux (recommended)

sudo pacman -Syu base-devel android-tools android-udev clang jdk17-openjdk llvm openssl cmake wget p7zip git

Python3.10 Support

Note

If you want to compile your App using Python3.10 you need to install Python3.10 with shared libraries. You only need this if you want Python3.10

PySide-Setup

Explanation:

This is the source directory of PySide6. Just execute the bash stuff below. It will install the needed stuff. Execute this one time and REMEMBER where you've cloned this to, as we need this later :)

python -m venv venv # Needed, trust me...
source venv/bin/activate
git clone https://code.qt.io/pyside/pyside-setup
wget https://download.qt.io/development_releases/prebuilt/libclang/libclang-release_140-based-linux-Rhel8.2-gcc9.2-x86_64.7z
7z x libclang-release_140-based-linux-Rhel8.2-gcc9.2-x86_64.7z
export LLVM_INSTALL_DIR=$PWD/libclang

if [ -n "$ZSH_VERSION" ]; then
    echo "export LLVM_INSTALL_DIR=$PWD/libclang" >> ~/.zshrc
elif [ -n "$BASH_VERSION" ]; then
    echo "export LLVM_INSTALL_DIR=$PWD/libclang" >> ~/.bashrc
fi

cd pyside-setup
pip install -r requirements.txt
pip install -r tools/cross_compile_android/requirements.txt
pip install pyside6
cd

Building the Qt Wheels

Explanation:

We are going inside the pyside-setup folder which you've cloned. This folder is the source code of PySide6. The tool for compiling the wheels is located in tools/cross_compile_android/main.py.

There are 4 Android architectures:

• aarch64
• armv7a
• x86_64
• i686

You want to build your Application for all of these architectures, so that your App runs on any Android Device including the oldest phone from 11 years ago and a new Android Tablet from 2024 :)

Note

If you want to use Python3.10 instead of Python3.11 modify the main.py script. You'll find a line saying: "PYTHON_VERSION = 3.11". Change this to 3.10. (It's line 21)

Note

If you want to use a different NDK version than r26b, go into tools/cross_compile_android/android_utilities.py and change the value in the NDK version to your preferred one (at the top of the script)

Quick Information: You only need to build the wheels once, and you can use them for all your projects. So this is a one time step!

The basic command for building the wheels is the following:

python tools/cross_compile_android/main.py --plat-name= --qt-install-path= --api-level 34 --verbose

Note

If you want to save some time when cloning the Cpython repository, modify the main.py script. Search for: if not cpython_dir.exists(): Under it, you see the Repo.clone_from() call. Add the following argument to it: depth=1

This will only clone the latest commits and branch from the Python repository, otherwise you'll clone a lot of unnecessary data.

Warning

DO NOT REMOVE THE --verbose flag! The installer redirects all output from the SDK / NDK installation to the logs. Android will prompt you to accept the license, and you need to type y and proceed. If you don't use the --verbose line, you simply won't see this and the script is stuck forever!

--plat-name = Here comes your Android architecture. e.g, aarch64 or armv7a
--qt-install-path = Here comes your Qt installation path. e.g, "/home/$USER/Qt/6.8.0" or "/opt/Qt/6.8.0"
--api-level = Here comes your target android API level. I recommend 34. Now, execute this command for all 4 Android architectures. Your Wheels should be in the dist folder at the end.

If you get any errors, try to use the --clean-cache all argument first.