Can OvisOCR2 0.8B run on vivo S2?
What this means
Our estimate says OvisOCR2 0.8B should fit comfortably on your vivo S2.
Download the Q4_K_M version, which is about 0.6 GB. We expect it to use about 1.3 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 31 seconds to finish.
This result is calculated from the phone and model specifications. It has not been measured on this exact phone and setup.
See how fast it feels
Estimated at 12.8 tokens/s — faster than you read. A ~300-word reply takes about 31 seconds on this phone.
Where the memory goes
| Component | Detail | GB |
|---|---|---|
| Model weights | Q4_K_M GGUF (0.6 GB) + mmap overhead | 0.6 |
| KV cache | 4K context window | 0.1 |
| Runtime | llama.cpp + app overhead | 0.6 |
| Total needed | at Q4_K_M, 4K context | 1.3 |
| Working budget | 8 GB RAM − Android system reserve | 6 |
| Headroom | remaining inside the working budget | 4.7 |
Pick your quant
| Quant | Download | Verdict | Speed |
|---|---|---|---|
| Q2_K | 0.4 GB | ✓ Runs great | ~19.2 tokens/s |
| IQ4_XS | 0.5 GB | ✓ Runs great | ~15.4 tokens/s |
| Q3_K_M | 0.5 GB | ✓ Runs great | ~15.4 tokens/s |
| Q4_0 | 0.5 GB | ✓ Runs great | ~15.4 tokens/s |
| Q4_K_S | 0.5 GB | ✓ Runs great | ~15.4 tokens/s |
| Q4_K_M BEST HERE | 0.6 GB | ✓ Runs great | ~12.8 tokens/s |
| Q5_K_M | 0.6 GB | ✓ Runs great | ~12.8 tokens/s |
| Q6_K | 0.7 GB | ✓ Runs great | ~11 tokens/s |
| Q8_0 | 0.8 GB | ✓ Runs great | ~9.6 tokens/s |
Use the right workflow for this model
This model is designed to turn document-page images into structured Markdown, including text, tables, and formulas. PocketPal does not provide the required an OCR workflow that can send page images through the model—not a text-only chat window, so the tracked file is not a beginner phone-chat path.
Read the publisher workflow ↗If you only want a normal private chat, use this simpler model instead:
Check Qwen3 0.6B