Gemma 4 Secret MTP Discovery Sparks Developer Backlash
Is this a scandal?
No longer — the story has resolved. Noise 1/100, cooling down, across 0 sources.
Independent researchers will likely attempt to patch the Gemma 4 weights to re-enable MTP within the next few weeks. Google may face pressure to release an 'Experimental' or 'Turbo' branch of Gemma 4 that officially supports these faster inference methods.
Noise 1/100 — louder than 85% of tracked AI controversies.
Why it matters
The removal of performance-enhancing features suggests a growing trend of 'nerfing' open-weights models to maintain a gap between free and paid enterprise offerings. This impacts developers' ability to optimize on-device inference for mobile applications.
Key points
- A developer discovered hidden Multi-Token Prediction (MTP) weights in Gemma 4 files via the LiteRT API.
- A Google employee allegedly confirmed MTP was disabled to ensure 'compatibility and broad usability' across different hardware.
- The community is exploring reverse-engineering the LiteRT compute graph to restore the disabled performance features.
The story
Google has come under scrutiny after developers discovered that the Gemma 4 model architecture contains latent Multi-Token Prediction (MTP) weights that were disabled in the official release. The discovery was made by a developer using the LiteRT API on a Google Pixel 9 device, where tensor shape errors revealed the presence of MTP heads designed for speculative decoding. A Google representative reportedly confirmed that the feature was intentionally removed to ensure broad compatibility across various hardware environments. This revelation follows previous community disappointment regarding the unreleased Gemma 124B model. Technical experts are now discussing the possibility of reverse-engineering the LiteRT compute graph to reactivate these high-speed generation capabilities. Google has not yet issued a formal statement regarding whether a 'Pro' version of the weights with MTP enabled will be released to the public.
Who's involved
Discovered the hidden weights and expressed frustration that Google 'nerfed' the model's speed.
Argues that Google is gatekeeping performance and wants full transparency regarding model capabilities.
Maintains that removing the feature was a technical decision to ensure the model runs reliably on a wider range of consumer devices.
Noise Level
The timeline
Google confirmation reported
The developer claims a Google employee confirmed the intentional removal of MTP for compatibility reasons on a Hugging Face discussion thread.
Hidden MTP weights discovered
Reddit user Electrical-Monitor27 reports finding MTP prediction heads while debugging LiteRT on a Pixel 9.
The forecast
Independent researchers will likely attempt to patch the Gemma 4 weights to re-enable MTP within the next few weeks. Google may face pressure to release an 'Experimental' or 'Turbo' branch of Gemma 4 that officially supports these faster inference methods.
Forecast, not fact — an editorial estimate we score when this resolves.
That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.
Join the Discussion
Discuss this story
Community comments coming in a future update
Be the first to share your perspective. Subscribe to comment.