Hardware Field Availability States
In naive hardware diagnostic applications, when a value cannot be retrieved, the utility frequently displays 0, an empty string, or simply omits the row. Under Architectural Decision ADR-001, Voodoo Hardware Info guarantees that every field explicitly reports its operational availability status.
If an Android 14 phone shows no Wi-Fi BSSID, does the device lack Wi-Fi hardware? Has the user denied location permission? Did Google restrict access in Android 10? Or did the Wi-Fi service fail? Conflating these cases obscures the truth. Voodoo assigns one of 9 discrete states to every inspection property so you know the exact operational cause.
The 9 Canonical Availability States
- AVAILABLE Value Present
-
The metric was successfully retrieved and validated from the Android platform API, Linux kernel filesystem (
/procor/sys), system properties, or hardware driver. The raw and formatted values are populated, and JSON serialization outputs the true primitive value. - UNAVAILABLE Hardware Absent
- The physical hardware or subsystem is not installed or enabled on this specific device. Examples: an external barometer sensor on a budget handset, or a removable microSD slot on an unexpandable phone.
- UNSUPPORTED OS Version Incompatible
-
The underlying Android operating system release does not support this query API. For example, querying
Build.SOC_MODELon an Android 10 device, or querying HDR display capabilities on Android 4.4. - PERMISSION_REQUIRED Ungranted Manifest Permission
- The field can be queried via standard platform APIs, but requires an optional Android runtime permission that has not yet been requested from the user (such as location access for active GNSS status).
- PERMISSION_DENIED User Explicit Denial
- The user explicitly declined the runtime permission prompt, or revoked it in system settings. The app continues to function cleanly, marking only the affected property as denied.
- ROOT_REQUIRED Kernel Privilege Boundary
- The target node is protected by Linux filesystem permissions (e.g. readable only by UID 0) or SELinux policies that block third-party application sandboxes. Reading it requires an elevated su shell (e.g. certain raw battery current registers or protected GPU clock sysfs paths).
- RESTRICTED_BY_ANDROID Platform Privacy Gate
-
The field is intentionally concealed or restricted by Google platform security changes. Even with normal permissions, standard userland apps are prohibited from reading it. Examples:
Build.getSerial()on API 29+ requiring privileged system apps, or randomized MAC addresses. - RETRIEVAL_FAILED Runtime Operational Error
- An unexpected exception occurred during collection: a system service crashed, an IPC binder call timed out, or a kernel file handle produced unparseable contents.
- UNKNOWN Unresolved Status
- The state cannot be deterministically determined at collection time (e.g. before an initial asynchronous sensor listener triggers).
How Availability States Appear in JSON Reports
When a field is not AVAILABLE, the JSON serializer sets value: null, preserves the state enum in availability, and populates unavailability_reason with the human-readable description:
{
"id": "general.serial_number",
"display_name": "Device Serial Number",
"data_type": "STRING",
"availability": "RESTRICTED_BY_ANDROID",
"value": null,
"unavailability_reason": "Restricted by Android (Privileged System Permission Required on API 29+)",
"formatted_value": "[Restricted by Android 10+]",
"source": "ANDROID_API",
"min_api_required": 26
}