text model · Phi-3.5 · Android
Can I run Phi-3.5-mini 3.8B on Samsung Galaxy S25 Ultra (16GB, 1TB config only)?
Yes. Phi-3.5-mini 3.8B runs on Samsung Galaxy S25 Ultra (16GB, 1TB config only) at Q4_K_M (~3.7 GB of ~12 GB usable).
Runs at Q4_K_M using ~3.7 GB of ~12 GB usable. You have room for FP16 for higher quality.
- Q4_K_M needed
- ~3.7 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
- 3.82B
- Q4_K_M size
- 2.39 GB
- Q8_0 size
- 4.06 GB
- Context
- 128k
- Ollama tag
- phi3.5:3.8b
- 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 Phi-3.5-mini 3.8B on other hardware
FAQ
Can Samsung Galaxy S25 Ultra (16GB, 1TB config only) run Phi-3.5-mini 3.8B?
Yes. Phi-3.5-mini 3.8B runs on Samsung Galaxy S25 Ultra (16GB, 1TB config only) at Q4_K_M (~3.7 GB of ~12 GB usable).
How much memory does Phi-3.5-mini 3.8B need?
Samsung Galaxy S25 Ultra (16GB, 1TB config only) has room to spare. At Q4_K_M the weights are ~2.39 GB; with KV cache and runtime overhead, budget ~3.7 GB at a 4k context.
What is the best tool to run Phi-3.5-mini 3.8B 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.