Can AREX Turbo 4B run on vivo V80 Lite 5G (Pakistan)?
YES — Runs, barely
Formula estimate
What this means
Our estimate says AREX Turbo 4B should fit, but replies are likely to arrive slowly.
Download the Q4_K_M version, which is about 2.9 GB. We expect it to use about 4 GB of the roughly 6 GB available to a model on this phone.
At the estimated speed, a roughly 300-word answer may take about 2 minutes to finish.
This result is calculated from the phone and model specifications. It has not been measured on this exact phone and setup.
2.7tokens/s
estimated · slower than you read
4GB
needed at Q4_K_M
Q4_K_M
quant checked
needs 4 GBusable 6 GB
Dimensity 7360-Turbo8 GB RAMCPU / GPU
Make it bearable
1
Drop context to 2K — saves ~0.2 GB of KV cache and a little speed.
2
Close every other app before loading — the 2 GB headroom is real; Android may kill the app otherwise.
3
Expect throttling after ~10 min of sustained generation on a phone chassis.
See how fast it feels
Estimated at 2.7 tokens/s — slower than you read. A ~300-word reply takes about 148 seconds on this phone.
Where the memory goes
| Component | Detail | GB |
|---|---|---|
| Model weights | Q4_K_M GGUF (2.9 GB) + mmap overhead | 3 |
| KV cache | 4K context window | 0.3 |
| Runtime | llama.cpp + app overhead | 0.6 |
| Total needed | at Q4_K_M, 4K context | 4 |
| Working budget | 8 GB RAM − Android system reserve | 6 |
| Headroom | remaining inside the working budget | 2 |
Pick your quant
| Quant | Download | Verdict | Speed |
|---|---|---|---|
| Q2_K | 2.1 GB | ! Runs, barely | ~3.7 tokens/s |
| Q3_K_M | 2.4 GB | ! Runs, barely | ~3.2 tokens/s |
| IQ4_XS | 2.5 GB | ! Runs, barely | ~3.1 tokens/s |
| Q4_0 | 2.6 GB | ! Runs, barely | ~3 tokens/s |
| Q4_K_S | 2.7 GB | ! Runs, barely | ~2.9 tokens/s |
| Q4_K_M BEST HERE | 2.9 GB | ! Runs, barely | ~2.7 tokens/s |
| Q5_K_M | 3.3 GB | ! Runs, barely | ~2.3 tokens/s |
| Q6_K | 3.7 GB | ! Runs, barely | ~2.1 tokens/s |
| Q8_0 | 4.5 GB | ! Runs, barely | ~1.7 tokens/s |
Get your first offline chat working
Recommended app: PocketPal. Follow the point-and-click steps below. The speed above is an estimate, not a measurement from this exact app and phone.
1
Install or update PocketPal from Google Play. It is free and does not require an account. Use a current version so its loader supports newer model architectures.
2
Open the exact model. In PocketPal, go to Models → + → Add from Hugging Face, then paste
bartowski/BAAI_AREX-Turbo-GGUF.3
Choose the Q4_K_M GGUF file. The download is about 2.9 GB, so use Wi-Fi and keep the app open. Choose the main GGUF weights, not a vision projector, mmproj, or other helper file.
4
Tap Download, then Load. Start with a 4K (4096-token) context. Keep the app’s default Android backend for the first run.
5
Send a simple first prompt. Try “Explain why the sky is blue in three sentences.” This page estimates about 2.7 tokens/s, but that number is not a PocketPal measurement unless it carries a ✓ Verified label.
6
Confirm it is really offline. After the first reply, turn on airplane mode and ask a second question. If it still answers, the model is running on your phone.
If it does not work
- Model not listed: update PocketPal and paste the exact repository
bartowski/BAAI_AREX-Turbo-GGUF. - App closes while loading: close other apps, restart the phone, and try 2K context. If it still closes, choose a smaller model.
- No offline reply: confirm that the Q4_K_M GGUF file is loaded in the chat rather than a remote model.
Related checks
More on vivo V80 Lite 5G (Pakistan)
AREX Turbo 4B on other phones