Skip to Content
Platform.Ontology

Build fingerprint and kernel version

Reads the full build ID string and kernel version.

Gets silentlyDevice detailsSoftware stateAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can see your exact phone software build, a long label often over 100 characters

Reads the full build ID string and kernel version.

Pins the exact firmware (model, build, patch) and so the OEM and carrier variant. Tight fingerprint; also tells where a phone was sold.

What it can and can't do

What the user does: Nothing. The app can look it up as soon as it opens

It can

  • See the full Android build label, with tags and type
  • See the kernel version on Android and iPhone
  • Use the label as one clue to tell similar phones apart

It cannot

  • Learn who you are from this label alone
  • See a carrier version on iPhone; Apple gives a plain build and kernel version
  • Change the build or install a different one

How it differs between platforms: Android shows a long detailed label. iPhone shows less and only a partial guess in some cases.

On Android and iPhone

AndroidiPhone
StatusSupportedPartial
First versionAndroid 1.0 (API 1)iOS 2.0
Permission or entitlementNot listednone
Protection levelnonenone
How access is grantednonenone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyNone listedNone listed
APIBuild.FINGERPRINT, ID, DISPLAY, TAGS, TYPE; System.getProperty(os.version)Build and Darwin version; no carrier variant
NotesTypically 100+ charactersNone

Data you get

What comes back: Build fingerprint
Shape: string
How often: Changes on update

FieldTypeUnitRangePrecision
fingerprintstringNoneabout 100 charsexact

Technical limits

  • Rooted or custom ROMs often show test-keys in TAGS

The story

What it is

An app can read the exact firmware and system build of your phone.

For you

You never see it. It is a long label with your phone's maker, build and patch. It tells an app what exact software you have and often where the phone was sold.

For makers

Makers use it for bug fixes on one firmware version and for fraud checks. Because the label is so exact, it is also a strong fingerprint detail for tracking.

Where you see it

TypeExampleApps
gamesA game applies a graphics workaround for a bug on one phone maker's build.None named
securityA bank notices a login from a build string that does not match a real phone.None named
developerA crash tool groups crashes by firmware so engineers find the bad update.Firebase Crashlytics
adsAn ad firm adds the build label to a device fingerprint.None named
mediaA streaming app checks that a build supports a video codec before offering 4K.None named
shoppingA fraud team spots a fake phone because its build label does not exist.None named

Risks

  • Strong fingerprint detail
  • Shows where phone was sold

Android and iPhone in short

  • Android: Available as Build.FINGERPRINT with no prompt.
  • iPhone: iOS shows a coarser build number and kernel version through system calls.

Good uses and abuse

Legitimate uses

  • Crash reports

Known abuse

  • Fingerprint
  • Rooted-device detection

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits5Rough identifying entropy, when known

History

  • 2008-09, Android 1.0 (API 1): Build.FINGERPRINT available

Sources

How well checked: Based on official documentation.

On this page