Run an optimized vision-language model from the Arm AI Portal on Android
Introduction
Prepare the Android command-line tools for Vision Chat
Connect an Arm-based Android phone and run Vision Chat
Import and run an Arm AI Portal vision-language model on Android
Understand the Vision Chat Android application
Next Steps
Run an optimized vision-language model from the Arm AI Portal on Android
Who is this for?
This Learning Path is for Android and machine learning developers who want to run an optimized vision-language model locally on an Arm-based Android device.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Prepare the Android command-line tools and connect an Arm-based Android phone.
- Download and run the supported Qwen3-VL model package from the Arm AI Portal.
- Trace how Vision Chat validates and extracts the model package ZIP, prepares an image and prompt, runs llama.cpp, and generates text.
- Interpret model-load, image-and-prompt, and token-generation measurements on a physical phone.
Prerequisites
Before starting, you will need the following:
- A macOS, Linux, or Windows development machine
- An Arm-based Android phone with Android 9 or later,
asimddpandi8mmCPU features, and at least 4 GB of free storage - Basic familiarity with terminal commands and Android applications
- Git installed on the development machine
- Python 3 with the
venvandpipmodules on the machine - Java Development Kit (JDK) 17 or later on the machine, available on your
PATH - A tool for downloading files and a tool for extracting ZIP archives on the machine
- A data-capable USB cable
- A Hugging Face account
- Network access for the first Gradle build and model downloads
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
adb devices -l and confirm that your phone appears as an authorized device. If you see unauthorized, unlock your phone, accept the USB debugging prompt, and run the command again. If your phone doesn’t appear, see
Run apps on a hardware device
.Q4_K_M language-model GGUF and the matching Q8_0 mmproj GGUF together.