Mobile

Can Immortalis-G925 run Gemma 4?

Shared mobile memory with mobile acceleration limits. The checker below ranks Gemma 4 E2B, E4B, 12B, 26B A4B, and 31B specifically for Immortalis-G925.

GPU
VRAMshared
BW~77 GB/s
RAM--
CORES--
WebGPU
0RUNS GREAT
0RUNS WELL
0DECENT
0TIGHT FIT
0BARELY RUNS
0TOO HEAVY
Gemma 4 only
Gemma 4 E2BbestQ4_K_M

Phones, tablets, old laptops, and the fastest local proof.

Memory: 3.1 GBUse: --Speed: ~10 tok/sScore: 0/100
UNKNOWN
0/100

Better phones, Apple silicon laptops, and mainstream desktops.

Memory: 4.6 GBUse: --Speed: ~7 tok/sScore: 0/100
UNKNOWN
0/100

16GB+ unified-memory Macs and desktops with room for context.

Memory: 7.1 GBUse: --Speed: ~4 tok/sScore: 0/100
UNKNOWN
0/100

The instruct 12B when you want chat, vision, and a 256K window on 16GB+ machines.

Memory: 7.1 GBUse: --Speed: ~4 tok/sScore: 0/100
UNKNOWN
0/100
Gemma 4 26B-A4B IT4B activeQ4_K_M

Strong desktop GPUs and disciplined 24GB+ Apple silicon setups.

Memory: 15.8 GBUse: --Speed: ~2 tok/sScore: 0/100
UNKNOWN
0/100

Gemma-family MoE when you want the newer diffusion decode path and multimodal prompts.

Memory: 13.8 GBUse: --Speed: ~2 tok/sScore: 0/100
UNKNOWN
0/100

High-end workstations where local quality matters more than convenience.

Memory: 19 GBUse: --Speed: ~2 tok/sScore: 0/100
UNKNOWN
0/100

Full Model Directory

Explore 130+ Other Open-Weight Models on This Hardware

Compare Llama 3.3, Qwen 3, DeepSeek-R1, Mistral, and Phi on Immortalis-G925, or run a side-by-side GPU and Apple Silicon benchmark comparison.

Hardware Memory Analysis

Usable Memory Pool & Bandwidth Profile for Immortalis-G925

Immortalis-G925 shares system LPDDR memory (8 GB profile, ~77 GB/s bandwidth) across the OS kernel, display buffers, and AI runtime. Android Low Memory Killer (LMK) and iOS Jetsam enforce strict headroom limits near 50–55% of physical RAM (5.6 GB practical budget), which is why mobile deployments focus on Gemma 4 E2B and compact E4B bundles rather than desktop checkpoints.

Practical Model Budget

5.6 GB

Memory Bandwidth

~77 GB/s

Recommended Checkpoint

Gemma 4 E2B (Q4_K_M)

Gemma 4 Checkpoint Compatibility Matrix on Immortalis-G925

Evaluated at Q4_K_M baseline weights plus 0.5 GB baseline runtime overhead against Immortalis-G925's 5.6 GB usable budget. Leave at least 1.5–4 GB spare headroom for multi-turn KV cache expansion.

ModelQ4_K_M MemoryEst. SpeedGradePractical Headroom Verdict
Gemma 4 E2B3.1 GB~10 tok/sUnknownExceeds on-device memory budget
Gemma 4 E4B4.6 GB~7 tok/sUnknownExceeds on-device memory budget
Gemma 4 12B7.1 GB~4 tok/sUnknownExceeds on-device memory budget
Gemma 4 12B IT7.1 GB~4 tok/sUnknownExceeds on-device memory budget
Gemma 4 26B-A4B IT15.8 GB~2 tok/sUnknownExceeds on-device memory budget
DiffusionGemma 26B-A4B IT13.8 GB~2 tok/sUnknownExceeds on-device memory budget
Gemma 4 31B19 GB~2 tok/sUnknownExceeds on-device memory budget

Mobile Thermal & Memory Watchdog Guide for Immortalis-G925

  • Deploy Gemma 4 E2B first using Google AI Edge Gallery (Android LiteRT) or PocketPal (iOS/Android GGUF).
  • Close camera apps, games, and heavy browser tabs before loading weights to maximize headroom beneath Android LMK and iOS Jetsam limits.
  • Keep prompts short and context capped at 2K–4K tokens; continuous 10+ minute sessions on phones trigger passive thermal throttling.

Frequently Asked Questions for Immortalis-G925

What is the best Gemma 4 model to run on Immortalis-G925?
Based on Immortalis-G925's 5.6 GB practical memory budget and ~77 GB/s bandwidth, Gemma 4 E2B (Q4_K_M, 3.1 GB) is the strongest comfortable fit (~10 tok/s).
Can Immortalis-G925 run Gemma 4 26B-A4B MoE locally?
No. Gemma 4 26B-A4B requires ~15.8 GB at Q4_K_M, exceeding Immortalis-G925's 5.6 GB on-device memory budget. Use Gemma 4 E2B instead.
How fast does Immortalis-G925 generate tokens with Gemma 4?
With ~77 GB/s memory bandwidth, Gemma 4 E2B at Q4_K_M averages roughly 10 tokens per second when fully resident without swap or PCIe spillover.
Which quantization format works best on Immortalis-G925?
Start with Q4_K_M (~4.5 bits/weight) to keep memory headroom free for 8K+ context windows. Step up to Q6_K or Q8_0 only if Q4_K_M consumes well under 60% of available VRAM or unified memory.