Charging: Record the second GrapheneOS device in the qualification ledger - #94
Merged
Conversation
…dger A Pixel 10 `frankel` on GrapheneOS 2026081301 running Amply 0.5.0-beta0 reported in on issue #49. It closes two of the gaps the GrapheneOS row carried since the Shizuku re-gate: Amply's own Shizuku service reading the key and offering the control had only ever been inferred from the tester's adb runs on `komodo`, and no minified build had been seen on the ROM at all. The `beta` build type minifies and shrinks resources, so this run covers the R8 leg too. Scoped deliberately narrow. The reporter said the app works, not that they watched it hold at 80%, so the row records no new enforcement evidence and the open-gap bullet keeps every enforcement claim on this ROM resting on the `komodo` observation. A full-charge session, its restore, and boot recovery stay unrun. No code change: the GrapheneOS gate is identity-based (`app.grapheneos.*` system packages plus the system user) with no codename allowlist, so a new device needs no entry to be supported.
github-actions
Bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
No user-facing behavior change. Documentation only: the device-qualification ledger gains a second GrapheneOS device (Pixel 10
frankel, GrapheneOS 2026081301, Amply 0.5.0-beta0) reported on issue #49, and the GrapheneOS open-gap list narrows to what that report leaves unverified.Technical Context
app.grapheneos.*system packages plus the system user) with no codename allowlist, unlike the Xiaomi HyperOS 3 adapter. A Pixel 10 on GrapheneOS already matched; the Pixel adapter can't claim it either, since its gate requires the Settings Intelligence charging-optimization action GrapheneOS doesn't ship.komodo, and no minified build had run on the ROM.betasetsisMinifyEnabled/isShrinkResources, so this covers the R8 leg as well.komodoobservation. Full-charge session, its restore, and boot recovery stay unrun.GrapheneOsChargingAdapter.reconnectGestureSupport = ReconnectSupport.NONE, which follows frompolicyLatchesAtPlug. Noted in the row as correct rendering under R8, not as a defect.Refs #49