CPU cores and ABI
Reads core count and CPU architecture with no prompt.
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
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 1.0 (API 1) | iOS 2.0 |
| Permission or entitlement | Not listed | none |
| Protection level | none | none |
| How access is granted | none | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | None listed |
| API | Runtime.availableProcessors(), Build.SUPPORTED_ABIS (API 21), /proc/cpuinfo (restricted per app on newer builds) | Cores 2 to 10 on iPhone; arm64 only |
| Notes | Core count 4 to 10; ABI arm64-v8a on nearly all current phones | None |
Data you get
What comes back: Core count, ABI list
Shape: integer
How often: Static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
cores | integer | cores | 2 to 10 | exact |
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
| Type | Example | Apps |
|---|---|---|
| games | A 3D game picks high graphics on an eight core phone and low graphics on a four core phone. | None named |
| creative | A video editor uses all cores to render a clip faster, and fewer on weak phones. | None named |
| media | A streaming app picks a video decoder that fits your chip. | None named |
| ar-vr | An AR app turns off heavy effects on phones with few cores so tracking stays smooth. | None named |
| ads | An ad firm adds core count to a device fingerprint. | None named |
| developer | A 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2014-11, Android 5.0 (API 21): SUPPORTED_ABIS list replaces CPU_ABI strings
Related capabilities
Related
- RAM size. Can see how much memory your phone has, down to the exact byte, with no prompt
Same idea on the web
- CPU logical core count. Can see how many processor threads your device has
Sources
How well checked: Inferred from related behavior.