Skip to Content
Platform.Ontology

CPU cores and ABI

Reads core count and CPU architecture with no prompt.

Gets silentlyDevice detailsHardware capacityAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can see how many CPU cores your phone has and what chip type, with no prompt

Reads core count and CPU architecture with no prompt.

Identifies chipset class (4 to 10 cores). A device-model proxy: apps pick builds and thread pools with it, trackers add it to a fingerprint.

What it can and can't do

What the user does: Nothing. The app checks when it starts, often to pick graphics or video settings

It can

  • See the number of cores, typically 4 to 10 on Android and 2 to 10 on iPhone
  • See the chip type; nearly all current phones are 64 bit ARM
  • Pick lighter or heavier settings to match your phone

It cannot

  • See detailed chip info on newer Android, where per-app limits block parts of CPU info files
  • Learn who you are from core count alone
  • Change how fast the chip runs

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
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
APIRuntime.availableProcessors(), Build.SUPPORTED_ABIS (API 21), /proc/cpuinfo (restricted per app on newer builds)Cores 2 to 10 on iPhone; arm64 only
NotesCore count 4 to 10; ABI arm64-v8a on nearly all current phonesNone

Data you get

What comes back: Core count, ABI list
Shape: integer
How often: Static

FieldTypeUnitRangePrecision
coresintegercores2 to 10exact

Technical limits

  • Low entropy within a model

The story

What it is

An app can see how many processor cores your phone has and what chip type.

For you

You never see this check. Apps use it to decide how hard to work your phone. It also shows how powerful or old your phone is.

For makers

Makers pick graphics quality and how many tasks to run at once. Trackers add core count to a device fingerprint, since it is a stable detail.

Where you see it

TypeExampleApps
gamesA 3D game picks high graphics on an eight core phone and low graphics on a four core phone.None named
creativeA video editor uses all cores to render a clip faster, and fewer on weak phones.None named
mediaA streaming app picks a video decoder that fits your chip.None named
ar-vrAn AR app turns off heavy effects on phones with few cores so tracking stays smooth.None named
adsAn ad firm adds core count to a device fingerprint.None named
developerA developer builds a different app file for each chip type to keep the download small.None named

Risks

  • Shows how new your phone is
  • Adds to a fingerprint

Android and iPhone in short

  • Android: Read through system properties with no prompt, including the chip type.
  • iPhone: Read through system calls with no prompt.

Good uses and abuse

Legitimate uses

  • Thread pool sizing

Known abuse

  • Fingerprint

Scores

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

History

  • 2014-11, Android 5.0 (API 21): SUPPORTED_ABIS list replaces CPU_ABI strings
  • RAM size. Can see how much memory your phone has, down to the exact byte, with no prompt

Same idea on the web

Sources

How well checked: Inferred from related behavior.

On this page