Charging: Record the marblein native-UI confirmation in the ledger - #70
Merged
Conversation
A native-UI screenshot from the Poco F5 (marblein, HyperOS 3.0.2) contributor shows the Battery protection screen carries exactly two charging-protection entries, "Charge fully" and "Intelligent charging", with no hard-cap option. That upgrades the earlier wizard-capture inference to a direct observation of the OEM UI. It does not disentangle the cause: tanzanite differs from marblein in both model and Android 16 / ROM 3.0.3, so model-dependence and Android-16/OS-3.0.3-dependence stay confounded, and the qualified- codename gate remains the only sound design either way. Also records why marblein must not be allowlisted for xiaomi-hyperos3-v1: that adapter's protective default is FixedLimit(80) = mode 2, which this device lacks, so apply() would write "2", read it back from the settings row and decode Verified(FixedLimit(80)) while the daemon ignores it, claiming a cap that is not active.
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. This is a documentation-only update to the device-qualification ledger, recording that the Poco F5 (
marblein, HyperOS 3.0.2) has no hard-cap charging mode and why it stays diagnostics-only.Technical Context
tanzanitediffers frommarbleinin both model and Android 16 / ROM 3.0.3, so model-dependence and Android-16/OS-3.0.3-dependence remain confounded. The qualified-codename gate stays the only sound design under either explanation.xiaomi-hyperos3-v1: that adapter's protective default isFixedLimit(80)= mode2, which the device lacks, soapply()would write"2", read it back from the settings row and decodeVerified(FixedLimit(80))while the daemon ignores it, claiming a cap that is not active.QUALIFIED_HYPEROS_VERSIONfrom2, whose sole protective mode is Adaptive. That is blocked on the existing project-wide open item (adaptive enforcement unobserved on both HyperOS generations), not on anything specific to this device.