Installation Guide on KnightLi Blog

Running Android Apps on Ubuntu 26.04 LTS: Waydroid Setup and Practical Notes

Sat, 16 May 2026 17:34:59 +0800

On Ubuntu 26.04 LTS, the most practical way to run Android apps is still Waydroid.

Waydroid is not a traditional Android emulator. It runs a LineageOS-based Android system inside a Linux container. The benefit is lower overhead and better desktop integration; the limitation is that it depends heavily on Wayland, kernel features, graphics drivers, and each app’s compatibility.

If you only need to occasionally open an Android utility, test an APK, or run lightweight apps, Waydroid is worth trying. If you want to play heavy mobile games, rely on banking apps, or use Google services heavily, keep expectations modest.

Check whether it fits your setup

Ubuntu 26.04 LTS was released on April 23, 2026. The official desktop requirements include at least a 2 GHz dual-core CPU, 6 GB of RAM, and 25 GB of storage. Waydroid needs additional disk, memory, and graphics resources, so a more comfortable baseline is:

8 GB of RAM or more;
at least 10 GB of free disk space;
a working Wayland session;
recent Intel, AMD, or NVIDIA graphics drivers;
acceptance that some Android apps will not work perfectly.

Waydroid’s documentation also notes that Ubuntu 22.04 and later desktops need a Wayland session. Ubuntu 26.04 LTS defaults more strongly to Wayland, which actually helps here.

Install Waydroid

Install the basic dependencies first:

`1`	`sudo apt install curl ca-certificates -y`

Add the official Waydroid repository:

`1`	`curl -s https://repo.waydro.id \| sudo bash`

Then install Waydroid:

`1`	`sudo apt install waydroid -y`

After installation, you can start Waydroid from the app menu or from the terminal.

Initialize Android

On first launch, Waydroid needs to initialize the Android system image. The default image is usually enough.

If the graphical flow does not appear, start the container manually:

`1`	`sudo waydroid container start`

Then start the user session:

`1`	`waydroid session start`

Open the full Android UI:

`1`	`waydroid show-full-ui`

You should now see an Android tablet-like interface. Apps you install later can be opened inside Waydroid, and some may appear in Ubuntu’s app launcher.

Install APK files

If you already have an APK file, install it directly:

`1`	`waydroid app install app.apk`

List installed apps:

`1`	`waydroid app list`

Launch an app by package name:

`1`	`waydroid app launch com.example.app`

This is useful for F-Droid, open-source tools, test builds, or your own APKs. Avoid random APKs from unknown sources, especially apps that ask for accounts, payments, contacts, or SMS permissions.

Multi-window mode

By default, Waydroid feels more like one full Android window. If you want Android apps to appear as separate desktop windows, enable multi-window mode:

`1`	`waydroid prop set persist.waydroid.multi_windows true`

Restart the session:

1
2

waydroid session stop
waydroid session start

After that, launched apps should behave more like normal desktop windows. The experience still depends on the app, desktop environment, and graphics drivers.

Should you install Google Play?

Waydroid is not the same as a fully Google-certified Android device.

Many users really want Google Play, Google Play Services, and apps that depend on Google’s framework. This can be configured, but it is not a stable production assumption:

Google services involve device certification and account risk checks, so login behavior can change.
Some apps check SafetyNet, Play Integrity, root status, virtual environments, or device fingerprints.
Banking, payment, games, and streaming apps are more likely to fail.

For ordinary tools, prefer F-Droid, open-source APKs, or apps that do not require Google services. That usually fits a Linux desktop better.

Common issues

If the screen is black after launch, first confirm that you are using Wayland rather than X11:

`1`	`echo $XDG_SESSION_TYPE`

You should see:

wayland

If the container is not running:

`1`	`sudo waydroid container start`

If the session is stuck, restart it:

1
2

waydroid session stop
waydroid session start

Check logs if the issue continues:

`1`	`waydroid log`

NVIDIA users may see more graphics-stack issues. Ubuntu 26.04 LTS has better Wayland and NVIDIA support than older releases, but Waydroid is still not a normal native desktop app, so rendering, black-screen, or window problems can happen.

How it differs from emulators and VMs

Waydroid is closer to “Android in a container” than a full virtual machine.

Its strengths are fast startup, low resource usage, and good desktop integration. Its weaknesses are host-system sensitivity, high graphics-stack dependency, and weaker fit for security-sensitive apps.

Traditional Android emulators are better for development testing and device simulation, but they usually use more resources. Virtual machines provide stronger isolation, but graphics acceleration and desktop integration are often worse.

Option	Best for	Main issue
Waydroid	Lightweight apps, APK testing, Linux desktop integration	Google services and some apps are unstable
Android Studio Emulator	Development and device simulation	High resource usage, not ideal for daily users
Virtual machine	Isolated testing and experiments	Graphics and performance are usually weaker

My recommendation

Treat Waydroid on Ubuntu 26.04 LTS as a supplementary tool, not a full Android tablet replacement.

Good use cases:

F-Droid tools;
testing your own or downloaded APKs;
temporarily using an Android app without a Linux version;
keeping a lightweight Android environment on the Linux desktop.

Poor fits:

long-term banking, payment, or securities apps;
heavy mobile games;
apps that strongly depend on Google Play certification;
workflows that need reliable notifications, background services, location, Bluetooth, or camera access.

If you only want to occasionally open Android apps on Ubuntu, Waydroid is the first option to try. It is not perfect, but setup is simple and it matches Ubuntu 26.04 LTS’s Wayland direction well.

References

How to Install and Run Gemma 4 on Android: Complete Getting-Started Guide

Wed, 08 Apr 2026 17:55:53 +0800

If you want to run Gemma 4 offline on your phone, this guide walks you through the full process from setup to practical usage.

Step 1: Get the App

Google AI Edge Gallery is currently not available on Google Play, so you need to install it via APK sideloading.

On your Android device, go to:

Settings -> Apps -> Special app access -> Install unknown apps

Then:

Find your browser (for example, Chrome or Firefox) and enable “Allow from this source.”
Open the Google AI Edge Gallery GitHub Releases page in your mobile browser.

URL: https://github.com/google-ai-edge/gallery/releases

Download the latest .apk package.
After the download completes, open the file from notifications or your file manager and follow the prompts.

With a stable connection, this step usually takes around 2 minutes.

Step 2: Open the App and Grant Permissions

When you first open AI Edge Gallery, it will request storage permission to save model files. It’s best to allow this; otherwise, the app cannot download or load models.

You will typically see these sections on the home screen:

Ask Image: Vision tasks (describe images, answer questions about photos)
AI Chat: Standard text chat
Summarize: Paste text and generate summaries
Smart Reply: Generate reply suggestions

For most users, AI Chat is the primary entry point.

Step 3: Download a Gemma 4 Model

Enter AI Chat.
Tap Get Models when prompted.
Choose a Gemma 4 model from the list (model size is shown).
Pick based on your device capability; if your phone has 8GB RAM, start with Gemma 4 4B.
Tap Download and let it run in the background.

Note: Larger models take longer to download. You can download multiple models and switch between them later. Downloaded models stay on your device, so you do not need to re-download them.

Step 4: Start Chatting

After the model download is finished:

Tap the model name to load it (the first load usually takes 10 to 30 seconds depending on model size and device performance).
Enter your prompt in the chat box and send it.
The model generates responses locally, and your data does not leave the phone.

The first reply is often slower due to model warm-up. Later messages in the same session are usually faster.

Step 5: Try Vision Features (Gemma 4 Multimodal)

If you downloaded a Gemma 4 multimodal variant:

Go back to the main menu and open Ask Image.
Select an image or take a photo.
Ask a question (for example, “What’s in this image?” or “Is there any text I should pay attention to?”).
Wait for the model to analyze the image locally and return a result.

This feature works offline, and your image is not sent to external servers.