Why variant data matters more than you think

Last week a friend asked me why his "Galaxy A52" was running Android 12 when his neighbor's "Galaxy A52" was running Android 14. They bought the same phone, same retailer, same week.

They didn't, actually. He had an SM-A525F (international single-SIM). His neighbor had an SM-A526U (Verizon US). Different model numbers, different chipsets (Snapdragon 750G vs 778G), different cellular bands, and crucially different firmware update schedules. Samsung pushed the international variant to Android 14. The Verizon variant got the update three months later because Verizon insists on certifying every firmware before it ships.

The two phones share a marketing name. They share almost nothing else.

How spec sites usually present this

Look up "Samsung Galaxy A52" on any of the big spec sites. You'll get one page. The page picks one variant — usually the international flagship — and presents its specs as the canonical ones. The chipset listed is the 778G. The bands listed are the international ones. The Android version is whatever the international SKU is on right now.

If you bought the Verizon model, the page is wrong about most of those things. Not maliciously wrong — there's just nowhere on the page to indicate which variant you have.

This is fine for the median user looking up a phone they're considering buying. It's terrible for the user trying to figure out why their specific phone behaves differently from the spec sheet.

The data is public

Google maintains a catalog of every Android device that's eligible to install apps from the Play Store. The catalog has every variant. It's been public for years. Anyone can query it.

The catalog uses an internal protobuf format that almost nobody bothered to write a converter for, which is most of why it didn't get used widely. We wrote one (it's in the methodology page if you want the technical detail) and turned the catalog into the Soft9 database.

That's why every device page on this site has a "Known variants" table. It's not a feature we added — it's the natural way to present the data once you have it.

Concrete examples

A few cases where the variant matters:

• Samsung Galaxy A02s — 44 variants. Some have 2GB RAM, some have 4GB. Some have NFC, some don't. The "Galaxy A02s" page on most spec sites will tell you it has NFC. Three out of every four units don't.
• Pixel 6a — 6 variants. The ones sold through Google Fi vs the unlocked Google Store version vs the carrier-specific variants behave differently around eSIM provisioning. If you're trying to add a Google Voice number to a Pixel 6a and it's not working, this is the first thing to check.
• Xiaomi Redmi 12 — 27 variants. Indian, Indonesian, Brazilian, and global ROMs ship different default app bundles and different MIUI/HyperOS update schedules. If you imported one from a different region, your update path is genuinely different.
• Motorola Edge 40 — 8 variants. The European variants got Android 14 six months before the Latin American variants. The Latin American variants are still running Android 13 as I write this.

Why this matters when you're buying

If you're shopping internationally — gray-market imports, expat re-exports, traveling and buying locally — the variant you end up with directly affects:

• Which cellular bands work in your home country
• Whether you'll get OS updates on the same schedule as the international flagship
• Which carrier-specific apps are pre-installed and can't be removed
• Whether the phone's eSIM works with your carrier
• Whether the warranty applies in your region

A "global" variant (suffix _global in many model codes) is usually the safest bet for cross-border use. A US carrier variant (suffix often includes the carrier code, e.g. U for Verizon, T for T-Mobile) is the worst — locked to that carrier's bands, on that carrier's update schedule, with that carrier's bloatware.

What we surface

On every device page, you'll see:

• The full list of known variants with their model codes
• The product code / variant ID for each
• Known marketing names per region
• Aggregated data showing what RAM, Android versions, and display configurations exist across all variants

If your specific variant isn't in the list, it's because it's not in Google's catalog. Either the device truly doesn't ship that variant, or it ships but isn't Play-Store-eligible (rare, but happens with some Chinese-domestic-only phones).

What we don't yet surface

We're working on:

• Per-variant firmware update history. This is hard because Google's catalog tells us what API levels are supported, not what build numbers have actually shipped. Probably needs a different data source.
• Per-variant carrier band tables. Same problem — the data isn't in the catalog directly. We can derive partial information from the model code patterns but it's not reliable enough yet.
• Pricing per variant. No good public source for this.

If you have a need for variant-level data we don't currently surface, tell us. The dataset is rich enough that we can probably extract it; we just need to know what's worth surfacing.

— Marcus