docs: define Android live-audio route design - #12
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.
Summary
This design-only slice selects Android API 26+ foreground playback/capture as AudioModem's first experimental live-audio platform target. It does not implement an Android adapter or enable any route.
It adds bilingual research comparing Android’s explicit permission/focus/PCM lifecycle with Linux PipeWire session/routing scope, plus a bilingual Android foreground live-audio RFC. The RFC fixes a narrow default-route design: 48 kHz mono PCM16 LE must be verified after native creation; microphone permission, playback focus, route changes, interruption and stop/dispose behavior are first-class gates; no auto-resume, background service, route picker, Bluetooth/cable/radio scope, duplex or physical-delivery claim is allowed.
The device-acceptance schema and zero-dependency validator now reserve a machine-checkable
adapter_observationfor future real Android speaker-to-microphone measurements. It requires the v1 adapter contract, API level 26+, exact requested/effective PCM format, granted permission, granted/delayed focus, stop-without-auto-resume and discarded raw PCM. The added JSON fixture is an unexecuted template and contains no device/run/outcome evidence.Documentation indexes, implementation plan, platform matrix, roadmap, CI bilingual pair checks and public status are synchronized to describe this as a draft design only.
Explicit non-claims
This pull request does not add microphone capture, speaker playback, a Flutter/Android audio plugin,
RECORD_AUDIO, audio focus code, an Android target build, Android runtime verification, a device result, speaker-to-microphone delivery, Bluetooth/cable/radio support, encryption or a supported-platform claim.Validation
The following completed successfully:
cargo fmt --all -- --checkcargo clippy --workspace --all-targets -- -D warningscargo test --workspaceflutter analyzeflutter test— 10 passing tests and 2 deliberately skipped opt-in native-runtime testsflutter build web --releaseflutter build linux --debuggit diff --checkThe web build completes with the existing
flutter_rust_bridgewasm dry-run warning. The native bridge remains intentionally unavailable in the web build.