Fara 1.5 4B on Other Android device with an Exynos 1380 to 1680 (8 GB RAM)

Can the Other Android device with an Exynos 1380 to 1680 (8 GB RAM) run Fara 1.5 4B?

Yes, it runs well

Runs well. At Q4_K_M it needs about 3.6 GB of 4.4 GB usable, with an estimated speed of 10.2 tok/s.

Best quant: Q4_K_M
Generation speed: 10.2 tok/s
Prompt processing: 15.2 tok/s
First token (1K prompt): 67.5 s
Largest safe context: 30K

Best app to run it on the Other Android device with an Exynos 1380 to 1680 (8 GB RAM)

On Android

PocketPal AI

Mobile app · runs on llama.cpp

Runs the model on the device itself, offline: download it once in the app.

Get it on Google Play Then download Fara 1.5 4B in the app

ChatterUI Runs the model on the device itself, offline: download it once in the app.

Want an agent? Fara 1.5 4B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Fara 1.5 4B

On a phone, tablet or other mobile device you install a chat app and get the model file through it, so there are no commands to copy. Use Fara1.5-4B-Q4_K_M.gguf for the Other Android device with an Exynos 1380 to 1680 (8 GB RAM).

On Android

PocketPal AI

Free mobile app · runs the model on the device with llama.cpp

Get it on Google Play

Install PocketPal AI (free) and open it.
Tap the menu (☰), then Models, then + and Add from Hugging Face.
Search for bartowski/Fara1.5-4B-GGUF, open it and download Fara1.5-4B-Q4_K_M.gguf.
Tap Load next to the model and start a chat. It runs on the device, with no connection needed from then on.

Also works: ChatterUI

Files and commands for a computer

Recommended for the Other Android device with an Exynos 1380 to 1680 (8 GB RAM): Q4_K_M. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q4_K_M file (opens in a new tab)

huggingface.co/bartowski/Fara1.5-4B-GGUF (opens in a new tab)

ollama run hf.co/bartowski/Fara1.5-4B-GGUF:Q4_K_M

Original weights · Hugging Face

Full-precision files from Microsoft, for fine-tuning, vLLM, Transformers.

huggingface.co/microsoft/Fara1.5-4B (opens in a new tab)

No sign-in needed.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 55Good quality (B) · 55 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs well: How well it runs on the Other Android device with an Exynos 1380 to 1680 (8 GB RAM): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	24.8 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	7.6 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	72.4 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Other Android device with an Exynos 1380 to 1680 (8 GB RAM)

Quant	Memory needed	Available	Speed	Runs	Quality	File to pick in the app
`Q2_K`	2.7 GB	4.4 GB	16.7 tok/s	Runs well	40Fair quality (C) · 40 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	`Q2_K`
`Q3_K_M`	3.1 GB	4.4 GB	13.2 tok/s	Runs well	48Fair quality (C) · 48 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	`Q3_K_M`
`Q4_K_M`	3.6 GB	4.4 GB	10.2 tok/s	Runs well	55Good quality (B) · 55 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.	`Q4_K_M`
`Q5_K_M`	4.1 GB	4.4 GB	8.4 tok/s	Slowtight fit	56Good quality (B) · 56 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	`Q5_K_M`
`Q6_K`	4.6 GB	4.4 GB	—	Won't runover the app memory limit	57Good quality (B) · 57 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	`Q6_K`
`Q8_0`	5.7 GB	4.4 GB	—	Won't runover the app memory limit	58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	`Q8_0`
`F16`	9.9 GB	4.4 GB	—	Won't runover the app memory limit	58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	`BF16`

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER F16 · 42.6 tok/s · Runs great
58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER F16 · 46.7 tok/s · Runs great
58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti F16 · 56.8 tok/s · Runs great
58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 F16 · 60.9 tok/s · Runs great
57Good quality (B) · 57 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Q6_K · 51.0 tok/s · Runs great
58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 Q8_0 · 47.9 tok/s · Runs great

Quick answers

How much memory does Fara 1.5 4B need on the Exynos 1380 to 1680 8GB?

At Q4_K_M it needs about 3.6 GB. The Exynos 1380 to 1680 8GB has 4.4 GB usable.

How fast is Fara 1.5 4B on the Exynos 1380 to 1680 8GB?

About 10.2 tok/s at Q4_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Fara 1.5 4B should I use on the Exynos 1380 to 1680 8GB?

Q4_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.