text model · MiniMax · Android
Can I run MiniMax-M1-80k on Samsung Galaxy S26 Ultra (16GB, 1TB config)?
No. MiniMax-M1-80k needs ~284.6 GB even at Q4_K_M, but Samsung Galaxy S26 Ultra (16GB, 1TB config) only has ~12 GB usable.
Needs ~284.6 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 272.6 GB: MiniMax-M1-80k needs roughly 284.6 GB at Q4_K_M and Samsung Galaxy S26 Ultra (16GB, 1TB config) leaves only about 12 GB usable for a model. No single tracked device has enough memory; MiniMax-M1-80k needs a multi-GPU or high-memory rig.
- Q4_K_M needed
- ~284.6 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
- 456B (MoE, 45.9B active)
- Q4_K_M size
- 278.7 GB
- Context
- 1000k
- 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
FAQ
Can Samsung Galaxy S26 Ultra (16GB, 1TB config) run MiniMax-M1-80k?
No. MiniMax-M1-80k needs ~284.6 GB even at Q4_K_M, but Samsung Galaxy S26 Ultra (16GB, 1TB config) only has ~12 GB usable.
How much memory does MiniMax-M1-80k need?
Samsung Galaxy S26 Ultra (16GB, 1TB config) does not have enough memory. At Q4_K_M the weights are ~278.7 GB; with KV cache and runtime overhead, budget ~284.6 GB at a 4k context. It is a Mixture-of-Experts model (456B total / 45.9B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run MiniMax-M1-80k 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/minimax-m1-80k/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.