Skip to content

t1k:android-hardware-features

FieldValue
Modulet1k-qa
Version1.1.23
Effortlow
Tools—

Keywords: androidmanifest feature, excluded devices, hardware features, install blocked, play console device, required true, unsupported devices, uses-feature

/t1k:android-hardware-features
<app.apk | app.aab> [--json]

Android hardware features: what Google Play treats as required

Section titled “Android hardware features: what Google Play treats as required”

Answers “which hardware features are marked required=true, so Google Play excludes some devices from installing this build?” — the Play Console warning “Your app uses hardware features that some devices don’t have”. Reads a built .apk or .aab. Report only: it never edits a manifest or proposes a fix.

The device-blocking features are almost never written in the manifest as <uses-feature required="true">. They are IMPLIED, and Google Play computes them from two sources:

  1. Permissions. ACCESS_WIFI_STATE implies android.hardware.wifi (required). CAMERA implies android.hardware.camera. ACCESS_FINE_LOCATION implies android.hardware.location.gps. A dozen more — ad/analytics SDKs pull these in.
  2. Screen orientation. An activity with android:screenOrientation="portrait" implies android.hardware.screen.portrait (required); a landscape one implies screen.landscape.

An implied feature is required=true unless the manifest explicitly declares <uses-feature android:name="X" android:required="false"/> to override it.

android:required defaults to true when the attribute is omitted. So a bare <uses-feature android:name="android.hardware.camera"/> is a required feature, not an optional one.

A tool that only lists the explicit <uses-feature> elements will report “everything is required=false, looks fine” and be wrong — it misses every implied one, which is where the real device exclusions come from. This skill replicates aapt2’s implied-feature logic so the report matches what Play actually sees.

Terminal window
S="$(ls -d .claude/skills/t1k-android-hardware-features "$HOME/.claude/skills/t1k-android-hardware-features" 2>/dev/null | head -1)/scripts"
python -I "$S/check_hardware_features.py" app.apk # human table
python -I "$S/check_hardware_features.py" app.aab --json # machine-readable facts

On Windows use python -I or py -I (the python.org installer ships no python3).

InputHow it is readNeeds
.apk / .xapk / .apksaapt2 dump xmltree on the binary manifestaapt2 (Android SDK build-tools; auto-located via ANDROID_HOME/LOCALAPPDATA, or on PATH)
.aabpure-Python protobuf read of base/manifest/AndroidManifest.xmlnothing — no Java, no bundletool

Exit codes: 0 no required hardware feature (no device excluded), 1 one or more required features (devices excluded), 2 usage error, unreadable input, or aapt2 missing for an APK.

Each required feature is tagged by risk of real-world device exclusion:

  • [HIGH] — commonly excludes real devices: wifi, telephony, camera, location.gps, bluetooth, nfc, microphone, touchscreen. For a game pulling these from an ad SDK, they are almost always unintended.
  • [MED] — screen.portrait / screen.landscape: excludes devices locked to the other orientation (some TVs, foldables, car displays).
  • [low] — unlikely to matter in practice.

DECLARED means the manifest wrote required="true"; IMPLIED means Play derived it from a permission or an orientation, and the fix is an override the build never added.

The JSON (--json) carries required_features (name, reason, risk, implied), not_required_features, high_risk_required, and verdict (BLOCKS_DEVICES | NO_REQUIRED_HARDWARE). The script emits facts; the caller reasons over them.

For one build the APK and the AAB come from the same merged manifest, so both report the same set — the skill reads whichever you hand it. Validated on a real build: the AAB protobuf parse produces the identical required set to aapt2 dump badging on the APK.

Reporting the hardware features an APK/AAB marks (or implies) as required=true, and the devices they exclude. Not in scope: editing the manifest, proposing or applying required="false" overrides, build-config changes, Play upload, permissions auditing beyond the feature-implication they cause, or non-hardware <uses-feature> (software/GL features are listed but risk-rated low). Remediation belongs to the engine kit that produces the build.

check_hardware_features.py is a deterministic read. Any caller may run it and quote its output. The severity judgment and any decision to change the build stay with the reasoning caller.