Sensor list and vendor metadata
Lists the sensors the phone has, with vendor, resolution and range.
In one line
Can list the sensors your phone has, with maker, range and precision
Lists the sensors the phone has, with vendor, resolution and range.
The set of sensors with vendor and power numbers differs by model and firmware and is a stable device identifier.
What it can and can't do
What the user does: Nothing. It happens when the app or game checks what hardware it can use
It can
- List all sensors on Android, often 20 to 60
- See each sensor's maker, resolution and range
- Check which sensors exist on iPhone as yes or no answers
- Use the list as a clue in a device fingerprint
It cannot
- Get maker, range and precision details on iPhone; only yes or no answers
- See your sensor data from the list itself
- Change a sensor
How it differs between platforms: Android shows full details. iPhone shows only whether each sensor is available.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 1.5 (API 3) | iOS 4.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 | SensorManager.getSensorList(TYPE_ALL), Sensor.getVendor(), getResolution(), getMaximumRange() | Only availability booleans |
| Notes | Typically 20 to 60 sensors | None |
Data you get
What comes back: Sensor list
Shape: list
How often: Static
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
sensors | list | None | 20 to 60 on Android | exact |
Technical limits
- iOS exposes availability only
The story
What it is
An app can list your phone's sensors, with maker names and ranges, which differ by model.
For you
You do not see it. Apps just check whether your phone has a gyroscope or a heart rate sensor before offering a feature. The list can also single out your model and firmware.
For makers
Makers use it to turn features on or off for each phone. The details, like vendor and range, also form a stable fingerprint of the model. It is more useful to trackers on Android than on iPhone.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A tilt controlled game checks that you have a gyroscope before it shows motion controls. | None named |
| ar-vr | An AR app checks for the sensors it needs and tells you if your phone is too old. | Pokemon GO |
| fitness | A fitness app checks for a step counter and heart rate sensor to decide what to show. | Samsung Health |
| analytics | An analytics SDK reads the vendor names and ranges to tell which exact phone model you have. | None named |
| security | An anti fraud tool sees a sensor list that looks like an emulator and blocks the sign up. | None named |
| developer | A developer logs sensor lists in crash reports to find a bug that hits one phone model. | None named |
Risks
- Fingerprint of the model
- Emulator detection can block users
Android and iPhone in short
- Android: Android apps can list every sensor with vendor, resolution and range with no prompt.
- iPhone: iPhone has no public list, but apps can test sensors one by one.
What the platform says
- Google: Sensors overview. Android lets apps list the sensors on a device so they can use what is there.
Good uses and abuse
Legitimate uses
- Feature detection
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 | 6 | Rough identifying entropy, when known |
Related capabilities
Related
- Sensor calibration fingerprint (SensorID). Can maybe recognize your phone from tiny sensor flaws, with no ID or prompt
Sources
How well checked: Inferred from related behavior.