Repository navigation
Prepare Ventoid 0.4.1: reliable USB operations and diagnostics - #22
Merged
Merged
Conversation
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
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.
USB preparation could be interrupted by Activity recreation, and Refresh could re-enable operation controls while a write was active. This prepares Ventoid 0.4.1 (versionCode 17) with service-owned USB operations and support tools.
Validation: release lint and debug/release APK, AAB, and test APK builds passed. Unit tests: 126 passed, 4 QEMU image-output fixture tests skipped. Android 16 emulator: 6 instrumentation tests passed, covering rotation/control locking, confirmation restoration/cancel, Korean strings/help, diagnostic share/save/provider scope, and failed/stale service starts. Automation checks passed; new test dependency hashes were independently checked against Google Maven/Maven Central.
The emulator uses a synthetic USB target and does not write a physical drive. Firmware payloads are unchanged from the QEMU-verified 0.4.0 release. F-Droid metadata is appended in a separate commit referencing the immutable release source commit.