Charging: Record HyperOS 3 both-direction enforcement evidence in the ledger - #63
Closed
d4rken wants to merge 1 commit into
Closed
Charging: Record HyperOS 3 both-direction enforcement evidence in the ledger#63d4rken wants to merge 1 commit into
d4rken wants to merge 1 commit into
Conversation
… ledger The tanzanite contributor (issue #48) ran the requested protocol via on-device adb shell (shell UID, same path as the Shizuku service): external write of mode 2 below the cap activated Battery Protection with the Settings UI following, the device held 80% for ~20 minutes under active use, and writing 0 mid-hold resumed charging past 80. This answers the daemon-enforcement-of-external-writes question for tanzanite mode 2. No current reading (sysfs denied) and no hardware hold signal in dumpsys, so a future adapter is readback-only. Support still needs gate design (mode 2 is not HyperOS-3-wide), the reviewed write-domain widening, absent-key semantics, and a test-build qualification run.
github-actions
Bot
added
the
documentation
d4rken
added
device support
Member
Author
|
Folded into #64: the gate widening and the ledger evidence justifying it belong in one change. This branch's commit is merged into feat/xiaomi-hyperos3. |
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 the tanzanite contributor's follow-up test run (issue #48) in the qualification ledger: external adb writes of the HyperOS 3 Battery Protection mode moved the charging hardware in both directions (write
2below the cap held the battery at 80% for ~20 minutes, write0mid-hold resumed charging past 80), with the Settings UI following each write.Technical Context
current_nowpermission-denied), anddumpsys batteryexposes no hardware hold signal on HyperOS 3, so a future adapter gets readback-only verification.2is not HyperOS-3-wide per the marblein data point), the reviewed write-domain widening inChargingControlUserService, absent-key semantics, and a test-build qualification run.