text model · Granite · Android
Can I run Granite 3.1 2B on Samsung Galaxy S26 Ultra (16GB, 1TB config)?
Yes. Granite 3.1 2B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~2.8 GB of ~12 GB usable).
Runs at Q4_K_M using ~2.8 GB of ~12 GB usable. You have room for FP16 for higher quality.
- Q4_K_M needed
- ~2.8 GB
- Usable on device
- ~12 GB
- Device memory
- 16 GB
- Best quant
- Q4_K_M
How to run it
On Android use PocketPal AI (Polished app, download GGUF and run offline.). NPU acceleration is limited and chip-specific; most apps run on CPU. Expect 1B-4B class.
- Parameters
- 2.53B
- Q4_K_M size
- 1.55 GB
- Q8_0 size
- 2.69 GB
- Context
- 128k
- Ollama tag
- granite3.1-dense:2b
- 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 Granite 3.1 2B on other hardware
FAQ
Can Samsung Galaxy S26 Ultra (16GB, 1TB config) run Granite 3.1 2B?
Yes. Granite 3.1 2B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~2.8 GB of ~12 GB usable).
How much memory does Granite 3.1 2B need?
Samsung Galaxy S26 Ultra (16GB, 1TB config) has room to spare. At Q4_K_M the weights are ~1.55 GB; with KV cache and runtime overhead, budget ~2.8 GB at a 4k context.
What is the best tool to run Granite 3.1 2B 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.
Sources
Memory figures are estimates. See methodology.