Can OneJev 9B run on vivo Y600i?
Weights exceed this memory budget · custom workflow required
Weight fit is not phone app support
The tracked Q4_K_M weights are 5.6GB; the generic working-memory estimate is 7.1GB against 4GB usable. Image inputs need additional projector memory.
OneJev scores typed decisions in a single forward pass, not chat replies. The decode estimates below are not measured decision latency. The publisher's qev server and System One client are required; AICanRun has not verified a phone app route.
−3.1GB short
memory that doesn't exist here
7.1GB
needed at Q4_K_M
Q4_K_M
quant checked
needs 7.1 GBusable 4 GB · short 3.1 GB
Snapdragon 4 Gen 26 GB RAMCPU / GPU
Three ways forward
1
Try a smaller quant
No quant of OneJev 9B fits this phone — even the smallest is too big. Options 2 and 3 are your real choices.
3
Run it in the cloud
The full OneJev 9B, no download, at data-center speed — pay per token.
provider recommendations coming later
Where the memory goes
| Component | Detail | GB |
|---|---|---|
| Model weights | Q4_K_M GGUF (5.6 GB) + mmap overhead | 5.9 |
| KV cache | 4K context window | 0.6 |
| Runtime | llama.cpp + app overhead | 0.6 |
| Total needed | at Q4_K_M, 4K context | 7.1 |
| Working budget | 6 GB RAM − Android system reserve | 4 |
| Headroom | memory shortfall | −3.1 |
Pick your quant
| Quant | Download | Verdict | Speed |
|---|---|---|---|
| Q2_K | 3.8 GB | ✕ Won't fit | won't fit |
| Q3_K_M | 4.6 GB | ✕ Won't fit | won't fit |
| IQ4_XS | 5.2 GB | ✕ Won't fit | won't fit |
| Q4_K_S | 5.4 GB | ✕ Won't fit | won't fit |
| Q4_K_M | 5.6 GB | ✕ Won't fit | won't fit |
| Q5_K_M | 6.5 GB | ✕ Won't fit | won't fit |
| Q6_K | 7.4 GB | ✕ Won't fit | won't fit |
| Q8_0 | 9.5 GB | ✕ Won't fit | won't fit |
Related checks
More on vivo Y600i
OneJev 9B on other phones