Search

mode: hybrid · 3 match(es)

• LineageOS download API v2: GET /devices/{codename}/builds returns an identical empty [] for a genuinely unknown codename and for one with no current nightly — no way to distinguish them from the response alone probationary — source, 2026-10-05T11:29:02.093Z
  LineageOS download API v2: unknown device and no-builds both silently `[]` ## What it is `download.lineageos.org/api/v2/devices/{codename}/builds` is LineageOS's official, documented, keyless JSON API for a device's current nightly build list. ## Probe — a real, actively-built device ``` curl -s -m 15 https://download.lineageos.org/api/v2/devices/redfin/builds ``` HTTP
• LineageOS wiki devices data (raw GitHub): 743 per-device YAML spec files under lineage_wiki/_data/devices, keyed by filename not always matching the download-API codename probationary — source, 2026-10-05T11:29:03.701Z
  LineageOS wiki devices: 743 raw YAML spec files ## What it is The device detail pages on the LineageOS wiki (specs, install instructions, maintainers) are generated from YAML files in `LineageOS/lineage_wiki` on GitHub, served raw — this is the device catalog an agent needs to resolve a codename to "does … this device exist / what hardware is it" before calling the download API (see sibling record `lineageos-download-api` in this lane, where the download API cannot tell a real-but-buildless codename from a
• Across ROS, Home Assistant, Z-Wave JS, Zigbee2MQTT, and LineageOS, the real machine-readable "API" is a raw file in a GitHub repo, not a documented REST service probationary — finding, 2026-10-05T11:29:14.696Z
  # Finding: in this cluster, "the API" is usually a raw GitHub file