text model · Gemma · Android
Can I run Gemma 4 E2B on Generic Android Phone (8GB RAM)?
Yes. Gemma 4 E2B runs on Generic Android Phone (8GB RAM) at Q4_K_M (~4.4 GB of ~4.5 GB usable).
Fits at Q4_K_M (~4.4 GB of ~4.5 GB usable) but with little headroom. Close background apps, and expect slow generation on a phone.
That figure is at a 4k context and moves about ±15% as context length changes. Generic Android Phone (8GB RAM) leaves ~0.1 GB of headroom.
- Q4_K_M needed
- ~4.4 GB
- Usable on device
- ~4.5 GB
- Device memory
- 8 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
- 5.1B
- Q4_K_M size
- 3.11 GB
- Q8_0 size
- 5.05 GB
- Context
- 128k
- Ollama tag
- gemma4:e2b
- Memory
- 8 GB ram
- Usable for weights
- ~4.5 GB
- Best runtime
- llama.cpp (PocketPal or SmolChat)
You could also run
Run Gemma 4 E2B on other hardware
FAQ
Can Generic Android Phone (8GB RAM) run Gemma 4 E2B?
Yes. Gemma 4 E2B runs on Generic Android Phone (8GB RAM) at Q4_K_M (~4.4 GB of ~4.5 GB usable).
How much memory does Gemma 4 E2B need?
It is a tight fit on Generic Android Phone (8GB RAM). At Q4_K_M the weights are ~3.11 GB; with KV cache and runtime overhead, budget ~4.4 GB at a 4k context.
What is the best tool to run Gemma 4 E2B 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/gemma-4-e2b/android-generic-8gb) Sources
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.