text model · Seed-OSS · Android
Can I run Seed-OSS 36B Instruct on Samsung Galaxy S26 Ultra (16GB, 1TB config)?
No. Seed-OSS 36B Instruct needs ~22.5 GB even at Q4_K_M, but Samsung Galaxy S26 Ultra (16GB, 1TB config) only has ~12 GB usable.
Needs ~22.5 GB even at Q4_K_M, but only ~12 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 10.5 GB: Seed-OSS 36B Instruct needs roughly 22.5 GB at Q4_K_M and Samsung Galaxy S26 Ultra (16GB, 1TB config) leaves only about 12 GB usable for a model. The lightest tracked hardware that runs Seed-OSS 36B Instruct is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Seed-OSS 36B Instruct on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~22.5 GB
- Usable on device
- ~12 GB
- Device memory
- 16 GB
Which quant fits
How to run it
On Android use PocketPal AI (Polished app, download GGUF and run offline.).
- Parameters
- 36B
- Q4_K_M size
- 20.27 GB
- Q8_0 size
- 35.78 GB
- Context
- 512k
- Memory
- 16 GB ram
- Usable for weights
- ~12 GB
- Best runtime
- llama.cpp (PocketPal) or MLC-LLM (Adreno GPU path)
What you can run instead
Run Seed-OSS 36B Instruct on other hardware
FAQ
Can Samsung Galaxy S26 Ultra (16GB, 1TB config) run Seed-OSS 36B Instruct?
No. Seed-OSS 36B Instruct needs ~22.5 GB even at Q4_K_M, but Samsung Galaxy S26 Ultra (16GB, 1TB config) only has ~12 GB usable.
How much memory does Seed-OSS 36B Instruct need?
Samsung Galaxy S26 Ultra (16GB, 1TB config) does not have enough memory. At Q4_K_M the weights are ~20.27 GB; with KV cache and runtime overhead, budget ~22.5 GB at a 4k context.
What is the best tool to run Seed-OSS 36B Instruct 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/seed-oss-36b/samsung-s26-ultra) 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.