Android’s model number, device code, product name, build number and build fingerprint can all appear in diagnostics. They describe different things, and using the wrong one can make a phone-model lookup fail.
The model number is intended to identify a hardware/device variant. Examples can look like SM-G991B, CPH2581 or a manufacturer-specific alphanumeric code. This is usually the most useful value for the LocationOf Android model lookup.
The marketing name is the human-friendly product name: for example, a Galaxy, Pixel, Xperia or another branded phone family. One marketing name can map to several model identifiers.
LocationOf’s `/phones/` pages group known model identifiers under the marketing name so users do not need a separate near-duplicate SEO page for every regional code.
The build number normally identifies a particular software/firmware build. It can change after an operating-system update even though the physical phone model has not changed.
A long build string is therefore not ideal as the primary hardware identifier.
An Android build fingerprint is an even more detailed software identity string containing manufacturer, product, build and version information. It is useful for software diagnostics and compatibility, but it is not the same as the concise model number a human usually wants to search.
Android build properties can also expose internal `device` and `product` names. Those may be codenames or platform identifiers rather than the retail name.
When a lookup does not recognize one string, check whether Settings shows a separate “Model” or “Model number” value.
LocationOf historically receives a platform/model value from mobile clients and maps that value to a human-readable device. The catalog lookup is designed around those known mappings. Feeding it an unrelated serial number, IMEI or firmware fingerprint will not necessarily produce the phone name.
On modern Android, look in Settings → About phone or About device. Manufacturers use different labels, so you may need to open a model/hardware subsection.
For a step-by-step explanation, continue with How to find your Android model number.
Imagine a phone whose retail name stays the same for three years of software updates. Its model number can remain constant while the Android version and build number change several times. If you search the latest build number in a hardware catalog, you may get no result even though the model itself is well known.
Conversely, two regional variants sold under the same retail name can have different model numbers while running the same Android build family.
If the problem is device compatibility, include the retail name, model number and Android version. If the problem began after an update, include the build number as well. That gives support enough context without forcing one identifier to do every job.
Model numbers and software builds are generally much less sensitive than identifiers tied to one physical unit. Still, there is rarely a reason to publish an IMEI, serial number or account identifier in a public forum when a model code is all that is needed for compatibility help.