Charging: Record the HyperOS 3 cap-percent follow-up in the qualification ledger - #61
Merged
Conversation
…tion ledger A GitHub follow-up (PR #52 comment / issue #48) from the tanzanite contributor claims mode 2 hard-caps at 80% with a dumpsys snapshot at the cap. Recorded as a cap-percent candidate (80) only: a single snapshot with status=2 (charging) and no hold/current observation is not hold evidence, and how the mode was set is unstated, so daemon enforcement of external writes stays unproven. The requested follow-up runs (sustained hold, both-direction external-write test) are listed in the issue #48 thread.
github-actions
Bot
added
the
documentation
d4rken
added
device support
…ap mode) A Poco F5 contribution report (HyperOS 3.0.2 / Android 15) shows only the two HyperOS-2-style modes on security_pc_secure_protect_mode_key, answering the ledger's open question: the tanzanite hard-cap value 2 is not HyperOS-3-wide but model- and/or Android-16-dependent, so a future HyperOS 3 gate cannot infer it from the version code alone. Caveats recorded: one wizard row withheld by the contributor, prior root with FDE.ai charge-limit control.
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: records two HyperOS 3 follow-up data points in the device-qualification ledger — the claimed 80% hard cap on the
tanzanitecontributor device (as a cap-percent candidate that does not yet qualify the ROM), and a second device report showing the hard-cap mode is not HyperOS-3-wide.Technical Context
dumpsys batterysnapshot at level 80 while AC-powered; it still reportsstatus: 2(charging) and no hold duration or current reading, so it is recorded as a cap-percent data point, not hold evidence.marbleincontribution report (support mail, HyperOS 3.0.2 / Android 15) shows only the two HyperOS-2-style modes on the same key, no value 2 — so a future HyperOS 3 gate cannot infer the hard-cap mode fromro.mi.os.version.code == 3alone.