ObliviOS Developer portal Project site

Home / Decisions / ADR-166

Move the upstream baseline from GrapheneOS manifest tag 2026091900 to 2026100600.

Proposed, recorded 14 October 2026.

Decision
ADR-166
Date
2026-10-14
Status
ProposedProposed (owner, 2026-10-14). Accepted when a lynx image on the tag has booted and the ADR-096-class checks pass on the device, and the stallion candidate on the tag is signed and installed.
Mentions
ADR-008, ADR-096, ADR-099
Mentioned by
ADR-218

1Decision

Move the upstream baseline from GrapheneOS manifest tag 2026091900 to 2026100600 (signature verified, manifest commit 26f7e8a760d4), by an in-place repo sync of the existing platform-primary tree as in ADR-099, with the patch packages re-applied on new per-project branches sovereignos-2026100600. One source tree and two output directories (out-lynx, out-stallion) stay; the owner asked to merge nothing. Atlas, the bug fixes and the boot picture reach stallion once, on the new tag, after a lynx image on the tag.

2Why and evidence

Three releases (2026092500, 2026100200, 2026100600) are out: security patch level 2026-10-05, Pixel drivers and firmware on Android 17 QPR1, and a kernel that restores the Android 17 mmap read-ahead behaviour that stalls under memory pressure.

Evidence of 2026-10-14: the tag signature is good (contact@grapheneos.org, the allowed-signers hash of ADR-008 unchanged); 42 of 1057 projects change revision, 6 of the 12 patched projects among them; a whole-branch git merge-tree of each old branch gave no conflict except vendor/adevtool device-common.mk, where upstream and every package append at the end of the file (both kept, upstream first); the exported packages applied with plain git am on the new revisions give the trees of the new build-server branches in all six changed projects (frameworks/base a759681c0630, Settings fa553172abd8, Bluetooth 790eda61b13a, build/release 89ad23af4ccd, system/core 4db206bc1c76, vendor/adevtool f2cef3527ae1).

adevtool generate-all ran for lynx and stallion and showed that memory/zram-size and memory/cached-process-cap had only dropped the stock values from the inclusion lists, which adevtool treats as unknown entries and includes: the regenerated modules carried mmd.zram.size=50% and config_customizedMaxCachedProcesses=1024 again.

Both are now on exclusion lists (zram-size/0002, cached-process-cap/0002); against the unmodified regeneration the only differences are those two entries (MEM-018).

lynx-cur-userdebug 2026101404 built (38111 steps, exit 0, package gate passed; one mmd.zram.size=100%, cap 48 in framework-res, none in the vendor overlay, MEM-019) and the stallion user candidate 2026101405 the same way (39046 steps, exit 0, package gate passed, cap 48, one mmd.zram.size=100%, no debug harness). Details: sovereignos-manifest/provenance/2026100600.md.

3Consequences

The vendor modules are regenerated with --noVerify because they differ from upstream's FileTreeSpec by design; adevtool then writes $(warning into the pin file, which was put back to $(error by hand. Upstream now enables the mmd writeback limit (24 GiB a day), which changes the reading of MEM-005. The branches sovereignos-2026091900* stay as rollback.

The lynx flashset requires bootloader lynx-17.0-15902555 and baseband g5300q-260604-260807-B-16036236. The adevtool caches (about 32 GB) return with every generate-all; -k keeps the unpacked images of the named devices only. The lynx image 2026101404 booted on the device on 2026-10-14 and the decoy switch held in both directions (IMG-003); the stallion candidate has not run on a device.

4Review when

A patch misbehaves on a device or the API check fails in the stallion build; lynx boot or ADR-096-class checks regress; the Updater or the signing path refuses the candidate; a further upstream release arrives before the candidate is installed.

Read from docs/governance/decision-log.md, entry ADR-166.