text model · Llama 3.2 Vision · Android
Can I run Llama 3.2 Vision 11B on Samsung Galaxy S26 Ultra (16GB, 1TB config)?
Yes. Llama 3.2 Vision 11B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~9 GB of ~12 GB usable).
Runs at Q4_K_M using ~9 GB of ~12 GB usable.
That figure is at a 4k context and moves about ±15% as context length changes. Samsung Galaxy S26 Ultra (16GB, 1TB config) leaves ~3 GB of headroom.
- Q4_K_M needed
- ~9 GB
- Usable on device
- ~12 GB
- Device memory
- 16 GB
- Best quant
- Q4_K_M
Which quant fits
How to run it
On Android use PocketPal AI (Polished app, download GGUF and run offline.).
- Parameters
- 10.7B
- Q4_K_M size
- 7.36 GB
- Q8_0 size
- 11.49 GB
- Context
- 128k
- Ollama tag
- llama3.2-vision:11b
- Memory
- 16 GB ram
- Usable for weights
- ~12 GB
- Best runtime
- llama.cpp (PocketPal) or MLC-LLM (Adreno GPU path)
You could also run
Run Llama 3.2 Vision 11B on other hardware
FAQ
Can Samsung Galaxy S26 Ultra (16GB, 1TB config) run Llama 3.2 Vision 11B?
Yes. Llama 3.2 Vision 11B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~9 GB of ~12 GB usable).
How much memory does Llama 3.2 Vision 11B need?
Samsung Galaxy S26 Ultra (16GB, 1TB config) has room to spare. At Q4_K_M the weights are ~7.36 GB; with KV cache and runtime overhead, budget ~9 GB at a 4k context.
What is the best tool to run Llama 3.2 Vision 11B on Android?
On Android, PocketPal AI (Polished app, download GGUF and run offline.) is the go-to option. NPU acceleration is limited and chip-specific; most apps run on CPU. Expect 1B-4B class.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/llama-3.2-vision-11b/samsung-s26-ultra) Sources
- github.com/a-ghorbani
- github.com/google-ai-edge
- github.com/mlc-ai
- github.com/shubham0204
- github.com/Vali-98
- gsmarena.com
- huggingface.co/leafspark
- huggingface.co/meta-llama
- layla-network.ai
- notebookcheck.net
- ollama.com/library/llama3.2-vision
- ollama.com/library/llama3.2-vision/tags
- qualcomm.com
- sammobile.com
- sammyfans.com
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.